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 24290 - [xslt 3.0] Avoid the term "overlap"
Summary: [xslt 3.0] Avoid the term "overlap"
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC All
: 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-01-14 15:40 UTC by Michael Kay
Modified: 2014-02-24 15:55 UTC (History)
1 user (show)

See Also:


Attachments

Description Michael Kay 2014-01-14 15:40:05 UTC
In a number of places we use the term "overlap" to describe a relationship between trees (or their roots) in the sense that two trees overlap if they have nodes in common.

The term is unfortunate (a) because overlap implies a more complex relationship than containment, and (b) there's a whole literature devoted to overlap in markup which is to do with handling of non-hierarchic relationships, and our use of the term is quite unrelated to this.

See current discussion on xsl-list.
Comment 1 Michael Kay 2014-01-28 18:19:09 UTC
I have fixed this editorially by replacing the use of the word "overlapping" with "nested" or similar, with suitable explanation of the term where the context requires it.