Date: Mon, 07 Nov 1994 15:42:11 -0700 (PDT)
From: Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject: Re: x-uri draft
In-Reply-To: Your message dated "Mon, 07 Nov 1994 13:34:00 +0000"
To: Martin Hamilton <martin@mrrl.lut.ac.uk>
Message-Id: <01HJ7FH7O8QI91VY3G@SIGURD.INNOSOFT.COM>
> I've written up my proposal for an X-URI: header as a sort of pseudo
> Internet Draft. Before touting it around anywhere else I thought I
> would post it here to see if there were any comments, flames, ... :-)
First of all, let me say that I think the ability to include URI information in
message headers is a really terrific idea.
However, I don't think an X-URI header is the right way to do it.
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.
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?
What about URI pointers to other sorts of information. If we're going to
define a means of embedding URI information in headers it needs to be more
general than this.
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 the
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.
URI information in the subject line would also be useful. Heck I could
see putting a URI in the Date header that points at a calendar entry of
some kind...
Ned