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

2004/ws/addressing ws-addr-core.xml,1.63,1.64

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 22 Apr 2005 17:55:08 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DP2Mu-0006Od-Km@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-core.xml 
Log Message:
Added resolution to lc15 - clarified cardinality of [relationship] properties using predefined reply URI

Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.63
retrieving revision 1.64
diff -C2 -d -r1.63 -r1.64
*** ws-addr-core.xml	22 Apr 2005 17:50:12 -0000	1.63
--- ws-addr-core.xml	22 Apr 2005 17:55:06 -0000	1.64
***************
*** 96,101 ****
                      lines (010) to (012).</p>
                  <p>Lines (003) to (008) contain the message information header blocks. Specifically,
!                     line (002) specifies the identifier for this message and lines (004) to
!                     (006) specify the endpoint to which replies to this message should be sent as an
                      Endpoint Reference. Line (007) specifies the address URI of the ultimate
                      receiver of this message. Line (008) specifies an action URI identifying
--- 96,101 ----
                      lines (010) to (012).</p>
                  <p>Lines (003) to (008) contain the message information header blocks. Specifically,
!                     line (002) specifies the identifier for this message and lines (004) to (006)
!                     specify the endpoint to which replies to this message should be sent as an
                      Endpoint Reference. Line (007) specifies the address URI of the ultimate
                      receiver of this message. Line (008) specifies an action URI identifying
***************
*** 199,211 ****
                              <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 consuming
!                                 applications. 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>
                          </def>
                      </gitem>
--- 199,210 ----
                              <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 consuming applications.
!                                 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>
                          </def>
                      </gitem>
***************
*** 218,225 ****
                                  consuming application, 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, or
                                  between embedded metadata and metadata obtained from a different
--- 217,224 ----
                                  consuming application, 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, or
                                  between embedded metadata and metadata obtained from a different
***************
*** 240,244 ****
                  <p>The wsa:EndpointReferenceType type is used wherever a Web service endpoint is
                      referenced. The following describes the contents of this type:</p>
!                     <eg xml:space="preserve">&lt;wsa:EndpointReference&gt;
      &lt;wsa:Address&gt;xs:anyURI&lt;/wsa:Address&gt;
      &lt;wsa:ReferenceParameters&gt;... &lt;/wsa:ReferenceParameters&gt; ?
--- 239,243 ----
                  <p>The wsa:EndpointReferenceType type is used wherever a Web service endpoint is
                      referenced. The following describes the contents of this type:</p>
!                 <eg xml:space="preserve">&lt;wsa:EndpointReference&gt;
      &lt;wsa:Address&gt;xs:anyURI&lt;/wsa:Address&gt;
      &lt;wsa:ReferenceParameters&gt;... &lt;/wsa:ReferenceParameters&gt; ?
***************
*** 271,275 ****
                          </def>
                      </gitem>
-                     
                      <gitem>
                          <label> /wsa:EndpointReference/wsa:ReferenceParameters</label>
--- 270,273 ----
***************
*** 386,404 ****
              <p>This section defines the information model and syntax of message addressing
                  properties.</p>
! 	    <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 feedback will help
! 		the Working Group determine whether it needs to
! 		re-examine this issue.
! 	      </p>
! 	    </note>
              <p> Message addressing properties provide references for the endpoints involved in an
                  interaction. The use of these properties to support specific interaction is in
--- 384,398 ----
              <p>This section defines the information model and syntax of message addressing
                  properties.</p>
!             <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
!                     feedback will help the Working Group determine whether it needs to re-examine
!                     this issue. </p>
!             </note>
              <p> Message addressing properties provide references for the endpoints involved in an
                  interaction. The use of these properties to support specific interaction is in
***************
*** 408,427 ****
                  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 Reply" 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 reply). A reply 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 Reply 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-reply
! 				MEPs.  More advanced MEPs may require additional message addressing
! 				properties to augment the facilities provided here. </p>
              <p>Message addressing properties collectively augment a message with the following
                  abstract properties to support one way, request reply, and other interaction
--- 402,420 ----
                  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 Reply" 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
!                 reply). A reply 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 Reply 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-reply MEPs. More advanced MEPs may
!                 require additional message addressing properties to augment the facilities provided
!                 here. </p>
              <p>Message addressing properties collectively augment a message with the following
                  abstract properties to support one way, request reply, and other interaction
***************
*** 431,436 ****
                      <label> [destination] : IRI (mandatory)</label>
                      <def>
!                         <p>An absolute IRI
!                             representing the address of the intended receiver of this message.</p>
                      </def>
                  </gitem>
