Re: Proposal to do away with netconf attributes in data model payloads

[Andy Bierman <abierman@cisco.com>]

At 01:38 PM 3/30/2004, Juergen Schoenwaelder wrote:
>On Tue, Mar 30, 2004 at 01:14:33PM -0800, Andy Bierman wrote:
> 
>> Your proposal is essentially the same as above,
>> except you removed the <config> container.
>> The only reason there aren't any assumptions
>> about naming is that there's no naming in your example.
>> The data modeling language will have to specify 
>> how naming is done.  
>> 
>> As I pointed out in my previous emails, this approach
>> is too simplistic because the agent needs to know the
>> specific element sub-tree associated with the edit-action.
>> That's why we're using the 'operation' attribute now.
>
>So you are saying naming is defined by the protocol and not by the 
>data model?

no. 
But the naming will be expressible in XML, and therefore
an XPath expression.  From the protocol POV, the start-path
attribute is just a string.  


>Note that I do not believe that it will be possible to press everything
>into a single naming hierarchy. I believe we will see a need for cross
>references and hence I would like to filter what I retrieve or select
>what I modify not only by specifying a simple path.

I agree.
I kept my example simple, but I think the instance-id
needs to be 1 or more components, and the instance-id
components can be locally defined (in the object being
defined) or externally defined, even in another namespace.


>/js

Andy



>-- 
>Juergen Schoenwaelder               International University Bremen
><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany
>
>--
>to unsubscribe send a message to netconf-request@ops.ietf.org with
>the word 'unsubscribe' in a single line as the message text body.
>archive: <http://ops.ietf.org/lists/netconf/> 


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>