XML-binary Optimized Packaging Errata

About this document

This document lists known errata to the Recommendation. Each entry has the following information:

• A unique entry number
• The date it was added to the errata page.
• Whether the entry is considered an important error, a minor typographical error, a clarification, or a known problem with the document itself.
• The section referred to.
• A description of the problem and correction if applicable.

Note: see the section on Errata Management in the W3C Process Document ([PROCESS] section 7.6.1) for more information about normative corrections.

Known Errors

• [28rec]
  • 2005-05-09
  • document problem
  • Section 1, Section 1.1
  • First paragraph of both section 1 and 1.1, the [XMLInfoSet] link should match the Reference section entry "XMLInfoset"
• [32rec]
  • 2005-05-09
  • minor typographical
  • Section 1.2, Section 1.3, Section 3.1, Section 4.1
  • The namespace prefix used in all the sections listed above should be xmime: instead of xmlmime:
• [34rec]
  • 2005-10-26
  • minor typographical
  • Section 1.2
  • The startinfo parameter used in the sections listed above should be start-info
• [35rec]
  • 2005-10-26
  • minor editorial
  • Section 1.2
  • The value of the action parameter must be an absolute URI. Therefore all its occurences in the section listed above should be action="http://www.example.com/ProcessData"
• [36rec]
  • 2005-10-26
  • clarification
  • Section 3.1
  • To remove any possible ambiguity, the following text is to be added at the end of the 3rd bullet of section 3.1:

    Note that this rule requires that the [children] of the element information item to be optimized contains only character information items.

• [40rec]
  • 2006-02-22
  • minor editorial
  • Section 1.2
  • The URLs used in the examples belonging to the CID URL Scheme should have the form of a RFC 822 addr-spec prefixed by "cid:". Therefore, Example 2 should read:

    MIME-Version: 1.0
    Content-Type: Multipart/Related;boundary=MIME_boundary;
        type="application/xop+xml";
        start="<mymessage.xml@example.org>";
        startinfo="application/soap+xml; action=\"ProcessData\""
    Content-Description: A SOAP message with my pic and sig in it
    
    --MIME_boundary
    Content-Type: application/xop+xml; 
        charset=UTF-8; 
        type="application/soap+xml; action=\"ProcessData\""
    Content-Transfer-Encoding: 8bit
    Content-ID: <mymessage.xml@example.org>
    
    <soap:Envelope
        xmlns:soap='http://www.w3.org/2003/05/soap-envelope'
        xmlns:xmlmime='http://www.w3.org/2004/11/xmlmime'>
      <soap:Body>
        <m:data xmlns:m='http://example.org/stuff'>
          <m:photo 
      xmlmime:contentType='image/png'><xop:Include 
        xmlns:xop='http://www.w3.org/2004/08/xop/include' 
        href='cid:mypicture.png@example.org'/></m:photo>
          <m:sig 
      xmlmime:contentType='application/pkcs7-signature'><xop:Include 
        xmlns:xop='http://www.w3.org/2004/08/xop/include' 
        href='cid:mysignature.hsh@example.org'/></m:sig>
        </m:data>
      </soap:Body>
    </soap:Envelope>
    
    --MIME_boundary
    Content-Type: image/png
    Content-Transfer-Encoding: binary
    Content-ID: <mypicture.png@example.org>
    
    // binary octets for png
    
    --MIME_boundary
    Content-Type: application/pkcs7-signature
    Content-Transfer-Encoding: binary
    Content-ID: <mysignature.hsh@example.org>
    
    // binary octets for signature
    
    --MIME_boundary--
    

    And Example 4 should read:

    MIME-Version: 1.0
    Content-Type: Multipart/Related;boundary=MIME_boundary;
        type="application/xop+xml";
        start="<mymessage.xml@example.org>";
        start-info="text/xml"
    Content-Description: An XML document with my pic and sig in it
    
    --MIME_boundary
    Content-Type: application/xop+xml; 
        charset=UTF-8; 
        type="text/xml"
    Content-Transfer-Encoding: 8bit
    Content-ID: <mymessage.xml@example.org>
    
    <m:data xmlns:m='http://example.org/stuff'>
      <m:photo><xop:Include 
      xmlns:xop='http://www.w3.org/2004/08/xop/include' 
      href='cid:mypicture.png@example.org'/></m:photo>
      <m:sig><xop:Include 
      xmlns:xop='http://www.w3.org/2004/08/xop/include' 
      href='cid:mysignature.hsh@example.org'/></m:sig>
    </m:data>
    
    --MIME_boundary
    Content-Type: image/png
    Content-Transfer-Encoding: binary
    Content-ID: <mypicture.png@example.org>
    
    // binary octets for png
    
    --MIME_boundary
    Content-Type: application/pkcs7-signature
    Content-Transfer-Encoding: binary
    Content-ID: <mysignature.hsh@example.org>
    
    // binary octets for signature
    
    --MIME_boundary--
    

• [42rec]
  • 2007-02-21
  • minor editorial
  • Section 1.2, Section 1.3, Section 3.1, Section 4.1
  • Replace xmlmime by xmime (9 occurences).
    Replace http://www.w3.org/2004/11/xmlmime by http://www.w3.org/2005/05/xmlmime (3 occurences).
    Remove the Editorial note in 1.3.
    Update the reference in B.1 Normative References for "Describing Media Content of Binary Data in XML"