--- 424,429 ----
                      <label> [destination] : IRI (mandatory)</label>
                      <def>
!                         <p>An absolute IRI representing the address of the intended receiver of this
!                             message.</p>
                      </def>
                  </gitem>
***************
*** 457,463 ****
                              this message. When formulating a fault message as defined in <specref
                                  ref="formreplymsg"/>, the sender MUST use the contents of the [fault
!                             endpoint], when present, of the message being replied to formulate
!                             the fault message. If this property is present, the [message id]
!                             property is REQUIRED.</p>
                      </def>
                  </gitem>
--- 450,456 ----
                              this message. When formulating a fault message as defined in <specref
                                  ref="formreplymsg"/>, the sender MUST use the contents of the [fault
!                             endpoint], when present, of the message being replied to formulate the
!                             fault message. If this property is present, the [message id] property is
!                             REQUIRED.</p>
                      </def>
                  </gitem>
***************
*** 465,470 ****
                      <label> [action] : IRI (mandatory)</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 port type.
--- 458,463 ----
                      <label> [action] : IRI (mandatory)</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 port type.
***************
*** 477,484 ****
                      <label> [message id] : IRI (0..1)</label>
                      <def>
!                         <p>An absolute IRI that
!                             uniquely identifies this message in time and space. No two
!                             messages with a distinct application intent may share a [message id]
!                             property. A message MAY be retransmitted for any purpose including
                              communications failure and MAY use the same [message id] property. The
                              value of this property is an opaque IRI whose interpretation beyond
--- 470,476 ----
                      <label> [message id] : IRI (0..1)</label>
                      <def>
!                         <p>An absolute IRI that uniquely identifies this message in time and space.
!                             No two messages with a distinct application intent may share a [message
!                             id] property. A message MAY be retransmitted for any purpose including
                              communications failure and MAY use the same [message id] property. The
                              value of this property is an opaque IRI whose interpretation beyond
***************
*** 491,499 ****
                      <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 well-known URI that means
!                             "unspecified message": <attval>&nsuri;/id/unspecified</attval>
                          </p>
                          <p>This specification has one predefined relationship type as shown in
--- 483,491 ----
                      <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 well-known URI that
!                             means "unspecified message": <attval>&nsuri;/id/unspecified</attval>
                          </p>
                          <p>This specification has one predefined relationship type as shown in
***************
*** 517,522 ****
                          </table>
                          <p>A reply message MUST contain a [relationship] property consisting of the
!                             predefined reply URI and the message id property of the request
!                         message.</p>
                      </def>
                  </gitem>
--- 509,515 ----
                          </table>
                          <p>A reply message MUST contain a [relationship] property consisting of the
!                             predefined reply URI and the [message id] property of the request message.
!                             A reply message MUST NOT contain more than one [relationship] property
!                             using the predefined reply URI</p>
                      </def>
                  </gitem>
***************
*** 552,557 ****
                  <p>The following shows the XML Infoset representation of message addressing
                      properties:</p>
!                     <eg xml:space="preserve"
!                     >
  &lt;wsa:MessageID&gt;xs:anyURI &lt;/wsa:MessageID&gt;
  &lt;wsa:RelatesTo RelationshipType="xs:anyURI"?&gt;xs:anyURI&lt;/wsa:RelatesTo&gt;
--- 545,549 ----
                  <p>The following shows the XML Infoset representation of message addressing
                      properties:</p>
!                 <eg xml:space="preserve">
  &lt;wsa:MessageID&gt;xs:anyURI &lt;/wsa:MessageID&gt;
  &lt;wsa:RelatesTo RelationshipType="xs:anyURI"?&gt;xs:anyURI&lt;/wsa:RelatesTo&gt;
***************
*** 656,663 ****
                          </def>
                      </gitem>
-                     
                  </glist>
!                 <p>Note that each of the element information items described above allows
!                     attribute wildcards for future extensibility.</p>
                  <div3 id="compiri">
                      <head>Comparing IRIs</head>
--- 648,654 ----
                          </def>
                      </gitem>
                  </glist>
!                 <p>Note that each of the element information items described above allows attribute
!                     wildcards for future extensibility.</p>
                  <div3 id="compiri">
                      <head>Comparing IRIs</head>
***************
*** 665,670 ****
                          [relationship] are absolute IRIs. The purpose of these IRIs is primarily
                          identification, rather than resource retrieval. As such, simple string
!                         comparison, as indicated in Internationalized
! 			Resource Identifiers <bibref
                              ref="RFC3987"/> section 5.3.1, is sufficient to determine equivalence of
                          these IRIs.</p>
