Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Differences in derivation by extension of complex types between Schema 1.0 and 1.1

From: "Michael Kay" <mike@--------.--->
To: "'Tobias Koenig'" <tobias.koenig@---------.--->, <xmlschema-dev@--.--->
Date: 2/19/2009 6:12:00 PM
For the record:

- this relates to test particlesZ031
- you have raised bug #6600 against this test
- there is previous discussion of this problem in the entry for bug #5943 at

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

Michael Kay
 

> -----Original Message-----
> From: xmlschema-dev-request@w... 
> [mailto:xmlschema-dev-request@w...] On Behalf Of Tobias Koenig
> Sent: 19 February 2009 11:25
> To: xmlschema-dev@w...
> Subject: Differences in derivation by extension of complex 
> types between Schema 1.0 and 1.1
> 
> Hej,
> 
> let's assume we have the following schema
> 
> --------------------------------------------------------------
> -------------------
> <xs:schema xmlns="http://cscB2BCIDXSchemas.Schema1" 
> xmlns:b="http://schemas.microsoft.com/BizTalk/2003" 
> targetNamespace="http://cscB2BCIDXSchemas.Schema1" 
> xmlns:xs="http://www.w3.org/2001/XMLSchema">
>   <xs:element name="Root" type="Type1" />
>   <xs:element name="Record" type="Type2" />
> 
>   <xs:complexType name="Type1">
>     <xs:simpleContent>
>       <xs:extension base="xs:string">
>         <xs:attribute name="Field1" type="xs:string" />
>       </xs:extension>
>     </xs:simpleContent>
>   </xs:complexType>
> 
>   <xs:complexType name="Type2">
>     <xs:complexContent>
>       <xs:extension base="Type1">
>         <xs:attribute name="Field2" type="xs:string" />
>       </xs:extension>
>     </xs:complexContent>
>   </xs:complexType>
> 
> </xs:schema>
> --------------------------------------------------------------
> -------------------
> 
> Type1 would have a content type with variety 'Simple', as it 
> contains the <xs:simpleContent> tag. According to Schema 1.0 
> the content type of Type2 is constructed by rule 3 of the 
> {content type} section in 
> http://www.w3.org/TR/xmlschema-1/#declare-type.
> Therefor the content type of Type2 will be the same as the 
> content type of Type1 and both will have the variety of 'Simple'
> 
> In Schema 1.1, the content type of Type1 is 'Simple' as well, 
> but when constructing the content type of Type2, it seems the 
> matching rule is 4.2 and 4.2.1 of the {content type} section 
> in http://www.w3.org/TR/xmlschema11-1/#dcl.ctd.ctcc which 
> points back to rule 4.1, so Type2 ends up with an 'Empty' 
> content type which is wrong IMHO.
> 
> So is that different behaviour in Schema 1.1 intended? Or did 
> I follow the wrong path when constructing the types for the 
> above schema?
> 
> Ciao,
> Tobias
> 


From simon.price@b... Fri Feb 20 22:34:48 2009
Received: from bart.w3.org ([128.30.52.63])
	by frink.w3.org 


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent