Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Diamond problem using extensions and substitution groups

From: noah_mendelsohn@--.---.---
To: "Michael Kay" <mike@--------.--->
Date: 8/16/2006 10:24:00 AM
XML Schema made a design decision to go with single rather than multiple 
inheritance in the type system.  First of all, there are quite a few 
complexities that come of doing multiple inheritance in any language. Look 
careuflly at what C++ does to achieve this, for example, and you'll 
realize that it's tricky.  In the particular case of XML, there is the 
issue that the order of elements is significant.  If you inherit from 
complex combinations of base types, it can be rather tricky to figure out 
what a sensible order for the actual content would be, and whether users 
would even like it.

Sunstitution groups in XML Schema depend on the type system, so the 
constraint to single inheritance is "inherited" there.

Noah

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





From easirois@r... Thu Aug 17 22:56:36 2006
Received: from lisa.w


transparent
Print
Mail
Digg
delicious
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