[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 14.1: Retrieval Subset specification proposal
On Tue, Mar 16, 2004 at 12:36:34PM -0800, Andy Bierman wrote:
> The design team discussed the different proposed data subset
> specification mechanisms discussed in 14.1.1 .. 14.1.5.
> The more details were discussed the more each feature seemed
> like a reinvention of some aspect of XPath expressions.
> The design team suggested that we either do nothing
> about this issue right now, or bring back the
> #xpath capability (large devices can implement the optional
> XPath feature, which is defined outside the protocol
> specification. The #xpath capability just means that
> the agent will support XPath expressions as attributes
> in the data model content. The data modelling language
> document needs to clarify any further XPath usage requirements.
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. We need something like
get-config(source, filter)
and I only see the option to leave filter completely undefined
(saying that the data modeling work has to define how filters look
like) or we say that filter is one of the generic XML mechanism
(e.g. XPATH) and we later define what the conformance requirements
are (where we might want to subset XPATH capabilities in case people
really find full XPATH support way too hard to support on their boxes).
/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/>