[Bug 6644] Context determined type table

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





--- Comment #4 from Sandy Gao <sandygao@ca.ibm.com>  2009-04-16 18:34:22 ---
> you might consider it as an option:
> ... (that is, dropping clause 2.2)

I think clause 2.2 is there to make sure the following works:

  <xs:complexType name="base">
    <xs:sequence>
      <xs:element name="a" type="xs:decimal">
        <xs:alternative test="1" type="xs:integer"/>
      </xs:element>
    </xs:sequence>
  </xs:complexType>

  <xs:complexType name="restriction">
    <xs:complexContent>
      <xs:restriction base="base">
        <xs:sequence>
          <xs:element name="a" type="xs:int"/>
        </xs:sequence>
      </xs:restriction>
    </xs:complexContent>
  </xs:complexType>

For element "a", base assigns "xs:integer" and and restriction assigns
"xs:int", it should be OK.

Without clause 2.2, T_T for "restriction" would be absent, and "Validation
Rule: Conditional Type Substitutable in Restriction" would fail.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 16 April 2009 18:34:31 UTC