- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Wed, 26 May 2004 07:47:50 +0600
- To: "Jonathan Marsh" <jmarsh@microsoft.com>, <www-ws-desc@w3.org>
Hi Jonathan,
> Issue 96: Intermediaries support
> RESOLUTION: Close 185 by removing soap:header.
> RESOLUTION: Close 186 as obsolete.
> ACTION: Editors to remove soap:header.
Done during F2F.
> Issue 181: Bind to other protocols
> RESOLUTION: Close issue 181 by dropping the word "only" from
> 2.2.2 SOAP Binding Component and describe what
> happens if a different uri (which must be
> compatible with the wsdl soap binding) is used.
> ACTION: Editors to fix 2.2.2 to allow other protocols.
Done (in the commit I will make when I get to a network).
> Issue 182: defaultMEP inheritance-syntax or model?
> RESOLUTION: Change component model to remove default* properties,
> use mapping from syntax instead.
> ACTION: Editors to fix component model to remove default*
> properties, use mapping from syntax instead.
TBD.
> Issue 1: How to specify an empty SOAP action
> RESOLUTION: Closed, no @soapaction means no header.
> ACTION: Sanjiva to implement the resolution that @soapaction not
> there means no soapaction.
TBD.
> Issue 191: Relationship between wsdl mep and soap mep.
> RESOLUTION: Closed with a statement in the introduction "if you
> are familiar with soap meps, wsdl meps are the same
> but a little bit more abstract"
> ACTION: Part 2 Editors to add such a statement.
> ACTION: Part 3 Editors to add a statement to relate each of the
> two soap meps to wsdl meps.
TBD.
> Issue 194: Why interleave wsdl: and wsoap: namespaced elements?
> RESOLUTION: Closed, by adopting Sanjiva's proposal as amended
> by Roberto (add @type).
Done.
> Issue 190: Layering of SOAP webMethod on top of HTTP binding
> RESOLUTION: Agreed to remove {web method} property and associated
> attribute.
> ACTION: Editors to remove the {web method} property from the
> component model (and related syntax, including defaulting
> syntax).
Done.
> RESOLUTION: http:inputSerialization will not be added to SOAP
> binding.
> ACTION: Editors to add ednotes to the spec to indicate areas that
> had contention.
> RESOLUTION: Remove @separator from HTTP binding.
> ACTION: Editors to remove @separator from HTTP binding.
> ACTION: DaveO to write up a scenario to motivate path creation
> on a per-operation basis.
> RESOLUTION: Allow http:version, http:authenticationType,
> http:authenticationRealm, http:cookies,
> http:transfer-coding on the SOAP binding.
> ACTION: Editors to write up that we allow http:version etc.
> in the soap binding when the protocol is http.
> RESOLUTION: Close 190 per above resolutions.
TBD.
> Issue 188: wsoap:address vs. http:address?
> RESOLUTION: coalesce http:address and soap:address.
> ACTION: Editors to update part 1 to add optional
> /service/endpoint/@address
Done.
> ACTION: Editors to update part 3 to remove soap:address and
> http:address and update binding details accordingly.
> RESOLUTION: issue 188 closed per above.
Done for SOAP binding.
> Issue 61: Additional SOAP binding for HTTP GET-in/SOAP-out.
> RESOLUTION: Close issue 61, add support for HTTP URI binding
> rules.
> ACTION: Editors to update part 3 to say that for SOAP Response
> MEPs the URI will be generated following the HTTP
> binding rules for generating a URI (for GET).
TBD.
> Issue 184:
> RESOLUTION: Closed with editorial Action Item to make sure the
> wording does not preclude MTOM use.
> ACTION: Editors to update soap binding default rules to allow
> use of MTOM.
TBD.
Sanjiva.
Received on Tuesday, 25 May 2004 22:09:53 UTC