This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This archived bug list includes all the bugs for the product or component specified, including bugs that have been resolved.
- Product: WS Choreography
334 bugs found.
| ID | Product | Comp | Assignee | Status | Resolution | Summary | Opened | Changed |
|---|---|---|---|---|---|---|---|---|
| 220 | WS Chore | Requirem | steve | RESO | FIXE | Correlation | 2003-06-10 | 2004-03-04 |
| 267 | WS Chore | Requirem | steve | RESO | WONT | Specific Language for Describing MEPs | 2003-07-15 | 2004-03-23 |
| 268 | WS Chore | Uncatego | martin.chapman | RESO | FIXE | Formalism Task Force | 2003-07-15 | 2003-07-15 |
| 269 | WS Chore | Uncatego | martin.chapman | RESO | FIXE | Evaluate Inputs Listed in Charter | 2003-07-15 | 2003-07-15 |
| 270 | WS Chore | Spec: Na | martin.chapman | RESO | FIXE | Party Identify in an Interaction | 2003-07-15 | 2004-08-24 |
| 271 | WS Chore | Spec | martin.chapman | RESO | WONT | Choreography States | 2003-07-15 | 2004-03-24 |
| 272 | WS Chore | Spec | martin.chapman | RESO | WONT | State Exposure | 2003-07-15 | 2004-03-24 |
| 273 | WS Chore | Spec | martin.chapman | RESO | FIXE | Enforcement of a Choreography | 2003-07-15 | 2004-03-04 |
| 274 | WS Chore | Spec: Co | steve | CLOS | WONT | Communication of State Change | 2003-07-15 | 2005-01-04 |
| 275 | WS Chore | Uncatego | martin.chapman | RESO | DUPL | Expand WSDL | 2003-07-15 | 2004-01-08 |
| 276 | WS Chore | Spec | martin.chapman | RESO | FIXE | Where does Web Services Choregraphy ground? | 2003-07-15 | 2004-03-23 |
| 280 | WS Chore | Requirem | steve | RESO | WONT | Semantics of messages | 2003-07-29 | 2017-01-01 |
| 281 | WS Chore | Spec | steve | RESO | WONT | MEP as a simple choreography | 2003-07-29 | 2004-03-24 |
| 282 | WS Chore | Uncatego | martin.chapman | RESO | FIXE | Our time lines are constrained by the WSDL progress | 2003-07-29 | 2004-03-04 |
| 302 | WS Chore | Uncatego | martin.chapman | RESO | WONT | What do we mean by external process choreography | 2003-08-27 | 2004-03-04 |
| 303 | WS Chore | Uncatego | martin.chapman | RESO | WONT | What do we mean by internal process choreography? | 2003-08-27 | 2004-03-04 |
| 304 | WS Chore | Requirem | steve | RESO | WONT | what do users actually need? | 2003-08-27 | 2004-03-04 |
| 305 | WS Chore | Requirem | steve | RESO | WONT | Is this group about internal, extrenal, or both aspects of a business process? | 2003-08-27 | 2004-03-04 |
| 306 | WS Chore | Spec | martin.chapman | RESO | WONT | Is a choreography defintion exectutable? | 2003-08-27 | 2004-03-04 |
| 307 | WS Chore | Spec | martin.chapman | RESO | FIXE | What is the difference (if any) between choreography and orchestration? | 2003-08-27 | 2004-03-04 |
| 308 | WS Chore | Requirem | steve | RESO | FIXE | Reusable choreographies and data formats | 2003-08-27 | 2004-03-04 |
| 309 | WS Chore | Uncatego | martin.chapman | RESO | DUPL | should choreographies be enforced? | 2003-08-27 | 2004-01-08 |
| 310 | WS Chore | Requirem | steve | RESO | FIXE | Do we encode time into choreographies? | 2003-08-27 | 2004-03-04 |
| 311 | WS Chore | Requirem | steve | RESO | WONT | Storing and retreiving choreographies | 2003-08-27 | 2004-03-04 |
| 312 | WS Chore | Requirem | steve | RESO | FIXE | Can actual partipants in a choreography change during the lifetime of a choreography | 2003-08-27 | 2004-03-04 |
| 313 | WS Chore | Spec | martin.chapman | RESO | FIXE | What is our formal underpinning? | 2003-08-27 | 2004-03-04 |
| 314 | WS Chore | Spec | martin.chapman | RESO | FIXE | how are decisions expressed in a choreography | 2003-08-27 | 2004-03-04 |
| 315 | WS Chore | Uncatego | martin.chapman | RESO | FIXE | Is a choreography a contract? | 2003-08-27 | 2004-03-04 |
| 316 | WS Chore | Requirem | steve | RESO | FIXE | is negotiation part of the choreography language or should it be modelled as a choreography? | 2003-08-27 | 2004-03-04 |
| 317 | WS Chore | Requirem | steve | RESO | FIXE | Do all participants need to be known in advance? | 2003-08-27 | 2004-03-04 |
| 318 | WS Chore | Uncatego | martin.chapman | RESO | DUPL | how are state changes (e.g. new participant join) communicated? part of the choreography infrastructure or built into a choreography? | 2003-08-27 | 2004-01-08 |
| 319 | WS Chore | Spec | martin.chapman | RESO | FIXE | should transport "signals" be modelled in a choreography? | 2003-08-27 | 2004-03-04 |
| 320 | WS Chore | Spec | martin.chapman | RESO | DUPL | how do you compose two web services together? | 2003-08-27 | 2004-01-08 |
| 321 | WS Chore | Spec | martin.chapman | RESO | FIXE | Is a choreography an MEP? | 2003-08-27 | 2004-03-23 |
| 322 | WS Chore | Uncatego | martin.chapman | RESO | DUPL | How much state needs to be exposed? | 2003-08-27 | 2004-01-08 |
| 323 | WS Chore | Uncatego | martin.chapman | RESO | DUPL | what states do we need to distinguish, and what ones do choreography have to describe? | 2003-08-27 | 2004-01-08 |
| 324 | WS Chore | Uncatego | martin.chapman | RESO | FIXE | what does validation mean for a choreography language? | 2003-08-27 | 2004-03-04 |
| 325 | WS Chore | Spec: Fo | martin.chapman | RESO | FIXE | Is a choreography itself a web service (i.e has a wsdl interface)? | 2003-08-27 | 2004-08-24 |
| 326 | WS Chore | Uncatego | martin.chapman | RESO | FIXE | What is the lifecycle of a choreography? | 2003-08-27 | 2004-03-23 |
| 332 | WS Chore | Requirem | steve | RESO | WONT | What do we mean by semantics of web services and what are they for. | 2003-09-03 | 2004-03-04 |
| 333 | WS Chore | Requirem | steve | RESO | FIXE | We need a choreography protocol use case. | 2003-09-03 | 2004-03-04 |
| 342 | WS Chore | Requirem | steve | RESO | FIXE | Turing complete or not turing complete | 2003-09-16 | 2004-03-04 |
| 431 | WS Chore | Requirem | steve | RESO | FIXE | Security as related to specifying policy and/or assertions. | 2003-12-16 | 2004-03-04 |
| 432 | WS Chore | Requirem | steve | RESO | FIXE | CSF-004 - not addressed in requirements use cases | 2003-12-16 | 2004-03-04 |
| 433 | WS Chore | Requirem | steve | RESO | FIXE | Can there be a choreography with no web services? | 2003-12-16 | 2004-03-04 |
| 434 | WS Chore | Primer | martin.chapman | RESO | LATE | concrete use case to show differences between BPEL abstract processes and WS-CDL | 2003-12-16 | 2005-07-14 |
| 435 | WS Chore | Uncatego | martin.chapman | RESO | FIXE | Intermediaries | 2003-12-16 | 2004-03-04 |
| 436 | WS Chore | Requirem | steve | RESO | FIXE | Transaction capability in CDL | 2003-12-16 | 2004-03-04 |
| 464 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | CDL - Flesh out section on structured references | 2004-01-20 | 2004-12-01 |
| 465 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | CDL - DocumentReferece should be a URI, not URL | 2004-01-20 | 2004-09-07 |
| 466 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | CDL - Seems to imply that all messages handles by the choreography are SOAP | 2004-01-20 | 2004-09-07 |
| 467 | WS Chore | Spec | gritzinger | RESO | WONT | CDL - WSDL port types are mentioned as example of physical structure | 2004-01-20 | 2004-04-19 |
| 468 | WS Chore | Spec | gritzinger | RESO | WONT | CDL - The table lists the "Message Structure" and "Technology used" entries for Portable as "Defined". | 2004-01-20 | 2004-04-19 |
| 469 | WS Chore | Spec: Im | gritzinger | RESO | FIXE | CDL - "Import" is a concept used in XML Schema, WSDL and BPEL. | 2004-01-20 | 2004-09-30 |
| 470 | WS Chore | Spec | gritzinger | RESO | WONT | CDL - A Concrete Channel Type is defined to be the same as Portable Channel Type | 2004-01-20 | 2004-04-19 |
| 471 | WS Chore | Spec: Co | gritzinger | RESO | FIXE | CDL - At run time new information is added to a Concrete Interaction Channel Variable. | 2004-01-20 | 2004-09-30 |
| 472 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Are abstract choreographies worth the effort? | 2004-01-20 | 2004-03-04 |
| 473 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - ability to handle legacy web service | 2004-01-20 | 2004-03-04 |
| 474 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - benefit of having an 'active' choreography mechanism that is required to manage its own state | 2004-01-20 | 2004-04-19 |
| 475 | WS Chore | Requirem | martin.chapman | RESO | FIXE | Is fork/join covered as requirements | 2004-01-20 | 2004-03-04 |
| 476 | WS Chore | Requirem | martin.chapman | RESO | DUPL | Is external/internal choice is covered as requirements? | 2004-01-20 | 2004-01-20 |
| 484 | WS Chore | Spec: Im | gritzinger | RESO | WONT | CDL - Issue CCI-01 | 2004-01-23 | 2004-09-30 |
| 485 | WS Chore | Spec: Im | gritzinger | RESO | FIXE | CDL - Issue CCI-02 | 2004-01-23 | 2004-09-30 |
| 486 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | CDL - Issue TVT-01 | 2004-01-23 | 2004-08-12 |
| 487 | WS Chore | Spec | steve | RESO | FIXE | CDL - Issue TVT-02 | 2004-01-23 | 2004-12-01 |
| 488 | WS Chore | Spec | gritzinger | RESO | WONT | CDL - Issue I-01 | 2004-01-23 | 2004-04-19 |
| 489 | WS Chore | Spec: Co | gritzinger | CLOS | FIXE | CDL - Issue I-02 | 2004-01-23 | 2005-01-04 |
| 490 | WS Chore | Spec: Ex | gritzinger | RESO | WONT | CDL - Issue I-03 | 2004-01-23 | 2004-12-01 |
| 491 | WS Chore | Spec: Va | gritzinger | RESO | WONT | CDL - Issue I-04 | 2004-01-23 | 2004-08-12 |
| 492 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Issue ACS-01 | 2004-01-23 | 2004-05-18 |
| 493 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Issue ACS-02 | 2004-01-23 | 2004-09-30 |
| 494 | WS Chore | Spec: Ex | gritzinger | RESO | FIXE | CDL - Issue CET-01 | 2004-01-23 | 2004-08-24 |
| 495 | WS Chore | Spec: Ex | gritzinger | RESO | FIXE | CDL - Issue CET-02 | 2004-01-23 | 2004-08-24 |
| 496 | WS Chore | Spec: Ex | gritzinger | RESO | WONT | CDL - Issue CET-03 | 2004-01-23 | 2004-08-11 |
| 497 | WS Chore | Spec: Ex | gritzinger | RESO | FIXE | CDL - Issue CET-04 | 2004-01-23 | 2004-08-24 |
| 498 | WS Chore | Spec: Va | gritzinger | RESO | WONT | CDL - Issue CET-05 | 2004-01-23 | 2004-08-12 |
| 499 | WS Chore | Spec: Re | gritzinger | RESO | WONT | CDL - Issue CET-06 | 2004-01-23 | 2004-09-30 |
| 500 | WS Chore | Spec: Ex | gritzinger | RESO | FIXE | CDL - Issue CET-07 | 2004-01-23 | 2010-12-24 |
| 506 | WS Chore | Spec: Re | gritzinger | CLOS | WONT | CDL - Identifying Choreographies | 2004-01-23 | 2005-01-04 |
| 516 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Do we need 3 levels of abstraction for choreographies? | 2004-02-03 | 2004-03-04 |
| 550 | WS Chore | Spec: Co | martin.chapman | RESO | FIXE | Should we support wsdl 1.1 | 2004-02-20 | 2004-09-16 |
| 552 | WS Chore | Spec | martin.chapman | CLOS | LATE | State alignment | 2004-02-23 | 2005-07-14 |
| 553 | WS Chore | Spec | gritzinger | RESO | WONT | BPEL | 2004-02-23 | 2004-04-19 |
| 554 | WS Chore | Spec | gritzinger | CLOS | FIXE | QOS, reliability and security | 2004-02-23 | 2005-01-04 |
| 555 | WS Chore | Spec: Co | martin.chapman | RESO | FIXE | Dependency to other technologies - Section 3.5.3 | 2004-02-23 | 2004-12-01 |
| 556 | WS Chore | Spec: Co | gritzinger | CLOS | FIXE | Dependency to other technologies - Section 3.5.6 | 2004-02-23 | 2005-01-04 |
| 557 | WS Chore | Spec: Co | gritzinger | RESO | DUPL | Dependency to other technologies - Section 2.3 | 2004-02-23 | 2004-12-01 |
| 558 | WS Chore | Spec | gritzinger | RESO | DUPL | Dependency to other technologies - Section 2.4 | 2004-02-23 | 2004-04-26 |
| 559 | WS Chore | Spec | gritzinger | RESO | FIXE | Abstract CDL | 2004-02-23 | 2004-03-04 |
| 560 | WS Chore | Spec | gritzinger | RESO | FIXE | Transactions | 2004-02-23 | 2004-04-26 |
| 561 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | Import | 2004-02-23 | 2005-07-14 |
| 562 | WS Chore | Spec: Ed | gritzinger | RESO | WONT | Section 3.4.1.2 - Role changes may dictate constraints on the definition of channels | 2004-02-23 | 2004-09-07 |
| 563 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | Business Semantic - Variable values | 2004-02-23 | 2005-01-04 |
| 564 | WS Chore | Spec | gritzinger | RESO | WONT | Section 3.4.2.1 - Clarify verbiage | 2004-02-23 | 2004-10-11 |
| 565 | WS Chore | Spec: Ex | gritzinger | RESO | FIXE | Section 3.5 - Interactions and exceptions | 2004-02-23 | 2004-12-01 |
| 566 | WS Chore | Primer | gritzinger | ASSI | --- | Section 3.6 - Work Unit | 2004-02-23 | 2007-03-29 |
| 569 | WS Chore | Spec | gritzinger | RESO | DUPL | Number of abstraction levels in the language specification | 2004-02-24 | 2004-03-04 |
| 607 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL Figure 2: Doesn't recognize the potential value of integration within an | 2004-03-23 | 2004-04-26 |
| 608 | WS Chore | Spec | gritzinger | RESO | INVA | CDL - Resolve issue on abstract combination into portable and concrete | 2004-03-23 | 2004-04-26 |
| 609 | WS Chore | Spec: Im | gritzinger | RESO | FIXE | CDL - May be importing or 'receiving' rules outside of the choreography | 2004-03-23 | 2004-09-30 |
| 610 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | CDL - "Relationship" not within WS_CHOR 's scope | 2004-03-23 | 2004-09-30 |
| 611 | WS Chore | Spec: Im | gritzinger | RESO | FIXE | CDL - Import dependency on rules | 2004-03-23 | 2004-09-30 |
| 612 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | CDL - Business process failures outside of the scope of WS-Chor | 2004-03-23 | 2004-09-30 |
| 613 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Explain how an assign can be made within only one role when the choreography should be recognizing all parties in the interaction | 2004-03-23 | 2004-04-26 |
| 614 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | CDL - A control mechanism that indicates a Finalization WorkUnit must complete before a parent choreography | 2004-03-23 | 2004-09-30 |
| 615 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | CDL - Explain example in section 3.0 | 2004-03-23 | 2004-12-01 |
| 616 | WS Chore | Spec | gritzinger | RESO | WONT | CDL - Hold on extensibility until we know how this will be accommodated in WSDL 2.0 | 2004-03-23 | 2004-04-26 |
| 617 | WS Chore | Spec | gritzinger | RESO | DUPL | CDL - Import does not address dependencies, priority or impacts/conflicts | 2004-03-23 | 2004-04-26 |
| 618 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Clarify description of Role construct | 2004-03-23 | 2004-04-26 |
| 619 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Relationship / Channel clarification or correction | 2004-03-23 | 2004-05-21 |
| 620 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | CDL - How can we allow non-visible behavior (Variables)? | 2004-03-23 | 2004-09-07 |
| 621 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | CDL - Explain what a ChoreographyNotation is | 2004-03-23 | 2004-12-01 |
| 622 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Explain what a common viewpoint is | 2004-03-23 | 2004-04-26 |
| 623 | WS Chore | Spec: Re | martin.chapman | RESO | FIXE | CDL - Editorial - Suggested editorial changes. | 2004-03-23 | 2004-12-01 |
| 624 | WS Chore | Requirem | gritzinger | RESO | WONT | CDL - Definition of Choreography and CDL | 2004-03-23 | 2005-12-12 |
| 625 | WS Chore | Spec: Fo | gritzinger | RESO | WONT | CDL - Precision of Specification | 2004-03-23 | 2004-08-24 |
| 626 | WS Chore | Spec | gritzinger | RESO | WONT | CDL - Collaboration Types | 2004-03-23 | 2004-05-18 |
| 627 | WS Chore | Spec: In | gritzinger | RESO | FIXE | CDL - MEP support | 2004-03-23 | 2004-12-01 |
| 628 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Definition of Choreograpy Transaction | 2004-03-23 | 2004-05-18 |
| 629 | WS Chore | Spec: Va | gritzinger | RESO | FIXE | CDL - Variable definition | 2004-03-23 | 2004-09-30 |
| 630 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Editorial - Editors List | 2004-03-23 | 2004-05-18 |
| 631 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | CDL - Editorial - 4th paragraph of Introduction section | 2004-03-23 | 2004-09-07 |
| 632 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Editorial - figure 1 | 2004-03-23 | 2004-05-18 |
| 633 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Editorial - section 1.4 | 2004-03-23 | 2004-05-18 |
| 634 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Editorial - Section 3. example | 2004-03-23 | 2004-05-18 |
| 635 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Editorial - WSDL example | 2004-03-23 | 2004-05-18 |
| 636 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Editorial - Section 4 | 2004-03-23 | 2004-05-18 |
| 661 | WS Chore | Spec: Na | gritzinger | RESO | WONT | Adding partnerType and roleType to the language model | 2004-04-13 | 2004-12-01 |
| 662 | WS Chore | Spec: Le | gritzinger | RESO | FIXE | specify at least two levels or types of Choreography description | 2004-04-13 | 2004-12-01 |
| 663 | WS Chore | Primer | gritzinger | RESO | DUPL | The specification should contain the basic underlying model of the | 2004-04-13 | 2005-12-12 |
| 664 | WS Chore | Primer | gritzinger | NEW | --- | Add UML diagram to primer along with textual description | 2004-04-13 | 2015-10-05 |
| 665 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | Concrete WSDL defined by each participant must built on this abstract WSDL? | 2004-04-13 | 2004-12-01 |
| 666 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | Why specify a message type in the interaction? | 2004-04-13 | 2004-09-07 |
| 667 | WS Chore | Spec | gritzinger | RESO | DUPL | No Notifcation and Sollicite-Response will be needed/allowed? | 2004-04-13 | 2004-05-18 |
| 668 | WS Chore | Spec: Co | gritzinger | RESO | WONT | The granularity at which isAligned() can be used is too big | 2004-04-13 | 2004-10-05 |
| 677 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | proprietary terminology used | 2004-04-19 | 2004-09-07 |
| 678 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | If you are going to use a registry reference you should specify | 2004-04-19 | 2004-10-05 |
| 679 | WS Chore | Spec | gritzinger | RESO | FIXE | application integration in Figure 1 | 2004-04-19 | 2004-05-18 |
| 680 | WS Chore | Spec | gritzinger | RESO | DUPL | No explicit references provided for abstract and concrete | 2004-04-19 | 2004-05-18 |
| 681 | WS Chore | Spec | gritzinger | RESO | DUPL | Import and overwritten objects | 2004-04-19 | 2004-05-18 |
| 682 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | Element visibility | 2004-04-19 | 2004-10-05 |
| 683 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | Clarify that the reference with support from tokens, token types, etc. | 2004-04-19 | 2005-01-04 |
| 684 | WS Chore | Spec: Re | gritzinger | RESO | INVA | Variable and role assumptions | 2004-04-19 | 2004-10-05 |
| 686 | WS Chore | Spec: Re | gritzinger | RESO | DUPL | Need to address concerns on reuse before assessing against recovery | 2004-04-20 | 2004-10-11 |
| 687 | WS Chore | Spec: Re | gritzinger | RESO | FIXE | Clearly differentiate a performed choreography vs. an imported definition. | 2004-04-20 | 2004-12-01 |
| 688 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | Schema element attribute values need to be in quotes | 2004-04-20 | 2004-09-07 |
| 691 | WS Chore | Spec: Va | martin.chapman | RESO | FIXE | Locally defined variables: Structure: How are locally defined variables defined when they are not consistent between roles that participate in the choreography? | 2004-04-26 | 2005-01-04 |
| 692 | WS Chore | Spec: Va | martin.chapman | RESO | WONT | Types, variables and tokens: Dual variable objects are for different purposes in the abstract and portable context. | 2004-04-26 | 2004-08-12 |
| 693 | WS Chore | Spec: Va | martin.chapman | RESO | FIXE | Variable combinations (Issue TVT-02) | 2004-04-26 | 2004-12-01 |
| 709 | WS Chore | Spec: Ed | gritzinger | RESO | FIXE | In namespace table in Section 1.1 Notational Conventions: | 2004-05-10 | 2012-10-26 |
| 721 | WS Chore | Spec | martin.chapman | RESO | FIXE | Lack of a conformance clause | 2004-05-21 | 2005-01-04 |
| 722 | WS Chore | Spec: Va | martin.chapman | RESO | DUPL | Use of participants for scoping | 2004-05-21 | 2004-12-01 |
| 723 | WS Chore | Spec | martin.chapman | RESO | WONT | Channels and Channel Ends | 2004-05-21 | 2004-09-09 |
| 724 | WS Chore | Spec: Va | martin.chapman | RESO | FIXE | Editorial | 2004-05-21 | 2005-01-04 |
| 741 | WS Chore | Primer | martin.chapman | ASSI | --- | Semantics examples needed | 2004-05-24 | 2005-12-12 |
| 742 | WS Chore | Spec: Va | martin.chapman | RESO | FIXE | Maybe we should look at existential qualifiers | 2004-05-24 | 2004-09-28 |
| 743 | WS Chore | Primer | gritzinger | NEW | --- | Examples in the CDL specification and the Primer | 2004-05-24 | 2015-10-05 |
| 753 | WS Chore | Spec: Na | martin.chapman | RESO | WONT | Replace 'interaction' with 'interact' | 2004-05-28 | 2004-12-01 |
| 779 | WS Chore | Spec | martin.chapman | RESO | WONT | Participants aren't explicitly used anywhere | 2004-06-01 | 2004-09-09 |
| 780 | WS Chore | Spec | martin.chapman | RESO | WONT | "Roles within Roles". Can one have a role within a role? | 2004-06-01 | 2004-09-09 |
| 781 | WS Chore | Requirem | martin.chapman | RESO | WONT | Delegation Use Case (The Agent Acting On Behalf) | 2004-06-01 | 2004-09-09 |
| 782 | WS Chore | Spec: In | martin.chapman | RESO | FIXE | Exchanges & MEPs. We will need to explore this relationship. | 2004-06-01 | 2004-12-01 |
| 783 | WS Chore | Spec: In | martin.chapman | RESO | FIXE | Relationships (1:1 behaviour?) | 2004-06-01 | 2004-09-28 |
| 792 | WS Chore | Spec: Na | martin.chapman | RESO | WONT | Change <reference> to <serviceReference> | 2004-06-10 | 2004-12-01 |
| 839 | WS Chore | Spec: Ed | martin.chapman | RESO | WONT | Description of WS Choreography:Spec component contains a typo: 'Choreograpghy' | 2004-08-17 | 2004-09-09 |
| 846 | WS Chore | Spec: St | martin.chapman | RESO | FIXE | The defining characteristic of a Participant | 2004-08-24 | 2004-12-01 |
| 849 | WS Chore | Spec: Na | martin.chapman | RESO | DUPL | The defining characteristic of a Participant | 2004-08-27 | 2004-09-09 |
| 850 | WS Chore | Spec | martin.chapman | RESO | DUPL | Conformance Statements in CDL | 2004-08-27 | 2004-12-01 |
| 853 | WS Chore | Spec | martin.chapman | RESO | WONT | We need InputChannelVariable, OutputChannelVariable, FaultChannelVariable | 2004-08-31 | 2004-09-09 |
| 854 | WS Chore | Spec | martin.chapman | RESO | WONT | Requirements for rules governing endpoint generation both in the absence and presence of WSDL | 2004-08-31 | 2004-09-09 |
| 855 | WS Chore | Spec: In | martin.chapman | RESO | FIXE | Investigate the solicit-response and notification in WSDL 1.0 and WDSL 2.0 | 2004-08-31 | 2004-12-01 |
| 867 | WS Chore | Spec | martin.chapman | RESO | WONT | There are currently two mechanisms for performing assignment. | 2004-09-07 | 2004-09-30 |
| 868 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | There is unnecessary redundancy in the syntax of the 'assign' activity. | 2004-09-07 | 2004-09-30 |
| 869 | WS Chore | Spec: St | martin.chapman | RESO | WONT | There is no explicit mechanism for defining a repeating set of activities. | 2004-09-07 | 2004-09-29 |
| 870 | WS Chore | Spec | martin.chapman | RESO | WONT | The current reactive mechanism is complex because it introduces implicit links. | 2004-09-07 | 2004-12-01 |
| 871 | WS Chore | Spec: Ne | martin.chapman | RESO | LATE | The current 'composition/perform' mechanism does not enable complex choreographies to be composed. | 2004-09-07 | 2005-07-14 |
| 872 | WS Chore | Part 2 ( | martin.chapman | ASSI | --- | Support for overcoming race conditions, other than by using variables. | 2004-09-07 | 2005-12-12 |
| 883 | WS Chore | Spec | martin.chapman | RESO | FIXE | There is no mechanism to define the absence of any work (nop) in CDL | 2004-09-15 | 2004-09-30 |
| 884 | WS Chore | Spec | martin.chapman | RESO | FIXE | There is no mechanism to obtain/set in CDL of the reference/identity of channel variable | 2004-09-15 | 2004-09-30 |
| 885 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | Concept of "global time" or the absense of it and how we work around this | 2004-09-15 | 2004-12-01 |
| 886 | WS Chore | Spec | martin.chapman | RESO | FIXE | Catch All does not exist for an Exception | 2004-09-15 | 2004-09-30 |
| 897 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | Move contents in WS-CDL Functions section into the body of the specification. | 2004-09-28 | 2004-10-25 |
| 898 | WS Chore | Spec: Va | martin.chapman | RESO | FIXE | How can a variable become unavailable? | 2004-09-28 | 2004-12-01 |
| 899 | WS Chore | Spec: Na | martin.chapman | RESO | FIXE | silentAction attribute in variableDefinition shuld be renamed | 2004-09-29 | 2004-12-01 |
| 901 | WS Chore | Spec | martin.chapman | RESO | FIXE | Raise the allowed isolation level of nested choreographies as an issue. | 2004-10-05 | 2004-12-01 |
| 913 | WS Chore | Primer | martin.chapman | RESO | WONT | Clarification on workunit guard projectionI understand the role of the globalizedTrigger, to provide a guard condition for each role that is relevant to a work unit.However, if a work unit does not use a globalizedTrigger, and the guard condition is re... | 2004-10-12 | 2004-12-01 |
| 916 | WS Chore | Spec: Va | martin.chapman | RESO | FIXE | If a "free" variable in an enclosed choreography is not BOUND then what is the variable's status? | 2004-10-12 | 2004-12-01 |
| 923 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | No explanation of "action" and "new" in channel type defns2.3.4 Channel Types<channelType name="ncname" usage="once"|"unlimited"? action="request-respond"|"request"|"respond"? > <passing channel="qname" action="request-respond"|"request... | 2004-10-25 | 2004-12-01 |
| 927 | WS Chore | Spec | martin.chapman | RESO | FIXE | Removing the attribute root on a Choreography definition | 2004-10-28 | 2004-12-01 |
| 928 | WS Chore | Spec | martin.chapman | RESO | FIXE | ParticipantType and RoleType implementation restrictions are outside the scope of WS-CDL | 2004-10-28 | 2004-12-01 |
| 929 | WS Chore | Spec: Ed | martin.chapman | CLOS | WONT | CDL order of interpretation is not clearly defined. | 2004-10-28 | 2005-01-04 |
| 930 | WS Chore | Spec: In | martin.chapman | CLOS | WONT | Correlating separate channel instances to a choreography instance | 2004-10-29 | 2005-01-04 |
| 935 | WS Chore | Spec | martin.chapman | RESO | INVA | Clarification on interaction identifying an operation | 2004-11-08 | 2004-11-08 |
| 937 | WS Chore | Spec: Ed | martin.chapman | RESO | WONT | include description at 2.4.6 overuses word "Choreography" | 2004-11-09 | 2005-01-04 |
| 938 | WS Chore | Spec | martin.chapman | RESO | WONT | Support for sub-choreography being performed concurrently with multiple participants | 2004-11-09 | 2005-01-04 |
| 939 | WS Chore | Spec | martin.chapman | RESO | FIXE | Boolean conditions | 2004-11-09 | 2005-01-04 |
| 940 | WS Chore | Spec | martin.chapman | RESO | DUPL | Correlating separate channel instances to a choreography instance | 2004-11-09 | 2004-11-16 |
| 943 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | RFC 2119 terminology usage | 2004-11-16 | 2005-01-04 |
| 944 | WS Chore | Spec: St | martin.chapman | RESO | DUPL | CDL does not support a choreography which needs to *concurrently* perform multiple instances of a sub-choreography against multiple participants | 2004-11-16 | 2004-12-01 |
| 945 | WS Chore | Spec: Ed | martin.chapman | RESO | FIXE | Section 2.4.9.1 - typo, says "getGlobalizedTrigger" instead of "globalizedTrigger". | 2004-11-16 | 2004-12-01 |
| 946 | WS Chore | Spec: Va | martin.chapman | RESO | FIXE | Section 2.5.2.3 - record element, target variable attribute. | 2004-11-16 | 2004-12-01 |
| 947 | WS Chore | Spec: St | martin.chapman | RESO | FIXE | CDL does not contain any mechanisms to detect whether a timeout actually occurred or not | 2004-11-17 | 2005-01-04 |
| 957 | WS Chore | Last Cal | ylafon | CLOS | FIXE | XHTML Compliance | 2004-12-20 | 2005-08-03 |
| 958 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Normative sections and References | 2004-12-20 | 2005-08-02 |
| 959 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Namespace name | 2004-12-20 | 2005-05-10 |
| 960 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Notation/Psuedo Schema | 2004-12-20 | 2005-05-10 |
| 961 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Informal vs Formal Definition | 2004-12-20 | 2005-08-02 |
| 962 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Different visual blocks per example | 2004-12-20 | 2005-08-02 |
| 963 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Different styles for syntax and examples | 2004-12-20 | 2005-08-03 |
| 964 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | cdl namespace prefix | 2004-12-20 | 2005-05-10 |
| 965 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | XML Well-formedness | 2004-12-20 | 2005-08-02 |
| 966 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Editorial in References | 2004-12-20 | 2005-08-03 |
| 967 | WS Chore | Last Cal | ylafon | CLOS | LATE | Ambiguity in the spec | 2004-12-20 | 2005-08-03 |
| 968 | WS Chore | Last Cal | ylafon | CLOS | FIXE | CDL MIME Type | 2004-12-20 | 2005-09-28 |
| 969 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Xpath name | 2004-12-20 | 2005-08-02 |
| 970 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | example domain | 2004-12-20 | 2005-08-02 |
| 971 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Break up section 2 | 2004-12-20 | 2005-08-02 |
| 972 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | getVariable usage | 2004-12-20 | 2005-08-02 |
| 973 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Extension Wording | 2004-12-20 | 2005-09-28 |
| 977 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Finalization text | 2004-12-21 | 2005-08-02 |
| 996 | WS Chore | Last Cal | martin.chapman | CLOS | LATE | CDL Last Call comment - Choice of response message in WSDL | 2005-01-10 | 2005-05-17 |
| 997 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | some minor editorial comments | 2005-01-10 | 2005-09-28 |
| 998 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | State that sequential lexically ordering is the default for interpretation of CDL | 2005-01-10 | 2005-05-17 |
| 999 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Short Circuit Evaluation | 2005-01-10 | 2005-08-03 |
| 1000 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | CDL 'ROLE' FUNCTIONS | 2005-01-10 | 2005-08-02 |
| 1001 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | CORRELATION OF CHANNEL INSTANCES | 2005-01-10 | 2005-09-28 |
| 1002 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | RELATIONSHIP BETWEEN RELATIONSHIP TYPES | 2005-01-10 | 2005-05-10 |
| 1003 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | RELINGUISHING CONTROL OF PASSED OUTPUT CHANNELS | 2005-01-10 | 2005-09-28 |
| 1004 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | WORKUNIT GUARD CONDITION SEMANTICS | 2005-01-10 | 2005-08-02 |
| 1005 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | WORKUNIT REPETITION | 2005-01-10 | 2005-08-02 |
| 1006 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | RECORD REFERENCE (in Interaction) RESTRICTION | 2005-01-10 | 2005-05-12 |
| 1007 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | CHOICE WITH MIXTURE OF BLOCKING AND NON-BLOCKING ELEMENTS | 2005-01-10 | 2005-09-28 |
| 1008 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | FAULT HANDLING | 2005-01-10 | 2005-08-02 |
| 1014 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity- Section 2.1, 1st bullet, last sentence | 2005-01-20 | 2005-07-18 |
| 1015 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity - Section 2.2.3, 5th paragraph. | 2005-01-20 | 2005-07-18 |
| 1016 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity - Section 2.2.3, 6th paragraph | 2005-01-20 | 2005-07-18 |
| 1017 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Point of clarity - Section 2.2.4, Title | 2005-01-20 | 2005-07-18 |
| 1018 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Information model - Section 2.3.2, 2nd last paragraph | 2005-01-20 | 2005-08-03 |
| 1019 | WS Chore | Last Cal | martin.chapman | RESO | DUPL | Point of clarity - Section 2.3.2, 2nd last paragraph | 2005-01-20 | 2005-08-03 |
| 1020 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Information model - Section 2.3.2, last paragraph, 1st sentence | 2005-01-20 | 2005-07-18 |
| 1021 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Point of clarity - Section 2.3.3, 3rd paragraph, 2nd sentence | 2005-01-20 | 2005-07-18 |
| 1022 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Point of clarity - Section 2.3.3, 3rd paragraph, 2nd sentence | 2005-01-20 | 2005-07-18 |
| 1023 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Question on constraint - Section 2.3.3, 3rd paragraph, last sentence | 2005-01-20 | 2005-08-03 |
| 1024 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Missing descriptive text - Section 2.3.4, 5th last paragraph | 2005-01-20 | 2005-07-18 |
| 1025 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Information model - Section 2.3.4, 4th last paragraph | 2005-01-20 | 2005-07-18 |
| 1026 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Information model - Section 2.3.4, 3rd last paragraph, last sentence | 2005-01-20 | 2005-07-18 |
| 1027 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Question on constraint - Section 2.3.4, 2nd last paragraph, 1st sentence | 2005-01-20 | 2005-08-03 |
| 1028 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Missing descriptive text on Information model - Section 2.4.2, 1st paragraph | 2005-01-20 | 2005-07-18 |
| 1029 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity - Section 2.4.3.1, 1st function, 1st sentence | 2005-01-20 | 2005-07-18 |
| 1030 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity - Section 2.4.3.1, 2nd function, 1st sentence | 2005-01-20 | 2005-07-18 |
| 1031 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity - Section 2.4.3.1, 3rd function, 1st sentence | 2005-01-20 | 2005-07-18 |
| 1032 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity - Section 2.4.3.1, 4th function, 1st sentence | 2005-01-20 | 2005-07-18 |
| 1033 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Point of clarity - Section 2.4.3.1, 9th function, 1st sentence | 2005-01-20 | 2005-08-03 |
| 1034 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Point of clarity - Section 2.4.3.1, 2nd last function, 1st sentence | 2005-01-20 | 2005-07-18 |
| 1035 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Point of clarity - Section 2.5.2.3, 11th paragraph, 3rd bullet | 2005-01-20 | 2005-07-18 |
| 1036 | WS Chore | Last Cal | martin.chapman | CLOS | DUPL | Point of clarity - Section 2.5.2.3, 11th paragraph, 4th bullet | 2005-01-20 | 2005-07-14 |
| 1037 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Comments of editorial nature | 2005-01-20 | 2005-07-18 |
| 1038 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Section 3 is Incomplete | 2005-01-20 | 2005-07-18 |
| 1039 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Section 8 is Incomplete | 2005-01-20 | 2008-12-02 |
| 1053 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Define the bindings between related concepts in WS-CDL and WS-Addressing | 2005-01-25 | 2005-07-18 |
| 1054 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | An old version of WS-Addressing specification Abstract is quoted | 2005-01-25 | 2005-07-18 |
| 1055 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | The purpose of the createNewID function does not seem clear | 2005-01-25 | 2005-08-02 |
| 1062 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Section 2.4.7 does not describe whether the 'complete' could cause the premature completion of a finalizer | 2005-01-27 | 2005-08-02 |
| 1063 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Finalization of an enclosed choreography when exception occurs | 2005-01-27 | 2005-08-02 |
| 1064 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | WSDL dilemma about outbound operations not fully resolved | 2005-01-27 | 2005-07-18 |
| 1066 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Section 2.2.5 Semantics, working towards solidifying two items | 2005-01-31 | 2010-10-12 |
| 1067 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Section 2.4.2 Be specific about when the information is available | 2005-01-31 | 2005-08-02 |
| 1068 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | How are the blocking guard condition semantics would be projected to BPEL? | 2005-01-31 | 2005-09-28 |
| 1074 | WS Chore | Last Cal | martin.chapman | CLOS | DUPL | Language Extensibility and Binding - suggested change to an Extensions rule | 2005-02-07 | 2005-05-10 |
| 1075 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Channel Types - attribute "usage" should be made an Element | 2005-02-07 | 2005-08-02 |
| 1076 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Information Exchange Capturing Variables Definition | 2005-02-07 | 2005-08-02 |
| 1077 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Add enforcement level to the silent action specification | 2005-02-07 | 2005-05-26 |
| 1078 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Marking the Absence of Actions - reword section to better relate to what actions are not performed | 2005-02-07 | 2005-08-02 |
| 1079 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Interaction Syntax - successul-sending and properly-received are not clearly defined | 2005-02-07 | 2005-12-12 |
| 1084 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | State the relationship between WS-CDL and the UN/CEFACT Modeling Methodology | 2005-02-07 | 2005-08-02 |
| 1086 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Clarify which role ref/refs is/are valid in XML schema | 2005-02-07 | 2005-08-03 |
| 1088 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Clarify Variable and Token Information Type usage | 2005-02-07 | 2005-08-02 |
| 1092 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | State relationship between WS-CDL and ebBP | 2005-02-07 | 2005-08-02 |
| 1093 | WS Chore | Last Cal | martin.chapman | CLOS | DUPL | How would the blocking guard condition semantics would be projected to BPEL? | 2005-02-07 | 2005-08-03 |
| 1094 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | 2.3.4. Overall. (editorial) | 2005-02-07 | 2005-08-02 |
| 1095 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | 2.3.4. Para "The value of Variables:". (editorial) | 2005-02-07 | 2005-08-02 |
| 1096 | WS Chore | Last Cal | martin.chapman | CLOS | INVA | 2.3.4. The last two paragraphs, about "roleType" attribute. (needs clarification) | 2005-02-07 | 2005-08-02 |
| 1097 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | 2.4.4. The first para. (editorial) | 2005-02-07 | 2005-08-02 |
| 1098 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | 2.4.5. The second para, last sentence. (editorial) | 2005-02-07 | 2005-08-02 |
| 1099 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Specify that the evaluation of the guard expression is done in a fixed order | 2005-02-07 | 2005-09-28 |
| 1100 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | Decompose workunit construct into "loop", "conditional" and "workunit" | 2005-02-07 | 2005-05-12 |
| 1101 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | The operational behaviour involving "complete condition" is not clear | 2005-02-07 | 2005-08-02 |
| 1102 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Combine Finalizer blocks etc. in their corresponding workunits | 2005-02-07 | 2005-08-02 |
| 1103 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | 2.5.2.1. Interaction Based Information Alignment (editorial) | 2005-02-07 | 2005-08-02 |
| 1104 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | 2.5.2.3, Interaction Syntax, exchange element. (editorial) | 2005-02-07 | 2005-08-02 |
| 1105 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | 2.5.2.3. Interaction Syntax, record element. (editorial / clarification) | 2005-02-07 | 2005-08-02 |
| 1106 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | 2.5.4. Assigning Variables, the second para. (editorial) | 2005-02-07 | 2005-08-02 |
| 1107 | WS Chore | Last Cal | gritzinger | CLOS | FIXE | Mapping of roles and binding of variables (needs clarification) | 2005-02-07 | 2005-08-02 |
| 1108 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Isolated sub-choreography terminates unsuccessfully (needs clarification) | 2005-02-07 | 2005-09-28 |
| 1109 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Remote reads with cdL:getVariable (clarification) | 2005-02-07 | 2005-08-02 |
| 1110 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | When a copy expression references a variable that has not been set, what should happen? | 2005-02-07 | 2005-08-02 |
| 1126 | WS Chore | Last Cal | martin.chapman | CLOS | WONT | usage of 'time' within CDL | 2005-02-14 | 2005-08-02 |
| 1128 | WS Chore | Last Cal | steve | CLOS | WONT | Accessing and modifying members of lists and arrays | 2005-02-22 | 2005-09-28 |
| 1129 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Extending Choreographies | 2005-02-22 | 2005-05-17 |
| 1166 | WS Chore | Last Cal | martin.chapman | CLOS | LATE | Handling an arbitrary number of concurrent flows | 2005-03-09 | 2005-08-03 |
| 1175 | WS Chore | Spec | martin.chapman | RESO | WONT | Mandatory reference token in channels | 2005-03-21 | 2005-06-20 |
| 1176 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Workunit inside an exception handler | 2005-03-21 | 2005-07-26 |
| 1177 | WS Chore | Spec | martin.chapman | RESO | WONT | Mandatory reference token in channels | 2005-03-22 | 2005-12-12 |
| 1178 | WS Chore | Spec | martin.chapman | RESO | DUPL | Workunit inside an exception handler | 2005-03-22 | 2005-07-14 |
| 1455 | WS Chore | Primer | steve | ASSI | --- | Interaction Syntax - successul-sending and properly-received are not clearly defined | 2005-05-17 | 2005-12-12 |
| 1456 | WS Chore | Primer | steve | ASSI | --- | Accessing and modifying members of lists and arrays | 2005-05-17 | 2005-12-12 |
| 1457 | WS Chore | Primer | steve | ASSI | --- | Question on constraint - Section 2.3.4, 2nd last paragraph, 1st sentence | 2005-05-17 | 2011-08-16 |
| 1459 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | We should clearly state in the spec that nested isolation choreographies are not permitted | 2005-05-17 | 2005-08-02 |
| 1486 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Use of rns: and tns: namespace prefixes in example | 2005-05-27 | 2005-08-02 |
| 1493 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Ordering of activities in finalization | 2005-06-13 | 2005-08-02 |
| 1496 | WS Chore | Last Cal | martin.chapman | CLOS | FIXE | Making explicit the session mechanism | 2005-06-14 | 2005-09-28 |
| 1503 | WS Chore | Primer | steve | ASSI | --- | Accessing and modifying members of lists and arrays | 2005-06-20 | 2005-12-12 |
| 1831 | WS Chore | Last Cal | martin.chapman | RESO | WONT | Use of "capturing" to describe certain variables | 2005-08-03 | 2005-09-28 |
| 2360 | WS Chore | Primer | martin.chapman | ASSI | --- | Section 4.2 says: A relationshipType identifies the roleTypes and behaviors, where mutual commitments between two parties MUST be made for collaborations to be successful. However, you indicate in Section 3.1 that relationshipType MAY only be used in ... | 2005-10-18 | 2005-12-12 |
| 3101 | WS Chore | Implemen | martin.chapman | RESO | FIXE | hasChoreographyCompleted | 2006-04-11 | 2006-07-18 |
| 3102 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Perform bind variable types | 2006-04-11 | 2006-07-18 |
| 3103 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Choice | 2006-04-11 | 2006-07-18 |
| 3104 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Exchange type | 2006-04-11 | 2006-07-18 |
| 3105 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Service endpoint projection | 2006-04-11 | 2006-08-08 |
| 3106 | WS Chore | Implemen | martin.chapman | RESO | REMI | Channel Passing | 2006-04-11 | 2006-08-01 |
| 3107 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Multipart variable with single part | 2006-04-11 | 2006-08-01 |
| 3108 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Activity names | 2006-04-11 | 2006-08-01 |
| 3109 | WS Chore | Implemen | martin.chapman | RESO | REMI | hasExchangeOccurred | 2006-04-11 | 2006-08-01 |
| 3110 | WS Chore | Implemen | martin.chapman | RESO | FIXE | description element | 2006-04-11 | 2006-08-01 |
| 3111 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Recursive performs | 2006-04-11 | 2006-08-01 |
| 3484 | WS Chore | Implemen | martin.chapman | RESO | WONT | working mode of enclosed choreography while finalizing | 2006-07-18 | 2008-12-02 |
| 3568 | WS Chore | Implemen | martin.chapman | RESO | REMI | Participants without roles, roles without behaviour | 2006-08-01 | 2008-12-02 |
| 3569 | WS Chore | Implemen | martin.chapman | RESO | WONT | It is impossible to compare QNames | 2006-08-01 | 2006-08-08 |
| 3570 | WS Chore | Implemen | martin.chapman | RESO | FIXE | add optional name to token locator | 2006-08-01 | 2006-08-01 |
| 3571 | WS Chore | Implemen | martin.chapman | RESO | WONT | optional query for TokenLocator | 2006-08-01 | 2006-08-08 |
| 3588 | WS Chore | Implemen | martin.chapman | RESO | WONT | channel passing example | 2006-08-08 | 2007-03-20 |
| 3843 | WS Chore | Implemen | martin.chapman | RESO | FIXE | Redundant 'initiate' flag on interaction | 2006-10-17 | 2008-12-02 |
| 3901 | WS Chore | Implemen | martin.chapman | RESO | WONT | Notification Message Exchange Type | 2006-10-31 | 2007-03-06 |
| 24472 | WS Chore | Spec: Ne | martin.chapman | NEW | --- | bdsm toilet pain slave | 2014-02-02 | 2014-02-02 |
