W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2003

Re: Proposed Infoset Addendum to SOAP Messages with Attachments

From: Marc Hadley <Marc.Hadley@Sun.COM>
Date: Tue, 01 Apr 2003 11:11:54 -0500
To: Martin Gudgin <mgudgin@microsoft.com>
Cc: xml-dist-app@w3.org
Message-id: <A7DE6388-645C-11D7-8D6B-0003937568DC@sun.com>

Comments below.

On Tuesday, Apr 1, 2003, at 05:45 US/Eastern, Martin Gudgin wrote:
>>>
>>> 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>
>
This kind of sidesteps my question by only using a single xbinc:Include 
to refer to the attachment in conjunction with an application specific 
referencing mechanism in the body. Now if I sign the body I sign the 
reference but not the data. I wonder if we need an additional standard 
referencing mechanism to complete the picture. E.g.:

<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 swa:RepresentationRef="http://example.org/me.png" />
       </x:Person>
       <x:Person>
         <x:name>David Chappell</x:name>
         <x:img swa:RepresentationRef="http://example.org/me.png" />
       </x:Person>
     </x:MyData>
   </soap:Body>
</soap:Envelope>

Though how this would play with multiple representations of the same 
resource I'm still not sure.

Marc.

--
Marc Hadley <marc.hadley@sun.com>
Web Technologies and Standards, Sun Microsystems.
Received on Tuesday, 1 April 2003 11:11:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:14 GMT