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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: XML Schemas: Best Practices

[ Lists Home | Date Index | Thread Index ]
  • From: Francis Norton <francis@redrice.com>
  • To: "Roger L. Costello" <costello@mitre.org>
  • Date: Tue, 07 Nov 2000 09:52:18 +0000

"Roger L. Costello" wrote:
> One simple solution is that when you create Chameleon components assign
> them a global unique id (a GUID).  The XML Schema spec allows you to add
> an attribute, id, to all element, attribute, complexType, and simpleType
> components.  This id attribute can be used by a tool to "locate" a
> Chameleon component, regardless of what "face" (namespace) it currently
> wears.  That is, the tool opens up an instance document using DOM, and
> the DOM API will provide the tool access to the id value for all
> components in the instance document.
Could one (should one?) generalise this to suggest a convention whereby
we use IDs for syntactic re-use and namespaces for semantic re-use?

It has a certain appeal - namespaces carrying more obvious semantic
information than GUIDs...

Francis Norton.

why not?


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

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