[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

SV: Substitution Groups - Use 'em or lose 'em?

• To: "'DuCharme, Bob (LNG-CHO)'" <bob.ducharme@l...>,"'Henry S. Thompson'" <ht@i...>,Marty Burns <burnsmarty@c...>
• Subject: SV: Substitution Groups - Use 'em or lose 'em?
• From: James Lindley Walford <jlw@i...>
• Date: Wed, 31 Aug 2005 10:20:41 +0200
• Cc: xml-dev@l...

Well GML (Geographic Markup Language) is built up using substitution groups,
the idea being that they provide generic data structures such as Feature,
but that application schemas will then be able to define their own list of
real-world Features, such as Road, House, Factory, Damn etc.

Paul Spencer wrote below that GML 3.1 schemas contained errors not found
prior to release, but I don't have details of them.

James Walford

-----Oprindelig meddelelse-----
Fra: DuCharme, Bob (LNG-CHO) [mailto:bob.ducharme@l...]
Sendt: 30. august 2005 15:27
Til: 'Henry S. Thompson'; Marty Burns
Cc: xml-dev@l...
Emne: RE:  Substitution Groups - Use 'em or lose 'em?


I'm glad I looked through my xml-dev folder before resuming work on my XML
2005 paper... can anyone point me to a well-known, shared (e.g. "industry
standard" for some industry or another) XSD schema that uses substitution
groups to make local customization of the schema easier? 

thanks,

Bob DuCharme   www.snee.com/bob       <bob@  
snee.com> weblog on linking-related topics: 
http://www.oreillynet.com/pub/au/1191

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>

• Prev by Date: RE: Names As Types
• Next by Date: SV: Names As Types
• Previous by thread: RE: Substitution Groups - Use 'em or lose 'em?
• Next by thread: Generating implicit wrapper element
• Index(es):
  • Date
  • Thread