[
Lists Home |
Date Index |
Thread Index
]
Hmm... I missed this one. Well, that would certainly be a good way to do
it. However, I was just suggesting that if someone wanted to use a URL to
identify a namespace, just use a scheme other than the "http". To avoid
ending up with a proliferation of new scheme names, we could just define a
common one that everyone can use. Whether the URL would be helpful in
locating schema documentation or not is another question. The main point is
to avoid the use of the "http" scheme when using the URL format, which would
at least reduce the confusion caused in situations like
"http://www.govtalk.gov.uk/CR/core";.
---
Seairth Jacobs
seairth@seairth.com
SDML/GTP: http://www.seairth.com
----- Original Message -----
From: "Bullard, Claude L (Len)" <clbullar@ingr.com>
To: "'Seairth Jacobs'" <seairth@seairth.com>; "xml-dev"
<xml-dev@lists.xml.org>
Sent: Monday, March 04, 2002 3:49 PM
Subject: RE: [xml-dev] Namespaces and URIs (was: A good case for Namespace
URIs)
> We took this up last week. John Cowan pointed to
>
> http://www.ietf.org/rfc/rfc3151.txt
>
> It is unlikely that anyone who sees one of these would
> mistake it for a URL. Howsomeever, should they actually
> want to resolve it, they could use an XML OASIS Catalog
> and do so by mapping a name to a location.
>
> All I am saying is that you don't have to invent
> anything new.
>
> len
>
> From: Seairth Jacobs [mailto:seairth@seairth.com]
>
> Sorry, I don't understand what you are saying. What public ID?
>
>
|
