[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW Issue: WS-C: Split out 007 a) -- Distinguish example from normative,for subordinated CreateCoordinationContext behaviour
Issue name -- WS-C: Split out 007 a) -- Distinguish example from normative, for subordinated CreateCoordinationContext behaviour 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 Draft: Coord spec working draft uploaded 2005-12-02 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 3 "Coordination Service", ll. 181-209 Issue type: Design / editorial Related issues: None Issue Description: This issue separates out sub-issue a) of Issue 007, which can be found here: http://www.oasis-open.org/apps/org/workgroup/ws-tx/email/archives/200512/msg00059.html Precisely specify normative behaviour of CreateCoordinationContext against existing (superior) context Issue Details: [This issue stems from Choreology Contribution issue TX-17.] The initial part of Section 3 (up to and inluding the diagram, Figure 2., on p. 10) uses an example to convey three things: a) the basic interactions of a registering application service and a Registration Service, and their relationship to Coordinators and Participants b) the notion of an interposed Coordinator, and c) some seemingly normative rules relating to how interposed coordination works. It should be made clear what is exemplification, and what is normative. It is possible that the exposition of basic (C-P) and interposed (C-P/C-P) behaviours may be easier to grasp with two successive and related examples. These are primarily editorial matters. In the proposed resolution I will call this sub-issue a). Proposed Resolution: Editorial work required to clarify example, and accompanying figure, and to create a section that describes the model and normative operation of sub-coordination.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]