W3C home > Mailing lists > Public > uri@w3.org > November 1995

Re: mid and cid URLs

From: Al Gilman <asg@severn.wash.inmet.com>
Date: Tue, 21 Nov 1995 17:17:48 -0500 (EST)
Message-Id: <9511212217.AA07499@severn.wash.inmet.com>
To: moore@cs.utk.edu (Keith Moore)
Cc: asg@severn.wash.inmet.com, uri@bunyip.com, elevinso@Accurate.COM, ietf-types@uninett.no, moore@cs.utk.edu
To follow up on what Keith Moore said ...
  
  
  I've been thinking of "cid", "message/external-body; access-type=cid"
  (and by association, "mid") as *URL* schemes, especially (for the
  former two) within the context of multipart/related.  Such a scheme is
  useful even without the URN infrastructure.
  
For all the reasons that Ned has been teaching me, a "cid" does
not represent a reliable _location_ reference.  It is a name used
in searching for the cited object.  Even inside the same MIME
multipart.

The Message-ID is in use today as an object name in the
"In-reply-to" header in RFC 822 mail that knows nothing about
MIME.  And it is now used by Hypermail at random _receiving_
sites that have nothing to do with the sending location to
reconstruct threads of dialog.

The Message-ID is a URN that is successful today.  Content-ID is
[?? you tell me.].

You don't have to define and provide a retrieval service for object
naming on widely-distributed objects like RFC 822 mail and News to
be a useful construct.

Al  
  
  
Received on Tuesday, 21 November 1995 17:18:40 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 10 October 2021 22:17:32 UTC