[Bug 5156] 3.4.2 XML Representation of Complex Type Definitions

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5156

           Summary: 3.4.2 XML Representation of Complex Type Definitions
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: johnarwe@us.ibm.com
         QAContact: www-xml-schema-comments@w3.org


- Heading 3.4.2 is inconsistent with others, lacks "Schema Components" on end

CTD w/ simple content:
- {assertions} "in order" means in document order?  in some other well-known
and
  normative order?

- {attribute uses} item 3 "base [attribute]" base is ambiguous.  I "think" you
mean xs:extension/@xs:base or xs:restriction/@xs:base, not xml:base (or any
other bases)

- {attribute uses} item 3 could use some re-wording to make it more readable.

- "When the <complexContent> alternative is chosen, the following elements are
relevant (as are the <attributeGroup> and <anyAttribute> elements, not repeated
here), ".  If you want the spec to be more consumable, repeat them.

- "shorthand for complex content restricting ·xs:anyType·, and the details of
the mappings must be modified as necessary."  Again, be explicit or be obtuse. 
This kind of hand-waving just leaves room for human readers to misinterpret.

CTD w/ complex content:
- {content type} 2.1.3 clarify
  from: "There is a <choice> among the [children] with no [children] of its own
excluding <annotation> whose minOccurs [attribute] has the ·actual value· 0;"
  to:   "There is a <choice> among the [children], and none of the <choice>'s
[children] has a minOccurs [attribute] with the ·actual value· 0 (excluding the
<choice>'s <annotation> [children]);"

Received on Monday, 8 October 2007 19:35:08 UTC