[no subject]

[owner-netconf@ops.ietf.org]

earn=3Dham=20
=09version=3D3.1.0
Received: from [217.12.11.79] (helo=3Dsmtp010.mail.ukl.yahoo.com)
=09by psg.com with smtp (Exim 4.60 (FreeBSD))
=09(envelope-from <cridligv@loria.fr>)
=09id 1ElY3l-000Ama-3y
=09for netconf@ops.ietf.org; Sun, 11 Dec 2005 20:44:41 +0000
Received: (qmail 62444 invoked from network); 11 Dec 2005 20:44:39 -000=
0
Received: from unknown (HELO =3F192.168.0.2=3F) (cridligv@213.44.86.98 =
with plain)
  by smtp010.mail.ukl.yahoo.com with SMTP; 11 Dec 2005 20:44:39 -0000
Message-ID: <439C9008.30808@loria.fr>
Date: Sun, 11 Dec 2005 21:46:00 +0100
From: Cridlig Vincent <cridligv@loria.fr>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To:  netconf@ops.ietf.org
Subject: Re: xpath filter
References: <20051211.212034.84459880.mbj@tail-f.com>
In-Reply-To: <20051211.212034.84459880.mbj@tail-f.com>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed
Content-Transfer-Encoding: 7bit
Sender: owner-netconf@ops.ietf.org
Precedence: bulk

I totally agree with your suggestion.
I proposed earlier on this list to add a "contexts" element, seebling o=
f=20
"filter", and containing one or more "context" elements (namespace +=20=

prefix).
But I think the way you propose is more generally accepted in the XML=20=

community.

It will be much much more efficient (at least in our Netconf=20
implementation) to find the right XML nodes in the case of such XPath=20=

relative expression: "//name"

Moreover, the XPath expressions without prefix are still valid.

Vincent CRIDLIG
Madynes

Martin Bjorklund wrote:

>Hi,
>
>I know that this has been up on the list before, but I never saw any
>replies.  The question is how to handle namespaces with the xpath
>capability.  Consider the example in 8.9.5.1:
>
>         <filter type=3D"xpath"> <!-- get the user named fred -->
>           top/users/user[name=3D"fred"]
>         </filter>
>
>If the box supports multiple namespaces, which namespace does top
>belong to=3F  You could argue that this is a filter, so it should retu=
rn
>results from all namespaces which match the filter.  But what if you
>want to explicitly match a certain namespace=3F
>
>The XPath specification says that an xpath expression is evaluated
>with respect to a context
>(http://www.w3.org/TR/xpath#section-Introduction).  A context
>contains, amongst other things, the set of namespace declarations in
>scope for the expression (a mapping from prefixes to namespace URIs).
>
>As one example, XSLT defines the context in
>http://www.w3.org/TR/xslt#section-Expressions.  It defines the
>namespace declarations as:
> =20
>  the set of namespace declarations are those in scope on the element
>  which has the attribute in which the expression occurs; this
>  includes the implicit declaration of the prefix xml required by the
>  the XML Namespaces Recommendation [XML Names]; the default namespace=

>  (as declared by xmlns) is not part of this set
>
>
>I suggest that NETCONF uses a similar definition, so that one can
>write a filter such as:
>
>  <filter type=3D"xpath" xmlns:d=3D"http://www.example.com/Datamodel";>=

>     d:top/d:users/d:user[name=3D"fred"]
>  </filter>
>
>Also, I think that the XPath Core functions should be sufficient for
>NETCONF compliance; this is also not defined in the current draft.
>
>
>/martin
>
>--
>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/>
> =20
>


=09

=09
=09=09
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=20
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messen=
ger=20
T=E9l=E9chargez cette version sur http://fr.messenger.yahoo.com




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