[Bug 26780] New: [XSLT30] Forwards compatibility mode and packages, after xsl:stylesheet became obsolete as a child

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

[Bug 26780] New: [XSLT30] Forwards compatibility mode and packages, after xsl:stylesheet became obsolete as a child

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

            Bug ID: 26780
           Summary: [XSLT30] Forwards compatibility mode and packages,
                    after xsl:stylesheet became obsolete as a child
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

We say, under 3.6 Packages:
"The version attribute indicates the version of the XSLT language specification
to which the package manifest conforms. The value SHOULD be 3.0."

Before we merged xsl:stylesheet into xsl:package, this made sense, because on
the child xsl:stylesheet one could still specify another version. Except that
as written it limited the way you could use forwards or backwards compatibility
mode on children of xsl:package.

Now that all declarations are allowed as children of xsl:package, it has become
more synonymous with xsl:stylesheet. I think we should bring the description of
the allowed values for the version attribute in line to allow the same kinds of
forwards compatibility processing (and perhaps even backwards compatibility
processing, though I think a version lower than 3.0 would yield an error either
way) as xsl:stylesheet had.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 26780] [XSLT30] Editorial: forwards compatibility mode and packages

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

Abel Braaksma <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[XSLT30] Forwards           |[XSLT30] Editorial:
                   |compatibility mode and      |forwards compatibility mode
                   |packages, after             |and packages
                   |xsl:stylesheet became       |
                   |obsolete as a child         |

--- Comment #1 from Abel Braaksma <[hidden email]> ---
As discussed by mail (see
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Sep/0030.html and previous,
member only), the conclusion was:

- I misinterpreted the spec, the "SHOULD" does not preclude forwards/backwards
  compatibility mode on package manifests

- The suggestion in the mail by MKay was to change the sentence as follows,
  which prompted me to mark this bug as Editorial.

Textual proposal from MKay:

> "For this version of XSLT, the value SHOULD normally be 3.0. Specifying a
> different value invokes backwards-compatible processing (see 3.10), or
> forwards-compatible processing (see 3.11)."

Marked EDITORIAL.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 26780] [XSLT30] Editorial: forwards compatibility mode and packages

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26780

Michael Kay <[hidden email]> changed:

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

--- Comment #2 from Michael Kay <[hidden email]> ---
This was resolved editorially prior to publishing the LCWD on 2 October 2014.

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