W3C home > Mailing lists > Public > public-ws-addressing-comments@w3.org > April 2005

Merge Core and SOAP Binding specs (SOAP, substantive)

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Tue, 12 Apr 2005 14:03:43 -0700
Message-ID: <7DA77BF2392448449D094BCEF67569A507280F31@RED-MSG-30.redmond.corp.microsoft.com>
To: <public-ws-addressing-comments@w3.org>

The current split between Core and SOAP Binding specifications makes the
combined result difficult to read and comprehend and doesn't seem to
help separate abstraction from a concrete binding.  For example:

- The Core contains examples using SOAP, even the Core is supposedly
independent of SOAP.

- XML representations for the abstract properties are defined in the
Core, even though these representations are used as SOAP headers.

- Conversely, if you were looking for a concrete definition of a WS-A
SOAP header, you would not find it in the SOAP Binding spec.

- The definition of the wsa namespace is split between documents,
implying that versioning of these two specs must be held in lockstep,
further implying that they really are a single spec published as two
parts.

- There's lots of redundancy between Core and SOAP boilerplate.

To alleviate this confusion and simplify the spec, we request that the
SOAP Binding specification should be merged back into the Core.  Since
they are on the same timeline and have the same status (Rec track),
there should be minimal process issues.

We are willing to develop a concrete proposal to facilitate this, but
the general idea is to insert sections 2-6 of the SOAP spec as divisions
of a new Section 4 in the Main spec, and merging introductory and
bibliographic material as necessary.  Some consolidation or
specialization of the Security Considerations might also be
contemplated.
Received on Tuesday, 12 April 2005 21:03:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:38 GMT