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

2004/ws/addressing ws-addr-wsdl.xml,1.52,1.53

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 10 Oct 2005 20:20:33 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1EP48P-000571-47@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-wsdl.xml 
Log Message:
Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only

Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -C2 -d -r1.52 -r1.53
*** ws-addr-wsdl.xml	15 Sep 2005 19:16:00 -0000	1.52
--- ws-addr-wsdl.xml	10 Oct 2005 20:20:30 -0000	1.53
***************
*** 152,156 ****
                              <p>A QName identifying a description of the sequences of messages that a
                                  service sends and/or receives. This corresponds to a WSDL 2.0
!                                 interface and/or a WSDL 1.1 port type. When this element is included in an EPR, the
                                  EPR is considered to be specific to the interface or port type
                                  it identifies.</p>
--- 152,156 ----
                              <p>A QName identifying a description of the sequences of messages that a
                                  service sends and/or receives. This corresponds to a WSDL 2.0
!                                 interface or, for backwards compatibility, a WSDL 1.1 port type. When this element is included in an EPR, the
                                  EPR is considered to be specific to the interface or port type
                                  it identifies.</p>
***************
*** 162,166 ****
                              <p>A QName that identifies the set of endpoints at which a particular
                                  Web service is deployed. The set of endpoints is represented by a
!                                 service in WSDL 2.0 and WSDL 1.1.</p>
                          </def>
                      </gitem>
--- 162,167 ----
                              <p>A QName that identifies the set of endpoints at which a particular
                                  Web service is deployed. The set of endpoints is represented by a
!                                 service in WSDL 2.0 or, for backwards compatibility, a WSDL 1.1
!                                 service.</p>
                          </def>
                      </gitem>
***************
*** 170,174 ****
                              <p>An NCName that identifies one endpoint amongst the set identified by
                                  by the service name above. An endpoint is represented by an endpoint
!                                 in WSDL 2.0 and a port in WSDL 1.1.  When this attribute is
                                  specified, the
                                  EPR is considered to be specific to the endpoint or port
--- 171,175 ----
                              <p>An NCName that identifies one endpoint amongst the set identified by
                                  by the service name above. An endpoint is represented by an endpoint
!                                 in WSDL 2.0 or, for backwards compatibility, a port in WSDL 1.1.  When this attribute is
                                  specified, the
                                  EPR is considered to be specific to the endpoint or port
***************
*** 200,204 ****
              <div2 id="embedmetadataepr">
                  <head>Embedding WSDL Metadata in an EPR</head>
!                 <p>WSDL 1.1 or 2.0 definitions can be embedded in the metadata section of an EPR to
                      provide a consuming application with WSDL information that applies to the
                      referenced endpoint. To do so, the creator of an EPR MAY include a WSDL 2.0
--- 201,205 ----
              <div2 id="embedmetadataepr">
                  <head>Embedding WSDL Metadata in an EPR</head>
!                 <p>WSDL 2.0 or, for backwards compatibility, 1.1 definitions can be embedded in the metadata section of an EPR to
                      provide a consuming application with WSDL information that applies to the
                      referenced endpoint. To do so, the creator of an EPR MAY include a WSDL 2.0
***************
*** 577,581 ****
              <div2 id="defactionwsdl11">
                  <head> Default Action Pattern for WSDL 1.1</head>
!                 <p>In the absence of the wsa:Action attribute, the following pattern is used to
                      construct a default action for inputs and outputs. The general form of an action
                      IRI is as follows:</p>
--- 578,582 ----
              <div2 id="defactionwsdl11">
                  <head> Default Action Pattern for WSDL 1.1</head>
!                 <p>A default pattern is also defined for backwards compatibility with WSDL 1.1. In the absence of the wsa:Action attribute, the following pattern is used to
                      construct a default action for inputs and outputs. The general form of an action
                      IRI is as follows:</p>
***************
*** 668,672 ****
                      <p>output action = http://example.com/stockquote/StockQuotePortType/Quote</p>
                      <p>fault action =
!                         http://example.com/stockquote/StockQuotePortType/GetLastTradePriceFault:Error</p>
                  </example>
                  <p>WSDL defines rules for a default input or output name if the name attribute is
--- 669,673 ----
                      <p>output action = http://example.com/stockquote/StockQuotePortType/Quote</p>
                      <p>fault action =
!                         http://example.com/stockquote/StockQuotePortType/GetLastTradePriceFault/Error</p>
                  </example>
                  <p>WSDL defines rules for a default input or output name if the name attribute is
***************
*** 706,713 ****
              <head>WS-Addressing and WSDL Message Exchange Patterns</head>
              <p> This section describes which of the core message properties are mandatory or
!                 optional for messages in the various MEPs defined by WSDL 1.1 and WSDL 2.0. </p>
              <div2 id="WSDL11MEPS">
                  <head>WSDL 1.1 Message Exchange Patterns</head>
!                 <p> This section describes which of the core message properties are mandatory or
                      optional for messages in the various MEPs defined by WSDL 1.1. </p>
                  <div3 id="wsdl11oneway">
--- 707,714 ----
              <head>WS-Addressing and WSDL Message Exchange Patterns</head>
              <p> This section describes which of the core message properties are mandatory or
!                 optional for messages in the various MEPs defined by WSDL. </p>
              <div2 id="WSDL11MEPS">
                  <head>WSDL 1.1 Message Exchange Patterns</head>
!                 <p> For backwards compatibility, this section describes which of the core message properties are mandatory or
                      optional for messages in the various MEPs defined by WSDL 1.1. </p>
                  <div3 id="wsdl11oneway">
Received on Monday, 10 October 2005 20:20:46 GMT

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