270 Leave open (related to coordination protocol) 271,272 candidates for deletion (have been changed to resolved, wontfix) Issue 274: how are state changes (e.g. new participant join) communicated? part of the choreography infrastructure or built into a choreography? Can't answer issue at the moment so remains open. Issue 276, 281: Can answer clearly with contents of specification: close as resolved, fixed but with note note to spec editors to ensure meps/choreos and recursion grounding are well explained Issue 267: Do we need a specific language for describing MEPs? we will only address a choreo language not an MEP one. Resolve, Wontfix. Issue 321. A choreo is not an MEP. resolved/fixed Issue 325: kevin may have commented on this. feeling that this has been rsolved but leave open for the moment Issue 326. What is the lifecycle of a choreo? Resolved w/ note to spec editors, ensure editors discuss the lifecycle Issues464 to 474 assigned to editors group issue 464: editorial: applies to section 2.2.4 of edit copy 03 apr 2004 assign to editors. issue 465: same section as issue 464 (2.2.4) editorial: agreed to make it a uri: assign to editors issue 466: in 2.5.2.4 remove implied or normative referneces to SOAP and add text to say whatever protocols wsdl can support or describe. change to resolved/fixed issue 467: does not apply in the cdl spec (03 apr 2004), so will depend on what happens to model overview. change to resolved/wontfix issue 468: does not apply in the cdl spec (03 apr 2004), so will depend on what happens to model overview. change to resolved/wontfix issue 469: intention is for import to be the same as schema, wsdl, bpel etc (section 2.4.6.2 03apr 2004). If overriding is required then a new concept needs to be added (issue number xx. change to Resolved/fixed issue 470: does not apply in the cdl spec (03 apr 2004), so will depend on what happens to model overview. change to resolved/wontfix issue 471: reexamine section 2.5.2.4 of editors copy 03 apr 2004. accept and assign (default). issue 474: was resolved at f2f or con call after (check with SRT). change to resolved/fix issue 484: changed to depends on 469 issue 485: accept and assign (default) issue 486: accept and assign (default) issue 487: add editoral comment that guards cannot have arithementic expression on varaibles in different roles. assign to editors issue 488: does not apply in the cdl spec (03 apr 2004), so will depend on what happens to model overview. change to resolved/wontfix issue 489: accept and assign to nick issue 490: accept and assign (default) issue 491: accept and assign (default) issue 492: repeat mechanism should cover this, assign to David. issue 493: perform with aliasing should cover this, assign to David issue 494: work units should cover this, assign to david issue 495: work units should cover this, assign to david issue 496: accept and assign (default) issue 497: accept and assign (default) issue 498: accept and assign (default) issue 499: accept and assign to nick (clarify issue) issue 500: already covered in cdl, but editorial comment is required. assign to editors issue 506: accept and assign david issue 553: does not apply in the cdl spec (03 apr 2004), so will depend on what happens to model overview. change to resolved/wontfix issue 554: accept and assign (default) Issue 555: Dependency to other technologies - Section 3.5.3: apr 3 version of ws-cdl does contain referneces to ongpoing standrds work, so we need to examine this as we get closer to finalising the spec. accept and assign to martin. Issue 556: Dependency to other technologies - Section 3.5.6: accept as issue as it also relates to the cdl spec and mark as being dependant on issue 555 Issue 557: Dependency to other technologies - Section 2.3: accept as issue and mark as dependant on 554. Issue 558: Dependency to other technologies - Section 2.4: dupl of 555 Issue 560: Transactions: We have agreed that transactions are in our scope, but we have other open issues as to the level of detail. Resolve/Fixed. Issue 561: Import: Accept as issue and assign to default. but greg to break other embedded issues Issue 562: Section 3.4.1.2 - Role changes may dictate constraints on the definition of channels: The rules of what can change at runtime are clear (i.e only ednpoint addessing changes), but may need some editorial clarification. Assign to editors. Issue 563: Business Semantic - Variable values: This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica). Issue 564: Section 3.4.2.1 - Clarify verbiage: relates to model ovewview text as so is dependapt on what happened to the model overview document. Issue 565: Section 3.5 - Interactions and exceptions: This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica). Issue 566: Section 3.6 - Work Unit: This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica) Issue 607: CDL Figure 2: Doesn't recognize the potential value of integration within an : made more explicit in apr 3 cdl version. mark as Resolved/fix. Issue 608: CDL - Resolve issue on abstract combination into portable and concrete: not an issue recoird as resolved/invalid Issue 609: CDL - May be importing or 'receiving' rules outside of the choreography: mark as dependant on issue 561. Issue 610: CDL - "Relationship" not within WS_CHOR 's scope: This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica) Issue 611: CDL - Import dependency on rules. accept and mark as dependant on 561. Issue 612: CDL - Business process failures outside of the scope of WS-Chor. for part a This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica). part b is banana calc and we already have work in progess. Issue 613: CDL - Explain how an assign can be made within only one role when the choreography should be recognizing all parties in the interaction: Section 2.4.2 explains this mark as resolved/invalid. Issue 614: CDL - A control mechanism that indicates a Finalization WorkUnit must complete before a parent choreography: This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica) Issue 615: CDL - Explain example in section 3.0: This issue is not clear to us, request clarification within the context of the apr 3 cdl spec from orignator (monica) Issue 616: CDL - Hold on extensibility until we know how this will be accommodated in WSDL 2.0: ws-cdl extensibility can be in addition to wsdl extenibikity. Resolve/Wontfix. Issue 617: CDL - Import does not address dependencies, priority or impacts/conflicts: mark as dupl of 561 Issue 618: CDL - Clarify description of Role construct: process type dose not exist in apr 3 version . Resolved/fixed. Issue 619: CDL - Relationship / Channel clarification or correction: This has been re-written in apr 03 edition, originator needs to check new text. Issue 620: CDL - How can we allow non-visible behavior (Variables)?: non-observable behavior of a partipant can be defined, as described in section 2.5.5 apr 3 edition, but agreed some editorial fixes needed. Accept and assign to editors. Issue 621: CDL - Explain what a ChoreographyNotation is: The use of notation terminology is used throughout and needs group discussion. Accept and assign to editors Issue 622: CDL - Explain what a common viewpoint is: viewpoint element has been removed. Resolve/Fixed. Issue 623: CDL - Editorial - Suggested editorial changes. accept and assign to editors. Issue 624: CDL - Definition of Choreography and CDL: apr 3 edition updted the definition. Resolved/fixed. Issue 625: CDL - Precision of Specification: accept and assign default, also reword to focus issue on infoset question. issue 626: CDL - Collaboration Types. the three levels do not exist in 03 apr draft. Resolve/wontfix issue 627: CDL - MEP support. still and issue, assign(deafult) issue 628: CDL - Definition of Choreography Transaction. Already done. Resolved/fixed issue 629: CDL - Variable definition. probably editorial. Accept (default) issue 630: CDL - Editorial - Editors List. fixed in public wd 27-apr 04 issue 631: CDL - Editorial - 4th paragraph of Introduction section. accept and assign to editorial team issue 632: CDL - Editorial - figure 1. figure removed in 27-apr 04 wd. resolved fixed issue 633: CDL - Editorial - section 1.4. fixed in 27-apr 04 wd. resolved fixed issue 634: CDL - Editorial - Section 3. example not in latest, 27 apr 04 wd. resolved fixed issue 635: CDL - Editorial - WSDL example. example not in latest, 27 apr 04 wd. resolved fixed issue 636: CDL - Editorial - Section 4. fixed in 27-apr-04. resolved fixed. issue 661: Adding partnerType and roleType to the language model. accept/default issue 662: specify at least two levels or types of Choreography description. accept, assign issue 663: The specification should contain the basic underlying model of the language (uml). accept, assign/default. issue 664: Add UML diagram to primer along with textual description. Primer issue accept, assign/default issue 665: Concrete WSDL defined by each participant must built on this abstract WSDL? seek clarification from issue raiser. issue 666: Why specify a message type in the interaction? needs to be verified. accept and assign default. issue 667: No Notification and Solicit-Response will be needed/allowed? dupl of 627. issue 668: The granularity at which isAligned() can be used is too big. accept and assign default. issue 677: proprietary terminology used. assign to editors. issue 678: If you are going to use a registry reference you should specify. assign to editors. issue 679: application integration in Figure 1. fixed in 27 apr 04 wd, resolved/fixed. issue 680: No explicit references provided for abstract and concrete. dupl of 662 issue 681: Import and overwritten objects. dupl of 561 Issue 682: Element visibility. request clarification from issue raiser (Monica) issue 683: Clarify that the reference with support from tokens, token types, etc. Assign to editors Issue 684: Variable and role assumptions. request clarification from issue raiser (Monica), a small example would help Issue 686: Need to address concerns on reuse before assessing against recovery. request clarification from issue raiser (Monica), a small example would help Issue 687: Clearly differentiate a performed choreography vs. an imported definition. 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. Issue 688: Schema element attribute values need to be in quotes. Accept and assign to editors. Issue 709: In namespace table in Section 1.1 Notational Conventions: assign to editors