- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 26 Jun 2007 16:30:02 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4766 Summary: [FS] 2.4.4 Example is backwards Product: XPath / XQuery / XSLT Version: Recommendation Platform: All URL: http://www.w3.org/TR/xquery- semantics/#sec_top_level_definitions OS/Version: All Status: NEW Severity: minor Priority: P3 Component: Formal Semantics AssignedTo: jmdyck@ibiblio.org ReportedBy: bungeman@gmail.com QAContact: public-qt-comments@w3.org The first example in section 2.4.4 <complexType name="UKAddress"> <complexContent> <extension base="ipo:Address"> <sequence> <element name="postcode" type="ipo:UKPostcode"/> </sequence> <attribute name="exportCode" type="positiveInteger" fixed="1"/> </extension> </complexContent> </complexType> is represented as follows define type UKAddress extends ipo:Address { attribute exportCode of type ipo:UKPostcode, element postcode of type positiveInteger }; has the types of "exportCode" and "postcode" backwards. This should be represented as define type UKAddress extends ipo:Address { attribute exportCode of type positiveInteger, element postcode of type ipo:UKPostcode };
Received on Tuesday, 26 June 2007 16:30:09 UTC