W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2014

[Bug 24266] New: [XSLT 3.0] Decouple XSLT and XPath versions

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Jan 2014 06:10:38 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24266-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 24266
           Summary: [XSLT 3.0] Decouple XSLT and XPath versions
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

XSLT and XPath development are no longer synchronized and it is quite possible
that an XPath 3.1 specification will be published during the lifetime of XSLT
3.0. We should therefore consider whether XSLT should adopt the same policy as
for other dependencies such as Unicode, XML, and XSD, namely to allow use of
XSLT 3.0 with XPath 3.0 or any later version.

This would have to take into account the possibility of data model changes. My
proposal would be that an XSLT 3.0 processor

* may allow use of versions of XPath, F+O, and Serialization later than 3.0

* must reject any XPath expression with a static or dynamic error as
appropriate if it returns a value that is outside the value space of XDM 3.0.
(For example, an array).

(But note, we currently allow extension functions to return values that are
outside the value space of XDM 3.0. So perhaps in the second rule, "must
reject" should be "may reject")

If future versions of XPath extend the static or dynamic context, then such
extended parts of the context should take an implementation-defined value.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 10 January 2014 06:10:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:45 UTC