Re: Content-ID

[Christopher Ferris <chris.ferris@east.sun.com>]

I could see the Envelope Content-ID as carrying the same value as
the MessageId element in the ebXMLHeader document as having some
merit. I would think that having both but with different values
would be confusing at best, and could possibly lead to more
serious problems.

Since there is nothing to prevent the Content-ID header from 
being present, it may make sense to tackle this issue next week.

Cheers,

Chris

Michael Joya wrote:
> 
>     Saikat Saha writes, "As per ebXML TRP 0.92, we do not have any Content-ID
> for the message envelope as such although we have Content-ID for Header
> envelope as well as for the Payload envelope." He then asks, "Don't we need
> Content-Id for the entire message?"
> 
>     It should be satisfactory to identify a message using the MessageID
> element located in the EbxmlHeader. That id alone should distinguish one ebxml
> message from the universe of other ebxml messages. If you included Content-Id
> in the Message envelope, you would be identifying a single instance of
> multipart/related content. This may have merits on its own account, but
> I don't see how it would contribute to the ebxml message protocol.
> 
> --
> // Michael Joya
> // XML Global Research and Development
> // 1818 Cornwall Ave. Suite 9
> // Vancouver, Canada
> // 604-717-1100x230
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:;;One Network Drive;Burlington;Ma;01803-0903;USA
version:2.1
email;internet:chris.ferris@east.sun.com
title:Senior Staff Engineer
fn:Christopher Ferris
end:vcard