OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-tx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue 073 - WS-BA: Message definitions


This is identified as WS-TX issue 073.

 

Please ensure follow-ups have a subject line starting "Issue 073 - WS-BA: Message definitions".

 

From: Peter Furniss [mailto:peter.furniss@erebor.co.uk]
Sent: Thursday, June 29, 2006 5:28 PM
To: ws-tx@lists.oasis-open.org
Subject: [ws-tx] WS-BA: Message definitions

 

Issue name -- WS-BA: Message definitions

 

PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS
ASSIGNED A NUMBER.

 

The issues coordinator will notify the list when that has occurred.

 

Target document and draft:

 

Protocol:  WS-BA

 

Artifact:  spec

 

Draft:  BA spec cd 2

 

Link to the document referenced:

 

 

Section and PDF line number:  section , lines

 


Issue type:  editorial

 


Related issues:

 

New issue: definition of Compensated

 

Issue Description:

 

The message definitions in 3.1 should be defined from the perspective of the sender,
not the receiver.

 

Issue Details

 

The message definitions in 3.1 are given from the perspective of the receiver. Although
this is appropriate in terms of describing a (one-way) WSDL interface, it really the wrong
way round to describe the semantics of the messages. The meaning of a message is
better understood in terms of what it says about the sender - who has typically just
undergone a state change, rather than what can be inferred by the receiver.

 

Some of the messages are also defined in the glossary – however, cancel and close are
there defined as actions, and the others as messages in terms of the sender (as
suggested for 3.1). Not all messages/actions are covered in the glossary.

 


Proposed resolution

 

Standardize the description of the messages, and in 3.1 express this primarily from the perspective of the sender.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]