A Dependency Markup Language for Web Services

Authors:
Robert Tolksdorf
Affiliations:
-
Venue:
Revised Papers from the NODe 2002 Web and Database-Related Workshops on Web, Web-Services, and Database Systems
Year:
2002

Citing 8
Cited 3

The interdisciplinary study of coordination

ACM Computing Surveys (CSUR)
Applying specialization to process models

COCS '95 Proceedings of conference on Organizational computing systems
Regular types for active objects

Object-oriented software composition
E-Business Process Modeling: The Next Big Step

Computer
Models of Coordination

ESAW '00 Proceedings of the First International Workshop on Engineering Societies in the Agent World: Revised Papers
DAML-S: Web Service Description for the Semantic Web

ISWC '02 Proceedings of the First International Semantic Web Conference on The Semantic Web
Dependency Charts as a Means to Model Inter-Scenario Dependencies

Modellierung 2001, Workshop der Gesellschaft für Informatik e. V. (GI)
Tools for Inventing Organizations: Toward a Handbook of Organizational Processes

Management Science

Framework for Semantic Web Process Composition

International Journal of Electronic Commerce
Service dependency model for dynamic and stateful grid services

ICA3PP'07 Proceedings of the 7th international conference on Algorithms and architectures for parallel processing
Autonomous Participation in Cloud Services

UCC '12 Proceedings of the 2012 IEEE/ACM Fifth International Conference on Utility and Cloud Computing

Quantified Score

Hi-index	0.00

Visualization

Abstract

Current mechanisms for the description of Web Services and their composition are either to coarse - by specifying a functional interface only - or too fine - by specifying a concrete control flow amongst services.We argue that more adequate specifications can be built on the notion of dependency of activities and coordination activities to manage these dependencies. We propose a Dependency Markup Language to capture dependencies amongst activities and generalizations/specializations amongst processes. With that, we can describe composite services at more suited levels of abstraction and have several options to use such descriptions for service coordination, service discovery and service classification.