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

Last Call (Core): Editorial Comments

From: Prasad Yendluri <pyendluri@webmethods.com>
Date: Tue, 05 Apr 2005 17:12:26 -0700
Message-ID: <4253296A.2040107@webmethods.com>
To: public-ws-addressing-comments@w3.org
Ref: WS-Addressing 1.0 - Core 
(http://www.w3.org/TR/2005/WD-ws-addr-core-20050331/)

1.  Section 2.2: Example 2-1?
     The contents the "Example" are (normative?) schema for the 
wsa:EndpointReference element.
     Don't call it an "Example".
2. Section 2.2 description of  
/wsa:EndpointReference/wsa:ReferenceParameters/{any}
         Rephrase as follows:

    "Each element information item found in [reference parameters]
    (including all of its [children], [attributes] and [in-scope
    namespaces]) is represented as is."

3. Section 3, 3rd paragraph after editorial note, last sentence:
    Rephrase as follows:
          "The contract between the interacting parties may specify that 
multiple or even a variable number of replies be delivered."
4. Section 3, description of [fault endpoint]. Rephrase to eliminate "to 
to" in,
    "the sender MUST use the contents of the [fault endpoint], when
    present, of the message being replied to to formulate the fault
    message."

5. Section 3.1, "Example 3-1"?
    The contents of  "Example 3-1" are actually "XML Infoset 
representation of message addressing properties".
     Don't call it an "Example".

6. Section 3.1 /[reference parameters]* is not shown in XML Infoset 
representation of message addressing properties in "Example 3-1"

7. Section 3.1 /[reference parameters]* description. Rephrase as follows:
    "Each element information item found in [reference parameters] 
(including all of its [children], [attributes] and [in-scope 
namespaces]) is represented as is."

         
Received on Wednesday, 6 April 2005 00:14:56 GMT

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