W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > July to September 2005

2004/ws/addressing ws-addr-core.xml,1.100,1.101

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 12 Jul 2005 15:57:24 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DsN8O-00007q-GP@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv469

Modified Files:
	ws-addr-core.xml 
Log Message:
Added resolution to issue 107 - assorted editorial fixes wrt alignment with WSDL terminology

Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.100
retrieving revision 1.101
diff -C2 -d -r1.100 -r1.101
*** ws-addr-core.xml	11 Jul 2005 19:58:33 -0000	1.100
--- ws-addr-core.xml	12 Jul 2005 15:57:22 -0000	1.101
***************
*** 425,429 ****
                  and interfaces; business processes and e-commerce specifications, among others, can
                  also be used to define explicit contracts between the parties.</p>
!             <p> The basic interaction pattern from which all others are composed is "one way". In
                  this pattern a source sends a message to a destination without any further
                  definition of the interaction. "Request-response" is a common interaction pattern that
--- 425,429 ----
                  and interfaces; business processes and e-commerce specifications, among others, can
                  also be used to define explicit contracts between the parties.</p>
!             <p> The basic interaction pattern from which all others are composed is "one-way". In
                  this pattern a source sends a message to a destination without any further
                  definition of the interaction. "Request-response" is a common interaction pattern that
***************
*** 433,437 ****
                  other message. Note, however, that reply messages may be sent as part of other
                  message exchanges as well, and are not restricted to the usual single Request,
!                 single Response pattern, or to a particular WSDL MEP. The contract between the
                  interacting parties may specify that multiple or even a variable number of replies
                  be delivered. </p>
--- 433,437 ----
                  other message. Note, however, that reply messages may be sent as part of other
                  message exchanges as well, and are not restricted to the usual single Request,
!                 single Response pattern, or to a particular WSDL transmission primitive or MEP. The contract between the
                  interacting parties may specify that multiple or even a variable number of replies
                  be delivered. </p>
***************
*** 481,485 ****
                              message.</p>
                          <p>It is RECOMMENDED that the value of the [action] property is an IRI
!                             identifying an input, output, or fault message within a WSDL interface.
                              An action may be explicitly or implicitly associated with the
                              corresponding WSDL definition. &wsa-wsdl.title;[<bibref
--- 481,486 ----
                              message.</p>
                          <p>It is RECOMMENDED that the value of the [action] property is an IRI
!                             identifying an input, output, or fault message within a WSDL interface
!                             or port type.
                              An action may be explicitly or implicitly associated with the
                              corresponding WSDL definition. &wsa-wsdl.title;[<bibref
Received on Tuesday, 12 July 2005 15:57:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:40 GMT