This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Example in 3.0 We determined in F2F that subchoreographies or dependent choreographies did not exist and that we only saw the red not the blue boxes. Please explain example then in this section.
This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica)
clarification from Monica: The inclusion of <alias> addresses some of the original question. See Section 2.5.3 in most recent draft. There seem to be two parts of the discussion: a. Use of a performed choreography or an enclosing choreography with enclosed choreographies. b. A composition where one choreography (not a fragment) may need to succeed before another choreography can complete. See Section 2.4.6.1 where the CustomerNotifyChoreo is enclosed in the PurchaseChoreo. Could there be rules that specify the CustomerNotifyChoreo cannot occur unless it in the PurchaseChoreo? Is this a dependency that is created and a constraint applies. If you look at that example, there is a guard that applies to get PO acknowledgment from warehouse before the customer is notified. This is similar to the condition I reference. In this case, you would not have typically sent a customer notification unless an order was occurring.My question still is do we allow this constraint to be applied which limits where the choreography can be used. I am not indicating this is specific to the isolation raised in the call today 7 Sept. This issue does, however, relate to the composition proposal provided by Enigmatic.
question boils down to can one nest choreos: <choreo A> .... <choreo B> .... <\choreo B> perform<choreo B> <\choreo A> i.e. b cannot be perfomred outside of a?