Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


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

From: noah_mendelsohn@--.---.---
To: Guillaume Lebleu <gl@---------.--->
Date: 3/8/2007 4:47:00 PM
I haven't thought through your example in great detail, but my intuition 
is that it can be handled by deriving not simple types, but complex types 
with simple content.  Complex types with simple content are usually used 
in cases where you want an element like this:

        <e a="1">234</e>

where the element is complex (because it has attributes) but has content 
(in this case the 234) of simple type (perhaps xs:integer).  So, if what 
you're after is:

        <car refid="xxxx">corvette</car>

then that's what you'd want.   In fact, even if what you want is 

        <car>corvette</car>

which has no attributes, you can derive a complex type with simple content 
(perhaps string in this case), that just happens to have no attributes. 

Noah

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------





From gl@b... Fri Mar 09 03:17:43 2007
Received: from maggie.w3.org ([1


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