• To: Dan Vint <dvint@m...>
• Subject: Re: Data streams and schema use and identification
• From: John Cowan <cowan@m...>
• Date: Wed, 23 Apr 2003 15:18:34 -0400
• Cc: xml-dev@l...
• In-reply-to: <5.2.1.1.2.20030423111522.0296a028@m...>
• References: <5.2.1.1.2.20030423080053.02ee7e98@m...> <5.2.1.1.2.20030422121632.02dd81f0@p...> <5.2.1.1.2.20030422121632.02dd81f0@p...> <5.2.1.1.2.20030423080053.02ee7e98@m...> <5.2.1.1.2.20030423111522.0296a028@m...>
• User-agent: Mutt/1.3.28i

Dan Vint scripsit:

> I was sort of looking at the targetNamespace as providing some of the 
> benefit of the public identifier if you followed the process of putting a 
> version number in the URL and changed it with each significant change.  

So it can, provided you remember that its presence is merely a hint and
Schema-based tools need not respect it.

RFC 3151 (http://www.ietf.org/rfc/rfc3151.txt) explains how to map a
public identifier (either an FPI or not) into a URI suitable for use
either as a namespace name or as a schema identification hint.

> But how many people are working with more than one schema? 

For me it's routine to use different schemata at different stages of
processing.

-- 
John Cowan      http://www.ccil.org/~cowan      jcowan@r...
Be yourself.  Especially do not feign a working knowledge of RDF where
no such knowledge exists.  Neither be cynical about RELAX NG; for in
the face of all aridity and disenchantment in the world of markup,
James Clark is as perennial as the grass.  --DeXiderata, Sean McGrath

• Follow-Ups:
  • Re: Data streams and schema use and identification
    • From: Dan Vint <dvint@m...>

• References:
  • Re: Data streams and schema use and identification
    • From: Dan Vint <dvint@m...>
  • Data streams and schema use and identification
    • From: Danny Vint <dvint@m...>
  • Re: Data streams and schema use and identification
    • From: Dan Vint <dvint@m...>

• Prev by Date: Re: Data streams and schema use and identification
• Next by Date: Re: Data streams and schema use and identification
• Previous by thread: Re: Data streams and schema use and identification
• Next by thread: Re: Data streams and schema use and identification
• Index(es):
  • Date
  • Thread