This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 687 - Clearly differentiate a performed choreography vs. an imported definition.
Summary: Clearly differentiate a performed choreography vs. an imported definition.
Status: RESOLVED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Requires Clarification (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Greg Ritzinger
QA Contact:
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-20 09:57 UTC by Greg Ritzinger
Modified: 2004-12-01 16:47 UTC (History)
0 users

See Also:


Attachments

Description Greg Ritzinger 2004-04-20 09:57:11 UTC
Section 2.5.3
1. Please more clearly differentiate a performed choreography vs. an 
imported definition, as the former could be defined outside of the 
enclosing choreography or package. This in essence is an import.
2. As it relates to enclosing choreographies, what overrides are allowed 
if at all. What happens if conditions, parameters, constraints conflict? 
(relates to assumptions
for import).
3. In the F2F in March 2004, we indicated we did not acknowledge 
'dependent' choreographies (the blue boxes) that exist in the package or 
root (blue box). How then can we handle dependencies between imported, 
performed and choreographies with root=false?
Comment 1 Martin Chapman 2004-05-20 14:07:12 UTC
1. editors to clarify to say that performed choreographies decalred outside the 
package must be imported first
2. same as import issues
3. request clarification from originator (Monica) and a small example will help.
Comment 2 Greg Ritzinger 2004-09-07 17:33:39 UTC
1 - fixed
2 - fixed
3 - needs clarifaction