NEW Issue: Definition of CurrentContext

[Alastair Green <alastair.green@choreology.com>]

Issue name -- WS-C: More precise definition of /CreateCoordinationContext/CurrentContext

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:  WS-C

Artifact:  spec

Draft:

WS-C spec initial working draft uploaded 

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:

ll. 238-240


Issue type:

Editorial


Related issues:

Issues 018 - 021, relating to meaning of CurrentContext


Issue Description:

Make precise statement on meaning (at WS-C level) of /CreateCoordinationContext/CurrentContext. The presence of this element has no meaning other than: a relationship of some kind is being created between an existing context and a new context.


Issue Details:

In the course of discussions leading to resolution of issues 018 - 021, it seemed that differing interpretations and assumptions were likely when considering the meaning of the presence of the CurrentCoordinationContext element in the CreateCoordinationContext message. For example: under some circumstances (sub-coordination for an atomic outcome protocol) one might consider that the new and existing contexts were representations of the same overall activity (the atomic transaction tree). In that case, and in others, the presence of the relationship might subsequently be expressed in the sending of Register to the RS of the existing (current) context. However, in principle, the statement of relationship might be expressed in ways that do not involve use of Register.


Proposed Resolution:

The attached document, drafted by Max Feingold as a result of discussions on the 018-021 AI, seems like the right kind of wording, in the light of the above.

2006-03-21.proposed.resolution.CC.definition.doc