Proposal for Rec36

Dear all,

This is a proposal for solving the issue raised in [1] (which will 
become issue Rec36 as soon as the table is updated).

To remove any possible ambiguity from the 3rd bullet of section 3.1 
Creating XOP Packages from the XOP specification [2], I propose changing 
the current wording :

<current>
3. Identify within the Original XML Infoset the element information 
items to be optimized. To be optimized, the characters comprising the 
[children] of the element information item MUST be in the canonical form 
of xs:base64Binary (see [XML Schema Part 2: Datatypes Second 
Edition]3.2.16 base64Binary) and MUST NOT contain any whitespace 
characters, preceding, inline with or following the non-whitespace content.
</current>

<updated>
3. Identify within the Original XML Infoset the element information 
items to be optimized. To be optimized, the characters comprising the 
[children] of the element information item MUST be in the canonical form 
of xs:base64Binary (see [XML Schema Part 2: Datatypes Second 
Edition]3.2.16 base64Binary) and MUST NOT contain any whitespace 
characters, preceding, inline with or following the non-whitespace 
content. Note that this assume that the [children] of the element 
information item to be optimized contains only character information items.
</updated>

The second paragraph of 2.3.1 Sending a message of the MTOM 
specification [3] would be updated in the same manner.

Best regards,

Hervé.


[1] http://lists.w3.org/Archives/Public/xmlp-comments/2005Aug/0004.html
[2] 
http://www.w3.org/2000/xp/Group/3/06/Attachments/XOP.html#creating_xop_packages
[3] http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/#aof-sending

Received on Monday, 3 October 2005 15:28:34 UTC