OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

codelist message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [codelist] Comments on CVA spec WD0.2 21 Nov

Actually, I'm going to suggest that we support both XPath 1.0 and 2.0, and do so by leaving the level of support to individual implementers.  The reason is that, just recently, the W3C XProc working group proposed to support XPath 1.0/2.0 and XSLT 1.0/2.0 as separate things, and the W3C XSL working group complained.  The upshot is that XProc now supports XPath generally without mandating a specific version, and it is up to implementations to then decide what level of XPath support they provide.  See


for some discussion of this by Norman Walsh.

Cheers, Tony.

----- Original Message -----
From: "Paul Spencer" <paul.spencer@boynings.co.uk>
To: "G. Ken Holman" <gkholman@CraneSoftwrights.com>, codelist@lists.oasis-open.org
Sent: 11 January 2008 10:37:04 o'clock (GMT) Europe/London
Subject: RE: [codelist] Comments on CVA spec WD0.2 21 Nov

> -----Original Message-----
> From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com]
> Sent: 11 January 2008 03:43
> To: codelist@lists.oasis-open.org
> Subject: Re: [codelist] Comments on CVA spec WD0.2 21 Nov
> Thanks, Paul, for your thoughts on this.
> At 2008-01-08 09:42 +0000, Paul Spencer wrote:
> >Sorry it has taken me a while to catch up, but I have now read
> this draft.
> >
> >As a general point, why XPath 1.0, not 2.0?
> I felt this was an implementation issue.  As I understand it, there
> is only one available implementation of XSLT/XPath 2.0.  How about I
> replace "XPath 1.0" with just "XSLT/XPath", and then the user can
> choose the level of XSLT/XPath they use in their CVA
> file?  Schematron assumes XSLT/XPath 1.0 and if someone wishes to use
> a different binding language, they have to say that it isn't.
> While CVA doesn't need to be implemented in Schematron, it does use
> XSLT/XPath the same way that Schematron uses XSLT/XPath.
> I think I'd be more comfortable keeping CVA tied to XSLT/XPath 1.0
> for at least CVA version 1.0, but if the committee decides to allow
> other language bindings, then I'll ask that we have the same
> language= as Schematron and default it to XSLT/XPath 1.0 and allow
> users to specify other binding languages.  Examples of binding
> languages can be seen in ISO Schematron section 6.4: the default is
> "xslt" and the others are "stx, xslt1.1, exslt, xslt2, xpath, xpath2,
> and xquery.

I am quite happy with that. I was just wondering, not suggesting a change.
Anthony B. Coates
Senior Partner
Miley Watts LLP
Experts In Data
UK: +44 (20) 8816 7700, US: +1 (239) 344 7700
Mobile/Cell: +44 (79) 0543 9026
Data standards participant: genericode, ISO 20022 (ISO 15022 XML), UN/CEFACT, MDDL, FpML, UBL.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]