Re: Merge Core and SOAP Binding specs (SOAP, substantive)

Thank you for your comment [1].

The WG decided to close the issue with no action.

The WG feels there is not a compelling case for merging the two 
documents and some in the group feel that maintaining a separation of 
bindings and core aspects of the specification is desirable, while 
merging the two specifications would tightly couple the core and SOAP 
binding aspects of the specification.

Please let us know if this resolution is acceptable.
Absent a response within two weeks, we will presume the resolution is 
acceptable to you.

[1] http://www.w3.org/2002/ws/addr/lc-issues/#lc25

-----Original Message-----
From: Jonathan Marsh <jmarsh@microsoft.com 
<mailto:jmarsh@microsoft.com?Subject=Re:%20Merge%20Core%20and%20SOAP%20Binding%20specs%20%28SOAP%2C%20substantive%29&In-Reply-To=%3C7DA77BF2392448449D094BCEF67569A507280F31@RED-MSG-30.redmond.corp%3E&References=%3C7DA77BF2392448449D094BCEF67569A507280F31@RED-MSG-30.redmond.corp.%3E>> 

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 
<mailto:public-ws-addressing-comments@w3.org?Subject=Re:%20Merge%20Core%20and%20SOAP%20Binding%20specs%20%28SOAP%2C%20substantive%29&In-Reply-To=%3C7DA77BF2392448449D094BCEF67569A507280F31@RED-MSG-30.redmond.corp%3E&References=%3C7DA77BF2392448449D094BCEF67569A507280F31@RED-MSG-30.redmond.corp.%3E>> 

Subject: Merge Core and SOAP Binding specs (SOAP, substantive)

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.