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: NEW issue: WS-C: Remove fault 4.4. NoActivity


Issue name -- WS-C: Remove fault 4.4. NoActivity

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

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

Target document and draft:

Protocol:  Coord

Artifact:  spec / schema

Draft:

Coord spec working draft uploaded 2005-12-02
WS-Coordination schema contributed by input authors, not yet uploaded to 
Working Drafts folder

Link to the document referenced:

http://www.oasis-open.org/committees/download.php/15738/WS-Coordination-2005-11-22.pdf

Section and PDF line number:

Section 4.4 "No Activity", ll. 443-450


Issue type:

Design


Related issues:

Issue [] WS-C: Appropriate categories of fault


Issue Description:

NoActivity fault is not basic to all conceivable coordination protocols.


Issue Details:

[This issue stems from Choreology Contribution issue TX-19.]

Faults in WS-C should be divided into two categories: those which apply 
to the process of context creation and
registration (or which apply to the misuse of the conversational channel 
created by registration), and those
which are basic faults available to all coordination protocols.

NoActivity is not truly basic or general to all coordination protocols.

The preamble of this fault (l1. 444-445) states:

"This fault is sent by the coordinator if the participant has been quiet 
for too long and is presumed to have
ended."

Such a semantic is most unlikely to be useful for all coordination 
protocols. Indeed, WS-AT and WS-BA use
entirely different means to terminate the coordinator's relationship 
with a participant. They have no concept
of a "divorce heuristic". A future coordination protocol that does have 
such a concept should define its own
message to carry this semantic.

The Reason (l. 449) "The participant is not responding and is presumed 
to have ended." shows the same defect.


Proposed Resolution:

Remove ll. 443-450 of the specification.
Remove l. 104 of the schema document.



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