[
Lists Home |
Date Index |
Thread Index
]
Well said. The TP in htTP stands for transport protocol.
An address starting with 'http://' is like a stamped postcard with an
address written on it. Of course, you're not obligated to mail it, though
not doing so would be an exceptional case.
From the viewpoint of non-XML-expert page authors who are actually creating
most of the content on the Web, this concept resonates even
stronger--'http://' means 'please make an http request at this address'.
If the right thing to do is neither obvious nor intuitive, the vast majority
won't do it.
.micah
-----Original Message-----
From: Seairth Jacobs [mailto:seairth@seairth.com]
Sent: Tuesday, March 05, 2002 7:16 AM
To: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Namespaces and URIs (was: A good case for Namespace
URIs)
Yes, I agree. If you want to make something available for access via HTTP,
then use the "http" scheme in a URL. However, if you do not want to make
something accessible via HTTP, then you should not use the "http" scheme
(regardless of the conveniences). When someone sees the "http", this says
"here is a resource that can be retrieved with the Hypertext Transport
Protocol".
I agree that "xmlns://govtalk.gov.uk/CR/core" would have been no help to you
in finding related schema documentation. That is the point. You explicitly
know that this URL will not resolve to documentation, schema definition(s),
or anything else. For this reason (IMHO) a new scheme such as "xmlns" does
have more value than using "http" scheme in a URL that doesn't point to
anything.
---
Seairth Jacobs
seairth@seairth.com
SDML/GTP: http://www.seairth.com
|
