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

XInclude and MTOM

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Mon, 15 Sep 2003 08:31:23 -0700
Message-ID: <7C083876C492EB4BAAF6B3AE0732970E0C9FAE60@red-msg-08.redmond.corp.microsoft.com>
To: <xml-dist-app@w3.org>

At our telcon on 2003-09-10 I took an action item to start discussion of
requirements MTOM might place on Xinclude. This e-mail attempts to
fulfill that action item. 

XInclude currently has two parse types; xml and text, the former
allowing a subset of one Infoset to be merged into another, the latter
allowing text to be merged into an Infoset ( as character information
item in the [children] property of an element information item ).  The
xbinc:Include element in MTOM functions like Xinclude with a parse type
of base64Binary, it allows binary data to be merged into an Infoset ( as
character information item in the [children] property of an element
information item ). So possible requirements on Xinclude are:

1.	Defined a parse type value of base64Binary that allows binary
data to be merged into an Infoset.

2.	Define whether the character information items merged in 1. are
to be in canonical form or not.

Our spec would then define how one would convert binary data into
xinc:Include elements along with the rules for resolving the href
attribute on the xinc:Include element ( i.e. that the value of such
attributes must reference a MIME part in the multipart/related package
).

Please chime in with your own take on the requirements,

Gudge
Received on Monday, 15 September 2003 11:32:11 GMT

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