ietf-822
[Top] [All Lists]

Re: HTML in MIME mail

1994-11-21 20:10:47
At 3:43 PM 11/21/94, Nathaniel Borenstein wrote:
As for the URL's, you're also right:

"when interpreting relative URLs in a MIME multipart, the message
should be regarded as a directory, with each part being a file named
by its Content-ID. Multipart content-types are represented as directories".

In this way, a reference to <a href="content-1(_at_)message"> is perfectly
reasonable and unambiguous.

That strikes me as very reasonable, but should be spelled out in a
published spec for text/html.  What are the file naming conventions for
URL's in general?  That is, can this be distinguished from a local file
reference by absolute path names?  Should the latter be permitted inside
a MIME multipart at all?  I suspect not, but we need a clear spec.

FYI, there is a draft RFC on relative URLs, which has been released
recently.  I don't have the name directly in front of me, but it's by Roy
Fielding and comes out of the URI IETF working group.

The gist is that relative URLs don't start with a /, much like the rules
for Unix path names.  Of course, the opaque string might not be a Unix
path, it can be ANYTHING, as long as it conforms to the URL encoding rules.
So really, what we are saying is that it doesn't have a
/scheme://hostname/ part.


--
Dirk Herr-Hoyman <hoymand(_at_)gate(_dot_)net> |           I tried to contain 
myself
CyberBeach Publishing               |                                but
   * Internet publishing services   |                          I got out
Lake Worth, Florida, USA            |
Home Page: <URL:http://www.gate.net/~hoymand/cyberbeach.html>
Phone:     +1.407.540.8309



<Prev in Thread] Current Thread [Next in Thread>