W3C home > Mailing lists > Public > www-tag@w3.org > July 2003

Re: [metaDataInURI-31]: Initial draft finding for public review/ comme nt.

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Fri, 11 Jul 2003 16:00:36 -0400
To: www-tag@w3.org
Message-ID: <877k6o6dgb.fsf@nwalsh.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ "Williams, Stuart" <skw@hp.com> was heard to say:
|> -----Original Message-----
|> From: Norman Walsh [mailto:Norman.Walsh@sun.com] 
[...]
|> In fact, I think this could be described as a syntactic 
|> understanding of the URI as opposed to any sort of semantic 
|> understanding.
[...]
| I know I'm pushing on this. This is where this issue intersects with
| httpRange-14 (words to the effect of http URI without fragments identify
| documents aka networked resources...you can't use that to name Dan's
| car...). I would really like both resolved in a consistent way. No peaking
| means just that... 

Yes, it would be nice to get httpRange14 sorted. I think this also has
bearing on abstractComponentRefs-37. One of the questions that has to
be addressed is whether or not a URI that's intended to identify
abstract components can in some sense be known to be more than just a
random URI.

| [RFC2368 mailto scheme]
|    "The mailto URL scheme is used to designate the Internet mailing
|    address of an individual or service."

So, in looking at this utterance and the others, I think I could apply
the principle of being conservative in what you send and liberal about
what you receive (I've forgotten the pithy name for that principle, if
it has one).

If you construct a mailto: URI, make sure it identifies an internet
mailing address. If you receive a mailto: URI, do not assume that it
identifies an internet mailing address.

I know that some folks want to make assertions about things based on
the scheme of the URI used to identify them (hence httpRange-14), but
I remain unconvinced that such axiomatic assertions are a good idea.

| ...and of course the infamous...
|
| [RFC2616 http scheme]
| "3.2.2 http URL
|
|    The "http" scheme is used to locate network resources via the HTTP
|    protocol."

You know, RFC2616 is about the http *protocol*. That protocol clearly
uses (syntactic) information that it derives from http: scheme URIs to
locate network resources.

It's hair splitting, I know, but one might argue that other
specifications are free to use http scheme URIs in other ways. For
example, to identify cars or people.

                                        Be seeing you,
                                          norm

- -- 
Norman.Walsh@Sun.COM    | Note: you are currently using an unregistered
XML Standards Architect | evaluation copy of your life. Register now
Web Tech. and Standards | for the full-featured version and cheat codes!
Sun Microsystems, Inc.  | 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE/DxdkOyltUcwYWjsRAjJVAKCPXvoiapIVp4vgMPYBMWrTRHhffwCcDStu
eesDe19Qi71CHdHSXSYTaLs=
=Lcax
-----END PGP SIGNATURE-----
Received on Friday, 11 July 2003 16:01:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:18 GMT