Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: SimpleType as valid derivation of abstract type in 1.1 ?

From: "Pete Cordell" <petexmldev@--------------.--->
To: "Guillaume Lebleu" <gl@---------.--->
Date: 3/9/2007 5:57:00 PM
This may be a case where an explicit statement about node text content a-la 
Relax-NG (as opposed to schema's blunt "mixed" attribute) would helpful.

I'm not certain about the Relax-NG format, but the equivalent schema could 
look something like:

   <xs:complexType name="ObjId" abstract="true">
        <xs:sequence>
            <xs:value type="xs:int"/> <!-- New -or is it xs:data or 
xs:text? -->
        </xs:sequence>
    </xs:complexType>

    <xs:complexType name="CarId">
        <xs:complexContent>
            <xs:extension base="ObjId">
                <xs:sequence>
                ....
                </xs:sequence>
            </xs:extension>
        </xs:complexContent>
    </xs:complexType>

Other than that I'm stuck!!!

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware Ltd
for XML to C++ data binding visit
http://www.tech-know-ware.com/lmx/
http://www.codalogic.com/lmx/
=============================================

----- Original Message ----- 
From: "Guillaume Lebleu" <gl@b...>
To: "Pete Cordell" <petexmldev@t...>
Cc: <xmlschema-dev@w...>
Sent: Friday, March 09, 2007 12:59 PM
Subject: Re: SimpleType as valid derivation of abstract type in 1.1 ?


>
> Pete Cordell wrote:
>> In your example the ObjId type is defaulted to xs:anyType; a complex 
>> content type.  To make it simple content, you need to do something like:
>>
>> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
>>
>>   <xs:complexType name="ObjId" abstract="true">
>>        <xs:simpleContent>
>>            <xs:extension base="xs:...whatever..."/>
>>        </xs:simpleContent>
>>    </xs:complexType>
>>
>>    <xs:complexType name="CarId">
>>        <xs:simpleContent>
>>            <xs:extension base="ObjId"/>
>>        </xs:simpleContent>
>>    </xs:complexType>
>>
>> </xs:schema>
> This works and addresses partly my requirements. My requirements are: "All 
> objects have an Id, some objects' Id is complex, some objects' Id is 
> simple". With your approach, I still have to have two base types.
>
> Guillaume
>
> 



From swvemuri@c... Sat Mar 10 09:38:50 2007
Received: from lisa.w3.org ([128.30.52.41])
	by frink.w3.org wit


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