Re: Extension of xs:simpleContent

"Pete Cordell" <[email protected]>
Newsgroups gmane.text.xml.schema.devel
Message-ID <2F858CCD8A6F4AC3B968550333A6155D@Codalogic>
Many thanks Kevin.  It's exactly the same question.  A case of it's wrong 
but it's right!

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using C++ XML
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info

----- Original Message ----- 
From: "Kevin Braun" <[email protected]>
To: "Pete Cordell" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, November 17, 2010 6:27 PM
Subject: Re: Extension of xs:simpleContent


>
> Hi,
>
> I believe under XSD 1.0 it is valid but under XSD 1.1 it would not be. 
> See http://lists.w3.org/Archives/Public/xmlschema-dev/2009Feb/0040.html 
> and the subsequent discussion; I believe it is the same question.
>
> Kevin
>
> On 11/17/2010 12:15 PM, Pete Cordell wrote:
>> I have a customer who has a schema that extends a simple type double into 
>> a complex type with simple content, and then as a separate construct 
>> extends that into a complex type with complex content.  They do this 
>> along the following lines:
>>
>> <xs:complexType name="DoubleBase">
>> <xs:simpleContent>
>> <xs:extension base="xs:double">
>> <xs:attribute name="DoubleBaseAttr" type="xs:boolean"/>
>> </xs:extension>
>> </xs:simpleContent>
>> </xs:complexType>
>>
>> <xs:complexType name="DoubleBaseExtension">
>> <xs:complexContent>
>> <xs:extension base="DoubleBase">
>> <xs:attribute name="DoubleExtensionAttr" type="xs:boolean"/>
>> </xs:extension>
>> </xs:complexContent>
>> </xs:complexType>
>>
>> (To avoid confusion, the intent of the latter is to add the 
>> DoubleExtensionAttr attribute rather than mandate that you've got 
>> complexContent.)
>>
>> My feeling is this is wrong because DoubleBaseExtension should specify 
>> xs:simpleContent rather than xs:complexContent.
>>
>> However, XML Spy and Visual Studio seem to accept the above, and the 
>> example is actually based on a industry consortium schema that specifies 
>> similar constructs.
>>
>> So my questions are:
>>
>> 1) Is the above schema correct or not?
>>
>> 2) If it is technically incorrect, is it widely occurring (possibly 
>> because tools fail to pick it up) and therefore worth overlooking this 
>> error?
>>
>> Thanks,
>>
>> Pete Cordell
>> Codalogic Ltd
>> Interface XML to C++ the easy way using C++ XML
>> data binding to convert XSD schemas to C++ classes.
>> Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
>> for more info
>>
>>
>>
>>
>>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.