- From: Martin Gudgin <mgudgin@microsoft.com>
- Date: Tue, 1 Apr 2003 02:45:13 -0800
- To: "Marc Hadley" <Marc.Hadley@Sun.COM>
- Cc: <xml-dist-app@w3.org>
>
> -----Original Message-----
> From: Marc Hadley [mailto:Marc.Hadley@Sun.COM]
> Sent: 31 March 2003 19:41
> To: Martin Gudgin
> Cc: xml-dist-app@w3.org
>
> On Wednesday, Mar 26, 2003, at 12:17 US/Eastern, Martin Gudgin wrote:
> >>
> >> (ii) the current formulation misses an important facet of included
> >> attachments: their identity - i'll try to illustrate with a
> >> (contrived) example.
> > <SNIP>example</SNIP>
> >>
> >> I suspect that a constrained use of the swa:Representation element
> >> might help with this problem - that is if there is only 1
> >> representation of a given resource in the MIME package the
> >> swa:Representation/@href can be used. Alternatively an application
> >> specific attachment reference mechanism could be used but
> that kind
> >> of defeats the purpose.
> >
> > Certainly I was thinking that where identity was important
> > swa:Representation would be used.
> >
> Do you have any specific thoughts on how this could be done,
> particularly in respect to solving the following:
Sure, the href on the xbinc:Include element need not be the same value
as that on the swa:Representation element. Modifying the example from
section 5.2:
MIME-Version: 1.0
Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml;
start="<mymessage.xml@example.org>"
Content-Description: An XML document with my picture
--MIME_boundary
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID: <mymessage.xml@example.org>
<soap:Envelope xmlns:soap="http://www.w3.org/2002/12/soap-envelope"
xmlns:xbinc="http://schemas.xmlsoap.org/2003/03/xbinc" >
<soap:Header>
<xbinc:DoInclude
soap:role="http://www.w3.org/2002/12/soap-envelope/role/next"
soap:mustUnderstand="false"
soap:relay="true" />
<swa:Representation
xmlns:swa="http://schemas.xmlsoap.org/2003/03/swa"
URI="http://example.org/me.png"
swa:MediaType="image/png" >
<xbinc:Include href="cid:me@example.com" />
</swa:Representation>
</soap:Header>
<soap:Body>
<x:MyData xmlns:x="http://example.org/mystuff" >
<x:Person>
<x:name>Don Box</x:name>
<x:img src="http://example.org/me.png" />
</x:Person>
<x:Person>
<x:name>David Chappell</x:name>
<x:img src="http://example.org/me.png" />
</x:Person>
</x:MyData>
</soap:Body>
</soap:Envelope>
--MIME_boundary
Content-Type: image/png
Content-Transfer-Encoding: binary
Content-ID: <me@example.com>
fd a5 8a 29 aa 46 1b 24
--MIME_boundary--
( I know Don and Dave don't actually look alike ;-) )
Does this help?
Gudge
Received on Tuesday, 1 April 2003 05:45:40 UTC