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

Re: An approach to let XML 2.n resources hold multiple entitie

• To: Micah Dubinko <MDubinko@c...>, "'Rick Jelliffe'" <ricko@a...>, xml-dev@l...
• Subject: Re: An approach to let XML 2.n resources hold multiple entities
• From: Paul Prescod <paul@p...>
• Date: Thu, 20 Mar 2003 11:33:17 -0800
• In-reply-to: <BD2DBD26EE0BAA48B1A425C7BE7923002D0262@c...>
• References: <BD2DBD26EE0BAA48B1A425C7BE7923002D0262@c...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021212

Micah Dubinko wrote:
>
> 
> Since there are multiple versions of some vocabularies that can't be
> distinguished by the namespace, only by the DOCTYPE, something like this
> would help processors figure out what to do.

If this is an accurate statement of the problem, then I think that there 
are solutions out there. There are three separate issues:

  * multiple "related" namespaces
  * multiple versions of a namespace
  * multiple schemas for a single logical namespace

If you model your versions as different namespaces altogether, then you 
have no problem, just use different namespace declarations.

If you want to have a concept of multiple versions, then you could add a 
"version" attribute to your namespace and figure out what version you're 
dealing with through that.

If you want a single namespace and multiple schemas (whether for 
versioning or otherwise), you can use the XML Schema SchemaLocation 
attribute...or equivalent for other schema languages that have such a 
concept.

The current concensus view is that document types/vocabularies are 
distinct from schemas. The DOCTYPE declaration conflated them in a way 
that was harmful.

  Paul Prescod

• References:
  • RE: An approach to let XML 2.n resources hold multiple entities
    • From: Micah Dubinko <MDubinko@c...>

• Prev by Date: Re: Access XML
• Next by Date: Re: Is #x81 is invalid char in xml 1.0
• Previous by thread: RE: An approach to let XML 2.n resources hold multiple entities
• Next by thread: Tool to automate XML generation
• Index(es):
  • Date
  • Thread