Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Performance Vs Size of XSD + Extension of restriction

From: "Pete Cordell" <petexmldev@--------------.--->
To: "Sudheshna Iyer" <sudheshnaiyer@-------.--->,<xml-dev@-----.---.--->
Date: 2/5/2007 8:27:00 PM
----- Original Message From: "Sudheshna Iyer" > Pete, I didn't get what you 
are saying.
>
> I want my 'ChildType' to inherit the restrictions 'minLength' and 
> 'whiteSpace' from 'OrigType' and
> has its own 'maxLength'. So will the following info solve the requirements 
> relating to both syntax and semantics?
>
> <xs:simpleType name="OrigType">
> <xs:restriction base="xs:string">
> <xs:minLength value="1"/>
> <xs:maxLength value="20"/>
> <xs:whiteSpace value="collapse"/>
> </xs:restriction>
> </xs:simpleType>
>
> <xs:simpleType name="ChildType">
> <xs:restriction base="OrigType">
> <xs:maxLength value="40"/>
> </xs:restriction>
> </xs:simpleType>

As Michael said, restriction restricts what a type can accept.  So if you 
want to define types that only accept subsets of values that other types 
accept, then you have to start off defining the least restricted type and 
then progressively define each more restricted type from the previously 
(less) restricted type.

A type that accepts a string of 40 characters is less restricted than a 
string that accepts a string of 20 characters.  Therefore, in your case you 
have to define ChildType first.  Hence, using your names, you get:

<xs:simpleType name="ChildType">
<xs:restriction base="xs:string">
 <xs:minLength value="1"/>
 <xs:maxLength value="40"/>
 <xs:whiteSpace value="collapse"/>
</xs:restriction>
</xs:simpleType>

<xs:simpleType name="OrigType">
 <xs:restriction base="ChildType">
   <xs:maxLength value="20"/>
 </xs:restriction>
</xs:simpleType>

OrigType will inherit the restrictions of ChildType.  So OrigType is 
equivalent to:

<xs:simpleType name="OrigType">
 <xs:restriction base="ChildType">
   <xs:minLength value="1"/>
   <xs:maxLength value="20"/>
   <xs:whiteSpace value="collapse"/>
 </xs:restriction>
</xs:simpleType>

Note that I'm referring to order of derivation here, not the order they 
appear in the XSD file (which isn't) significant.  So the XSD file contents 
could equally be:

<xs:simpleType name="OrigType">
 <xs:restriction base="ChildType">
   <xs:maxLength value="20"/>
 </xs:restriction>
</xs:simpleType>

<xs:simpleType name="ChildType">
<xs:restriction base="xs:string">
 <xs:minLength value="1"/>
 <xs:maxLength value="40"/>
 <xs:whiteSpace value="collapse"/>
</xs:restriction>
</xs:simpleType>

HTH,

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


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