Content-Location MIME headers?

[christopher ferris <chris.ferris@east.sun.com>]

All,

I believe that we should seriously consider use of Content-Location
MIME headers as defined in RFC2557 as an option for addressing
a specific MIME part from within the Manifest [1].

This MAY make packaging of the payload and manifest simpler
and would allow for the "primary" payload object to refer to
composite elements (images, etc.) by an URI reference without
having to be changed to refer to MIME CID's.

From RFC2557:

   This standard specifies that body parts to be referenced can be
   identified either by a Content-ID (containing a Message-ID value) or
   by a Content-Location (containing an arbitrary URL). The reason why
   this standard does not only recommend the use of Content-ID-s is that
   it should be possible to forward existing web pages via e-mail
   without having to rewrite the source text of the web pages. Such
   rewriting has several disadvantages, one of them that security
   checksums will probably be invalidated.

Use of this approach might be combined with the addition of the
xml:base attribute to the ebXMLHeader.

Thoughts?

Chris

[1] http://ietf.org/rfc/rfc2557.txt?number=2557
begin:vcard 
n:Ferris;Christopher
tel;cell:508-667-0402
tel;work:781-442-3063
x-mozilla-html:FALSE
org:Sun Microsystems, Inc;XTC Advanced Development
adr:;;;;;;
version:2.1
email;internet:chris.ferris@east.sun.com
title:Sr. Staff Engineer
fn:Christopher Ferris
end:vcard