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.

Catching up on old email ...

If it's external you can just use a URL, e.g. http://www. ...

If it's internal then, if you have URN (or other GUID) associated with the
message then you can use that to identify the message.


-----Original Message-----
From: Prasad Yendluri [mailto:pyendluri@vitria.com]
Sent: Wednesday, March 08, 2000 2:48 PM
To: David Burdett
Cc: ebXML Transport (E-mail)
Subject: Re: MIME enveloping and Packaging work paper for Thursday


Assuming we go with the MIME packaging i.e. multiprt/related with Manifest
forming the first part, could we accomplish referring to entities in the
message or outside of the message from the Manifest as follows?:

A new attribute "ReferenceType" with values "local" and "external" is added
<DocumentReference> element of MessageManifest. Then if
we could use the "Content-ID" of the part and list that in a "ContentId"
attribute. If it is an external resource, URI attribute is used as usual.
However, this still does not address how one could reference a part in
message (MIME). What would a URN for such would look like?


David Burdett wrote:

> Dick
> I found the attached document interesting. However I'd like your views on
> how you would refer to MIME parts from within a Manifest, for example in
> Messaging I thought that the Message Manifest in the Message header might
> look something like ...
> <MessageManifest>
>   <DocumentReference Id='AB273' DocumentType='Text/XML'
>      URI='urn:example.com:ACV-CN-1999/2456#MessageRoutingInfo'
>      Purpose='MessageRoutingInfo' >
>   <DocumentReference Id='AB274' DocumentType='Text/XML'
>      URI='urn:example.com:ACV-CN-1999/2456#Invoice'
>      Purpose='NewInvoice' >
>   <DocumentReference Id='AB275' DocumentType='Image/Jpg'
>      URI='urn:example.com:ACV-CN-1999/2456#InvoiceImage'
>      Purpose='InvoiceAttachment' >
> </MessageManifest>
> The idea of using a URI is that you could refer to something that was:
> 1. In the same Message by specifying a URN, or
> 2. Somewhere on the web, by specifying a URL - if this was an ftp address
> then it could be useful for "sending" large files.
> You could also then use the URI as the unique identifier of a document
> you had taken the message apart and put the various parts in a file or
> database somewhere.
> Two questions:
> 1. how would this work if you wanted to refer to something in the same or
> another message
> 2. You'll also notice that I've made the Manifest 'flat' rather than the
> nested Mime-within-Mime that you had in your example. What do you think
> the pros and cons of this?
> I'd appreciate your thoughts on this.
> David
> -----Original Message-----
> From: Dick Brooks [mailto:dick@8760.com]
> Sent: Monday, March 06, 2000 12:06 PM
> To: Ebxml
> Cc: Dick Brooks
> Subject: MIME enveloping and Packaging work paper for Thursday con-call.
> The attached file is the work paper Nick and I agreed to produce during
> 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