- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 18 Nov 2005 00:39:00 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv13280/wsdl20
Modified Files:
wsdl20.xml
Log Message:
[LC344] Implemented resolutions of #1, #2, #6, #10, and #14.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.369
retrieving revision 1.370
diff -C2 -d -r1.369 -r1.370
*** wsdl20.xml 18 Nov 2005 00:20:47 -0000 1.369
--- wsdl20.xml 18 Nov 2005 00:38:58 -0000 1.370
***************
*** 205,209 ****
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. But it needs to be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
--- 205,209 ----
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. It must be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
***************
*** 2592,2598 ****
<p>
! Note that faults other than the ones described in the
<comp>Interface</comp>
! component can also be generated at run-time, i.e. faults are
an open set. The
<comp>Interface</comp>
--- 2592,2598 ----
<p>
! Faults other than the ones described in the
<comp>Interface</comp>
! component may also be generated at run-time, i.e. faults are
an open set. The
<comp>Interface</comp>
***************
*** 4834,4841 ****
<comp>Feature</comp> is identified by its IRI.</p>
! <p>Note that the WSDL 2.0's <comp>Feature</comp> concept is derived from SOAP 1.2's abstract
! feature concept (<bibref ref="SOAP12-PART1"/>). Thus, by
! definition, every SOAP 1.2 abstract feature is also a WSDL 2.0
! <comp>Feature</comp> so there is no need to define a separate WSDL 2.0 <comp>Feature</comp> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
--- 4834,4841 ----
<comp>Feature</comp> is identified by its IRI.</p>
! <p>WSDL 2.0's <comp>Feature</comp> concept is derived from SOAP 1.2's abstract
! feature concept (<bibref ref="SOAP12-PART1"/>). Every SOAP 1.2 abstract feature is
! therefore also a WSDL 2.0
! <comp>Feature</comp>. There is no need to define a separate WSDL 2.0 <comp>Feature</comp> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
***************
*** 6417,6421 ****
<item>
<p>
! Zero or more namespace qualified &AII;s whgse
[namespace name] is
NOT <attval>&wsdl-ns;</attval>.
--- 6417,6421 ----
<item>
<p>
! Zero or more namespace qualified &AII;s whose
[namespace name] is
NOT <attval>&wsdl-ns;</attval>.
***************
*** 9518,9523 ****
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and the
! second component has no additional properties.</p>
<p>Instances of properties of the same type are considered equivalent if
--- 9518,9522 ----
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and vice versa.</p>
<p>Instances of properties of the same type are considered equivalent if
***************
*** 9540,9545 ****
<item><p>Finally, set-based values are considered equivalent
! if they contain corresponding equivalent values, without
! regard to order.</p></item>
</ulist>
--- 9539,9544 ----
<item><p>Finally, set-based values are considered equivalent
! if for each value in the first, there is an equivalent value in
! the second, and vice versa.</p></item>
</ulist>
***************
*** 14197,14200 ****
--- 14196,14200 ----
<td><loc href="http://www.w3.org/2002/ws/desc/5/lc-issues/#LC344">LC344</loc>
: Reviewed use of "Note that" throughout and removed usages where they would be incorrectly interpreted as non-normative.
+ Implemented resolutions of #1, #2, #6, #10, and #14.
</td>
</tr>
Received on Friday, 18 November 2005 00:39:02 UTC