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 22934 - [XQX30] outer attribute
Summary: [XQX30] outer attribute
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQueryX 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: 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: 2013-08-13 08:52 UTC by Tim Mills
Modified: 2013-09-03 05:59 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2013-08-13 08:52:29 UTC 
The "outer" attribute is still present in the schema.  Is this not redundant following the addition of the allowingEmpty attribute?

  <xsd:complexType name="forClause">
    <xsd:sequence>
      <xsd:element ref="forClauseItem" minOccurs="1" maxOccurs="unbounded"/>
    </xsd:sequence>
    <xsd:attribute name="outer" type="xsd:boolean" default="false"/>
  </xsd:complexType>
Comment 1 Jim Melton 2013-08-30 22:46:09 UTC 
I believe that you are using an obsolete version of the XQueryX 3.0 LCWD. The version currently found at http://www.w3.org/TR/xqueryx-30/#Schema contains:

  <xsd:complexType name="forClause">
    <xsd:sequence>
      <xsd:element ref="forClauseItem" minOccurs="1" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>

  <xsd:element name="forClause" type="forClause"/>

Therefore, I'm marking this bug RESOLVED/INVALID.  If you agree, please mark it CLOSED.
Comment 2 Tim Mills 2013-08-31 05:42:35 UTC 
I followed the link you gave and still see use of "outer" in section 2.
Comment 3 Jim Melton 2013-09-02 20:32:02 UTC 
Arg. I forgot about the examples.  They're fixed now.  This time, I've marked the bug RESOLVED/FIXED.  If you agree, please mark it CLOSED.
Comment 4 Tim Mills 2013-09-03 05:59:06 UTC 
Thanks.