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
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
> > "applicat
On 08/02/2010, François Delyon 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 you'd use this f
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 appeari
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 à 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.
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 dev
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?
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 "applicatio
Around about 05/02/10 21:14, Roumen Petrov typed ...
Did you try to build for source tarbal when you remove
include/libxml/xmlversion.h in source directory ?
I guess you use build<>source directory.
Not sure what you're asking; we didn't _remove_ anything, just renamed
the #include statemen
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 wo
11 matches
Mail list logo
