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

2004/ws/addressing ws-addr-core.xml,1.53,1.54

From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 30 Mar 2005 21:02:07 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DGkKF-0005g8-Ta@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-core.xml 
Log Message:
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


Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -C2 -d -r1.53 -r1.54
*** ws-addr-core.xml	22 Mar 2005 15:50:17 -0000	1.53
--- ws-addr-core.xml	30 Mar 2005 21:02:05 -0000	1.54
***************
*** 56,60 ****
      <body>
          <div1 id="tocRange">
!             <head> Introduction</head>
              <p>Web Services Addressing (WS-Addressing) defines two constructs, message addressing
                  properties and endpoint references, that normalize the information typically
--- 56,60 ----
      <body>
          <div1 id="tocRange">
!             <head>Introduction</head>
              <p>Web Services Addressing (WS-Addressing) defines two constructs, message addressing
                  properties and endpoint references, that normalize the information typically
***************
*** 105,109 ****
              </example>
              <div2 id="notation">
!                 <head> Notational Conventions</head>
                  <p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
                      "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
--- 105,109 ----
              </example>
              <div2 id="notation">
!                 <head>Notational Conventions</head>
                  <p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
                      "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
***************
*** 123,127 ****
              </div2>
              <div2 id="namespaces">
!                 <head> Namespaces</head>
                  <p> This specification uses a number of namespace prefixes throughout; they are
                      listed in <specref ref="nsprefix"/>. Note that the choice of any namespace
--- 123,127 ----
              </div2>
              <div2 id="namespaces">
!                 <head>Namespaces</head>
                  <p> This specification uses a number of namespace prefixes throughout; they are
                      listed in <specref ref="nsprefix"/>. Note that the choice of any namespace
***************
*** 167,171 ****
          </div1>
          <div1 id="eprs">
!             <head> Endpoint References</head>
              <p>This section defines the information model and syntax of an endpoint reference.</p>
              <p> This specification introduces the endpoint reference, a construct designed to
--- 167,171 ----
          </div1>
          <div1 id="eprs">
!             <head>Endpoint References</head>
              <p>This section defines the information model and syntax of an endpoint reference.</p>
              <p> This specification introduces the endpoint reference, a construct designed to
***************
*** 191,195 ****
              </ulist>
              <div2 id="eprinfomodel">
!                 <head> Information Model for Endpoint References</head>
                  <p>An endpoint reference consists of the following abstract properties:</p>
                  <glist>
--- 191,195 ----
              </ulist>
              <div2 id="eprinfomodel">
!                 <head>Information Model for Endpoint References</head>
                  <p>An endpoint reference consists of the following abstract properties:</p>
                  <glist>
***************
*** 240,244 ****
              </div2>
              <div2 id="eprinfoset">
!                 <head> Endpoint Reference XML Infoset Representation</head>
                  <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
--- 240,244 ----
              </div2>
              <div2 id="eprinfoset">
!                 <head>Endpoint Reference XML Infoset Representation</head>
                  <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
***************
*** 362,366 ****
              </div2>
              <div2 id="eprcomp">
!                 <head> Endpoint Reference Comparison</head>
                  <p>This specification provides no concept of endpoint identity and therefore does
                      not provide any mechanism to determine equality or inequality of EPRs and does
--- 362,366 ----
              </div2>
              <div2 id="eprcomp">
!                 <head>Endpoint Reference Comparison</head>
                  <p>This specification provides no concept of endpoint identity and therefore does
                      not provide any mechanism to determine equality or inequality of EPRs and does
***************
*** 399,405 ****
          </div1>
          <div1 id="msgaddrprops">
!             <head> Message Addressing Properties</head>
              <p>This section defines the information model and syntax of message addressing
                  properties.</p>
              <p> Message addressing properties provide references for the endpoints involved in an
                  interaction. The use of these properties to support specific interaction is in
--- 399,420 ----
          </div1>
          <div1 id="msgaddrprops">
!             <head>Message Addressing Properties</head>
              <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
***************
*** 673,677 ****
              </div2>
              <div2 id="formreplymsg">
!                 <head> Formulating a Reply Message</head>
                  <p>The reply to a WS-Addressing compliant request message MUST be compliant to
                      WS-Addressing and is constructed according to the following rules:</p>
--- 688,692 ----
              </div2>
              <div2 id="formreplymsg">
!                 <head>Formulating a Reply Message</head>
                  <p>The reply to a WS-Addressing compliant request message MUST be compliant to
                      WS-Addressing and is constructed according to the following rules:</p>
***************
*** 828,832 ****
          </div1>
          <div1 id="references">
!             <head> References</head>
              <blist>
                  <bibl key="WS-Addressing-SOAP" id="WSADDR-SOAP"
--- 843,847 ----
          </div1>
          <div1 id="references">
!             <head>References</head>
              <blist>
                  <bibl key="WS-Addressing-SOAP" id="WSADDR-SOAP"
Received on Wednesday, 30 March 2005 21:02:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:01 UTC