W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > November 2007

Re: XPath version

From: Innovimax SARL <innovimax@gmail.com>
Date: Thu, 15 Nov 2007 16:39:54 +0100
Message-ID: <546c6c1c0711150739x85ffceej205ebd8f04cb5b08@mail.gmail.com>
To: "Henry S. Thompson" <ht@inf.ed.ac.uk>
Cc: "Norman Walsh" <ndw@nwalsh.com>, public-xml-processing-model-wg@w3.org

On Nov 15, 2007 4:31 PM, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Innovimax SARL writes:
>
> > On Nov 15, 2007 4:14 PM, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
> >>
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Norman Walsh writes:
> >>
> >> > 10. We add a p:xpath-version system property that returns the highest
> >> > version of XPath support that the implementation provides.
> >>
> >> Hmm, not really good enough if I want to know if native support for
> >> XPath 1.0 is available. . .
> >>
> >> Not sure what the right thing to do is -- p:xpath-versions, value a
> >> space-separated (not ideal, can lead to false positives) or
> >> space-bounded (e.g. " 1.0 2.0 " -- not ideal, as people will just
> >> think we've made a mistake unless we explain at length :-( ?
> >
> > isn't just the difference something like concat(' ', @p:xpath-versions, ' ') ?
>
> Yes, but w/o the longer version, to reliably test for an explicit
> version I have to do
>
> contains(concat(' ',@p:xpath-versions,' '),concat(' ',$version,' '))

>
> which just seems a bit much. . .

I just thing that's the *usual* way to deal with NMTOKENS and more
generally with list of space separated values



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Thursday, 15 November 2007 15:40:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:54 GMT