| W3C Web Services Choreography working group | |||||||||||||||
| Use case summary | |||||||||||||||
| 8th April 2003 | |||||||||||||||
| Use case or just useful (X) | Author | Date | Description | uri | |||||||||||
| X | Tony Fletcher | 18/3/03 | 3 scopes not 2: Not actually a use case but useful anyway | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0076.html | |||||||||||
| X | Jon Dart | 24/3/03 | Requirements Summary: Not a usecase but useful anyway | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0167.html | |||||||||||
| X | Hugo Haas | 3/4/03 | Usage scenarios and use cases: which is which? | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0038.html | |||||||||||
| Stephen White | 3/4/02 | Diagrams in support of Paul Lipton usecase above | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0062.html | ||||||||||||
| Assaf Arkin | 18/3/03 | This use case is interesting since it highlights how one would use Web services technologies like WSDL, WS-Policy, SAML and WS-Choreography even for interactions that are not SOAP enabled. | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0065.html | ||||||||||||
| Edwin Khodabakchia | 24/3/03 | Doctor Patient original defn | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0172.html | ||||||||||||
| Stephen White | 26/3/03 | Doctor Patient diagrams | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0228.html | ||||||||||||
| Steve Ross-Talbot | 27/3/03 | Client Server interaction | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0265.html | ||||||||||||
| Paul Lipton | 30/3/03 | The theme behind this use case is provisioning. | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0266.html | ||||||||||||
| Jim Hendler | 31/3/03 | A couple of scenarios, evidence for implementibility and impact on Chor based for a use case in which services are composed from existing services (without pre-arrangement on the parts of the service suppliers). | http://lists.w3.org/Archives/Public/public-ws-chor/2003Mar/0273.html | ||||||||||||
| Martin Chapman | 1/4/03 | A system already exists and a new party comes along and needs to plug into that system. | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0004.html | ||||||||||||
| David Burdett | 2/4/03 | In this choreography one choreography is dependent on another such that the second choreography can only be executed after an instance of the earlier choreography has occurred. | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/att-0005/Choreography_Dependency_use_case.htm | ||||||||||||
| David Burdett | 2/4/03 | This use case suggests the idea of defining an "Outstanding Activities" choreography instance designed to support recovery after a catastrophic failure. The idea is that the Outstanding Activities choreography could be used after the failure of ANY choreography and is therefore generally applicable and so will benefit from standardization | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/att-0015/Choreography_Recovery_Use_Case.htm | ||||||||||||
| David Burdett | 2/4/03 | Extensible Composable Choreographies Use Case: identification of different document exchange patterns (i.e. choreographies) that businesses follow when placing an order | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0017.html | ||||||||||||
| Greg Ritzinger | 2/4/03 | I don't recall if any of the submitted use cases include the notion of an observer, but in some choreography scenarios an observer would be desirable | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0012.html | ||||||||||||
| David Burdett | 3/4/03 | flow associated with the placement of an order style. | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0057.html | ||||||||||||
| Stephen White | 3/4/03 | error handling in the dependencies between choreographies use case | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0059.html | ||||||||||||
| Monica Martin | 4/4/03 | Alternative paths based on business rules or requirements. Similar to first case except raises exception issue | http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/0006.html | ||||||||||||
| David Burdett | 23/10/03 | eCommerce example | http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/att-0369/01-eCommerce_Use_Case.pdf | ||||||||||||
| http://www.xcbl.org/DevResources/BusinessTransactions.html |
|||||||||||||||
| http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0369.html | |||||||||||||||
| http://www.mindswap.org/papers/composition.pdf | |||||||||||||||
| http://lists.w3.org/Archives/Public/public-ws-chor/2003Apr/att-0057/PlaceOrderChoreography.xml | |||||||||||||||