--- 656,660 ----
                          [relationship] are absolute IRIs. The purpose of these IRIs is primarily
                          identification, rather than resource retrieval. As such, simple string
!                         comparison, as indicated in Internationalized Resource Identifiers <bibref
                              ref="RFC3987"/> section 5.3.1, is sufficient to determine equivalence of
                          these IRIs.</p>
***************
*** 687,695 ****
                                  <p>Otherwise, if the reply is a fault message and the incoming
                                      message's [fault endpoint] message addressing property is not
!                                     empty, select the EPR from that property. If the [fault endpoint] 
! 									property is empty, select the EPR from the incoming message's
! 									[reply endpoint] message addressing property. Otherwise, if the
! 									[reply endpoint] property is empty,	the behavior of the recipient
! 									of the incoming message is unconstrained by this specification.</p>
                              </item>
                          </ulist>
--- 677,686 ----
                                  <p>Otherwise, if the reply is a fault message and the incoming
                                      message's [fault endpoint] message addressing property is not
!                                     empty, select the EPR from that property. If the [fault
!                                     endpoint] property is empty, select the EPR from the incoming
!                                     message's [reply endpoint] message addressing property.
!                                     Otherwise, if the [reply endpoint] property is empty, the
!                                     behavior of the recipient of the incoming message is
!                                     unconstrained by this specification.</p>
                              </item>
                          </ulist>
***************
*** 825,829 ****
                      href="&w3c-designation-wsa-soap;">
                      <titleref>&wsa-soap.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
! <!--
                  <bibl key="WS-Addressing-WSDL" id="WSADDR-WSDL"
                      href="&w3c-designation-wsa-wsdl;">
--- 816,820 ----
                      href="&w3c-designation-wsa-soap;">
                      <titleref>&wsa-soap.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
!                 <!--
                  <bibl key="WS-Addressing-WSDL" id="WSADDR-WSDL"
                      href="&w3c-designation-wsa-wsdl;">
***************
*** 845,856 ****
                      S. Bradner. Internet Engineering Task Force, June 1999. Available at
                      http://www.ietf.org/rfc/rfc2119.txt. </bibl>
!                 <bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt"> M.
!                     Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)", January
                      2005.</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.
                      Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
!                     Consortium, 4 February 2004. This version of the XML
!                     1.0 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The <loc
                          href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</loc> is
                      available at http://www.w3.org/TR/REC-xml. </bibl>
--- 836,847 ----
                      S. Bradner. Internet Engineering Task Force, June 1999. Available at
                      http://www.ietf.org/rfc/rfc2119.txt. </bibl>
!                 <bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt">
!                     M. Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)", January
                      2005.</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.
                      Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
!                     Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is
!                     http://www.w3.org/TR/2004/REC-xml-20040204. The <loc
                          href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</loc> is
                      available at http://www.w3.org/TR/REC-xml. </bibl>
***************
*** 872,879 ****
                  <bibl id="XMLSchemaP1" key="XML Schema Structures"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
!                     <titleref>XML Schema Part 1: Structures Second Edition</titleref>, H. Thompson, D. Beech, M.
!                     Maloney, and N. Mendelsohn, Editors. World Wide
! 		    Web Consortium, 28 October 2004. This
!                     version of the XML Schema Part 1 Recommendation is
                      http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc
                          href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
--- 863,869 ----
                  <bibl id="XMLSchemaP1" key="XML Schema Structures"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
!                     <titleref>XML Schema Part 1: Structures Second Edition</titleref>, H. Thompson,
!                     D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 28
!                     October 2004. This version of the XML Schema Part 1 Recommendation is
                      http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc
                          href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
***************
*** 881,889 ****
                  <bibl key="XML Schema Datatypes" id="XMLSchemaP2"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
!                     <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron and A. Malhotra,
!                     Editors. World Wide Web Consortium, 28 October 2004. This version of the XML Schema
!                     Part 2 Recommendation is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The
!                         <loc href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
!                         Part 2</loc> is available at http://www.w3.org/TR/xmlschema-2. </bibl>
                  <bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework"
                      href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
--- 871,880 ----
                  <bibl key="XML Schema Datatypes" id="XMLSchemaP2"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
!                     <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron and
!                     A. Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This version
!                     of the XML Schema Part 2 Recommendation is
!                     http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <loc
!                         href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema Part
!                     2</loc> is available at http://www.w3.org/TR/xmlschema-2. </bibl>
                  <bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework"
                      href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
Received on Friday, 22 April 2005 17:55:09 GMT

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