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

issue 038 - my action item

From: Francisco Curbera <curbera@us.ibm.com>
Date: Wed, 5 Jan 2005 16:08:13 -0500
To: <public-ws-addressing@w3.org>
Message-ID: <OFE5D7FE37.096777A5-ON85256F80.006CFB75-85256F80.00741BF8@us.ibm.com>

Here is a first pass at the text to clarify the scope of message properties
issue. The idea is to state that many contracts are possible between the
parties, not only WSDL interfaces, and that the contract is an important
element in deciding when to use the properties. The text tries to be
generic when speaking about properties; a special mention about replies is

The text I propose below adds a few sentences to the beginning of Section 3
in the core spec. Changes are marked <pc>...</pc>. Please comment.



This section defines the information model and syntax of message addressing
Message addressing properties enable the identification and location of the
endpoints involved in an interaction. <pc>The use of these properties to
support specific interaction is in general defined by both the semantics of
the properties themselves and the implicit or explicit contract that
governs the message exchange. If explicitly available, this contract can
take different forms including but not being limited to WSDL MEPs and
interfaces; business processes and e-commerce specifications, among others,
can also be used to define explicit contracts between the parties.</pc>

The basic interaction pattern from which all others are composed is "one
way". In this pattern a source sends a message to a destination without any
further definition of the interaction. "Request Reply" is a common
interaction pattern that consists of an initial message sent by a source
endpoint (the request) and a subsequent message sent from the destination
of the request back to the source (the reply). A reply <pc>in this
case</pc> can be either an application message, a fault, or any other
message. <pc>Note, however, that reply messages may be sent as part of
other message exchanges as well, and are not restricted to the usual single
Request, single Reply pattern, or to a particular WSDL MEP. The contract
between the interacting parties may specify that multiple or even a
variable number or replies be delivered.</pc>

Message addressing properties collectively augment a message with the
following abstract properties to support one way, request reply, and any
other interaction pattern:
Received on Wednesday, 5 January 2005 21:08:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:08 UTC