4.5.2 Character Encoding of Attachments

• From: A. Vine <andrea.vine@Sun.COM>
• Date: Mon, 12 Apr 2004 16:32:34 -0700
• To: I18n WSTF <public-i18n-ws@w3.org>
• Message-id: <407B2712.9050800@sun.com>

This should replace the current example in:

4.5.2 Character Encoding of Attachments

I culled from the example in SOAP attachments and re-skimmed RFCs 2045 and 2046. 
  The only question I have is the start="<article123456@samplerepository.co.uk>" 
parm and the use of article123456@samplerepository.co.uk as a reference id vs. 
the URI I used within the SOAP body - 
http://samplerepository.co.uk/retrieval/database/article123456.

MIME-Version: 1.0
Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml;
         start="<article123456@samplerepository.co.uk>"
Content-Description: Sample SOAP envelope with attachment in ISO-8859-15.

--MIME_boundary
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID: <article123456@samplerepository.co.uk>

<?xml version='1.0' encoding="UTF-8" ?>
   <env:Envelope xmlns:env="http://www.w3.org/2002/06/soap-envelope" >
    <env:Header>
    </env:Header>
    <env:Body>
      <encExample:articleRetriever>
        <articleTitle xml:lang="fr">Voici le titre</articleTitle>
        <articleEncoding>ISO-8859-15</articleEncoding>
        <articleSize unit="byte">14355</articleSize>
      </encExample:articleRetriever>
<!-- ... -->
     <att:SecondaryPartBag>
	http://samplerepository.co.uk/retrieval/database/article123456
     </att:SecondaryPartBag>
    </env:Body>
   </env:Envelope>

--MIME_boundary
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
Content-ID: <article123456@samplerepository.co.uk>

...plain text article in ISO-8859-15...

--MIME_boundary--

Received on Monday, 12 April 2004 19:08:08 UTC