Re: Issue 14.1: Retrieval Subset specification proposal

[Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>]

On Tue, Mar 16, 2004 at 05:16:18PM -0800, Andy Bierman wrote:
> >
> >Not sure I understand the proposal. Does the proposal mean you
> >remove <config/> parameter from the <get-config> operation? I
> >believe this would be wrong. 
> 
> 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.
> The actual definition is outside the scope of NETCONF, defined
> by the W3C.

Some observations:

a) The <config> parameter of the get-config operation is used
   as a filter.

b) The semantics of <config> parameter of the get-config operation
   are currently not defined.

c) Defining the semantics either makes assumptions of the data model
   or you need to come up with generic filter semantics.

d) XPATH is a well defined selection mechanism for subsets of XML
   document which is backed up by several implementations out there.

Given this, I do not really understand why you want to reject an
approach like

	get-config(source, filter)

where filter is just an XPATH expression (or a subset thereof for
conformance). Perhaps I should wait until you have provided the
semantics for the <config> parameter of the get-config operation...
 
/js

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