- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 12 Jul 2005 18:48:44 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv26243
Modified Files:
ws-addr-core.html
Log Message:
Updated to match latest XML
Index: ws-addr-core.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -C2 -d -r1.32 -r1.33
*** ws-addr-core.html 11 Jul 2005 20:08:59 -0000 1.32
--- ws-addr-core.html 12 Jul 2005 18:48:42 -0000 1.33
***************
*** 71,75 ****
<hr><div class="toc">
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange">Introduction</a><br> 1.1 <a href="#notation">Notational Conventions</a><br> 1.2 <a href="#namespaces">Namespaces</a><br>2. <a href="#eprs">Endpoint References</a><br> 2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br> 2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br> 2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br> 2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br> 2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br> 3.1 <a href="#abstractmaps">Abstract Property Definitions</a><br> 3.2 <a href="#msgaddrpropsinfoset">XML Infoset Representation of MessageAddressing Properties</a><br> 3.2.1 <a href="#compiri">Comparing IRIs</a><br> 3.3 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br>5. <a href="#references">References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br> B.1 <a href="#N67208">Changes Since Last Call Working Draft</a><br> B.2 <a href="#N67218">Changes Since Second Working Draft</a><br> B.3 <a href="#N67228">Changes Since First Working Draft</a><br> B.4 <a href="#N67238">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
--- 71,75 ----
<hr><div class="toc">
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange">Introduction</a><br> 1.1 <a href="#notation">Notational Conventions</a><br> 1.2 <a href="#namespaces">Namespaces</a><br>2. <a href="#eprs">Endpoint References</a><br> 2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br> 2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br> 2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br> 2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br> 2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br> 3.1 <a href="#abstractmaps">Abstract Property Definitions</a><br> 3.2 <a href="#msgaddrpropsinfoset">XML Infoset Representation of MessageAddressing Properties</a><br> 3.2.1 <a href="#compiri">Comparing IRIs</a><br> 3.3 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br>5. <a href="#references">References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br> B.1 <a href="#N67285">Changes Since Last Call Working Draft</a><br> B.2 <a href="#N67295">Changes Since Second Working Draft</a><br> B.3 <a href="#N67305">Changes Since First Working Draft</a><br> B.4 <a href="#N67315">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
***************
*** 91,96 ****
<p>The following example illustrates the use of these mechanisms in a SOAP 1.2 message
being sent from http://example.com/business/client1 to
! http://example.com/fabrikam/Purchasing (see Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]
! for more information on the use of WS-Addressing in SOAP):</p>
<div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p>
--- 91,95 ----
<p>The following example illustrates the use of these mechanisms in a SOAP 1.2 message
being sent from http://example.com/business/client1 to
! http://example.com/fabrikam/Purchasing (see Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] for more information on the use of WS-Addressing in SOAP):</p>
<div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p>
***************
*** 111,123 ****
(13) </S:Envelope>
</pre></div>
! <p>Lines (02) to (09) represent the header of the SOAP message where the
! mechanisms defined in the specification are used. The body is represented by
! lines (10) to (12).</p>
<p>Lines (03) to (08) contain the message addressing header blocks. Specifically,
line (02) specifies the identifier for this message and lines (04) to (06)
specify the endpoint to which replies to this message should be sent as an
! endpoint reference. Line (07) specifies the address URI of the ultimate
! receiver of this message. Line (08) specifies an action URI identifying
! expected semantics.</p>
</div>
<div class="div2">
--- 110,122 ----
(13) </S:Envelope>
</pre></div>
! <p>Lines (02) to (09) represent the header of the SOAP message where the mechanisms
! defined in the specification are used. The body is represented by lines (10) to
! (12).</p>
<p>Lines (03) to (08) contain the message addressing header blocks. Specifically,
line (02) specifies the identifier for this message and lines (04) to (06)
specify the endpoint to which replies to this message should be sent as an
! endpoint reference. Line (07) specifies the address URI of the ultimate receiver
! of this message. Line (08) specifies an action URI identifying expected
! semantics.</p>
</div>
<div class="div2">
***************
*** 133,156 ****
<p>When describing concrete XML schemas [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>], this specification uses the notational convention of
WS-Security [<cite><a href="#WS-Security">WS-Security</a></cite>]. Specifically, each member of an
! Element Information Item's [children] or [attributes] property is described using an XPath-like
! notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates
! the presence of an element wildcard (<xs:any/>). The use of @{any}
! indicates the presence of an attribute wildcard
! (<xs:anyAttribute/>).
! In addition, where pseudo-schemas are provided for a component, they use
! BNF-style conventions for attributes and
! elements: "?" denotes optionality (i.e. zero or one occurrences), "*" denotes
! zero or more occurrences, "+" one or more occurrences, "[" and "]" are used to
! form groups, and "|" represents choice. Attributes are conventionally assigned
! a value which corresponds to their type, as defined in the normative schema.
! Elements with simple content are conventionally assigned a value which corresponds
! to the type of their content, as defined in the normative schema.</p>
! <p>When defining the cardinality of endpoint reference properties and
! message 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>
</div>
<div class="div2">
--- 132,155 ----
<p>When describing concrete XML schemas [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>], this specification uses the notational convention of
WS-Security [<cite><a href="#WS-Security">WS-Security</a></cite>]. Specifically, each member of an
! Element Information Item's [children] or [attributes] property is described
! using an XPath-like notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use
! of {any} indicates the presence of an element wildcard
! (<xs:any/>). The use of @{any} indicates the presence of an
! attribute wildcard (<xs:anyAttribute/>). In addition, where
! pseudo-schemas are provided for a component, they use BNF-style conventions for
! attributes and elements: "?" denotes optionality (i.e. zero or one occurrences),
! "*" denotes zero or more occurrences, "+" one or more occurrences, "[" and "]"
! are used to form groups, and "|" represents choice. Attributes are
! conventionally assigned a value which corresponds to their type, as defined in
! the normative schema. Elements with simple content are conventionally assigned a
! value which corresponds to the type of their content, as defined in the
! normative schema.</p>
! <p>When defining the cardinality of endpoint reference properties and message
! 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>
</div>
<div class="div2">
***************
*** 159,164 ****
<p> This specification uses a number of namespace prefixes throughout; they are
listed in <a href="#nsprefix">Table 1-1</a>. Note that the choice of any namespace
! prefix is arbitrary and not semantically significant (see
! [<cite><a href="#XMLNS">XML Namespaces</a></cite>]).</p>
<a name="nsprefix"></a><table summary="Namespace prefixes usage in this specification" border="1">
<caption>Table 1-1. Prefixes and Namespaces used in this specification</caption>
--- 158,162 ----
<p> This specification uses a number of namespace prefixes throughout; they are
listed in <a href="#nsprefix">Table 1-1</a>. Note that the choice of any namespace
! prefix is arbitrary and not semantically significant (see [<cite><a href="#XMLNS">XML Namespaces</a></cite>]).</p>
<a name="nsprefix"></a><table summary="Namespace prefixes usage in this specification" border="1">
<caption>Table 1-1. Prefixes and Namespaces used in this specification</caption>
***************
*** 182,195 ****
</tbody>
</table><br>
! <p>WS-Addressing may be used with SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>, <cite><a href="#SOAP11">SOAP 1.1</a></cite>] as described
! in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. WS-Addressing may be used
! with WSDL [<cite><a href="#WSDL20">WSDL 2.0</a></cite>, <cite><a href="#WSDL11">WSDL 1.1</a></cite>] described services as described in
Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>]. Examples in this
specification use an XML 1.0 [<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is
not a requirement.</p>
<p>All information items defined by this specification are identified by the XML
! namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] <a href="http://www.w3.org/@@@@/@@/addressing">http://www.w3.org/@@@@/@@/addressing</a>. A normative XML Schema
! [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document can be
! obtained by dereferencing the XML namespace URI.</p>
</div>
</div>
--- 180,191 ----
</tbody>
</table><br>
! <p>WS-Addressing may be used with SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>, <cite><a href="#SOAP11">SOAP 1.1</a></cite>] as described in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. WS-Addressing may be used with WSDL [<cite><a href="#WSDL20">WSDL 2.0</a></cite>, <cite><a href="#WSDL11">WSDL 1.1</a></cite>] described services as described in
Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>]. Examples in this
specification use an XML 1.0 [<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is
not a requirement.</p>
<p>All information items defined by this specification are identified by the XML
! namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] <a href="http://www.w3.org/@@@@/@@/addressing">http://www.w3.org/@@@@/@@/addressing</a>. A normative XML Schema [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>,
! <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document can be obtained by dereferencing the
! XML namespace URI.</p>
</div>
</div>
***************
*** 227,231 ****
<dt class="label"> [address] : IRI (1..1)</dt>
<dd>
! <p>An absolute IRI representing the address of the endpoint.</p>
</dd>
--- 223,266 ----
<dt class="label"> [address] : IRI (1..1)</dt>
<dd>
! <p>An absolute IRI representing the address of the endpoint. This
! specification introduces two predefined [address] values as shown in
! <a href="#predefaddr">Table 2-1</a>.</p>
! <a name="predefaddr"></a><table border="1" summary="Predefined [address] values">
! <caption>Table 2-1. Predefined [address] values</caption>
! <tbody>
! <tr>
! <th align="left" rowspan="1" colspan="1">URI</th>
! <th align="left" rowspan="1" colspan="1">Description </th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! "http://www.w3.org/@@@@/@@/addressing/anonymous"
! </td>
! <td rowspan="1" colspan="1">Due to the range of network technologies currently in
! wide-spread use (e.g., NAT, DHCP, firewalls), many
! deployments cannot assign a meaningful global IRI to a
! given endpoint. This URI is used to allow such endpoints
! to send and receive messages. Messages sent to EPRs
! whose [address] is this value MUST rely on some out-of-band
! mechanism for delivery (e.g.
! using a pre-existing transport
! connection) from a prior interaction.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! "http://www.w3.org/@@@@/@@/addressing/none"
! </td>
! <td rowspan="1" colspan="1">Messages sent to EPRs whose [address] is this
! value
! MUST be discarded (i.e. not sent). This URI
! is
! typically used in EPRs that designate a reply or fault
! endpoint (see section <a href="#abstractmaps"><b>3.1 Abstract Property Definitions</b></a>) to
! indicate
! that no reply or fault message should be
! sent.</td>
! </tr>
! </tbody>
! </table><br>
</dd>
***************
*** 233,245 ****
<dt class="label"> [reference parameters] : xs:any (0..unbounded).</dt>
<dd>
! <p>A reference may contain a number of individual parameters which are
associated with the endpoint to facilitate a particular interaction.
Reference parameters are namespace-qualified element information
items that are required to properly interact with the endpoint.
Reference parameters are provided by the issuer of the endpoint
! reference and are assumed to be opaque to other users of an
! endpoint refernce.
! The binding of reference parameters to messages depends upon the
! protocol binding used to interact with the endpoint -
Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] describes the
default binding for the SOAP protocol. </p>
--- 268,279 ----
<dt class="label"> [reference parameters] : xs:any (0..unbounded).</dt>
<dd>
! <p>A reference may contain a number of individual parameters that are
associated with the endpoint to facilitate a particular interaction.
Reference parameters are namespace-qualified element information
items that are required to properly interact with the endpoint.
Reference parameters are provided by the issuer of the endpoint
! reference and are assumed to be opaque to other users of an endpoint
! refernce. The binding of reference parameters to messages depends
! upon the protocol binding used to interact with the endpoint -
Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] describes the
default binding for the SOAP protocol. </p>
***************
*** 251,269 ****
<p>A reference may contain metadata that describes the behavior,
policies and capabilities of the endpoint. Metadata may be included
! in an endpoint reference to facilitate easier processing by
! a user of an endpoint reference, or because the metadata was dynamically
generated.</p>
<p>The metadata embedded in an EPR is not necessarily a complete
! statement of the metadata pertaining to the endpoint. Moreover, while
! embedded metadata is necessarily valid at the time the EPR is
initially created it may become stale at a later point in time.</p>
! <p>To deal with conflicts between the embedded metadata of two EPRs
! that have the same [address], or
! between embedded metadata and metadata obtained from a different
! source, or to ascertain the current validity of embedded metadata,
! mechanisms that are outside of the scope of this specification, such
! as EPR life cycle information (see <a href="#eprlifecycle"><b>2.4 Endpoint Reference Lifecycle</b></a>) or
! retrieval of metadata from an authoritative source, SHOULD be
! used.</p>
</dd>
--- 285,302 ----
<p>A reference may contain metadata that describes the behavior,
policies and capabilities of the endpoint. Metadata may be included
! in an endpoint reference to facilitate easier processing by a user
! of an endpoint reference, or because the metadata was dynamically
generated.</p>
<p>The metadata embedded in an EPR is not necessarily a complete
! statement of the metadata pertaining to the endpoint. Moreover,
! while embedded metadata is necessarily valid at the time the EPR is
initially created it may become stale at a later point in time.</p>
! <p>To deal with conflicts between the embedded metadata of two EPRs that
! have the same [address], or between embedded metadata and metadata
! obtained from a different source, or to ascertain the current
! validity of embedded metadata, mechanisms that are outside of the
! scope of this specification, such as EPR life cycle information (see
! <a href="#eprlifecycle"><b>2.4 Endpoint Reference Lifecycle</b></a>) or retrieval of metadata from an
! authoritative source, SHOULD be used.</p>
</dd>
***************
*** 275,280 ****
<p>This section defines an XML Infoset-based representation for an endpoint
reference as both an XML type (wsa:EndpointReferenceType) and as an XML element
! (<wsa:EndpointReference>). For brevity simple XML terms are used, e.g.
! 'element' instead of 'element information item' - this is not intended to
constrain use of the constructs defined in this section to textual XML
representations.</p>
--- 308,313 ----
<p>This section defines an XML Infoset-based representation for an endpoint
reference as both an XML type (wsa:EndpointReferenceType) and as an XML element
! (<wsa:EndpointReference>). For brevity simple XML terms are used,
! e.g. 'element' instead of 'element information item' - this is not intended to
constrain use of the constructs defined in this section to textual XML
representations.</p>
***************
*** 301,306 ****
<dt class="label"> /wsa:EndpointReference/wsa:Address</dt>
<dd>
! <p>This REQUIRED element (whose content is of type xs:anyURI) specifies the [address]
! property of the endpoint reference.</p>
</dd>
--- 334,339 ----
<dt class="label"> /wsa:EndpointReference/wsa:Address</dt>
<dd>
! <p>This REQUIRED element (whose content is of type xs:anyURI) specifies
! the [address] property of the endpoint reference.</p>
</dd>
***************
*** 316,321 ****
<dd>
<p>This OPTIONAL element may contain elements from any namespace. Such
! elements form the
! [reference parameters] of the reference.</p>
</dd>
--- 349,353 ----
<dd>
<p>This OPTIONAL element may contain elements from any namespace. Such
! elements form the [reference parameters] of the reference.</p>
</dd>
***************
*** 331,336 ****
<dd>
<p>Each element information item found in [reference parameters]
! (including all of that elements [children], [attributes] and [in-scope
! namespaces]) is represented as is.</p>
</dd>
--- 363,368 ----
<dd>
<p>Each element information item found in [reference parameters]
! (including all of that elements [children], [attributes] and
! [in-scope namespaces]) is represented as is.</p>
</dd>
***************
*** 339,344 ****
<dd>
<p>This OPTIONAL element may contain elements from any namespace. Such
! elements form the metadata that is relevant to the
! interaction with the endpoint.</p>
</dd>
--- 371,376 ----
<dd>
<p>This OPTIONAL element may contain elements from any namespace. Such
! elements form the metadata that is relevant to the interaction with
! the endpoint.</p>
</dd>
***************
*** 432,439 ****
<div class="note"><p class="prefix"><b>Note:</b></p>
<p> The Working Group requests feedback regarding the mechanism for and description
! of Message Addressing Property extensibility beyond the MEPs currently
! described in the WSDL specifications, along with use cases that illustrate how
! referencing specifications and other users of Addressing intend to extend them.
! Although the Working Group has resolved upon a <a href="http://www.w3.org/2002/ws/addr/wd-issues/#i054">particular
design</a>, some participants believe it is not adequately specified. Such
feedback will help the Working Group determine whether it needs to re-examine
--- 464,471 ----
<div class="note"><p class="prefix"><b>Note:</b></p>
<p> The Working Group requests feedback regarding the mechanism for and description
! of Message Addressing Property extensibility beyond the MEPs currently described
! in the WSDL specifications, along with use cases that illustrate how referencing
! specifications and other users of Addressing intend to extend them. Although the
! Working Group has resolved upon a <a href="http://www.w3.org/2002/ws/addr/wd-issues/#i054">particular
design</a>, some participants believe it is not adequately specified. Such
feedback will help the Working Group determine whether it needs to re-examine
***************
*** 447,578 ****
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
! consists of an initial message sent by a source endpoint (the request) and a
subsequent message sent from the destination of the request back to the source (the
! response). A response in this case can be either an application message, a fault, or any
! 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>
<p> The set of message addressing properties defined in this specification is sufficient
! for many simple variations of one-way and request-response MEPs. More advanced MEPs may
! require additional message addressing properties to augment the facilities provided
! here. </p>
!
<div class="div2">
<h3><a name="abstractmaps"></a>3.1 Abstract Property Definitions</h3>
!
! <p>Message addressing properties collectively augment a message with the following
! abstract properties to support one-way, request-response, and other interaction
! patterns:</p>
! <dl>
!
! <dt class="label"> [destination] : IRI (1..1)</dt>
! <dd>
! <p>An absolute IRI representing the address of the intended receiver of this
! message.</p>
! </dd>
!
!
! <dt class="label"> [source endpoint] : endpoint reference (0..1)</dt>
! <dd>
! <p>Reference to the endpoint from which the message originated.</p>
! </dd>
!
!
! <dt class="label"> [reply endpoint] : endpoint reference (0..1)</dt>
! <dd>
! <p>An endpoint reference for the intended receiver for replies to this
! message.</p>
! </dd>
!
!
! <dt class="label"> [fault endpoint] : endpoint reference (0..1)</dt>
! <dd>
! <p>An endpoint reference for the intended receiver for faults related to
! this message.</p>
! </dd>
!
!
! <dt class="label"> [action] : IRI (1..1)</dt>
! <dd>
! <p>An absolute IRI that uniquely identifies the semantics implied by this
! 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. Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>] describes the mechanisms of association.</p>
! </dd>
!
!
! <dt class="label"> [message id] : IRI (0..1)</dt>
! <dd>
! <p>An absolute IRI that uniquely identifies the message.
! When present, it is the responsibility of the sender to ensure
! that each message is uniquely identified. The behavior of a
! receiver when receiving a message that contains the same
! [message id] as a previously received message is
! unconstrained by this specification.</p>
! </dd>
!
!
! <dt class="label"> [relationship] : (IRI, IRI) (0..unbounded)</dt>
! <dd>
! <p>A pair of values that indicate how this message relates to another
! message. The type of the relationship is identified by an absolute IRI.
! The related message is identified by an absolute IRI that corresponds to
! the related message's [message id] property. The message identifier IRI
! may refer to a specific message, or be the following pre-defined URI that
! means "unspecified message": "http://www.w3.org/@@@@/@@/addressing/unspecified"
! </p>
! <p>This specification has one predefined relationship type as shown in
! <a href="#predefrels">Table 3-1</a>.</p>
! <a name="predefrels"></a><table border="1" summary="Predefined [relationship] type values">
! <caption>Table 3-1. Predefined [relationship] values</caption>
! <tbody>
! <tr>
! <th align="left" rowspan="1" colspan="1">URI</th>
! <th align="left" rowspan="1" colspan="1">Description </th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! "http://www.w3.org/@@@@/@@/addressing/reply"
! </td>
! <td rowspan="1" colspan="1">Indicates that this is a reply to the message identified by
! the [message id] IRI.</td>
! </tr>
! </tbody>
! </table><br>
! </dd>
!
!
! <dt class="label"> [reference parameters] : xs:any (0..unbounded).</dt>
! <dd>
! <p>Corresponds to the value of the [reference parameters] property of the
! endpoint reference to which the message is addressed.</p>
! </dd>
!
! </dl>
! <p>The [destination] and [action] properties indicate the target processing
! location and the verb or intent of the message respectively. The values of these
! properties can be used to facilitate the dispatch of messages.</p>
! <p>Due to the range of network technologies currently in wide-spread use (e.g., NAT,
! DHCP, firewalls), many deployments cannot assign a meaningful global IRI to a given
! endpoint. To allow these "anonymous" endpoints to send and receive messages,
! WS-Addressing defines the following pre-defined URI for use by endpoints that cannot
! have a stable, resolvable IRI: "http://www.w3.org/@@@@/@@/addressing/anonymous". Messages
! whose [reply endpoint], [source endpoint] and/or [fault endpoint] use this
! address MUST rely on some out-of-band mechanism for delivering replies or faults
! (e.g. returning the reply on the same transport connection).</p>
<p>A binding of WS_Addressing message addressing properties MUST reflect the
! property cardinality shown above. Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]
! defines such a binding for the SOAP
! [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>, <cite><a href="#SOAP11">SOAP 1.1</a></cite>] protocol.</p>
</div>
-
<div class="div2">
--- 479,599 ----
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 consists of an initial message sent by a source endpoint (the request) and a
subsequent message sent from the destination of the request back to the source (the
! response). A response in this case can be either an application message, a fault, or
! any 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>
<p> The set of message addressing properties defined in this specification is sufficient
! for many simple variations of one-way and request-response MEPs. More advanced MEPs
! may require additional message addressing properties to augment the facilities
! provided here. </p>
<div class="div2">
<h3><a name="abstractmaps"></a>3.1 Abstract Property Definitions</h3>
! <p>Message addressing properties collectively augment a message with the following
! abstract properties to support one-way, request-response, and other interaction
! patterns:</p>
! <dl>
!
! <dt class="label"> [destination] : IRI (1..1)</dt>
! <dd>
! <p>An absolute IRI representing the address of the intended receiver of
! this message.</p>
! </dd>
!
!
! <dt class="label"> [source endpoint] : endpoint reference (0..1)</dt>
! <dd>
! <p>Reference to the endpoint from which the message originated.</p>
! </dd>
!
!
! <dt class="label"> [reply endpoint] : endpoint reference (0..1)</dt>
! <dd>
! <p>An endpoint reference for the intended receiver for replies to this
! message.</p>
! </dd>
!
!
! <dt class="label"> [fault endpoint] : endpoint reference (0..1)</dt>
! <dd>
! <p>An endpoint reference for the intended receiver for faults related to
! this message.</p>
! </dd>
!
!
! <dt class="label"> [action] : IRI (1..1)</dt>
! <dd>
! <p>An absolute IRI that uniquely identifies the semantics implied by
! this 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.
! Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>] describes the
! mechanisms of association.</p>
! </dd>
!
!
! <dt class="label"> [message id] : IRI (0..1)</dt>
! <dd>
! <p>An absolute IRI that uniquely identifies the message. When present,
! it is the responsibility of the sender to ensure that each message
! is uniquely identified. The behavior of a receiver when receiving a
! message that contains the same [message id] as a previously received
! message is unconstrained by this specification.</p>
! </dd>
!
!
! <dt class="label"> [relationship] : (IRI, IRI) (0..unbounded)</dt>
! <dd>
! <p>A pair of values that indicate how this message relates to another
! message. The type of the relationship is identified by an absolute
! IRI. The related message is identified by an absolute IRI that
! corresponds to the related message's [message id] property. The
! message identifier IRI may refer to a specific message, or be the
! following pre-defined URI that means "unspecified message":
! "http://www.w3.org/@@@@/@@/addressing/unspecified"
! </p>
! <p>This specification has one predefined relationship type as shown in
! <a href="#predefrels">Table 3-1</a>.</p>
! <a name="predefrels"></a><table border="1" summary="Predefined [relationship] type values">
! <caption>Table 3-1. Predefined [relationship] values</caption>
! <tbody>
! <tr>
! <th align="left" rowspan="1" colspan="1">URI</th>
! <th align="left" rowspan="1" colspan="1">Description </th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! "http://www.w3.org/@@@@/@@/addressing/reply"
! </td>
! <td rowspan="1" colspan="1">Indicates that this is a reply to the message identified
! by the [message id] IRI.</td>
! </tr>
! </tbody>
! </table><br>
! </dd>
!
!
! <dt class="label"> [reference parameters] : xs:any (0..unbounded).</dt>
! <dd>
! <p>Corresponds to the value of the [reference parameters] property of
! the endpoint reference to which the message is addressed.</p>
! </dd>
!
! </dl>
! <p>The [destination] and [action] properties indicate the target processing location
! and the verb or intent of the message respectively. The values of these
! properties can be used to facilitate the dispatch of messages.</p>
<p>A binding of WS_Addressing message addressing properties MUST reflect the
! property cardinality shown above. Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] defines such a binding for the SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>, <cite><a href="#SOAP11">SOAP 1.1</a></cite>] protocol.</p>
</div>
<div class="div2">
***************
*** 596,603 ****
<dt class="label"> /wsa:To</dt>
<dd>
! <p>This OPTIONAL element (whose content is of type xs:anyURI) provides the value for the
! [destination] property. If this element is NOT present then the
! value of the [destination] property is
! "http://www.w3.org/@@@@/@@/addressing/anonymous".</p>
</dd>
--- 617,624 ----
<dt class="label"> /wsa:To</dt>
<dd>
! <p>This OPTIONAL element (whose content is of type xs:anyURI) provides
! the value for the [destination] property. If this element is NOT
! present then the value of the [destination] property is
! "http://www.w3.org/@@@@/@@/addressing/anonymous".</p>
</dd>
***************
*** 613,617 ****
<dd>
<p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides
! the value for the [reply endpoint] property.</p>
</dd>
--- 634,640 ----
<dd>
<p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides
! the value for the [reply endpoint] property. If this element is NOT
! present then the value of the [address] property of the [reply
! endpoint] EPR is "http://www.w3.org/@@@@/@@/addressing/anonymous".</p>
</dd>
***************
*** 626,631 ****
<dt class="label"> /wsa:Action</dt>
<dd>
! <p>This REQUIRED element (whose content is of type xs:anyURI) conveys the value of the
! [action] property.</p>
</dd>
--- 649,654 ----
<dt class="label"> /wsa:Action</dt>
<dd>
! <p>This REQUIRED element (whose content is of type xs:anyURI) conveys
! the value of the [action] property.</p>
</dd>
***************
*** 633,638 ****
<dt class="label"> /wsa:MessageID</dt>
<dd>
! <p>This OPTIONAL element (whose content is of type xs:anyURI) conveys the [message id]
! property.</p>
</dd>
--- 656,661 ----
<dt class="label"> /wsa:MessageID</dt>
<dd>
! <p>This OPTIONAL element (whose content is of type xs:anyURI) conveys
! the [message id] property.</p>
</dd>
***************
*** 642,647 ****
<p>This OPTIONAL (repeating) element information item contributes one
abstract [relationship] property value, in the form of an (IRI, IRI)
! pair. The content of this element (of type
! xs:anyURI) conveys the [message id] of the related message.</p>
</dd>
--- 665,670 ----
<p>This OPTIONAL (repeating) element information item contributes one
abstract [relationship] property value, in the form of an (IRI, IRI)
! pair. The content of this element (of type xs:anyURI) conveys the
! [message id] of the related message.</p>
</dd>
***************
*** 654,663 ****
</dd>
!
<dt class="label"> /[reference parameters]*</dt>
<dd>
<p>Each element information item found in [reference parameters]
! (including all of that elements [children], [attributes] and [in-scope
! namespaces]) is represented as is.</p>
</dd>
--- 677,686 ----
</dd>
!
<dt class="label"> /[reference parameters]*</dt>
<dd>
<p>Each element information item found in [reference parameters]
! (including all of that elements [children], [attributes] and
! [in-scope namespaces]) is represented as is.</p>
</dd>
***************
*** 689,695 ****
<ul>
<li>
! <p>If the reply is a normal message, select the EPR from the
! related message's [reply endpoint] message addressing property.
! If none is present, the processor MUST fault.</p>
</li>
<li>
--- 712,723 ----
<ul>
<li>
! <p>If the reply is a normal message, select the EPR from the related
! message's [reply endpoint] message addressing property. If none
! is present, the processor MUST fault. </p>
! <div class="note"><p class="prefix"><b>Note:</b></p><p>When using the XML Infoset representation, in the absence
! of a wsa:ReplyTo element the value of the
! [reply endpoint] message addressing property defaults to an EPR with
! an [address] property of "http://www.w3.org/@@@@/@@/addressing/anonymous" - see
! section <a href="#msgaddrpropsinfoset"><b>3.2 XML Infoset Representation of Message Addressing Properties</b></a>.</p></div>
</li>
<li>
***************
*** 703,720 ****
unconstrained by this specification.</p>
</li>
! <li><p>In either of the above cases, if the related message lacks a [message id] property,
! the processor MUST fault.</p></li>
</ul>
</li>
<li>
! <p>Populate the reply message's message addressing properties:</p>
<ul>
<li>
<p>[destination]: this property takes the value of the selected
! EPR's [address] property</p>
</li>
<li>
! <p>[relationship]: this property MUST include a
! pair of IRIs as
follows; the relationship type is the predefined reply URI
"http://www.w3.org/@@@@/@@/addressing/reply" and the related message's
--- 731,751 ----
unconstrained by this specification.</p>
</li>
! <li>
! <p>In either of the above cases, if the related message lacks a
! [message id] property, the processor MUST fault.</p>
! </li>
</ul>
</li>
<li>
! <p>If the selected EPR's [address] property is
! "http://www.w3.org/@@@@/@@/addressing/none" the reply message is discarded, if not
! then populate the reply message's message addressing properties:</p>
<ul>
<li>
<p>[destination]: this property takes the value of the selected
! EPR's [address] property.</p>
</li>
<li>
! <p>[relationship]: this property MUST include a pair of IRIs as
follows; the relationship type is the predefined reply URI
"http://www.w3.org/@@@@/@@/addressing/reply" and the related message's
***************
*** 816,846 ****
<h2><a name="securityconsiderations"></a>4. Security Considerations</h2>
! <p>Users of WS-Addressing and EPRs (i.e., entities creating and receiving
! Message Addressing Properties and EPRs) SHOULD only use EPRs from sources they
! trust. For example, such users might rely on the presence of a verifiable
! signature by a trusted party over the EPR, or an out-of-band means
! of establishing trust, to determine whether they should use a
! particular EPR.</p>
<p>EPRs and message addressing properties SHOULD be integrity-protected to prevent
! tampering. Such optional integrity protection might be provided by the transport,
! a message level signature, or use of an XML digital signature within EPRs.</p>
<p>To prevent information disclosure, EPR issuers SHOULD NOT put sensitive information
into the [address] or [reference parameters] properties.</p>
<p>Some processors may use message identifiers ([message id]) as part of a uniqueness
! metric in order to detect replays of messages. In this case, care should be taken to ensure that
! for purposes of replay detection, the message identifier is combined with other
! data, such as a timestamp, so that a legitimate retransmission of the message is not
! confused with a replay attack. It is also advisable to use message identifiers that are not
! predictable, to prevent attackers from constructing and sending
! an unsolicited reply to a message without having to
! see the actual message.</p>
! <p>When [reply endpoint] and/or [fault endpoint] do not contain the
! anonymous URI, the processor of such an EPR should take care to avoid
! a denial of service attack caused by opening an excessive number
! network connections, which are typically a scarce resource.</p>
! <p>Care should be taken to avoid participating in a denial of service
! attack in which an attacker sends messages to many receivers
! and includes a [reply endpoint] or [fault endpoint] for the target
! of the attack.</p>
</div>
<div class="div1">
--- 847,874 ----
<h2><a name="securityconsiderations"></a>4. Security Considerations</h2>
! <p>Users of WS-Addressing and EPRs (i.e., entities creating and receiving Message
! Addressing Properties and EPRs) SHOULD only use EPRs from sources they trust. For
! example, such users might rely on the presence of a verifiable signature by a
! trusted party over the EPR, or an out-of-band means of establishing trust, to
! determine whether they should use a particular EPR.</p>
<p>EPRs and message addressing properties SHOULD be integrity-protected to prevent
! tampering. Such optional integrity protection might be provided by the transport, a
! message level signature, or use of an XML digital signature within EPRs.</p>
<p>To prevent information disclosure, EPR issuers SHOULD NOT put sensitive information
into the [address] or [reference parameters] properties.</p>
<p>Some processors may use message identifiers ([message id]) as part of a uniqueness
! metric in order to detect replays of messages. In this case, care should be taken to
! ensure that for purposes of replay detection, the message identifier is combined
! with other data, such as a timestamp, so that a legitimate retransmission of the
! message is not confused with a replay attack. It is also advisable to use message
! identifiers that are not predictable, to prevent attackers from constructing and
! sending an unsolicited reply to a message without having to see the actual message.</p>
! <p>When [reply endpoint] and/or [fault endpoint] do not contain the anonymous URI, the
! processor of such an EPR should take care to avoid a denial of service attack caused
! by opening an excessive number network connections, which are typically a scarce
! resource.</p>
! <p>Care should be taken to avoid participating in a denial of service attack in which an
! attacker sends messages to many receivers and includes a [reply endpoint] or [fault
! endpoint] for the target of the attack.</p>
</div>
<div class="div1">
***************
*** 864,869 ****
http://www.ietf.org/rfc/rfc2119.txt. </dd>
<dt class="label"><a name="RFC3987"></a>[IETF RFC 3987] </dt><dd>
! <cite><a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a></cite>
! M. Duerst, M. Suignard, January 2005. Available at http://www.ietf.org/rfc/rfc3987.txt.</dd>
<dt class="label"><a name="XML10"></a>[XML 1.0] </dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third Edition)</a></cite>, T.
--- 892,897 ----
http://www.ietf.org/rfc/rfc2119.txt. </dd>
<dt class="label"><a name="RFC3987"></a>[IETF RFC 3987] </dt><dd>
! <cite><a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a></cite> M. Duerst, M.
! Suignard, January 2005. Available at http://www.ietf.org/rfc/rfc3987.txt.</dd>
<dt class="label"><a name="XML10"></a>[XML 1.0] </dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third Edition)</a></cite>, T.
***************
*** 903,911 ****
1.2 Part 1: Messaging Framework"</a> is available at
http://www.w3.org/TR/soap12-part1/. </dd>
! <dt class="label"><a name="SOAP11"></a>[SOAP 1.1] </dt><dd>Don Box,
! et al, <cite><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Simple Object Access Protocol (SOAP)
! 1.1</a></cite>, May 2000.</dd>
<dt class="label"><a name="WSDL11"></a>[WSDL 1.1] </dt><dd>E. Christensen, et al, <cite><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">Web Services Description Language (WSDL)
! 1.1</a></cite>, March 2001.</dd>
<dt class="label"><a name="WS-Security"></a>[WS-Security] </dt><dd> OASIS, <cite><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">Web Services Security: SOAP Message Security</a></cite>,
March 2004.</dd>
--- 931,938 ----
1.2 Part 1: Messaging Framework"</a> is available at
http://www.w3.org/TR/soap12-part1/. </dd>
! <dt class="label"><a name="SOAP11"></a>[SOAP 1.1] </dt><dd>Don Box, et al,
! <cite><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Simple Object Access Protocol (SOAP) 1.1</a></cite>, May 2000.</dd>
<dt class="label"><a name="WSDL11"></a>[WSDL 1.1] </dt><dd>E. Christensen, et al, <cite><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">Web Services Description Language (WSDL)
! 1.1</a></cite>, March 2001.</dd>
<dt class="label"><a name="WS-Security"></a>[WS-Security] </dt><dd> OASIS, <cite><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">Web Services Security: SOAP Message Security</a></cite>,
March 2004.</dd>
***************
*** 931,956 ****
<h2><a name="changelog"></a>B. Change Log (Non-Normative)</h2>
! <div class="div2">
!
! <h3><a name="N67208"></a>B.1 Changes Since Last Call Working Draft</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-07-11 @ 19:58</td><td>mhadley</td><td>Added resolution to issue lc90 - clarified use of message id as uniqueness metric</td></tr><tr><td>2005-06-21 @ 17:46</td><td>mhadley</td><td>Added resolution to issues lc75 and lc88 - updated description of [message id]</td></tr><tr><td>2005-06-20 @ 19:08</td><td>mhadley</td><td>Added resolution to issue lc106 - updated pseudo schemas to match the notational conventions used by WSDL 2.0</td></tr><tr><td>2005-06-03 @ 20:33</td><td>mhadley</td><td>Added resolutions to issues lc58, lc79, lc91, lc102</td></tr><tr><td>2005-06-02 @ 19:48</td><td>mhadley</td><td>Added resolution to issue lc78 - reworked formulating reply message text related to [relationship] to make it clear that the reply relationsship is not added top the relationships specified in the message being replied to</td></tr><tr><td>2005-06-02 @ 19:39</td><td>mhadley</td><td>Added resolution to issue lc84 - removed reundant co-occurrence requirements and concentrated conformance requirements in section 3.3</td></tr><tr><td>2005-06-02 @ 18:47</td><td>mhadley</td><td>Added resolution to issue lc89 - assorted editorial fixes</td></tr><tr><td>2005-06-02 @ 18:15</td><td>mhadley</td><td>Added resolution to issue lc37 - added DOS attack security considerations</td></tr><tr><td>2005-06-02 @ 18:07</td><td>mhadley</td><td>Added explanation of cardinality notation</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-25 @ 20:25</td><td>mhadley</td><td>Added resolution to issue lc39 - changed mandatory to 1..1</td></tr><tr><td>2005-05-25 @ 20:20</td><td>mhadley</td><td>Added resolution to issue lc66 - made it clear that type often refers to the content of elements rather than the element as a whole which can often also include attributes</td></tr><tr><td>2005-05-18 @ 19:49</td><td>mhadley</td><td>Added lc81 resolution - remove mutUnderstand attributes from examples</td></tr><tr><td>2005-05-18 @ 19:35</td><td>mhadley</td><td>Added lc51 resolution - reordered property list to match order in core</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-05-18 @ 18:58</td><td>mhadley</td><td>Added lc97 resolution - Endpoint Reference to endpoint reference</td></tr><tr><td>2005-05-18 @ 18:56</td><td>mhadley</td><td>Added lc95 resolution - added WSDL 1.1 citation to introduction</td></tr><tr><td>2005-05-18 @ 18:51</td><td>mhadley</td><td>Added lc94 resolution - changed element to Element Information Item</td></tr><tr><td>2005-05-18 @ 18:48</td><td>mhadley</td><td>Added lc93 resolution - added ref to soap binding document prior to soap example in introduction</td></tr><tr><td>2005-05-18 @ 18:44</td><td>mhadley</td><td>Added lc92 resolution - clarified document being referenced in introduction</td></tr><tr><td>2005-05-18 @ 18:40</td><td>mhadley</td><td>Addedlc80 resolution - made abstract properties into a separate list</td></tr><tr><td>2005-05-18 @ 18:34</td><td>mhadley</td><td>Added lc74 resolution - added suggested security consideration</td></tr><tr><td>2005-05-18 @ 18:24</td><td>mhadley</td><td>Added lc63 resolution - editorial fixes to security section</td></tr><tr><td>2005-05-18 @ 18:19</td><td>mhadley</td><td>Added lc44 resolution - changed and to or in security section</td></tr><tr><td>2005-05-18 @ 18:17</td><td>mhadley</td><td>Added lc43 resolution - added ref to SOAP 1.1</td></tr><tr><td>2005-05-18 @ 18:12</td><td>mhadley</td><td>Added lc42 resolution - reordered infoset representation to match order of abstract properties</td></tr><tr><td>2005-05-18 @ 18:03</td><td>mhadley</td><td>Added lc67 resolution - made namespace uri a link</td></tr><tr><td>2005-05-18 @ 17:58</td><td>mhadley</td><td>Added lc64 resolution - numerous editorial fixes</td></tr><tr><td>2005-05-16 @ 20:28</td><td>mgudgin</td><td>Fixed mismatched endtag in Section 3.1</td></tr><tr><d>2005-05-16 @ 20:16</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of other biblio entries</td></tr><tr><td>2005-04-22 @ 18:26</td><td>mhadley</td><td>Added resolution to lc22 - clarified ignore rule for extension attributes.</td></tr><tr><td>2005-04-22 @ 18:24</td><td>mhadley</td><td>Added resolution to lc21 - removed HTTP specific restriction on use of anonymous URI in [destination] for replies only.</td></tr><tr><td>2005-04-22 @ 18:18</td><td>mhadley</td><td>Added resolution to lc19 - clarified that [destination] value comparison is out of scope except for using simple string comparison to determine whether the anonymous destination is being used.</td></tr><tr><td>2005-04-22 @ 18:12</td><td>mhadley</td><td>Added resolution to lc18 - simplified description of wsa:To and wsa:Action elements</td></tr><tr><td>2005-04-22 @ 18:04</td><td>mhadley</td><td>Added resolution to lc17 - clarified that anonymous destination URI is not just for use in replies</td></tr><tr><td>2005-04-22 @ 18:01</td<td>mhadley</td><td>Added resolution to lc16 and lc54 - removed suggestion that required was required to use [destination] and [action] properties for dispatch</td></tr><tr><td>2005-04-22 @ 17:55</td><td>mhadley</td><td>Added resolution to lc15 - clarified cardinality of [relationship] properties using predefined reply URI</td></tr><tr><td>2005-04-22 @ 17:50</td><td>mhadley</td><td>Added resolution to lc14 - clarified reply IRI targetting</td></tr><tr><td>2005-04-22 @ 17:41</td><td>mhadley</td><td>Added resolution to lc13 - clarified wording in description of metadata</td></tr><tr><td>2005-04-22 @ 17:38</td><td>mhadley</td><td>Added resolution to lc12 - removed data encoding from description of reference parameters</td></tr><tr><td>2005-04-22 @ 17:30</td><td>mhadley</td><td>Added resolution to lc10 and lc11 - clarified types and opacity of reference parameters</td></tr><tr><td>2005-04-22 @ 17:25</td><td>mhadley</td><td>Added resolution to lc9 - changed IRI to absolute IRI where appropriate</td></tr><tr><td2005-04-22 @ 16:16</td><td>mhadley</td><td>Added resolution to lc8 - changed IRI to URI where used to refer to IRIs in the specification that are actually URIs</td></tr><tr><td>2005-04-22 @ 15:49</td><td>mhadley</td><td>Added resolution to lc7 - fixed editorial nits</td></tr><tr><td>2005-04-22 @ 15:32</td><td>mhadley</td><td>Added resolution to lc3 - removed single extensibility point from infoset representation to avoid impression that other extenisibility points are not also valid</td></tr><tr><td>2005-04-22 @ 15:06</td><td>mhadley</td><td>Added resolution to lc2 - assorted editorial changes</td></tr></table>
! </div>
! <div class="div2">
!
! <h3><a name="N67218"></a>B.2 Changes Since Second Working Draft</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-30 @ 21:02</td><td>plehegar</td><td>Removed some extra blanks
Added the note from David Hull at
http://lists.w3.org/Archives/Public/public-ws-addressing/2005Mar/0254.html
per teleconference March 28, 2005</td></tr><tr><td>2005-03-21 @ 22:36</td><td>mgudgin</td><td>Incorporated resolution of issue 50 into Section 3.2</td></tr><tr><td>2005-03-21 @ 22:06</td><td>mgudgin</td><td>Updated with resolution to issue 54</td></tr><tr><td>2005-03-21 @ 20:47</td><td>mgudgin</td><td>Removed parenthetical statement '(and opaquely)' from description of [action] property in Section 3 per resolution on 2005-03-21 telcon</td></tr><tr><td>2005-03-21 @ 16:39</td><td>mgudgin</td><td>s/that value/that the value in description of [action] property in Section 3</td></tr><tr><td>2005-03-21 @ 16:37</td><td>mgudgin</td><td>Split paragraph 2 in Section 3 into two seperate paragraphs</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 03:16</td><td>mhadley</td><td>Incorporated additional issue resolution text for issues 7 and 44 from H. Haas.</td></tr><tr><td>2005-03-02 @ 21:18</td><td>mhadley</td><td>Added rsolution to issue 4</td></tr><tr><td>2005-03-02 @ 20:30</td><td>mhadley</td><td>Added resolution to issue 7</td></tr><tr><td>2005-03-02 @ 19:36</td><td>mhadley</td><td>Added resolution to issues 22 and 51/</td></tr><tr><td>2005-03-02 @ 14:07</td><td>mhadley</td><td>Added issue 52 resolution.</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 21:42</td><td>mhadley</td><td>Added issue 48 resolution</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 14:34</td><td>mgudgin</td><td>
Added new section 2.5: Endpoint Reference Extensibility per resolution of issue i042</td></tr><tr><td>2005-02-17 @ 16:16</td><td>mhadley</td><td>Added resolution to issue 44</td></tr><tr><td>2005-02-15 @ 22:53</td><td>mhadley</td><td>Added resolution to issue 46</td></tr></table>
! </div>
! <div class="div2">
! <h3><a name="N67228"></a>B.3 Changes Since First Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-23 @ 21:13</td><td>mgudgin</td><td>Incorporated resolution of issue i014; edits to Section 2.3</td></tr><tr><td>2005-01-23 @ 20:52</td><td>mgudgin</td><td>Incorporated resolution of issue i006; made wsa:To optional</td></tr><tr><td>2005-01-23 @ 19:32</td><td>mgudgin</td><td>Incorporated resolution of Issue i001 by removing Reference Properties</td></tr><tr><td>2005-01-17 @ 02:13</td><td>mgudgin</td><td>Incorporated Paco's proposal for resolving Issue 038</td></tr><tr><td>2005-01-16 @ 22:40</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-17 @ 16:08</td><td>mhadley</td><td>Improved readability of introduction</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley/td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Switched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67238"></a>B.4 Changes Since Submission</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-22 @ 15:40</td><td>mhadley</td><td>Removed reference to WS-Policy</td></tr><tr><td>2004-11-15 @ 19:43</td><td>mhadley</td><td>Fixed some inter and intra spec references.</td></tr><tr><td>2004-11-12 @ 21:19</td><td>mgudgin</td><td>Removed TBD sections</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
--- 958,983 ----
<h2><a name="changelog"></a>B. Change Log (Non-Normative)</h2>
! <div class="div2">
!
! <h3><a name="N67285"></a>B.1 Changes Since Last Call Working Draft</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-07-12 @ 18:46</td><td>mhadley</td><td>Added resolution to issues lc69, lc108 - made wsa:ReplyTo default to anonymous, added new predefined address URI that designates no reply/fault</td></tr><tr><td>2005-07-12 @ 15:57</td><td>mhadley</td><td>Added resolution to issue 107 - assorted editorial fixes wrt alignment with WSDL terminology</td></tr><tr><td>2005-07-11 @ 19:58</td><td>mhadley</td><td>Added resolution to issue lc90 - clarified use of message id as uniqueness metric</td></tr><tr><td>2005-06-21 @ 17:46</td><td>mhadley</td><td>Added resolution to issues lc75 and lc88 - updated description of [message id]</td></tr><tr><td>2005-06-20 @ 19:08</td><td>mhadley</td><td>Added resolution to issue lc106 - updated pseudo schemas to match the notational conventions used by WSDL 2.0</td></tr><tr><td>2005-06-03 @ 20:33</td><td>mhadley</td><td>Added resolutions to issues lc58, lc79, lc91, lc102</td></tr><tr><td>205-06-02 @ 19:48</td><td>mhadley</td><td>Added resolution to issue lc78 - reworked formulating reply message text related to [relationship] to make it clear that the reply relationsship is not added top the relationships specified in the message being replied to</td></tr><tr><td>2005-06-02 @ 19:39</td><td>mhadley</td><td>Added resolution to issue lc84 - removed redundant co-occurrence requirements and concentrated conformance requirements in section 3.3</td></tr><tr><td>2005-06-02 @ 18:47</td><td>mhadley</td><td>Added resolution to issue lc89 - assorted editorial fixes</td></tr><tr><td>2005-06-02 @ 18:15</td><td>mhadley</td><td>Added resolution to issue lc37 - added DOS attack security considerations</td></tr><tr><td>2005-06-02 @ 18:07</td><td>mhadley</td><td>Added explanation of cardinality notation</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-25 @ 20:25</td><td>mhadley</td><td>Added resolution o issue lc39 - changed mandatory to 1..1</td></tr><tr><td>2005-05-25 @ 20:20</td><td>mhadley</td><td>Added resolution to issue lc66 - made it clear that type often refers to the content of elements rather than the element as a whole which can often also include attributes</td></tr><tr><td>2005-05-18 @ 19:49</td><td>mhadley</td><td>Added lc81 resolution - remove mustUnderstand attributes from examples</td></tr><tr><td>2005-05-18 @ 19:35</td><td>mhadley</td><td>Added lc51 resolution - reordered property list to match order in core</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-05-18 @ 18:58</td><td>mhadley</td><td>Added lc97 resolution - Endpoint Reference to endpoint reference</td></tr><tr><td>2005-05-18 @ 18:56</td><td>mhadley</td><td>Added lc95 resolution - added WSDL 1.1 citation to introduction</td></tr><tr><td>2005-05-18 @ 18:51</td><td>mhadley</td><td>Added lc94 resolution - changed element to Element Informaton Item</td></tr><tr><td>2005-05-18 @ 18:48</td><td>mhadley</td><td>Added lc93 resolution - added ref to soap binding document prior to soap example in introduction</td></tr><tr><td>2005-05-18 @ 18:44</td><td>mhadley</td><td>Added lc92 resolution - clarified document being referenced in introduction</td></tr><tr><td>2005-05-18 @ 18:40</td><td>mhadley</td><td>Added lc80 resolution - made abstract properties into a separate list</td></tr><tr><td>2005-05-18 @ 18:34</td><td>mhadley</td><td>Added lc74 resolution - added suggested security consideration</td></tr><tr><td>2005-05-18 @ 18:24</td><td>mhadley</td><td>Added lc63 resolution - editorial fixes to security section</td></tr><tr><td>2005-05-18 @ 18:19</td><td>mhadley</td><td>Added lc44 resolution - changed and to or in security section</td></tr><tr><td>2005-05-18 @ 18:17</td><td>mhadley</td><td>Added lc43 resolution - added ref to SOAP 1.1</td></tr><tr><td>2005-05-18 @ 18:12</td><td>mhadley</td><td>Added lc42 resolution - reordered infoset representation to atch order of abstract properties</td></tr><tr><td>2005-05-18 @ 18:03</td><td>mhadley</td><td>Added lc67 resolution - made namespace uri a link</td></tr><tr><td>2005-05-18 @ 17:58</td><td>mhadley</td><td>Added lc64 resolution - numerous editorial fixes</td></tr><tr><td>2005-05-16 @ 20:28</td><td>mgudgin</td><td>Fixed mismatched endtag in Section 3.1</td></tr><tr><td>2005-05-16 @ 20:16</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of other biblio entries</td></tr><tr><td>2005-04-22 @ 18:26</td><td>mhadley</td><td>Added resolution to lc22 - clarified ignore rule for extension attributes.</td></tr><tr><td>2005-04-22 @ 18:24</td><td>mhadley</td><td>Added resolution to lc21 - removed HTTP specific restriction on use of anonymous URI in [destination] for replies only.</td></tr><tr><td>2005-04-22 @ 18:18</td><td>mhadley</td><td>Added resolution to lc19 - clarified that [destination] value comparison is out of scope except for using simple string comparison to determine whether the anonymous detination is being used.</td></tr><tr><td>2005-04-22 @ 18:12</td><td>mhadley</td><td>Added resolution to lc18 - simplified description of wsa:To and wsa:Action elements</td></tr><tr><td>2005-04-22 @ 18:04</td><td>mhadley</td><td>Added resolution to lc17 - clarified that anonymous destination URI is not just for use in replies</td></tr><tr><td>2005-04-22 @ 18:01</td><td>mhadley</td><td>Added resolution to lc16 and lc54 - removed suggestion that required was required to use [destination] and [action] properties for dispatch</td></tr><tr><td>2005-04-22 @ 17:55</td><td>mhadley</td><td>Added resolution to lc15 - clarified cardinality of [relationship] properties using predefined reply URI</td></tr><tr><td>2005-04-22 @ 17:50</td><td>mhadley</td><td>Added resolution to lc14 - clarified reply IRI targetting</td></tr><tr><td>2005-04-22 @ 17:41</td><td>mhadley</td><td>Added resolution to lc13 - clarified wording in description of metadata</td></tr><tr><td>2005-04-22 @ 17:38</td><td>mhadley</td><td>Added resolution tolc12 - removed data encoding from description of reference parameters</td></tr><tr><td>2005-04-22 @ 17:30</td><td>mhadley</td><td>Added resolution to lc10 and lc11 - clarified types and opacity of reference parameters</td></tr><tr><td>2005-04-22 @ 17:25</td><td>mhadley</td><td>Added resolution to lc9 - changed IRI to absolute IRI where appropriate</td></tr><tr><td>2005-04-22 @ 16:16</td><td>mhadley</td><td>Added resolution to lc8 - changed IRI to URI where used to refer to IRIs in the specification that are actually URIs</td></tr><tr><td>2005-04-22 @ 15:49</td><td>mhadley</td><td>Added resolution to lc7 - fixed editorial nits</td></tr><tr><td>2005-04-22 @ 15:32</td><td>mhadley</td><td>Added resolution to lc3 - removed single extensibility point from infoset representation to avoid impression that other extenisibility points are not also valid</td></tr><tr><td>2005-04-22 @ 15:06</td><td>mhadley</td><td>Added resolution to lc2 - assorted editorial changes</td></tr></table>
! </div>
! <div class="div2">
!
! <h3><a name="N67295"></a>B.2 Changes Since Second Working Draft</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-30 @ 21:02</td><td>plehegar</td><td>Removed some extra blanks
Added the note from David Hull at
http://lists.w3.org/Archives/Public/public-ws-addressing/2005Mar/0254.html
per teleconference March 28, 2005</td></tr><tr><td>2005-03-21 @ 22:36</td><td>mgudgin</td><td>Incorporated resolution of issue 50 into Section 3.2</td></tr><tr><td>2005-03-21 @ 22:06</td><td>mgudgin</td><td>Updated with resolution to issue 54</td></tr><tr><td>2005-03-21 @ 20:47</td><td>mgudgin</td><td>Removed parenthetical statement '(and opaquely)' from description of [action] property in Section 3 per resolution on 2005-03-21 telcon</td></tr><tr><td>2005-03-21 @ 16:39</td><td>mgudgin</td><td>s/that value/that the value in description of [action] property in Section 3</td></tr><tr><td>2005-03-21 @ 16:37</td><td>mgudgin</td><td>Split paragraph 2 in Section 3 into two seperate paragraphs</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 03:16</td><td>mhadley</td><td>Incorporated additional issue resolution text for issues 7 and 44 from H. Haas.</td></tr><tr><td>2005-03-02 @ 21:18</td><td>mhadley</td><td>Added rsolution to issue 4</td></tr><tr><td>2005-03-02 @ 20:30</td><td>mhadley</td><td>Added resolution to issue 7</td></tr><tr><td>2005-03-02 @ 19:36</td><td>mhadley</td><td>Added resolution to issues 22 and 51/</td></tr><tr><td>2005-03-02 @ 14:07</td><td>mhadley</td><td>Added issue 52 resolution.</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 21:42</td><td>mhadley</td><td>Added issue 48 resolution</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 14:34</td><td>mgudgin</td><td>
Added new section 2.5: Endpoint Reference Extensibility per resolution of issue i042</td></tr><tr><td>2005-02-17 @ 16:16</td><td>mhadley</td><td>Added resolution to issue 44</td></tr><tr><td>2005-02-15 @ 22:53</td><td>mhadley</td><td>Added resolution to issue 46</td></tr></table>
! </div>
! <div class="div2">
! <h3><a name="N67305"></a>B.3 Changes Since First Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-23 @ 21:13</td><td>mgudgin</td><td>Incorporated resolution of issue i014; edits to Section 2.3</td></tr><tr><td>2005-01-23 @ 20:52</td><td>mgudgin</td><td>Incorporated resolution of issue i006; made wsa:To optional</td></tr><tr><td>2005-01-23 @ 19:32</td><td>mgudgin</td><td>Incorporated resolution of Issue i001 by removing Reference Properties</td></tr><tr><td>2005-01-17 @ 02:13</td><td>mgudgin</td><td>Incorporated Paco's proposal for resolving Issue 038</td></tr><tr><td>2005-01-16 @ 22:40</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-17 @ 16:08</td><td>mhadley</td><td>Improved readability of introduction</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley/td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Switched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67315"></a>B.4 Changes Since Submission</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-22 @ 15:40</td><td>mhadley</td><td>Removed reference to WS-Policy</td></tr><tr><td>2004-11-15 @ 19:43</td><td>mhadley</td><td>Fixed some inter and intra spec references.</td></tr><tr><td>2004-11-12 @ 21:19</td><td>mgudgin</td><td>Removed TBD sections</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
Received on Tuesday, 12 July 2005 18:49:00 UTC