[
Lists Home |
Date Index |
Thread Index
]
- From: "Ed Hilburn" <lan3bra7@hotmail.com>
- To: xml-dev@xml.org
- Date: Thu, 08 Jun 2000 07:08:39 GMT
As your average, usually competent internet developer I
have come to associate the "scheme:" prefix to a URI as
describing a protocol used to address, fetch, or otherwise
use a resource identified. Examples:
"ftp:" This tells me to use File Transfer Protocol
"mailto:" This tells me to use Simple Mail Transfer Protocol
"telnet:" This tells me to use TELNET protocol
"http:" This tells me to use HyperText Transfer Protocol
"shttp:" This tells me to use Secure HTTP
"file:" This tells me to use the local file system's protcol
For all of the above, I (perhaps naively) see the resource
identified as the producer (ftp server,telnet deamon,
http/shttp web server) or the consumer ( sendmail deamon,
web server accepting a POST) of a particular stream of data.
I have a few questions. If I use the "http:" scheme for
a namespace name URI, does it not imply that I should be
using the HyperText Transfer Protocol? Yes? Why or why not?
If so, what would I be fetching or posting? And how
does this at all help the notion of a namespace? I've
noticed that some of the namespaces give back a 401
page not found error. Does this mean that the namespace
is no longer valid?
Please assist,
Ed
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|