[Bug 24764] [xslt 3.0] xsl:context-item and the initial input sequence

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24764

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
The WG considered this today and asked the editor to produce a detailed
proposal.

Proposal (still an outline, but the next stage is drafting within the XML
master):

1. Change the term "initial context item" to "global context item".

Note: some refereces to the ICI, eg that in the second bullet of 2.3.3 and that
in the first bullet of 2.10, and in the last sentence of 3.9, are incorrect,
and should refer to items in the initial match selection.

2. Change the term "initial input sequence" to "initial match selection".

3. Add to the (two different) definitions of "source tree" in 2.1 and 4.4,
"trees containing nodes that are present in the initial match selection".

4. Drop xsl:context-item as a child of xsl:mode. This mainly affects 6.6.1 and
6.7 (in a substantial but fairly obvious way), and other isolated references to
xsl:context-item throughout the document.

5. Introduce a new top-level declaration xsl:global-context-item with the same
content model as the current xsl:context-item, and semantics closely modelled
on the xsl:context-item that currently appears as a child of xsl:mode; but
constraining the global context item, not the initial match selection. If there
are multiple declarations within a package the highest precedence one wins. If
there are declarations in several packages then the global context item must
satisfy all of them.

6. Rework the two examples (in 2.9 and 6.7.1) showing how to constrain the
global conetxt item and/or the initial match selection.

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

Received on Thursday, 24 April 2014 21:11:02 UTC