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.
ID | Product | Comp | Assignee | Status | Resolution | Summary | Opened | Changed |
---|---|---|---|---|---|---|---|---|
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 |
276 | WS Chore | Spec | martin.chapman | RESO | FIXE | Where does Web Services Choregraphy ground? | 2003-07-15 | 2004-03-23 |
281 | WS Chore | Spec | steve | RESO | WONT | MEP as a simple choreography | 2003-07-29 | 2004-03-24 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
516 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Do we need 3 levels of abstraction for choreographies? | 2004-02-03 | 2004-03-04 |
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 |
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 |
564 | WS Chore | Spec | gritzinger | RESO | WONT | Section 3.4.2.1 - Clarify verbiage | 2004-02-23 | 2004-10-11 |
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 |
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 |
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 |
622 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Explain what a common viewpoint is | 2004-03-23 | 2004-04-26 |
626 | WS Chore | Spec | gritzinger | RESO | WONT | CDL - Collaboration Types | 2004-03-23 | 2004-05-18 |
628 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Definition of Choreograpy Transaction | 2004-03-23 | 2004-05-18 |
630 | WS Chore | Spec | gritzinger | RESO | FIXE | CDL - Editorial - Editors List | 2004-03-23 | 2004-05-18 |
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 |
667 | WS Chore | Spec | gritzinger | RESO | DUPL | No Notifcation and Sollicite-Response will be needed/allowed? | 2004-04-13 | 2004-05-18 |
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 |
721 | WS Chore | Spec | martin.chapman | RESO | FIXE | Lack of a conformance clause | 2004-05-21 | 2005-01-04 |
723 | WS Chore | Spec | martin.chapman | RESO | WONT | Channels and Channel Ends | 2004-05-21 | 2004-09-09 |
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 |
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 |
867 | WS Chore | Spec | martin.chapman | RESO | WONT | There are currently two mechanisms for performing assignment. | 2004-09-07 | 2004-09-30 |
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 |
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 |
886 | WS Chore | Spec | martin.chapman | RESO | FIXE | Catch All does not exist for an Exception | 2004-09-15 | 2004-09-30 |
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 |
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 |
935 | WS Chore | Spec | martin.chapman | RESO | INVA | Clarification on interaction identifying an operation | 2004-11-08 | 2004-11-08 |
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 |
1175 | WS Chore | Spec | martin.chapman | RESO | WONT | Mandatory reference token in channels | 2005-03-21 | 2005-06-20 |
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 |