{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,4,29]],"date-time":"2026-04-29T19:25:50Z","timestamp":1777490750746,"version":"3.51.4"},"reference-count":25,"publisher":"SAGE Publications","issue":"3","license":[{"start":{"date-parts":[[2004,9,1]],"date-time":"2004-09-01T00:00:00Z","timestamp":1093996800000},"content-version":"tdm","delay-in-days":0,"URL":"https:\/\/journals.sagepub.com\/page\/policies\/text-and-data-mining-license"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["Concurrent Engineering"],"published-print":{"date-parts":[[2004,9]]},"abstract":"<jats:p>Web services can be seen as a newly emerging research area for Service-oriented Computing and their implementation in Service-oriented Architectures. Web services are self-contained, self-describing modular applications or components providing services. Web services may be dynamically aggregated, composed, and enacted as Web services Workflows. This requires frameworks and interaction protocols for their co-ordination and transaction support. In a Service-oriented Computing setting, transactions are more complex, involve multiple parties (roles), span many organizations, and may be long-running, consisting of a highly decentralized service partner and performed by autonomous entities. A Service-oriented Transaction Model has to provide comprehensive support for long-running propositions including negotiations, conversations, commitments, contracts, tracking, payments, and exception handling. Current transaction models and mechanisms including their protocols and primitives do not sufficiently cater for quality-aware and long running transactions comprising loosely-coupled (federated) service partners and resources. Web services transactions require co-ordination behavior provided by a traditional transaction mechanism to control the operations and outcome of an application. Furthermore, Web services transactions require the capability to handle the co-ordination of processing outcomes or results from multiple services in a more flexible manner. This requires more relaxed forms of transactions\u2014those that do not strictly have to abide by the ACID properties\u2014such as loosely-coupled collaboration and workflows. Furthermore, there is a need to group Web services into applications that require some form of correlation, but do not necessarily require transactional behavior. The purpose of this paper is to provide a state-of-the-art review and overview of some proposed standards surrounding Web services composition, co-ordination, and transaction. In particular the Business Process Execution Language for Web services (BPEL4WS), its co-ordination, and transaction frameworks (WS-Co-ordination and WS-Transaction) are discussed.<\/jats:p>","DOI":"10.1177\/1063293x04046193","type":"journal-article","created":{"date-parts":[[2004,9,1]],"date-time":"2004-09-01T18:38:40Z","timestamp":1094063920000},"page":"237-245","source":"Crossref","is-referenced-by-count":3,"title":["Web Services Workflows\u2014Composition, Co-Ordination, and Transactions                 in Service-Oriented Computing"],"prefix":"10.1177","volume":"12","author":[{"given":"Schahram","family":"Dustdar","sequence":"first","affiliation":[{"name":"Distributed Systems Group, Vienna University of Technology, A-1040 Wien,\r                        Austria,"}],"role":[{"role":"author","vocab":"crossref"}]}],"member":"179","published-online":{"date-parts":[[2004,9,1]]},"reference":[{"key":"atypb1","author":"van der Aalst, W.M.P.","year":"2003","journal-title":"IEEE Intelligent Systems"},{"key":"atypb2","volume-title":"Workflow Patterns, to appear in Distributed and Parallel Databases, 2003","author":"van der Aalst, W.M.P.","year":"2003"},{"key":"atypb3","unstructured":"3. http:\/\/www.bea.com\/products\/elink\/."},{"key":"atypb4","doi-asserted-by":"publisher","DOI":"10.1145\/230798.230809"},{"key":"atypb5","volume-title":"Business Process Execution Language for Web Services Specification","author":"BPEL4WS","year":"2002"},{"key":"atypb6","volume-title":"Business Process Execution Language for Web services Java Run Time","author":"BPWS4J","year":"2003"},{"key":"atypb7","volume-title":"Business Process Modeling Language","author":"BPML","year":"2002"},{"key":"atypb8","volume-title":"Towards Patterns of Web Service Composition","author":"Benatallah, B.","year":"2001"},{"key":"atypb9","doi-asserted-by":"publisher","DOI":"10.1007\/3-540-45140-4_3"},{"key":"atypb10","volume-title":"ebXML\u2014White Paper\u2014Enabling Electronic Business with ebXML"},{"key":"atypb11","first-page":"1","volume-title":"Proceedings of the TES 2001 Workshop, LNCS 2193","author":"Pilioura, T."},{"key":"atypb12","unstructured":"12. World Wide Web Consortium, (2001). SOAP (Simple Object Access Protocol), http:\/\/www.w3.org\/TR\/2001\/WD-soap12-part1-20011002\/."},{"key":"atypb13","unstructured":"13. Security Assertions Markup Language http:\/\/www.saml.org\/"},{"key":"atypb14","unstructured":"14. http:\/\/www.tibco.com."},{"key":"atypb15","volume-title":"Wf-XML Binding, WFMC-TC-1023, V. 1.0, WfMC","author":"Workflow Standard\u2014Interoperability","year":"2000"},{"key":"atypb16","unstructured":"16. W3C (2001). WSDL Web Service Description Language,\n                http:\/\/www.w3.org\/TR\/wsdl, 2001."},{"key":"atypb17","unstructured":"17. W3C (2003a). Web Services Architecture Usage Scenarios http:\/\/www.w3.org\/TR\/ws-arch-scenarios\/."},{"key":"atypb18","unstructured":"18. W3C (2003b). Web Services Choreography Interface WSCI) http:\/\/www.w3.org\/TR\/wsci\/."},{"key":"atypb19","unstructured":"19. W3C (2003c). Web Services Conversation Language http:\/\/www.w3.org\/TR\/wscl10\/."},{"key":"atypb20","unstructured":"20. W3C (2003d). Web Services Description Working Group http:\/\/www.w3.org\/2002\/ws\/desc\/."},{"key":"atypb21","unstructured":"21. WSEL (2001). Web Services Endpoint Language (WSEL). http:\/\/www.w3.org\/2001\/04\/wsws-proceedings\/rod_smith\/img13.htm."},{"key":"atypb22","unstructured":"22. WS-C (2003). Web Services Coordination, http:\/\/www-106.ibm.com\/developerworks\/library\/ws-coor\/."},{"key":"atypb23","unstructured":"23. WS-T (2003). Web Services Transaction, http:\/\/www-106.ibm.com\/developerworks\/library\/ws-transpec\/."},{"key":"atypb24","unstructured":"24. WSFL (2002). Web Services Flow Language, http:\/\/www-3.ibm.com\/software\/solutions\/webservices\/pdf\/WSFL.pdf."},{"key":"atypb25","unstructured":"25. XLANG (2002). XLANG-Specification, http:\/\/www.gotdotnet.com\/team\/xml_wsspecs\/xlang-c\/default.htm."}],"container-title":["Concurrent Engineering"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/journals.sagepub.com\/doi\/pdf\/10.1177\/1063293X04046193","content-type":"application\/pdf","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/journals.sagepub.com\/doi\/pdf\/10.1177\/1063293X04046193","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2026,4,28]],"date-time":"2026-04-28T14:47:55Z","timestamp":1777387675000},"score":1,"resource":{"primary":{"URL":"https:\/\/journals.sagepub.com\/doi\/10.1177\/1063293X04046193"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2004,9]]},"references-count":25,"journal-issue":{"issue":"3","published-print":{"date-parts":[[2004,9]]}},"alternative-id":["10.1177\/1063293X04046193"],"URL":"https:\/\/doi.org\/10.1177\/1063293x04046193","relation":{},"ISSN":["1063-293X","1531-2003"],"issn-type":[{"value":"1063-293X","type":"print"},{"value":"1531-2003","type":"electronic"}],"subject":[],"published":{"date-parts":[[2004,9]]}}}