[Bug 26965] New: [xslt 3.0] Undocumented incompatibility for version="1.1"

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 26965] New: [xslt 3.0] Undocumented incompatibility for version="1.1"

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26965

            Bug ID: 26965
           Summary: [xslt 3.0] Undocumented incompatibility for
                    version="1.1"
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

Stylesheets with version="1.1" are sometimes encountered in the wild (probably
because examples in my book used this value, as it went to press just before
XSLT 1.1 was cancelled).

XSLT 2.0 requires processors to treat such stylesheets as if version="1.0" were
specified (all values less than 2.0 are treated the same way).

XSLT 3.0 recommends that processors reject this value as a static error.

This is an incompatibility and should be recorded as such in the list of
incompatibilities.

(I'm not suggesting that we change the rule. It would be complicated. How would
we handle version="2.1"? That clearly has a different meaning to a 2.0
processor as to a 3.0 processor, by design.)

--
You are receiving this mail because:
You are the QA Contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 26965] [xslt 3.0] Undocumented incompatibility for version="1.1"

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26965

Michael Kay <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Michael Kay <[hidden email]> ---
Agreed we should document this incompatibility.

--
You are receiving this mail because:
You are the QA Contact for the bug.