[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proposed Update to Netconf Charter

Let me give more details about what I proposed.

The prefix concept is well defined in the XPath recommendation. I didn't invent this concept and I don't want to change XPath.

Using XPath prefix needs a namespace declaration. This is why I suggested to add some namespace declaration along with the Netconf request.
In fact, I might be wrong but I think it is not possible to fully support XPath without making it possible to send these declarations. These declarations are needed to build the expression context as described in the XPath recommendation.
If a manager sends an XPath request which contains prefixes, I don't know how an agent could guess the related (real) namespace URI.

Best regards,
Vincent CRIDLIG


Juergen Schoenwaelder wrote:

On Wed, Jul 06, 2005 at 09:59:35AM +0200, Vincent Cridlig wrote:



To improve this, what I suggest is to modify XPath filtering a little bit.
Most programming languages allow to define a namespace context before applying an XPath expression to a document.
It would be nice to allow namespaces contexts definition in the Netconf requests:

<filter type="xpath">
<expression>//net:network/if:interfaces/if:iface/if:name</expression>
<ns-contexts>
<ns-context>
<ns-short>net</ns-short>
<ns-long>urn:network:data:model</ns-long>
</ns-context>
<ns-context>
<ns-short>if</ns-short>
<ns-long>urn:network:interfaces:data:model</ns-long>
</ns-context>
</ns-contexts>
</filter>



I think this WG is not the right place to change XPath. Some of us have quite some experience with adapted subsets and I prefer not to do this
again. Subsetting for conformance might be OK, adapting is IMHO a poor
choice.

If relative paths are a real issue, why can a device not use a hash table
lookup to find out where potential starting points in its schemas are?
Yes, this might require some more coding but at the end there is the
benefit that you do not have to invent something special which might
bite you when XPath gets revised.

/js





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