W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > January to March 2006

2004/ws/addressing ws-addr-core.xml,1.136,1.137

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 14 Mar 2006 10:48:31 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <20060314104831.C86F44F396@homer.w3.org>

Update of /sources/public/2004/ws/addressing
In directory homer:/tmp/cvs-serv4819

Modified Files:
	ws-addr-core.xml 
Log Message:
Fixed typos


Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.136
retrieving revision 1.137
diff -C2 -d -r1.136 -r1.137
*** ws-addr-core.xml	14 Mar 2006 09:40:19 -0000	1.136
--- ws-addr-core.xml	14 Mar 2006 10:48:29 -0000	1.137
***************
*** 144,150 ****
                      addressing properties, this specification uses the following notation:
                          (<i>n</i>..<i>m</i>), where <i>n</i> is the minimum allowed number of
!                     ocurrances of the property and <i>m</i> is the maximum allowed number of
!                     occurances. When <i>n</i> has the same value as <i>m</i> then exactly that
!                     number of ocurrances of the property must be present in the associated endpoint
                      reference or message.</p>
              </div2>
--- 144,150 ----
                      addressing properties, this specification uses the following notation:
                          (<i>n</i>..<i>m</i>), where <i>n</i> is the minimum allowed number of
!                     occurrences of the property and <i>m</i> is the maximum allowed number of
!                     occurrences. When <i>n</i> has the same value as <i>m</i> then exactly that
!                     number of occurrences of the property must be present in the associated endpoint
                      reference or message.</p>
              </div2>
***************
*** 450,454 ****
                      processing model for such extensions is defined by the specification for those
                      extensions. Software that processes endpoint references can safely ignore any
!                     such extensions that it does not recognise or understand.</p>
                  <p>Extension elements and attributes MAY add additional properties to an endpoint
                      reference in addition to those specified in <specref ref="eprinfomodel"/>.
--- 450,454 ----
                      processing model for such extensions is defined by the specification for those
                      extensions. Software that processes endpoint references can safely ignore any
!                     such extensions that it does not recognize or understand.</p>
                  <p>Extension elements and attributes MAY add additional properties to an endpoint
                      reference in addition to those specified in <specref ref="eprinfomodel"/>.
***************
*** 458,463 ****
                      indicate that a different binding be used. </p>
                  <p>Note that this ability to modify existing properties and binding behavior, when
!                     coupled with the fact that software can ignore unknown or unrecognised
!                     extensions, may result in a difference in behaviour depending on whether such an
                      extended endpoint reference is processed by software that understands the
                      extension(s). When designing endpoint reference extensions designers should
--- 458,463 ----
                      indicate that a different binding be used. </p>
                  <p>Note that this ability to modify existing properties and binding behavior, when
!                     coupled with the fact that software can ignore unknown or unrecognized
!                     extensions, may result in a difference in behavior depending on whether such an
                      extended endpoint reference is processed by software that understands the
                      extension(s). When designing endpoint reference extensions designers should
***************
*** 889,893 ****
              <p>WS-Addressing supports capabilities that allow a message sender to instruct a message
                  receiver to send additional unsolicited messages to other receivers of their choice.
!                 To an extent the content of such unsolicted messages can also be controlled using 
                  reference parameters supplied by the initial message sender. Because of these 
                  capabilities it is essential that communications using WS-Addressing are adequately 
--- 889,893 ----
              <p>WS-Addressing supports capabilities that allow a message sender to instruct a message
                  receiver to send additional unsolicited messages to other receivers of their choice.
!                 To an extent the content of such unsolicited messages can also be controlled using 
                  reference parameters supplied by the initial message sender. Because of these 
                  capabilities it is essential that communications using WS-Addressing are adequately 
Received on Tuesday, 14 March 2006 10:48:44 GMT

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