W3C home > Mailing lists > Public > www-ws-desc@w3.org > August 2004

Editorial: Issue 177 Implementation

From: Asir Vedamuthu <asirv@webmethods.com>
Date: Mon, 2 Aug 2004 08:22:39 -0700
Message-ID: <5B10E50E14A4594EB1B5566B69AD9407068E67C9@maileast>
To: "'www-ws-desc@w3.org'" <www-ws-desc@w3.org>

ref: issue 177 [1]

On July 8th, we adopted [2] Jonathan's proposal [3]. I have one editorial
issue with 177 implementation.

The types of the following properties in Part 3, SOAP Binding, are defined
using prose instead of wsdls:* types. I request the following property-type

{soap underlying protocol}  => wsdls:anyURI
SOAP Module.{uri}           => wsdls:anyURI
SOAP Module.{required}      => wsdls:boolean
{soap fault code}           => wsdls:QName
{soap fault subcodes}       => list of wsdls:QName
{soap mep}                  => wsdls:anyURI
{soap action}               => wsdls:anyURI


(a) Consistent with Part 1 and HTTP Binding
(b) Otherwise, we will be using two similar types (xs:QName vs. wsdls:QName)
in the component model
(c) Equivalence in Part 1 is defined using wsdl simple types
(d) Part 3 is refuting Part 1 claim, "The component model uses a small set
of predefined simple types, such as boolean, string, token. In order to
avoid introducing a dependency on any particular serialization of the
component model, this specification provides its own definition of those
types" [5]

[2] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jul/0109.html
[3] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0258.html

Asir S Vedamuthu
asirv at webmethods dot com
Received on Monday, 2 August 2004 11:26:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:43 UTC