RE: Proposal to do away with netconf attributes in data model pay loads

[Andy Bierman <abierman@cisco.com>]

At 07:50 AM 4/1/2004, Glenn Waters wrote:

>Andy says: 
>
>> I think this was suggested already on the mailing list. 
>> IMO, if Xpath is supported, it's a much more efficient encoding 
>> than what we have now.  But I don't want to make Xpath mandatory. 
>
>To use Randy's terms there are two features: 
>(1) Specifying the path to the starting point in the tree. 

We have the operation attribute for this purpose now.

>(2) Specifying the set of instances within tree. 

We have element sub-tree filtering for this purpose now.

The ability to select start nodes by wildcard or
by criteria other than the instance identifier(s) 
is not considered mandatory.  It's something that
can be added later.  Xpath is a good choice for this
optional functionality that we don't have to put in v1.0.


>From a requirements perspective we need to do (1). I think we also need to do (2). 
>
>If we don't do XPath then how can we satisfy requirement (2)? 
>
>XPath seems like the obvious choice. And, as I have stated before, we *may* want to look at trimming XPath down, but that has its downsides as well.

The IESG has already said in other cases that sub-setting XML
standards is a bad idea.


>  
>> Andy 

Andy 


--
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/>