Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Schema for mixed content to provide backwards compatibility for an element with changing from complex type to simple type

From: William S Fulton <wsf@-------------.--.-->
To: xmlschema-dev@--.---
Date: 8/30/2007 10:44:00 PM
I'd like to upgrade our usage of XML dates to use the XML date type and 
be able to validate both the old and new xml elements. An example of our 
current xml date element looks like:

<date>
   <day>1</day>
   <month>2</month>
   <year>2000</year>
</date>

The desired change to use the xs:date type would look like:

<date>2000-02-01</date>

Is it possible to create a schema which will fully validate both 
versions of the date element? I've been experimenting and googling for 
some while now and cannot find a solution to getting a suitable schema. 
I'd like to avoid changing the name of the element from "date". The 
following mixed content will validate both, but it will validate any 
text instead of the XML date type, which isn't very good:

<xs:complexType name="DateType" mixed="true">
   <xs:sequence maxOccurs="1" minOccurs="0">
     <xs:element name="day" type="integer" />
     <xs:element name="month" type="integer" />
     <xs:element name="year" type="integer" />
   </xs:sequence>
</xs:complexType>

William




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