OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: Schema concepts

[ Lists Home | Date Index | Thread Index ]
  • From: Marc.McDonald@Design-Intelligence.com
  • To: xml-dev@xml.org
  • Date: Wed, 16 Feb 2000 15:32:06 -0800


"Wang,David" wrote:
> 
> Very simple.  Terseness is not a design goal. :-)
(...)
> OOP classes binds "elements and types" together as one (implicitly),
whereas
> in XML Schema they are actually separated, so all elements have to have a
> type or datatype.  Thus, you'd have to build up a type-hierarchy alongside
> an element one, depending on how you want to use it.

Sounds more like a class-instance model. Classes can inherit from classes,
but are purely definitional. Only instances can have data and they are of a
certain class. Instances can't inherit from instances. 

An object-prototype model is far more flexible and less verbose.

Marc B. McDonald 
Principal Software Scientist
Design Intelligence Inc
(www.design-intelligence.com)

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/threads.html
***************************************************************************




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS