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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] semantics in schema (xsd)

[ Lists Home | Date Index | Thread Index ]

Right.  But then you have to deal with co-occurrence constraints, 
if any.   This is much messier than your approach suggests, 
but you are choosing the right technology:  data objects.

There is an impact on those 'very big XML Schemas' that are 
pushed top-down from committees to local jurisdictions.  We 
use them to bulk-load the data dictionary, then customize. 
The conflict of note will be in the customizations, and 
that is why extensible enumerations (as you say, properties) 
are the best design, and abandon all hopes of global 
definitions throughout.


From: David Megginson [mailto:dmeggin@attglobal.net]

I'd say forget about classes and make your objects big bags of properties 
(attributes and relationships).  The main advantages of classes for 
object-oriented programming -- code reuse and type-safe polymorphism -- 
don't even apply to simple information representation, so why pay the costs 
of a class structure if you don't receive any benefits?

  There exists an entity A.
  A is human.
  A is male.
  A is married to B.
  A is a biological parent of C.


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

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