[Bug 26467] New: [xslt 3.0] Ambiguity for xsl:global-context-item

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

[Bug 26467] New: [xslt 3.0] Ambiguity for xsl:global-context-item

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

            Bug ID: 26467
           Summary: [xslt 3.0] Ambiguity for xsl:global-context-item
           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]

3.6.5 says

A type error is signaled if the supplied global context item does not match the
required type declared in the xsl:global-context-item declaration of any
package.

This is ambiguous. The intent is that the type of the supplied item should
match every type declaration, not that it is sufficient to match one of them.

Suggested rephrasing:

A type error is signaled if any package contains an xsl:global-context-item
that declares a required type which does not match the supplied global context
item.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 26467] [xslt 3.0] Ambiguity for xsl:global-context-item

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

Michael Kay <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
           Severity|normal                      |minor

--- Comment #1 from Michael Kay <[hidden email]> ---
Fixed editorially.

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