- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 12 Jul 2005 18:46:53 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv26025
Modified Files:
ws-addr-core.xml
Log Message:
Added resolution to issues lc69, lc108 - made wsa:ReplyTo default to anonymous, added new predefined address URI that designates no reply/fault
Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.101
retrieving revision 1.102
diff -C2 -d -r1.101 -r1.102
*** ws-addr-core.xml 12 Jul 2005 15:57:22 -0000 1.101
--- ws-addr-core.xml 12 Jul 2005 18:46:50 -0000 1.102
***************
*** 73,78 ****
<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 &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]
! for more information on the use of WS-Addressing in SOAP):</p>
<example>
<head>Use of message addressing properties in a SOAP 1.2 message.</head>
--- 73,78 ----
<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 &wsa-soap.title;[<bibref
! ref="WSADDR-SOAP"/>] for more information on the use of WS-Addressing in SOAP):</p>
<example>
<head>Use of message addressing properties in a SOAP 1.2 message.</head>
***************
*** 93,105 ****
(13) </S:Envelope>
</eg>
! <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>
</example>
<div2 id="notation">
--- 93,105 ----
(13) </S:Envelope>
</eg>
! <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>
</example>
<div2 id="notation">
***************
*** 115,138 ****
ref="XMLSchemaP2"/>], this specification uses the notational convention of
WS-Security [<bibref ref="WS-Security"/>]. 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>
</div2>
<div2 id="namespaces">
--- 115,138 ----
ref="XMLSchemaP2"/>], this specification uses the notational convention of
WS-Security [<bibref ref="WS-Security"/>]. 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>
</div2>
<div2 id="namespaces">
***************
*** 140,145 ****
<p> This specification uses a number of namespace prefixes throughout; they are
listed in <specref ref="nsprefix"/>. Note that the choice of any namespace
! prefix is arbitrary and not semantically significant (see
! [<bibref ref="XMLNS"/>]).</p>
<table summary="Namespace prefixes usage in this specification" id="nsprefix"
border="1">
--- 140,145 ----
<p> This specification uses a number of namespace prefixes throughout; they are
listed in <specref ref="nsprefix"/>. Note that the choice of any namespace
! prefix is arbitrary and not semantically significant (see [<bibref ref="XMLNS"
! />]).</p>
<table summary="Namespace prefixes usage in this specification" id="nsprefix"
border="1">
***************
*** 164,177 ****
</tbody>
</table>
! <p>WS-Addressing may be used with SOAP [<bibref ref="SOAP12-PART1"/>, <bibref ref="SOAP11"/>] as described
! in &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]. WS-Addressing may be used
! with WSDL [<bibref ref="WSDL20"/>, <bibref ref="WSDL11"/>] described services as described in
&wsa-wsdl.title;[<bibref ref="WSADDR-WSDL"/>]. Examples in this
specification use an XML 1.0 [<bibref ref="XML10"/>] representation but this is
not a requirement.</p>
<p>All information items defined by this specification are identified by the XML
! namespace URI [<bibref ref="XMLNS"/>] <xspecref href="&nsuri;">&nsuri;</xspecref>. A normative XML Schema
! [<bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>] document can be
! obtained by dereferencing the XML namespace URI.</p>
</div2>
</div1>
--- 164,179 ----
</tbody>
</table>
! <p>WS-Addressing may be used with SOAP [<bibref ref="SOAP12-PART1"/>, <bibref
! ref="SOAP11"/>] as described in &wsa-soap.title;[<bibref
! ref="WSADDR-SOAP"/>]. WS-Addressing may be used with WSDL [<bibref
! ref="WSDL20"/>, <bibref ref="WSDL11"/>] described services as described in
&wsa-wsdl.title;[<bibref ref="WSADDR-WSDL"/>]. Examples in this
specification use an XML 1.0 [<bibref ref="XML10"/>] representation but this is
not a requirement.</p>
<p>All information items defined by this specification are identified by the XML
! namespace URI [<bibref ref="XMLNS"/>] <xspecref href="&nsuri;"
! >&nsuri;</xspecref>. A normative XML Schema [<bibref ref="XMLSchemaP1"/>,
! <bibref ref="XMLSchemaP2"/>] document can be obtained by dereferencing the
! XML namespace URI.</p>
</div2>
</div1>
***************
*** 207,211 ****
<label> [address] : IRI (1..1)</label>
<def>
! <p>An absolute IRI representing the address of the endpoint.</p>
</def>
</gitem>
--- 209,252 ----
<label> [address] : IRI (1..1)</label>
<def>
! <p>An absolute IRI representing the address of the endpoint. This
! specification introduces two predefined [address] values as shown in
! <specref ref="predefaddr"/>.</p>
! <table id="predefaddr" border="1" summary="Predefined [address] values">
! <caption>Predefined [address] values</caption>
! <tbody>
! <tr>
! <th align="left">URI</th>
! <th align="left">Description </th>
! </tr>
! <tr>
! <td>
! <attval>&nsuri;/anonymous</attval>
! </td>
! <td>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>
! <attval>&nsuri;/none</attval>
! </td>
! <td>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 <specref ref="abstractmaps"/>) to
! indicate
! that no reply or fault message should be
! sent.</td>
! </tr>
! </tbody>
! </table>
</def>
</gitem>
***************
*** 213,225 ****
<label> [reference parameters] : xs:any (0..unbounded).</label>
<def>
! <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 -
&wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>] describes the
default binding for the SOAP protocol. </p>
--- 254,265 ----
<label> [reference parameters] : xs:any (0..unbounded).</label>
<def>
! <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 -
&wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>] describes the
default binding for the SOAP protocol. </p>
***************
*** 231,249 ****
<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 <specref ref="eprlifecycle"/>) or
! retrieval of metadata from an authoritative source, SHOULD be
! used.</p>
</def>
</gitem>
--- 271,288 ----
<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
! <specref ref="eprlifecycle"/>) or retrieval of metadata from an
! authoritative source, SHOULD be used.</p>
</def>
</gitem>
***************
*** 254,259 ****
<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>
--- 293,298 ----
<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>
***************
*** 280,285 ****
<label> /wsa:EndpointReference/wsa:Address</label>
<def>
! <p>This REQUIRED element (whose content is of type xs:anyURI) specifies the [address]
! property of the endpoint reference.</p>
</def>
</gitem>
--- 319,324 ----
<label> /wsa:EndpointReference/wsa:Address</label>
<def>
! <p>This REQUIRED element (whose content is of type xs:anyURI) specifies
! the [address] property of the endpoint reference.</p>
</def>
</gitem>
***************
*** 295,300 ****
<def>
<p>This OPTIONAL element may contain elements from any namespace. Such
! elements form the
! [reference parameters] of the reference.</p>
</def>
</gitem>
--- 334,338 ----
<def>
<p>This OPTIONAL element may contain elements from any namespace. Such
! elements form the [reference parameters] of the reference.</p>
</def>
</gitem>
***************
*** 310,315 ****
<def>
<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>
</def>
</gitem>
--- 348,353 ----
<def>
<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>
</def>
</gitem>
***************
*** 318,323 ****
<def>
<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>
</def>
</gitem>
--- 356,361 ----
<def>
<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>
</def>
</gitem>
***************
*** 358,363 ****
<example>
<head>Example endpoint reference.</head>
! <eg xml:space="preserve"
! >
<wsa:EndpointReference xmlns:wsa="&nsuri;">
<wsa:Address>http://example.com/fabrikam/acct</wsa:Address>
--- 396,400 ----
<example>
<head>Example endpoint reference.</head>
! <eg xml:space="preserve">
<wsa:EndpointReference xmlns:wsa="&nsuri;">
<wsa:Address>http://example.com/fabrikam/acct</wsa:Address>
***************
*** 409,416 ****
<note>
<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 <loc
href="http://www.w3.org/2002/ws/addr/wd-issues/#i054">particular
design</loc>, some participants believe it is not adequately specified. Such
--- 446,453 ----
<note>
<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 <loc
href="http://www.w3.org/2002/ws/addr/wd-issues/#i054">particular
design</loc>, some participants believe it is not adequately specified. Such
***************
*** 427,558 ****
<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>
!
<div2 id="abstractmaps">
<head>Abstract Property Definitions</head>
!
! <p>Message addressing properties collectively augment a message with the following
! abstract properties to support one-way, request-response, and other interaction
! patterns:</p>
! <glist>
! <gitem>
! <label> [destination] : IRI (1..1)</label>
! <def>
! <p>An absolute IRI representing the address of the intended receiver of this
! message.</p>
! </def>
! </gitem>
! <gitem>
! <label> [source endpoint] : endpoint reference (0..1)</label>
! <def>
! <p>Reference to the endpoint from which the message originated.</p>
! </def>
! </gitem>
! <gitem>
! <label> [reply endpoint] : endpoint reference (0..1)</label>
! <def>
! <p>An endpoint reference for the intended receiver for replies to this
! message.</p>
! </def>
! </gitem>
! <gitem>
! <label> [fault endpoint] : endpoint reference (0..1)</label>
! <def>
! <p>An endpoint reference for the intended receiver for faults related to
! this message.</p>
! </def>
! </gitem>
! <gitem>
! <label> [action] : IRI (1..1)</label>
! <def>
! <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. &wsa-wsdl.title;[<bibref
! ref="WSADDR-WSDL"/>] describes the mechanisms of association.</p>
! </def>
! </gitem>
! <gitem>
! <label> [message id] : IRI (0..1)</label>
! <def>
! <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>
! </def>
! </gitem>
! <gitem>
! <label> [relationship] : (IRI, IRI) (0..unbounded)</label>
! <def>
! <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": <attval>&nsuri;/unspecified</attval>
! </p>
! <p>This specification has one predefined relationship type as shown in
! <specref ref="predefrels"/>.</p>
! <table id="predefrels" border="1"
! summary="Predefined [relationship] type values">
! <caption>Predefined [relationship] values</caption>
! <tbody>
! <tr>
! <th align="left">URI</th>
! <th align="left">Description </th>
! </tr>
! <tr>
! <td>
! <attval>&nsuri;/reply</attval>
! </td>
! <td>Indicates that this is a reply to the message identified by
! the [message id] IRI.</td>
! </tr>
! </tbody>
! </table>
! </def>
! </gitem>
! <gitem>
! <label> [reference parameters] : xs:any (0..unbounded).</label>
! <def>
! <p>Corresponds to the value of the [reference parameters] property of the
! endpoint reference to which the message is addressed.</p>
! </def>
! </gitem>
! </glist>
! <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: <attval>&nsuri;/anonymous</attval>. 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. &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]
! defines such a binding for the SOAP
! [<bibref ref="SOAP12-PART1"/>, <bibref ref="SOAP11"/>] protocol.</p>
</div2>
-
<div2 id="msgaddrpropsinfoset">
<head>XML Infoset Representation of Message Addressing Properties</head>
--- 464,584 ----
<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>
<div2 id="abstractmaps">
<head>Abstract Property Definitions</head>
! <p>Message addressing properties collectively augment a message with the following
! abstract properties to support one-way, request-response, and other interaction
! patterns:</p>
! <glist>
! <gitem>
! <label> [destination] : IRI (1..1)</label>
! <def>
! <p>An absolute IRI representing the address of the intended receiver of
! this message.</p>
! </def>
! </gitem>
! <gitem>
! <label> [source endpoint] : endpoint reference (0..1)</label>
! <def>
! <p>Reference to the endpoint from which the message originated.</p>
! </def>
! </gitem>
! <gitem>
! <label> [reply endpoint] : endpoint reference (0..1)</label>
! <def>
! <p>An endpoint reference for the intended receiver for replies to this
! message.</p>
! </def>
! </gitem>
! <gitem>
! <label> [fault endpoint] : endpoint reference (0..1)</label>
! <def>
! <p>An endpoint reference for the intended receiver for faults related to
! this message.</p>
! </def>
! </gitem>
! <gitem>
! <label> [action] : IRI (1..1)</label>
! <def>
! <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.
! &wsa-wsdl.title;[<bibref ref="WSADDR-WSDL"/>] describes the
! mechanisms of association.</p>
! </def>
! </gitem>
! <gitem>
! <label> [message id] : IRI (0..1)</label>
! <def>
! <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>
! </def>
! </gitem>
! <gitem>
! <label> [relationship] : (IRI, IRI) (0..unbounded)</label>
! <def>
! <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":
! <attval>&nsuri;/unspecified</attval>
! </p>
! <p>This specification has one predefined relationship type as shown in
! <specref ref="predefrels"/>.</p>
! <table id="predefrels" border="1" summary="Predefined [relationship]
! type values">
! <caption>Predefined [relationship] values</caption>
! <tbody>
! <tr>
! <th align="left">URI</th>
! <th align="left">Description </th>
! </tr>
! <tr>
! <td>
! <attval>&nsuri;/reply</attval>
! </td>
! <td>Indicates that this is a reply to the message identified
! by the [message id] IRI.</td>
! </tr>
! </tbody>
! </table>
! </def>
! </gitem>
! <gitem>
! <label> [reference parameters] : xs:any (0..unbounded).</label>
! <def>
! <p>Corresponds to the value of the [reference parameters] property of
! the endpoint reference to which the message is addressed.</p>
! </def>
! </gitem>
! </glist>
! <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. &wsa-soap.title;[<bibref ref="WSADDR-SOAP"
! />] defines such a binding for the SOAP [<bibref ref="SOAP12-PART1"/>, <bibref
! ref="SOAP11"/>] protocol.</p>
</div2>
<div2 id="msgaddrpropsinfoset">
<head>XML Infoset Representation of Message Addressing Properties</head>
***************
*** 575,582 ****
<label> /wsa:To</label>
<def>
! <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
! <attval>&nsuri;/anonymous</attval>.</p>
</def>
</gitem>
--- 601,608 ----
<label> /wsa:To</label>
<def>
! <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
! <attval>&nsuri;/anonymous</attval>.</p>
</def>
</gitem>
***************
*** 592,596 ****
<def>
<p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides
! the value for the [reply endpoint] property.</p>
</def>
</gitem>
--- 618,624 ----
<def>
<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 <attval>&nsuri;/anonymous</attval>.</p>
</def>
</gitem>
***************
*** 605,610 ****
<label> /wsa:Action</label>
<def>
! <p>This REQUIRED element (whose content is of type xs:anyURI) conveys the value of the
! [action] property.</p>
</def>
</gitem>
--- 633,638 ----
<label> /wsa:Action</label>
<def>
! <p>This REQUIRED element (whose content is of type xs:anyURI) conveys
! the value of the [action] property.</p>
</def>
</gitem>
***************
*** 612,617 ****
<label> /wsa:MessageID</label>
<def>
! <p>This OPTIONAL element (whose content is of type xs:anyURI) conveys the [message id]
! property.</p>
</def>
</gitem>
--- 640,645 ----
<label> /wsa:MessageID</label>
<def>
! <p>This OPTIONAL element (whose content is of type xs:anyURI) conveys
! the [message id] property.</p>
</def>
</gitem>
***************
*** 621,626 ****
<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>
</def>
</gitem>
--- 649,654 ----
<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>
</def>
</gitem>
***************
*** 633,642 ****
</def>
</gitem>
! <gitem>
<label> /[reference parameters]*</label>
<def>
<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>
</def>
</gitem>
--- 661,670 ----
</def>
</gitem>
! <gitem>
<label> /[reference parameters]*</label>
<def>
<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>
</def>
</gitem>
***************
*** 667,673 ****
<ulist>
<item>
! <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>
</item>
<item>
--- 695,706 ----
<ulist>
<item>
! <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>
! <note><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 <attval>&nsuri;/anonymous</attval> - see
! section <specref ref="msgaddrpropsinfoset"/>.</p></note>
</item>
<item>
***************
*** 681,698 ****
unconstrained by this specification.</p>
</item>
! <item><p>In either of the above cases, if the related message lacks a [message id] property,
! the processor MUST fault.</p></item>
</ulist>
</item>
<item>
! <p>Populate the reply message's message addressing properties:</p>
<ulist>
<item>
<p>[destination]: this property takes the value of the selected
! EPR's [address] property</p>
</item>
<item>
! <p>[relationship]: this property MUST include a
! pair of IRIs as
follows; the relationship type is the predefined reply URI
<attval>&nsuri;/reply</attval> and the related message's
--- 714,734 ----
unconstrained by this specification.</p>
</item>
! <item>
! <p>In either of the above cases, if the related message lacks a
! [message id] property, the processor MUST fault.</p>
! </item>
</ulist>
</item>
<item>
! <p>If the selected EPR's [address] property is
! <attval>&nsuri;/none</attval> the reply message is discarded, if not
! then populate the reply message's message addressing properties:</p>
<ulist>
<item>
<p>[destination]: this property takes the value of the selected
! EPR's [address] property.</p>
</item>
<item>
! <p>[relationship]: this property MUST include a pair of IRIs as
follows; the relationship type is the predefined reply URI
<attval>&nsuri;/reply</attval> and the related message's
***************
*** 712,717 ****
<example>
<head>Example message.</head>
! <eg xml:space="preserve"
! >
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="&nsuri;">
--- 748,752 ----
<example>
<head>Example message.</head>
! <eg xml:space="preserve">
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="&nsuri;">
***************
*** 755,760 ****
<example>
<head>Example reply message.</head>
! <eg xml:space="preserve"
! >
<S:Envelope
xmlns:S="http://www.w3.org/2003/05/soap-envelope"
--- 790,794 ----
<example>
<head>Example reply message.</head>
! <eg xml:space="preserve">
<S:Envelope
xmlns:S="http://www.w3.org/2003/05/soap-envelope"
***************
*** 795,825 ****
<div1 id="securityconsiderations">
<head>Security Considerations</head>
! <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>
</div1>
<div1 id="references">
--- 829,856 ----
<div1 id="securityconsiderations">
<head>Security Considerations</head>
! <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>
</div1>
<div1 id="references">
***************
*** 850,855 ****
http://www.ietf.org/rfc/rfc2119.txt. </bibl>
<bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt">
! <titleref>Internationalized Resource Identifiers (IRIs)</titleref>
! M. Duerst, M. Suignard, January 2005. Available at http://www.ietf.org/rfc/rfc3987.txt.</bibl>
<bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204">
<titleref>Extensible Markup Language (XML) 1.0 (Third Edition)</titleref>, T.
--- 881,886 ----
http://www.ietf.org/rfc/rfc2119.txt. </bibl>
<bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt">
! <titleref>Internationalized Resource Identifiers (IRIs)</titleref> M. Duerst, M.
! Suignard, January 2005. Available at http://www.ietf.org/rfc/rfc3987.txt.</bibl>
<bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204">
<titleref>Extensible Markup Language (XML) 1.0 (Third Edition)</titleref>, T.
***************
*** 901,910 ****
http://www.w3.org/TR/soap12-part1/. </bibl>
<bibl id="SOAP11" key="SOAP 1.1"
! href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Don Box,
! et al, <titleref>Simple Object Access Protocol (SOAP)
! 1.1</titleref>, May 2000.</bibl>
<bibl id="WSDL11" key="WSDL 1.1" href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"
>E. Christensen, et al, <titleref>Web Services Description Language (WSDL)
! 1.1</titleref>, March 2001.</bibl>
<bibl id="WS-Security" key="WS-Security"
href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"
--- 932,940 ----
http://www.w3.org/TR/soap12-part1/. </bibl>
<bibl id="SOAP11" key="SOAP 1.1"
! href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Don Box, et al,
! <titleref>Simple Object Access Protocol (SOAP) 1.1</titleref>, May 2000.</bibl>
<bibl id="WSDL11" key="WSDL 1.1" href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"
>E. Christensen, et al, <titleref>Web Services Description Language (WSDL)
! 1.1</titleref>, March 2001.</bibl>
<bibl id="WS-Security" key="WS-Security"
href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"
***************
*** 916,930 ****
<back> &acknowledgements; <inform-div1 id="changelog">
<head>Change Log</head>
! <div2>
! <head>Changes Since Last Call Working Draft</head>
! <p role="ws-addr-core.xml:20050401:20060101">Placeholder for
! auto change log generation.</p>
! </div2>
! <div2>
! <head>Changes Since Second Working Draft</head>
! <p role="ws-addr-core.xml:20050211:20050330">Placeholder for
! auto change log generation.</p>
! </div2>
! <div2>
<head>Changes Since First Working Draft</head>
<p role="ws-addr-core.xml:20041206:20050210">Placeholder for auto change log
--- 946,960 ----
<back> &acknowledgements; <inform-div1 id="changelog">
<head>Change Log</head>
! <div2>
! <head>Changes Since Last Call Working Draft</head>
! <p role="ws-addr-core.xml:20050401:20060101">Placeholder for auto change log
! generation.</p>
! </div2>
! <div2>
! <head>Changes Since Second Working Draft</head>
! <p role="ws-addr-core.xml:20050211:20050330">Placeholder for auto change log
! generation.</p>
! </div2>
! <div2>
<head>Changes Since First Working Draft</head>
<p role="ws-addr-core.xml:20041206:20050210">Placeholder for auto change log
Received on Tuesday, 12 July 2005 18:47:01 UTC