[
Lists Home |
Date Index |
Thread Index
]
The W3C has released as a Working Draft one of the more opaque documents
I've seen. The inclusion mechanism (the most concrete thing I see in
it) appears to reinvent XInclude (as xbinc:Include) for non-XML data;
perhaps it's better to say that it's reinventing unparsed entities
specifically for SOAP?
http://www.w3.org/TR/soap12-mtom/
Excerpts:
------------------------------------------
This document describes an abstract feature and a concrete
implementation of it for optimizing the transmission and/or wire format
of SOAP messages.... The first part of this document (2. Abstract
Transmission Optimization Feature) describes an abstract feature for
optimizing the transmission and/or wire format of a SOAP message by
selectively re-encoding portions of the message, while still presenting
an XML Infoset to the SOAP application.
This Abstract Transmission Optimization Feature is intended to be
implemented by SOAP bindings, however nothing precludes implementation
as a SOAP module.
The usage of the Abstract Transmission Optimization Feature is a
hop-by-hop contract between a SOAP node and the next SOAP node in the
SOAP message path, providing no normative convention for optimization of
SOAP transmission through intermediaries. Additional specifications
could in principle be written to provide for optimized multi-hop
facilities provided herein, or in other ways that build on this
specification (e.g. by providing for transparent passthrough of
optimized messages).
The second part (3. Inclusion Mechanism) describes an Inclusion
Mechanism implementing part of the Abstract Transmission Optimization
Feature in a binding-independant way. The third part (4. HTTP
Transmission Optimization Feature) uses this Inclusion Mechanism for
implementing the Abstract Transmission Optimization Feature for an HTTP
binding.
This document represents a transmission optimization mechanism which was
inspired by a similar mechanism in the PASWA document (see [PASWA]). The
WG plans to work later on the other parts of that document (assigning
media types to binary data in XML infosets and including representations
of Web resources in SOAP messages) and to publish other drafts which
will include such mechanisms.
-----------------------------------------
If anyone has a good explanation of what this is about, I'd love to hear
it.
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org
|
