W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2004

i038 - Scope of message addressing properties

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Tue, 7 Dec 2004 09:49:09 -0800
Message-ID: <DD35CC66F54D8248B6E04232892B6338042A6380@RED-MSG-43.redmond.corp.microsoft.com>
To: <public-ws-addressing@w3.org>

Issue i038[1] is about the scope of the various WS-Addressing message
properties. Specifically, are they scoped to a WSDL operation or is
their scope potentially wider? Much of the discussion[2] so far (which
was actually about issue 28[3]) has focused on the [reply endpoint]
property and the corresponding wsa:ReplyTo header block.

The approach I'm going to take here is to examine each of the
WS-Addressing properties in turn and make some observations about their
usage and scope as it relates to messages and WSDL operations.

1.	[destination] (wsa:To)

Scope: Message(s)
Notes: Over time many messages may have the same value for this
property; it's scope is the set of messages with that same value. This
set of messages may span multiple WSDL operations.

2.	[source endpoint] (wsa:From)

Scope: Unbounded
Notes: Over time many messages may have the same value for this
property. However, unlike [destination] it's scope is not just the
messages it appears in, rather it is unbounded. The recipient of a
message containing this property may send messages to this endpoint
outside of the exchange of which the current message is part. Such
additional messages may span multiple WSDL operations.

3.	[reply endpoint] (wsa:ReplyTo)

Scope: Unbounded
Notes: Over time many messages may have the same value for this
property. However, unlike [destination] it's scope is not just the
message it appears in, rather is unbounded. The recipient of a message
containing this property may send messages to this endpoint outside of
the exchange of which the current message is part provided they are
correlated to the initial message via the [relationship] property. Such
additional messages may span multiple WSDL operations.

4.	[fault endpoint] (wsa:FaultTo)

Scope: Single operation
Notes: Over time many messages may have the same value for this
property. However, for any given message the scope of this property is
the current message exchange. The recipient of a message containing this
property may send a single fault message to the specified endpoint as
part of the current exchange. This fault message must be correlated to
the initial message in the exchange via the [relationship] property.

5.	[action] (wsa:Action)

Scope: Message(s)
Notes: Over time many messages may have the same value for this
property; it's scope is the set of messages with that same value. This
set of messages may span multiple WSDL operations.

6.	[message id] (wsa:MessageId)

Scope: Message
Notes: This property has a value unique to each message; it's scope is
that message. 

7.	[relationship] (wsa:RelatesTo)

Scope: Message(s)
Notes: Over time many messages may have the same value for this
property; it's scope is the set of messages with that same value. This
set of messages may span multiple WSDL operations.

Hope this is a reasonable stab at the issue, hopefully it will help us
get to closure

Cheers

Gudge

[1] http://www.w3.org/2002/ws/addr/wd-issues/#i038
[2]
http://lists.w3.org/Archives/Public/public-ws-addressing/2004Nov/0295.ht
ml
[3] http://www.w3.org/2002/ws/addr/wd-issues/#i028
Received on Tuesday, 7 December 2004 17:49:13 GMT

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