Message-Id: <199411081730.RAA24160@lust.mrrl.lut.ac.uk>
To: uri@bunyip.com
Subject: Re: x-uri draft
In-Reply-To: Your message of "Mon, 07 Nov 1994 15:42:11 MST."
<01HJ7FH7O8QI91VY3G@SIGURD.INNOSOFT.COM>
Date: Tue, 08 Nov 1994 17:30:13 +0000
From: Martin Hamilton <martin@mrrl.lut.ac.uk>
Ned Freed writes:
| For starters, standardized headers don't begin with X-, since X- means not
| subject to standardization. As such, the header would have to be URI: or WWW:
| or whatever.
I was thinking in terms of the X-URI: potentially becoming URI: if
there were any interest in it beyond experimental use. Do I have the
protocol wrong here ?
| Second, the mechanism you've described isn't general enough. You now have
| personal contact information in the header. But who is it for? The person or
| persons listed on the From: line? The sender? The reply-to address? How about
| contact information for recipients, so one recipient can find out about other
| recipients?
It would be the author of the message - the URI is analagous to the
sender's signature. Perhaps it should be Author-URI: to make the
semantics explicit ?
| I would much rather see something along the lines of the RFC1522 approach to
| handling non-ASCII character sets used to provide these services. A URI in th
| e
| personal name field associated with my address would be just right for my
| contact information, regardless of whether I'm the message originator or
| recipient.
Interesting... It would be nice to be able to include the URIs with
little or no mangling, so that users could copy and paste them if
necessary. Do you think that would that be feasible with an RFC 1522
type approach ?
Martin