This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24550 - Unclear what an input sequence is
Summary: Unclear what an input sequence is
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 00:18 UTC by Abel Braaksma
Modified: 2014-02-14 23:05 UTC (History)
1 user (show)

See Also:


Attachments

Description Abel Braaksma 2014-02-06 00:18:30 UTC
The term "input sequence" is used several times throughout the document and it seems to be quite an important term, for instance, understanding this term is required for understanding invoking an initial mode (first paragraph under 2.3.3).

Would it be a good idea to define this term? Or is it clear enough what it entails?
Comment 1 Michael Kay 2014-02-06 09:49:56 UTC
Yes, this term was introduced during the "last minute" change that allowed stylesheets to be invoked by calling functions as well as templates, and it's not defined as clearly as it might be. It is introduced in the first paragraph of 2.3.3, but not properly defined or explained. It's not necessarily true that all occurrences of the phrase "input sequence" throughout the document refer to this same concept.
Comment 2 C. M. Sperberg-McQueen 2014-02-13 09:45:34 UTC
We discussed this in Prague; some further editorial planing, sanding, and polishing may be needed.
Comment 3 Michael Kay 2014-02-14 23:05:57 UTC
I have made "initial input sequence" a defined term.

Reflecting points made during the discussion though not captured here, I have replaced the first bullet point (including the Note) in 2.3.3 with:

<p diff="chg" at="R-bug24550">The <termref def="dt-initial-input-sequence"/>. An API that chooses to maintain compatibility with previous versions of this specification <rfc2119>should</rfc2119> allow a singleton node to be provided, which is then used in two ways: the node itself acts as the <termref def="dt-initial-input-sequence"/>, and the document node of the containing document acts as the <termref def="dt-initial-context-item"/>.

(The Note was incorrect in saying that in 2.0, the initial context item used for global variables was the same as the initial context item used for template matching. The supplied node was used for template matching, and the root of its containing document for evaluating global variables.)