W3C home > Mailing lists > Public > xmlp-comments@w3.org > March 2004

XMLP Issue 462 closed

From: Jacek Kopecky <jacek.kopecky@systinet.com>
Date: Thu, 11 Mar 2004 16:28:50 +0100
To: net.dret@dret.net
Cc: XMLP Comments <xmlp-comments@w3.org>
Message-Id: <1079018930.1981.50.camel@localhost>

Erik,

In XMLP issue 462 [1] you are concerned with base64 data in the infoset
that contains whitespace; and the handling of such data in XOP. The WG
has resolved to close your issue by accepting the following explanation
and adding it where appropriate in the specs' introduction chapters.

The primary use-case for XOP is that an application wants to include a
chunk of binary data (that the application has as an octet stream, not
encoded for example as base64) in an XML document in some optimized
form. Where XOP requires canonical base64 data, that is only a
conceptual requirement, it is expected that any implementation will skip
encoding the original data into the infoset (or data model) but will
pass the data directly to the XOP layer which will put it directly into
the MIME envelope. Conceptually therefore, the data may be viewed as
present in the infoset in base64 canonical, even if the implementation
doesn't contain any base64-encoding code.

For the other use cases where the base64 form is actually used, we must
choose one unambiguous form (because we are required to reconstruct the
precise infoset at the receiving end), and we chose to reuse XML
Schema's canonical form (yet to be published?).

Does this satisfy your issue?

Best regards,

                   Jacek Kopecky

                   Systinet Corporation
                   http://www.systinet.com/


[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x462
Received on Thursday, 11 March 2004 10:28:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:40:22 UTC