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 26742 - [xslt 3.0] Histogram of preceding sibling counters
Summary: [xslt 3.0] Histogram of preceding sibling counters
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Working drafts
Hardware: PC All
: P2 normal
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-09-05 23:02 UTC by Michael Kay
Modified: 2014-09-11 23:05 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2014-09-05 23:02:25 UTC
At one time we proposed that a streamed node should carry with it some kind of set of counters indicating basic information about the number of preceding siblings of different kinds. I don't believe there is now any functionality in the spec that relies on this. However, I found a couple of references to the idea:

Section 2.10 "However, constructs (for example, simple forms of xsl:number, and 
simple positional patterns) that require knowledge of the number of preceding elements by name are permitted."

Similarly in 4.6: "Summary data about the preceding siblings of the node, and of each of its ancestor nodes: 
specifically, for each distinct combination of node kind, node name, and type annotation, a count of the number 
of preceding siblings that have that combination of properties. This information allows patterns such as 
match="para[1]" to be used, and it permits some limited use of the xsl:number instruction."

I think these two paragraphs are obsolete and should be deleted.

(For info: Saxon's streaming implementation does in fact carry this information, but makes very little use of it; about the only use I can find is to support simple positional patterns such as para[1]).
Comment 1 Michael Kay 2014-09-11 23:00:40 UTC
The WG agreed that these paragraphs should go.
Comment 2 Michael Kay 2014-09-11 23:05:20 UTC
The changes have been applied.