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

Re: i007: new proposal for discussion (was Re: Issue 7 convo from Melbourne)

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Tue, 1 Mar 2005 12:15:01 -0500
Message-Id: <c04b0aaab6241228341aaac0815b78e8@bea.com>
Cc: public-ws-addressing@w3.org
To: Hugo Haas <hugo@w3.org>

Modified Proposal:

1. Make the [reference parameters] message addressing property’s XML 
Infoset representation in Core’s section 3.1 the following, which was 
the second rule of the SOAP binding:

     /[reference parameters]*

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

2. Define a wsa:isRefParameter attribute information item of type 

3. Define the following as the first rule of the SOAP binding when 
_sending_ a message:

     3.1. All the message addressing properties are serialized as SOAP
        header blocks using their XML Infoset representation defined in
        Core section 3.1 XML Infoset Representation of Message
        Addressing Properties.

   3.2. Each SOAP header block resulting from a [reference parameters] 
is annotated with a wsa:isRefParameter attribute whose value is “true”.

4. Add the following rules when _receiving_ a SOAP message:

    4.1. The value of each message addressing property takes the value 
from the corresponding SOAP header block in the wsa namespace targeted 
at the node which matches the XML Infoset representation described in 
Core section 3.1.

5. Add the following note:

Note that the message addressing properties gathered by an intermediary 
when receiving a SOAP message do not necessarily get replayed as MAPs 
when resending the message along the message path.
Received on Tuesday, 1 March 2005 17:15:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:28:24 UTC