Issue 018 - WS-C: split out of 002 a) - Distinguish example from normative, for subordinated CreateCoordinationContext behaviour

["Peter Furniss" <peter.furniss@choreology.com>]

This is hereby identified as ws-tx issue 018.

Please follow up to this message or otherwise ensure your subject line
starts "Issue 018 - " 
  (after any Re:, [ws-tx] etc)

Alastair pointed out his original message referred to 007 when it should
have said 002. I have corrected the misreferences below.

========================================================================
==============


Issue name -- WS-C: Split out 002 a) -- Distinguish example from 
normative, for subordinated CreateCoordinationContext behaviour

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:

002, 019, 020, 021


Issue Description:

This issue separates out sub-issue a) of Issue 002, 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.