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

2004/ws/addressing ws-addr-wsdl.xml,1.66,1.67

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 13 Feb 2006 15:50:59 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1F8fyd-0004sF-Of@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-wsdl.xml 
Log Message:
Added resolution to issue 66, explicit note that wsaw:UsingAddressing could be used outside WSDL, e.g. in a policy framework

Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.66
retrieving revision 1.67
diff -C2 -d -r1.66 -r1.67
*** ws-addr-wsdl.xml	13 Feb 2006 14:47:02 -0000	1.66
--- ws-addr-wsdl.xml	13 Feb 2006 15:50:57 -0000	1.67
***************
*** 380,386 ****
                  <p>The inclusion of the wsaw:UsingAddressing element
                      indicates that the applicable WS-Addressing
!                     specifications are supported within the
!                     constraints of the WSDL binding being used. This
!                     inclusion allows the usage of anonymous or
                      non-anonymous URIs as addresses in an EPR.
                      Specifically, when included in a SOAP binding, the
--- 380,384 ----
                  <p>The inclusion of the wsaw:UsingAddressing element
                      indicates that the applicable WS-Addressing
!                     specifications are supported and allows use of anonymous or
                      non-anonymous URIs as addresses in an EPR.
                      Specifically, when included in a SOAP binding, the
***************
*** 432,437 ****
                      </ulist>
                  </div3>
              </div2>
!             <div2>
                  <head> Anonymous Element </head>
                  <p>
--- 430,447 ----
                      </ulist>
                  </div3>
+                 <div3>
+                     <head>Other Uses of UsingAddressing Extension Element</head>
+                     <p>The wsaw:UsingAddressing element may also be used in other contexts  
+                         (e.g., as a policy assertion in a policy framework). Its use  
+                         and that of related elements and attributes including  
+                         wsaw:Anonymous (see <specref ref="anonelement"/>) and wsaw:Action (see <specref ref="explicitaction"/>) in such contexts is semantically  
+                         equivalent to the use of wsaw:UsingAddressing as a WSDL extension.</p>
+                     <p>Note that the association of wsaw:UsingAddressing to WSDL constructs  
+                         where the wsaw:UsingAddressing WSDL extension element is not allowed  
+                         is not meaningful.</p>
+                 </div3>
+                 
              </div2>
!             <div2  id="anonelement">
                  <head> Anonymous Element </head>
                  <p>
***************
*** 441,449 ****
  		element. The usage of wsaw:Anonymous element is
  		associated with the usage constraints specified for
! 		wsaw:UsingAddressing element. Hence, it MUST NOT
  		contain the wsdl:required attribute.
                  </p>
                  <p>The inclusion of wsaw:Anonymous without inclusion
!                 of wsaw:UsingAddressing has no normative intent and is
                  only informational. In other words, the inclusion of
                  wsaw:Anonymous element in WSDL alone does not imply a
--- 451,459 ----
  		element. The usage of wsaw:Anonymous element is
  		associated with the usage constraints specified for
! 		the wsaw:UsingAddressing element. Hence, it MUST NOT
  		contain the wsdl:required attribute.
                  </p>
                  <p>The inclusion of wsaw:Anonymous without inclusion
!                 of wsaw:UsingAddressing has no normative meaning and is
                  only informational. In other words, the inclusion of
                  wsaw:Anonymous element in WSDL alone does not imply a
***************
*** 454,458 ****
                  initiative or as described by other elements of the
                  service contract, regardless of the presence or
!                 absence of wsaw:UsingAddressing element.
                  </p>
                  <p>The wsaw:Anonymous element MAY have three distinct
--- 464,468 ----
                  initiative or as described by other elements of the
                  service contract, regardless of the presence or
!                 absence of a wsaw:UsingAddressing element.
                  </p>
                  <p>The wsaw:Anonymous element MAY have three distinct
***************
*** 460,465 ****
                  for handling anonymous addresses in EPRs. In the
                  following text, the term response endpoint EPR refers
!                 to the [reply endpoint] and [fault endpoint] Message
!                 Addressing Properties collectively.
                  </p>
                  <ulist>
--- 470,475 ----
                  for handling anonymous addresses in EPRs. In the
                  following text, the term response endpoint EPR refers
!                 to the [reply endpoint] and [fault endpoint] message
!                 addressing properties collectively.
                  </p>
                  <ulist>
***************
*** 472,476 ****
                      <item>
  		        <p>"required":This value indicates that all
! 		        response endpoints EPRs in a request message
  		        MUST always use anonymous URI as an address.
                          </p>
--- 482,486 ----
                      <item>
  		        <p>"required":This value indicates that all
! 		        response endpoint EPRs in a request message
  		        MUST always use anonymous URI as an address.
                          </p>
***************
*** 493,497 ****
                      </item>
  	       </ulist>
!                <p>This element MAY appear as a child of operation
                 element in a binding element in WSDL 1.1, or as a
                 binding operation extension element in WSDL 2.0.</p>
--- 503,507 ----
                      </item>
  	       </ulist>
!                <p>This element MAY appear as a child of an operation
                 element in a binding element in WSDL 1.1, or as a
                 binding operation extension element in WSDL 2.0.</p>
***************
*** 517,521 ****
                 <div3>
                     <head>WSDL 2.0 Component Model Changes</head>
! 		   <p>Use of Anonymous element adds the following REQUIRED properties to the WSDL 2.0 component model: </p>
                     <ulist>
  		       <item>
--- 527,531 ----
                 <div3>
                     <head>WSDL 2.0 Component Model Changes</head>
! 		   <p>Use of the Anonymous element adds the following REQUIRED properties to the WSDL 2.0 component model: </p>
                     <ulist>
  		       <item>
Received on Monday, 13 February 2006 15:51:10 GMT

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