XML Schema equivClass.

Arnold, Curt Curt.Arnold at hyprotech.com
Thu Feb 3 02:27:33 GMT 2000

Ahh, the wonders of trying to force an OOP construct (inheritence) onto XML.  Basically, the problem is that "substitutibility" and "structure reuse" are very often at odds.  In OOP languages they go
together much more frequently than in XML.  equivClass really tries to address the substitutibility aspect.  While type inheritance primarily addresses the structure reuse aspect.  

However, content groups and attribute groups accomplish the same effects as type inheritance and equivClass's with much less complexity.  You might see my note
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000JanMar/0040.html , also you might check out my Schema HTMLHelp file at http://www.software.aeat.com/xml/resources.htm

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Please note: New list subscriptions and unsubscriptions
are  now ***CLOSED*** in preparation for list transfer to OASIS.

More information about the Xml-dev mailing list