OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: MIME enveloping and Packaging work paper for Thursday con-call.


Prasad,
 
The RosettaNet example you provided could easily be placed into the "payload" bodypart provided in our specification.  The approach described in the paper allows implementers to place ANYTHING into the "payload bodypart", including the multipart/related contents currently used by RosettaNet.

Dick Brooks
 
 -----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org [mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of Prasad Yendluri
Sent: Monday, March 06, 2000 3:42 PM
To: Ebxml
Subject: Re: MIME enveloping and Packaging work paper for Thursday con-call.

Hi,

I think it will be interesting to consider what RosettaNet had already done to address this issue. RNIF1.1 also uses a  MIME multipart construct to pack together XML and non-XML (e.g. binary) parts. However the "multipart/related" construct is used and  "content-id" is used to identify and reference the related parts.

I have attached a document that I wrote a little while back, to explain the use of the MIME construct by RosettaNet.

Thanks, Prasad

Dick Brooks wrote:

The attached file is the work paper Nick and I agreed to produce during the
last con-call. Please review and prepare to discuss during the con-call on
Thursday.

Thanks,

Dick Brooks
http://www.8760.com/



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC