Editorial Issue: Part 3 SOAP Binding from Asir Vedamuthu on 2004-07-22 (www-ws-desc@w3.org from July 2004)

From: Asir Vedamuthu <asirv@webmethods.com>
Date: Thu, 22 Jul 2004 05:55:48 -0700
To: www-ws-desc@w3.org
Message-ID: <5B10E50E14A4594EB1B5566B69AD94072EF677@maileast>

Editorial issue: wsoap:module/property

I bumped into conflicting prose, component properties and XML rep for SOAP
Modules. In [1] and [3] below, there is an optional "property" EII. This EII
is unnecessary.

[1] Section 2.8: XML Syntax Summary

"<wsoap:module uri="xs:anyURI" required="xs:boolean"? >
  <documentation />?
  <property ... />?
</wsoap:module>*"

[2] Section 2.5.3: SOAP Module Component

" ..  The properties of the SOAP Module component are as follows:

{uri} An absolute URI as defined by [IETF RFC 2396]. The value of this
property identifies the specific SOAP module that is in use, as defined in
the SOAP Protocol Binding Framework section of [SOAP 1.2 Part 1: Messaging
Framework].

{required} A boolean indicating if the SOAP module is required."

[3] Section 2.5.4: XML Representation

"<wsoap:module uri="uri"
			  required="boolean"? >
  <property ... />?
</wsoap:module>"

Regards,
Asir S Vedamuthu
asirv at webmethods dot com
http://www.webmethods.com/

Received on Thursday, 22 July 2004 08:59:19 UTC