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 4694 - [XQX] <forLetClauseItemExtensions> element not documented
Summary: [XQX] <forLetClauseItemExtensions> element not documented
Status: CLOSED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQueryX 1.0 (show other bugs)
Version: Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-22 09:36 UTC by Oliver Hallam
Modified: 2007-08-20 09:47 UTC (History)
0 users

See Also:


Attachments

Description Oliver Hallam 2007-06-22 09:36:25 UTC
The element <forLetClauseItemExtensions> is defined in the XQueryX schema as follows:

<!-- Represents all variable bindings in a for or let clause except typed and positional variable bindings -->
<xsd:element name="forLetClauseItemExtensions" abstract="true"/>

Beyond the comment there is no documentation for this element at all.
It is used in the schema in both the forClauseItem type and letClauseItem element, although it is an abstract element with no substitution groups defined.

None of the XQTS cases use this element either.
Comment 1 Oliver Hallam 2007-06-22 10:31:28 UTC
It turns out that the schema in the specification (at http://www.w3.org/TR/xqueryx/) is wrong - this has been fixed in the schema found at http://www.w3.org/2005/XQueryX/xqueryx.xsd
Comment 2 Jim Melton 2007-08-14 15:47:14 UTC
Actually, the schema in the XQueryX Recommendation (http://www.w3.org/TR/xqueryx/) is the correct schema; for reasons we have not been able to explain to ourselves, the schema document at http://www.w3.org/2005/XQueryX/xqueryx.xsd is an obsolete schema document left over from an earlier Working Draft.  We will correct that error shortly. 

The reason for the "undocumented" abstract type has to do with providing a mechanism for defining extensions to XQueryX in other documents under development (e.g., Full-Text and the Update Facility).  Therefore, it is not a "bug", but a deliberate feature.

As such, I am marking this bug resolved (INVALID) and ask that you mark it CLOSED at your earliest opportunity.