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

Re: Mixed notation and indirect terminology for MAPs (SOAP, clarification)

From: Marc Hadley <Marc.Hadley@Sun.COM>
Date: Thu, 05 May 2005 14:07:03 -0400
To: Jonathan Marsh <jmarsh@microsoft.com>
Cc: public-ws-addressing@w3.org
Message-id: <95bb937119c7f8923a7aa82dd583beb4@Sun.COM>

I believe that this is captured as issue 28 and that we closed this  
during the last con-call by accepting Jonathan's proposal with some  
discretion for the editors to tidy up the language (I note that the  
issue is not shown as closed in the issues list however). Inline below  
is the text I've put into the spec.

> The primary definition of the WS-A properties is in the Core, using the
> [property] notation, not in the SOAP Feature which assigns each of  
> these
> properties a URI.  The notation in Section 3.3 below mixes these two
> notations in referring to WS-A properties. Since the [property]  
> notation
> is primary, we suggest referring to the primary definition directly and
> using the [property] notation.  The notation also refers to these
> properties as SOAP 1.2 WS-Addressing 1.0 Feature properties instead of
> WS-Addressing 1.0 Message Addressing Properties, which exhibits the  
> same
> problem of unnecessary levels of indirection.
>
> Change the following sentence:
>
>   'When a message is to be addressed to an endpoint, the values of the
>   SOAP 1.2 WS-Addressing 1.0 Feature properties are mapped to the
>   message as SOAP header blocks with the following additional
>   modifications:'
>
> to read (also incorporating the changes requested at
> http://lists.w3.org/Archives/Public/public-ws-addressing-comments/ 
> 2005Ap
> r/0026.html):
>
>   'When a message is to be addressed to an endpoint, the XML
>   representation of each non-empty WS-Addressing 1.0 Message Addressing
>   Property is inserted into the message as a SOAP header block subject
>   to the following additional constraints:'
>
>

Spec: "When a message is to be addressed to an endpoint, the XML  
Infoset representation of each specified message addressing property is  
inserted into the message as a SOAP header block subject to the  
following additional constraints:"

> Change the first bullet in Section 3.3, which states:
>
>   'The value of the
>   http://www.w3.org/@@@@/@@/addressing/feature/ReferenceParameters
>   property is added to the SOAP message header.'
>
> to read:
>
>   'The value of the [reference parameters] property is added to the
>   SOAP message header.'
>
>

Spec: "The value of the [reference parameters] property is added to the  
SOAP message header: the element information item of each of the  
[reference parameters] (including all of its [children], [attributes]  
and [in-scope namespaces]) is added as a SOAP header block in the new  
message."

> Change the third bullet in Section 3.3, which states:
>
>   'Each property that is of type IRI MUST be serialized as an absolute
>   IRI in the SOAP message.'
>
> to read (also incorporating the changes requested at
> http://lists.w3.org/Archives/Public/public-ws-addressing-comments/ 
> 2005Ap
> r/0026.html):
>
>   'Each property that is of type IRI MUST be serialized as an absolute
>   IRI in the corresponding XML Infoset representation of that Message
>   Addressing Property.'

Spec: "The value of each message addressing property that is of type  
IRI MUST be serialized as an absolute IRI in the corresponding SOAP  
header block."

Note that the first paragraph above already talks about using the XML  
Infoset representation so there's no need to repeat that in the  
paragraph above.

Marc.

---
Marc Hadley <marc.hadley at sun.com>
Business Alliances, CTO Office, Sun Microsystems.
Received on Thursday, 5 May 2005 18:07:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:05 GMT