On Tue, Feb 09, 2010 at 04:07:06PM +0100, François Delyon wrote:
/* valid example */
exsltStrXpathCtxtRegister(ctxt, NULL);
...
xmlXPathRegisterNs(ctxt, str, http://exslt.org/strings;);
xmlXPathEval((const xmlChar *)str:concat(n), ctxt);
Now calls
On 09/02/2010, François Delyon f.del...@satimage.fr wrote:
exsltStrXpathCtxtRegister(ctxt, NULL) must occur once when I create
the context.
But the NSregistrations and the Xpath evaluations are up to the users
of my application.
Okay, that version makes some sense. I'm not sure whether it's
Le 8 févr. 10 à 18:32, Martin (gzlist) a écrit :
On 08/02/2010, François Delyon f.del...@satimage.fr wrote:
By the way (prefix and namespace), I have a request about exslt.
Some useful functions like exsltStrXpathCtxtRegister have been added.
But they require a non-null prefix, which is not
On Mon, Feb 08, 2010 at 03:08:49AM +0100, Iñaki Baz Castillo wrote:
Unfortunatelly in my case I'm implementing a XCAP (RFC 4825) client and
server. XCAP reuses Xpath but allows Xpath nodes without prefix matching an
application specified namespace. This is, the following Xpath should work
El Lunes, 8 de Febrero de 2010, Daniel Veillard escribió:
On Mon, Feb 08, 2010 at 03:08:49AM +0100, Iñaki Baz Castillo wrote:
Unfortunatelly in my case I'm implementing a XCAP (RFC 4825) client and
server. XCAP reuses Xpath but allows Xpath nodes without prefix matching
an application
On Mon, Feb 08, 2010 at 01:14:22PM +0100, Iñaki Baz Castillo wrote:
El Lunes, 8 de Febrero de 2010, Daniel Veillard escribió:
[...]
Does it mean that Xpath 2.0 allows the behavior I meant (present in RFC 4825)?
I don't know, I doubt it.
Is it planned libxml2 to implement Xpath 2.0?
I
On Mon, Feb 08, 2010 at 02:03:06PM +0100, Daniel Veillard wrote:
On Mon, Feb 08, 2010 at 01:14:22PM +0100, Iñaki Baz Castillo wrote:
RFC 4825 is a pain as it reuses Xpath 1.0 with some restrictions and
additions
(as the application default namespace which allows the Xpath deviation I
Le 8 févr. 10 à 14:03, Daniel Veillard a écrit :
On Mon, Feb 08, 2010 at 01:14:22PM +0100, Iñaki Baz Castillo wrote:
El Lunes, 8 de Febrero de 2010, Daniel Veillard escribió:
[...]
Does it mean that Xpath 2.0 allows the behavior I meant (present in
RFC 4825)?
I don't know, I doubt it.
El Lunes, 8 de Febrero de 2010, François Delyon escribió:
No XPath 2.0 does not allow this kind of ambiguity.
If a Default element/type namespace property exists in the static
context, this URI is used for for any unprefixed QName appearing in a
position where an element or type name is
Le 8 févr. 10 à 17:02, Iñaki Baz Castillo a écrit :
El Lunes, 8 de Febrero de 2010, François Delyon escribió:
No XPath 2.0 does not allow this kind of ambiguity.
If a Default element/type namespace property exists in the static
context, this URI is used for for any unprefixed QName appearing
On 08/02/2010, François Delyon f.del...@satimage.fr wrote:
By the way (prefix and namespace), I have a request about exslt.
Some useful functions like exsltStrXpathCtxtRegister have been added.
But they require a non-null prefix, which is not convenient in my case.
Can you explain exaclty how
On Mon, 2010-02-08 at 10:25 +0100, Daniel Veillard wrote:
On Mon, Feb 08, 2010 at 03:08:49AM +0100, Iñaki Baz Castillo wrote:
Unfortunatelly in my case I'm implementing a XCAP (RFC 4825) client and
server. XCAP reuses Xpath but allows Xpath nodes without prefix matching an
application
El Lunes, 8 de Febrero de 2010, François Delyon escribió:
Unfortunatelly it's common in XCAP protocol and applications as the
above example.
But as far as I understand XCAP, it is possible to use regular XPath
expression by providing a namespace-prefix pair in the request part
of
Hi, I'm user of Nokogiri, a Ruby library warpping libxml2. There is something
I cannot do with Nokogiri and just would like to know if it's feasible by
directly using libmlx2.
Let's suppose the following XML document:
-
?xml version=1.0 encoding=UTF-8?
root
14 matches
Mail list logo
