- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 28 Apr 2006 15:04:27 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv15774
Modified Files:
ws-addr-wsdl.xml
Log Message:
Incorporated resolution to issue lc132 - reworked section 4 to allow use of EPRs as WSDL endpoint/port extensions
Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.96
retrieving revision 1.97
diff -C2 -d -r1.96 -r1.97
*** ws-addr-wsdl.xml 28 Apr 2006 13:40:34 -0000 1.96
--- ws-addr-wsdl.xml 28 Apr 2006 15:04:25 -0000 1.97
***************
*** 51,56 ****
and messages. &wsa-wsdl.title; (this document) defines how the abstract
properties defined in &wsa-core.title; are described using WSDL.</p>
! <p>The classes of products for which this specification is designed to be
! relevant include WSDL and WS-Addressing EPR consumers.</p>
</abstract> &status; <langusage>
<language id="en-US">English</language>
--- 51,56 ----
and messages. &wsa-wsdl.title; (this document) defines how the abstract
properties defined in &wsa-core.title; are described using WSDL.</p>
! <p>The classes of products for which this specification is designed to be relevant
! include WSDL and WS-Addressing EPR consumers.</p>
</abstract> &status; <langusage>
<language id="en-US">English</language>
***************
*** 191,204 ****
<def>
<p>An NCName that identifies one endpoint amongst the set identified 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 it identifies.</p>
</def>
</gitem>
</glist>
! <p>The element information items defined above are used in an EPR's metadata section.
! The following shows an example endpoint reference. This references the interface
! named "ghns:reservationInterface" at the endpoint IRI
"http://greath.example.com/2004/reservation". Note the use of the WSDL[<bibref
ref="WSDL20"/>] wsdlLocation attribute.</p>
--- 191,204 ----
<def>
<p>An NCName that identifies one endpoint amongst the set identified 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 it identifies.</p>
</def>
</gitem>
</glist>
! <p>The element information items defined above are used in an EPR's metadata
! section. The following shows an example endpoint reference. This references the
! interface named "ghns:reservationInterface" at the endpoint IRI
"http://greath.example.com/2004/reservation". Note the use of the WSDL[<bibref
ref="WSDL20"/>] wsdlLocation attribute.</p>
***************
*** 300,316 ****
<div2 id="uaee">
<head><el>UsingAddressing</el> Extension Element</head>
! <p>
! WS-Addressing defines an empty global element,
! wsaw:UsingAddressing, that can be used to indicate
! that an endpoint conforms to the WS-Addressing
! specification. The wsdl:required attribute MAY be
! used to indicate whether WS-Addressing Message
! Addressing Properties are required in messages
! received from service requesters. <specref
! ref="mappresence"/> outlines the requirements on
! messages sent from an endpoint based on the
! contents of any preceding input message and how
! the use of addressing is indicated in the WSDL.
! </p>
<table border="1" id="mappresence">
<caption>MAPs Present in output message when wsaw:UsingAddressing is present</caption>
--- 300,310 ----
<div2 id="uaee">
<head><el>UsingAddressing</el> Extension Element</head>
! <p> WS-Addressing defines an empty global element, wsaw:UsingAddressing, that can be
! used to indicate that an endpoint conforms to the WS-Addressing specification.
! The wsdl:required attribute MAY be used to indicate whether WS-Addressing
! Message Addressing Properties are required in messages received from service
! requesters. <specref ref="mappresence"/> outlines the requirements on messages
! sent from an endpoint based on the contents of any preceding input message and
! how the use of addressing is indicated in the WSDL. </p>
<table border="1" id="mappresence">
<caption>MAPs Present in output message when wsaw:UsingAddressing is present</caption>
***************
*** 328,332 ****
<td>REQUIRED</td>
</tr>
! <tr>
<td>No</td>
<td>Fault</td>
--- 322,326 ----
<td>REQUIRED</td>
</tr>
! <tr>
<td>No</td>
<td>Fault</td>
***************
*** 336,367 ****
</tbody>
</table>
! <p>If WS-A is engaged, use of the message addressing
! properties MUST be fully compliant with this
! specification; in particular, senders MUST use all
! message addressing properties mandated by the
! &wsa-core.title;[<bibref ref="WSADDR-CORE"/>],
! applicable WS-Addressing protocol bindings (e.g.
! &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]),
! and this specification, and MUST follow all
! applicable WS-Addressing normative requirements.
! </p>
! <p>The wsaw:UsingAddressing element SHOULD appear as a
! child of the wsdl:binding element. Alternatively,
! the wsaw:UsingAddressing element MAY instead be
! included as a child of the wsdl20:endpoint (or
! wsdl11:port) when an endpoint intends to indicate
! compliance with WS-Addressing for a specific
! endpoint only.</p>
! <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
! wsaw:UsingAddressing marker identifies the use of
! Web Services Addressing 1.0 bound to SOAP as
! defined by &wsa-soap.title;[<bibref
! ref="WSADDR-SOAP"/>].The presence of this element
! can extend the semantics of the endpoint's WSDL
! binding. </p>
<example>
<head>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</head>
--- 330,350 ----
</tbody>
</table>
! <p>If WS-A is engaged, use of the message addressing properties MUST be fully
! compliant with this specification; in particular, senders MUST use all message
! addressing properties mandated by the &wsa-core.title;[<bibref
! ref="WSADDR-CORE"/>], applicable WS-Addressing protocol bindings (e.g.
! &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]), and this specification,
! and MUST follow all applicable WS-Addressing normative requirements. </p>
! <p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding
! element. Alternatively, the wsaw:UsingAddressing element MAY instead be included
! as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to
! indicate compliance with WS-Addressing for a specific endpoint only.</p>
! <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 wsaw:UsingAddressing marker identifies the use of Web Services
! Addressing 1.0 bound to SOAP as defined by &wsa-soap.title;[<bibref
! ref="WSADDR-SOAP"/>].The presence of this element can extend the semantics
! of the endpoint's WSDL binding. </p>
<example>
<head>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</head>
***************
*** 395,465 ****
<div3 id="wsdl20_usingaddressing">
<head>WSDL 2.0 Component Model Changes</head>
!
! <ednote>
! <name>HH</name>
! <edtext>This has NOT been approved by the WG yet.</edtext>
! </ednote>
!
! <p>Use of WS-Addressing adds the following property to the WSDL 2.0
! component model:</p>
<ulist>
<item>
! <p>{addressing} OPTIONAL, of type
! <code>xs:token</code> with one of the
! values <attval>required</attval> or
! <attval>optional</attval>, to the Binding
! and Endpoint components. When present, the
! property indicates that the use of
! addressing has been declared.
! </p>
! </item>
! </ulist>
!
! <p><specref ref="tab_addressing_Mapping"/> shows the
! mapping from the XML representation to the WSDL
! 2.0 component model.</p>
!
! <table border="1" id="tab_addressing_Mapping">
! <caption>Mapping from XML Representation to Binding and Endpoint components Extension Properties</caption>
! <tbody>
! <tr>
! <th rowspan="1" colspan="1">Property</th>
! <th rowspan="1" colspan="1">Value</th>
! </tr>
! <tr>
! <td>{addressing}</td>
! <td>
! If a <el>wsaw:UsingAddresing</el>
! extension element is present:
! <ulist>
! <item><p>if a
! <att>wsdl:required</att> &AII; is present
! and has a value of <attval>true</attval>,
! then <attval>required</attval></p></item>
! <item><p>otherwise
! <attval>optional</attval></p></item>
! </ulist>
! </td>
! </tr>
! </tbody>
! </table>
!
! <p><specref
! ref="mappresence"/> summarizes the
! meaning of the property as detailed in section <specref ref="uaee"/>.</p>
!
</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">
--- 378,436 ----
<div3 id="wsdl20_usingaddressing">
<head>WSDL 2.0 Component Model Changes</head>
! <ednote>
! <name>HH</name>
! <edtext>This has NOT been approved by the WG yet.</edtext>
! </ednote>
! <p>Use of WS-Addressing adds the following property to the WSDL 2.0 component
! model:</p>
<ulist>
<item>
! <p>{addressing} OPTIONAL, of type <code>xs:token</code> with one of the
! values <attval>required</attval> or <attval>optional</attval>, to
! the Binding and Endpoint components. When present, the property
! indicates that the use of addressing has been declared. </p>
! </item>
! </ulist>
! <p><specref ref="tab_addressing_Mapping"/> shows the mapping from the XML
! representation to the WSDL 2.0 component model.</p>
! <table border="1" id="tab_addressing_Mapping">
! <caption>Mapping from XML Representation to Binding and Endpoint components
! Extension Properties</caption>
! <tbody>
! <tr>
! <th rowspan="1" colspan="1">Property</th>
! <th rowspan="1" colspan="1">Value</th>
! </tr>
! <tr>
! <td>{addressing}</td>
! <td> If a <el>wsaw:UsingAddresing</el> extension element is present: <ulist>
! <item>
! <p>if a <att>wsdl:required</att> &AII; is present
! and has a value of <attval>true</attval>, then
! <attval>required</attval></p>
! </item>
! <item>
! <p>otherwise <attval>optional</attval></p>
! </item>
! </ulist>
! </td>
! </tr>
! </tbody>
! </table>
! <p><specref ref="mappresence"/> summarizes the meaning of the property as
! detailed in section <specref ref="uaee"/>.</p>
</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">
***************
*** 482,489 ****
fault back to the client if a message received includes a response epr with an
[address] that is unsupported by the endpoint. </p>
! <p>The wsaw:Anonymous element, if present, MUST have one of three distinct values that indicate
! three different levels of support 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>
<item>
--- 453,461 ----
fault back to the client if a message received includes a response epr with an
[address] that is unsupported by the endpoint. </p>
! <p>The wsaw:Anonymous element, if present, MUST have one of three distinct values
! that indicate three different levels of support 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>
<item>
***************
*** 561,568 ****
<p> In WSDL 2.0, a SOAP Module component can be used to declare the use of the
WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
! SOAP Module component is semantically equivalent to the {addressing}
! property defined in section <specref ref="wsdl20_usingaddressing"/>. Note that this module is only meaningful when
! used on WSDL components where the {addressing} property is allowed,
! i.e. as a member of the {soap modules} property of a Binding component.</p>
<p>The WS-Addressing 1.0 SOAP Module is described in &wsa-soap.title;[<bibref
ref="WSADDR-SOAP"/>] and is identified with the following URI:
--- 533,541 ----
<p> In WSDL 2.0, a SOAP Module component can be used to declare the use of the
WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
! SOAP Module component is semantically equivalent to the {addressing} property
! defined in section <specref ref="wsdl20_usingaddressing"/>. Note that this
! module is only meaningful when used on WSDL components where the {addressing}
! property is allowed, i.e. as a member of the {soap modules} property of a
! Binding component.</p>
<p>The WS-Addressing 1.0 SOAP Module is described in &wsa-soap.title;[<bibref
ref="WSADDR-SOAP"/>] and is identified with the following URI:
***************
*** 590,605 ****
specified using existing WSDL constructs, in other cases new WSDL extensions are
defined for that purpose.</p>
<div2 id="destinwsdl">
<head>Destination</head>
! <p>The value of the [destination]
! message addressing property for a message sent to
! an endpoint typically matches the value of the {address} property of the endpoint
! component (WSDL 2.0) or the address value provided by the relevant port
! extension (WSDL 1.1). For a SOAP 1.1 port described using WSDL 1.1, the value is
! provided by the location attribute of the soap11:address extension element.</p>
! <p>Additional runtime information could override the value of the [destination] message
! addressing property for messages sent to an endpoint, e.g. a runtime exchange might
! result in a redirection to a different EPR. Note that WS-Addressing does not define any normative
! mechanism for such redirection.</p>
</div2>
<div2 id="actioninwsdl">
--- 563,612 ----
specified using existing WSDL constructs, in other cases new WSDL extensions are
defined for that purpose.</p>
+ <div2 id="eprinendpoint">
+ <head>Extending WSDL Endpoints with an EPR</head>
+ <p>A wsdl20:endpoint or wsdl11:port element MAY be extended using a child
+ wsa:EndpointReference element. When extended this way, the [address] property of
+ the child EPR must match the {address} property of the endpoint component (WSDL
+ 2.0) or the address value provided by the relevant port extension (WSDL 1.1).
+ For example, in a SOAP 1.1 port described using WSDL 1.1, the location attribute
+ of a soap11:address element (if present) must have the same value as the
+ wsa:Address child element of the wsa:EndpointReference element.</p>
+ <div3>
+ <head>WSDL 2.0 Component Model Changes</head>
+ <p>Use of WS-Addressing adds the following OPTIONAL properties to the WSDL 2.0
+ component model:</p>
+ <ulist>
+ <item>
+ <p> A property of the Endpoint component, named {endpoint reference}.
+ This property is of type wsa:EndpointReference, with a cardinality
+ of 1. The property has the value of the wsa:EndpointReference
+ element used as a child of wsdl20:endpoint, if any. If no such
+ extension exists, this property is absent.</p>
+ </item>
+ </ulist>
+ </div3>
+ </div2>
<div2 id="destinwsdl">
<head>Destination</head>
! <p>The value of the [destination] message addressing property for a message sent to
! an endpoint typically matches the value of the {address} property of the
! endpoint component (WSDL 2.0) or the address value (if any) provided by the
! relevant port extension (WSDL 1.1). For a SOAP 1.1 port described using WSDL
! 1.1, the value is provided by the location attribute of the soap11:address
! extension element. For an endpoint or port extended with an EPR (see <specref
! ref="eprinendpoint"/>), the value is provided by the [address] property of
! the EPR.</p>
! <p>Additional runtime information could override the value of the [destination]
! message addressing property for messages sent to an endpoint, e.g. a runtime
! exchange might result in a redirection to a different EPR. Note that
! WS-Addressing does not define any normative mechanism for such redirection.</p>
! </div2>
! <div2 id="refpinwsdl">
! <head>Reference Parameters</head>
! <p>When a wsa:EndpointReference element is present in a wsdl20:endpoint or a
! wsdl11:port element (see <specref ref="eprinendpoint"/>), the value of the
! [reference parameters] message addressing property for a message sent to an
! endpoint MUST include the contents of the wsa:ReferenceParameters element, if
! one exists within that EPR.</p>
</div2>
<div2 id="actioninwsdl">
***************
*** 656,661 ****
</example>
<p>The action for the input of the opCheckAvailability operation within the
! SreservationInterface is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability.
! The action for the output of this same operation is
http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
<example>
--- 663,669 ----
</example>
<p>The action for the input of the opCheckAvailability operation within the
! SreservationInterface is explicitly defined to be
! http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability. The action
! for the output of this same operation is
http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
<example>
***************
*** 677,682 ****
</example>
<p>The action for the input of the opCheckAvailability operation within the
! reservationInterface port type is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability.
! The action for the output of this same operation is
http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
</div3>
--- 685,691 ----
</example>
<p>The action for the input of the opCheckAvailability operation within the
! reservationInterface port type is explicitly defined to be
! http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability. The action
! for the output of this same operation is
http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
</div3>
***************
*** 815,824 ****
<ulist>
<item>
! <p>A property of the Interface Message
! Reference and Interface Fault components named {action}. The
! property is of type xs:anyURI. The
! property value is the value of the wsaw:Action attribute information item, if present;
! otherwise the default value computed following the rules from
! section <specref ref="defactionwsdl20"/>.</p>
</item>
</ulist>
--- 824,832 ----
<ulist>
<item>
! <p>A property of the Interface Message Reference and Interface Fault
! components named {action}. The property is of type xs:anyURI. The
! property value is the value of the wsaw:Action attribute information
! item, if present; otherwise the default value computed following the
! rules from section <specref ref="defactionwsdl20"/>.</p>
</item>
</ulist>
***************
*** 827,832 ****
<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 wsaw: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>
<example>
--- 835,840 ----
<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 wsaw: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>
<example>
***************
*** 915,920 ****
<p> [fault name] = InvalidDate</p>
<p>Applying the pattern above with these values we have:</p>
! <p>input action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/CheckAvailability</p>
! <p>output action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/Availability</p>
<p>fault action =
http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailability/Fault/InvalidDate</p>
--- 923,930 ----
<p> [fault name] = InvalidDate</p>
<p>Applying the pattern above with these values we have:</p>
! <p>input action =
! http://greath.example.com/2004/wsdl/resSvc/reservationInterface/CheckAvailability</p>
! <p>output action =
! http://greath.example.com/2004/wsdl/resSvc/reservationInterface/Availability</p>
<p>fault action =
http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailability/Fault/InvalidDate</p>
***************
*** 956,983 ****
</div3>
</div2>
- <div2 id="refpinwsdl">
- <head>Reference Parameters</head>
- <p>The wsa:ReferenceParameters element (see &wsa-core.title;[<bibref
- ref="WSADDR-CORE"/>]) MAY be used as an extension child element of the
- wsdl20:endpoint or wsdl11:port elements. When present, the value of the
- [reference parameters] message addressing property for a message sent to an
- endpoint MUST include the contents of the wsa:ReferenceParameters WSDL extension
- element.</p>
- <div3 id="refpinwsdlcm">
- <head>WSDL 2.0 Component Model Changes</head>
- <p>Use of WS-Addressing adds the following OPTIONAL properties to the WSDL 2.0
- component model:</p>
- <ulist>
- <item>
- <p>A property of the Endpoint component, named {reference parameters}.
- This property is of type xs:any, with a cardinality of 0 to
- unbounded. The property has the value of the [reference parameters]
- message addressing property, if present; there is no default value -
- if the [reference parameters] message addressing property is not
- present, this property is likewise absent.</p>
- </item>
- </ulist>
- </div3>
- </div2>
</div1>
<div1 id="WSDLMEPS">
--- 966,969 ----
***************
*** 988,993 ****
<head>WSDL 1.1 Message Exchange Patterns</head>
<p> For backwards compatibility, this section describes which of the core message
! properties are mandatory for messages in the various MEPs defined by
! WSDL 1.1. </p>
<div3 id="wsdl11oneway">
<head>One-way</head>
--- 974,978 ----
<head>WSDL 1.1 Message Exchange Patterns</head>
<p> For backwards compatibility, this section describes which of the core message
! properties are mandatory for messages in the various MEPs defined by WSDL 1.1. </p>
<div3 id="wsdl11oneway">
<head>One-way</head>
***************
*** 1175,1180 ****
<div2 id="WSDL20MEPS">
<head>WSDL 2.0 Message Exchange Patterns</head>
! <p> This section describes which of the core message properties are mandatory
! for messages in the various MEPs defined by WSDL 2.0 [<bibref ref="WSDL20Adj"/>]. </p>
<div3 id="wsdl20inonly">
<head>In-only</head>
--- 1160,1165 ----
<div2 id="WSDL20MEPS">
<head>WSDL 2.0 Message Exchange Patterns</head>
! <p> This section describes which of the core message properties are mandatory for
! messages in the various MEPs defined by WSDL 2.0 [<bibref ref="WSDL20Adj"/>]. </p>
<div3 id="wsdl20inonly">
<head>In-only</head>
***************
*** 1509,1513 ****
constraints defined in sections <specref ref="mapvaluesinwsdl"/> and <specref
ref="WSDLMEPS"/>. </p>
! </div1>
<div1 id="references">
<head> References</head>
--- 1494,1498 ----
constraints defined in sections <specref ref="mapvaluesinwsdl"/> and <specref
ref="WSDLMEPS"/>. </p>
! </div1>
<div1 id="references">
<head> References</head>
***************
*** 1515,1523 ****
<bibl key="WS-Addressing-Core" id="WSADDR-CORE"
href="&w3c-designation-wsa-core;">
! <titleref>&wsa-core.title;</titleref>, M. Gudgin, M. Hadley, T. Rogers, Editors.</bibl>
<bibl key="WS-Addressing-SOAP" id="WSADDR-SOAP"
href="&w3c-designation-wsa-soap;">
! <titleref>&wsa-soap.title;</titleref>, M. Gudgin, M. Hadley, T. Rogers, Editors.</bibl>
! <bibl key="WSDL 2.0" id="WSDL20" href="http://www.w3.org/TR/2006/CR-wsdl20-20060106/">
<titleref>Web Services Description Language (WSDL) Version 2.0 Part 1: Core
Language</titleref>, R. Chinnici, J. J. Moreau, A. Ryman, S. Weerawarana,
--- 1500,1511 ----
<bibl key="WS-Addressing-Core" id="WSADDR-CORE"
href="&w3c-designation-wsa-core;">
! <titleref>&wsa-core.title;</titleref>, M. Gudgin, M. Hadley, T. Rogers,
! Editors.</bibl>
<bibl key="WS-Addressing-SOAP" id="WSADDR-SOAP"
href="&w3c-designation-wsa-soap;">
! <titleref>&wsa-soap.title;</titleref>, M. Gudgin, M. Hadley, T. Rogers,
! Editors.</bibl>
! <bibl key="WSDL 2.0" id="WSDL20"
! href="http://www.w3.org/TR/2006/CR-wsdl20-20060106/">
<titleref>Web Services Description Language (WSDL) Version 2.0 Part 1: Core
Language</titleref>, R. Chinnici, J. J. Moreau, A. Ryman, S. Weerawarana,
***************
*** 1526,1536 ****
href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</loc> is
available at http://www.w3.org/TR/wsdl20.</bibl>
! <bibl key="WSDL 2.0 Adjuncts" id="WSDL20Adj" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/">
! <titleref>Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts</titleref>,
! R. Chinnici, H. Haas, A. Lewis, J. J. Moreau, D. Orchard, S. Weerawarana,
! Editors. World Wide Web Consortium, 6 January 2006. This version of the WSDL 2.0
! Adjuncts specification is http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/. The <loc
! href="http://www.w3.org/TR/wsdl20-adjuncts">latest version of WSDL 2.0 Adjuncts</loc> is
! available at http://www.w3.org/TR/wsdl20-adjuncts.</bibl>
<bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
<titleref>Key words for use in RFCs to Indicate Requirement Levels</titleref>,
--- 1514,1526 ----
href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</loc> is
available at http://www.w3.org/TR/wsdl20.</bibl>
! <bibl key="WSDL 2.0 Adjuncts" id="WSDL20Adj"
! href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/">
! <titleref>Web Services Description Language (WSDL) Version 2.0 Part 2:
! Adjuncts</titleref>, R. Chinnici, H. Haas, A. Lewis, J. J. Moreau, D. Orchard,
! S. Weerawarana, Editors. World Wide Web Consortium, 6 January 2006. This version
! of the WSDL 2.0 Adjuncts specification is
! http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/. The <loc
! href="http://www.w3.org/TR/wsdl20-adjuncts">latest version of WSDL 2.0
! Adjuncts</loc> is available at http://www.w3.org/TR/wsdl20-adjuncts.</bibl>
<bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
<titleref>Key words for use in RFCs to Indicate Requirement Levels</titleref>,
Received on Friday, 28 April 2006 15:04:37 UTC