- From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 26 Apr 2007 13:10:50 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv4325
Modified Files:
wsdl20-adjuncts.xml
Log Message:
Done
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4468
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4435
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4436
Closed
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4422
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.265
retrieving revision 1.266
diff -C 2 -d -r1.265 -r1.266
*** wsdl20-adjuncts.xml 19 Apr 2007 16:06:24 -0000 1.265
--- wsdl20-adjuncts.xml 26 Apr 2007 13:10:48 -0000 1.266
***************
*** 728,739 ****
<p>An <comp>Interface Operation</comp> component conforming to the RPC style
MUST obey the constraints listed further
! below. Furthermore, if the <att>wrpc:signature</att> extension is
engaged simulatenously, the corresponding &AII; MUST be valid according to the schema
for the extension and additionally MUST obey the constraints listed
in <specref ref="InterfaceOperation_RPC_Signature_Definition"/>
and <specref ref="InterfaceOperation_RPC_Signature_XMLRep"/>.</p>
!
! <p>The RPC style places restrictions for Remote Procedure
! Call-types of interactions. When this value is used, the
associated messages MUST conform to the rules below,
described using XML Schema <bibref ref="XMLSchemaP1"/>. Note
--- 728,737 ----
<p>An <comp>Interface Operation</comp> component conforming to the RPC style
MUST obey the constraints listed further
! below. Also, if the <att>wrpc:signature</att> extension is
engaged simulatenously, the corresponding &AII; MUST be valid according to the schema
for the extension and additionally MUST obey the constraints listed
in <specref ref="InterfaceOperation_RPC_Signature_Definition"/>
and <specref ref="InterfaceOperation_RPC_Signature_XMLRep"/>.</p>
! <p>Furthermore, the
associated messages MUST conform to the rules below,
described using XML Schema <bibref ref="XMLSchemaP1"/>. Note
***************
*** 747,750 ****
--- 745,752 ----
property MUST have the value either <attval>&wsdl-mep-in-only;</attval> or <attval>&wsdl-mep-in-out;</attval>.</assert></p>
+ <p><assert class="component" id="RPCStyle-2029" cr-id="RPCStyle-5007">If the RPC style is used by an <comp>Interface Operation</comp>
+ component then its <prop comp="Interface Operation">message exchange pattern</prop>
+ property MUST have the value either <attval>&wsdl-mep-in-only;</attval> or <attval>&wsdl-mep-in-out;</attval>.</assert></p>
+
<p>If the <comp>Interface Operation</comp> component uses a
<prop comp="Interface Operation">message exchange pattern</prop> for which there is no output
***************
*** 3222,3226 ****
<bibref ref="RFC3986"/>).</assert> If the <prop
comp="Binding Operation">http location</prop> property
! is NOT set, the HTTP Request IRI is the value of the <prop
comp="Endpoint">address</prop> property of the
<comp>Endpoint</comp> component.
--- 3224,3228 ----
<bibref ref="RFC3986"/>).</assert> If the <prop
comp="Binding Operation">http location</prop> property
! is not set, the HTTP Request IRI is the value of the <prop
comp="Endpoint">address</prop> property of the
<comp>Endpoint</comp> component.
Received on Thursday, 26 April 2007 13:10:55 UTC