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

ARTF telcon summary

From: Mark Jones <jones@research.att.com>
Date: Wed, 30 Jul 2003 12:08:47 -0400 (EDT)
Message-Id: <200307301608.h6UG8lY10055@bual.research.att.com>
To: xml-dist-app@w3.org

Here is a brief summary of the ARTF telcon held from
11am-noon ET, July 30, 2003.

Mark Jones


1. New suggested title for the requirement doc --
   SOAP Optimized Serialization Requirements

2. Revised preamble text:


[Ed Note: Another paragraph may eventually be included to provide an
overall rationale and motivation for considering attachments/optimized
serializations in the first place.  This could reflect the kind of
rational seen in the SwA document and the kind of use cases that we

The requirements set below were shaped by the context of several
influential developments.  The "SOAP
Messages with Attachments" (SwA) W3C Note [1] provided a MIME
multipart/related packaging scheme that related accompanying
"entities" (including binary data) to a SOAP 1.1 message via
referencing rules.  The SwA approach did not, however, naturally
integrate attachments into the SOAP processing model and the XML
Infoset representation of a SOAP message.  The PASWA document [2], a
"Proposed Infoset Addendum to SOAP Messages with Attachments", offered
a more unified approach by suggesting that the accompanying entities
be logically considered a part of the SOAP message XML Infoset, while
retaining the flexibility for implementations to optimize their
behavior.  The requirements listed below are an attempt to capture
both the characteristics of the PASWA model and the constraints
embodied in the various use cases that motivate the inclusion of
entities in SOAP messages.

[1] W3C Note "SOAP Messages with Attachments",
John J. Barton, Satish Thatte, and Henrik Frystyk Nielsen, 11 December 2000,

[2] "Proposed Infoset Addendum to SOAP Messages with Attachments",
Adam Bosworth, Don Box, Martin Gudgin, Mark Jones, Franz-Josef Fritz,
Amy Lewis, Jean-Jacques Moreau, Mark Nottingham, David Orchard,
Hervé Ruellan, Jeffrey Schlimmer, Volker Wiechers,
Version 0.61 Draft, 1 April 2003,

3. Section 3.2 preamble

This section lists requirements placed upon the serialization.
In them, the phrase "infoset parts" identifies
those parts of the Infoset that are targeted for optimization, while
"serialization parts" is used to refer to their corresponding
serialization artifacts "on the wire."  When unqualified "parts" is
used, the requirement applies to both senses.

4. No other editorial pass or analysis of the use cases was done.
Received on Wednesday, 30 July 2003 12:08:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:24 UTC