W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

Issue 55: Proposed resolution

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Mon, 11 Feb 2002 17:32:01 -0800
Message-ID: <79107D208BA38C45A4E45F62673A434D0656A9A6@red-msg-07.redmond.corp.microsoft.com>
To: "John Ibbotson" <john_ibbotson@uk.ibm.com>
Cc: <xml-dist-app@w3.org>


You are listed as the initiator of the editorial issue 55 [1] (Subject:
Examples needed for encoding/encapsulation) which is based on
requirement 506 [2]. I inherited an action item from the ETF [3] to try
and resolve the issue so here goes...

The issue states that: "The SOAP 1.1 specification partially fulfils
this [506] requirement. It provides one mechanism for encapsulation and
encoding of data with limited examples of extensibility. The XP
specification must broaden these mechanisms via use cases."

Given that:

* The SOAP 1.2 spec provides a modular mechanism by which it is possible
to use multiple representations of user data including plain schema
based (document literal), using the SOAP encoding provided in part 2, or
some other encoding entirely, potentially involving data carried outside
the envelope (we at least do not claim to preclude this).

* The usage scenario WD [4] contains several examples of encoding data
both using document literal and the SOAP 1.2 encoding.

* The primer [5] provides several documented examples and use cases of
both document literal and the SOAP encoding.

would it be reasonable to suggest that we may at the current time cover
the call for multiple mechanisms brought forward and close the issue?

Henrik Frystyk Nielsen

[1] http://www.w3.org/2000/xp/Group/xmlp-issues#x55
[2] http://www.w3.org/TR/xmlp-reqs#z506
[3] http://www.w3.org/2000/xp/Group/etf
[4] http://www.w3.org/TR/2001/WD-xmlp-scenarios-20011217/
[5] http://www.w3.org/TR/2001/WD-soap12-part0-20011217/
Received on Monday, 11 February 2002 20:33:06 UTC

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