Re: Issue 14.1: Retrieval Subset specification proposal

[Andy Bierman <abierman@cisco.com>]

At 01:42 AM 3/17/2004, Juergen Schoenwaelder wrote:
>On Tue, Mar 16, 2004 at 05:16:18PM -0800, Andy Bierman wrote:
> 
>> No.  The protocol operations don't change.  The #xpath
>> capability would just mean that the agent supports
>> XPath expression attributes in the data model, in a manner 
>> similar to the 'operation' attribute embedded in the data model.
>
>I tend to believe that both solutions (xpath and operation
>attributes in the data model) are kind of broken and just
>attempts to push away work that really needs to be handled
>and specified by the protocol verbs.

I disagree.  The problem we are trying to solve has already
been addressed by XPath.  We are trying to use existing
XML standards, not reinvent or create static subsets.

The filter cannot be a parameter in the protocol operation
RPC for the same reasons as the 'operation' attribute.
It has to be embedded in the data model.  So we need
another standard attribute (called xfilter?) supported
by the TBD data modeling language.

The #xfilter capability (was called #xpath) would indicate 
that the agent has the ability to support 'xfilter' attributes
for XPath selection in <get> and <get-config> operations.
Every data model definition will contain any XPath 
implementation and conformance requirements for that data model.
It is also data model specific whether the xfilter attribute
can be used within <edit-config> operations.

FYI:

XPath standard:
http://www.w3.org/TR/xpath

Basic XPath tutorial:
http://www.zvon.org/xxl/XPathTutorial/General/examples.html


>/js

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