[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Content-ID
Michael, Thanks for the clarification. Advantage of having Content-Id in the envelope is simplicity of extracting that information from the envelope against from the ebXMLHeader's MessageId. Thanks, Saikat -----Original Message----- From: Michael Joya [mailto:mike.joya@xmlglobal.com] Sent: Thursday, February 08, 2001 1:18 PM To: Saha, Saikat Cc: ebXML Transport (E-mail); Burdett, David Subject: Re: Content-ID 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC