[Bug 27015] New: [xslt 3.0] xsl:context-item/@use = "prohibited": detailed wording

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

[Bug 27015] New: [xslt 3.0] xsl:context-item/@use = "prohibited": detailed wording

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

            Bug ID: 27015
           Summary: [xslt 3.0] xsl:context-item/@use = "prohibited":
                    detailed wording
           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]

The wording of the rule for @use="prohibited" is rather fuzzy:

If the value prohibited is specified, then there will be no context item
available to the body template (if the calling template has a context item, it
will not be made available to the called template).

(a) it doesn't mention what happens to position() or last()

(b) it assumes there is a calling template

Propose instead:

If the value prohibited is specified, then the contained sequence constructor,
and any xsl:param elements, are evaluated with an absent focus.

Note: it is not an error to call such a template with a non-absent focus; the
context item is simply treated as absent. This option is useful when streaming,
since an xsl:call-template instruction may become streamable if the referenced
template is declared to make no use of the 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 27015] [xslt 3.0] xsl:context-item/@use = "prohibited": detailed wording

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

--- Comment #1 from Michael Kay <[hidden email]> ---
There's a similar problem for xsl:global-context-item. It says "If the value
prohibited is specified, then the global context item must be absent." This
doesn't really indicate if we expect a dynamic error in this case (and what
error?), or if we expect the supplied global context item to be ignored. One
could say that the decision between the two is a matter of API design and
therefore out of scope. The analogy with xsl:context-item would suggest
ignoring the supplied context item rather than throwing an error. This also
might be appropriate given the existence of legacy APIs that supply a context
item and an initial match selection in the same breath.

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