ACM Home Page
Please provide us with feedback. Feedback
Web service interfaces
Full text PdfPdf (263 KB)
Source International World Wide Web Conference archive
Proceedings of the 14th international conference on World Wide Web table of contents
Chiba, Japan
SESSION: Web services table of contents
Pages: 148 - 159  
Year of Publication: 2005
ISBN:1-59593-046-9
Authors
Dirk Beyer  EPFL, Lausanne, Switzerland
Arindam Chakrabarti  University of California, Berkeley, CA
Thomas A. Henzinger  EPFL, Lausanne, Switzerland and University of California, Berkeley, CA
Sponsor
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 16,   Downloads (12 Months): 238,   Citation Count: 10
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1060745.1060770
What is a DOI?

ABSTRACT

We present a language for specifying web service interfaces. A web service interface puts three kinds of constraints on the users of the service. First, the interface specifies the methods that can be called by a client, together with types of input and output parameters; these are called signature constraints. Second, the interface may specify propositional constraints on method calls and output values that may occur in a web service conversation; these are called consistency constraints. Third, the interface may specify temporal constraints on the ordering of method calls; these are called protocol constraints. The interfaces can be used to check, first, if two or more web services are compatible, and second, if a web service A can be safely substituted for a web service B. The algorithm for compatibility checking verifies that two or more interfaces fulfill each others' constraints. The algorithm for substitutivity checking verifies that service A demands fewer and fulfills more constraints than service B.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
S. Anderson, M. Chapman, M. Goodner, P. Kackinaw, and R. Rekasius. Supply chain management use case model. Working group interim report, Web Services-Interoperability Organization, 2002.
 
3
A. Brogi, C. Canal, E. Pimentel, and A. Vallecillo. Formalizing web service choreographies. Proc. WS-FM. Elsevier, 2004.
4
 
5
A. Chakrabarti, L. de Alfaro, T. Henzinger, and M. Stoelinga. Resource interfaces. Proc. EMSOFT, LNCS 2855, pp. 117--133. Springer, 2003.
6
7
 
8
 
9
10
 
11
 
12
X. Fu, T. Bultan, and J. Su. Conversation protocols: A formalism for specification and verification of reactive electronic services. Proc. CIAA, LNCS~2759, pp. 188--200. Springer, 2003.
13
 
14
 
15
X. Fu, T. Bultan, and J. Su. WSAT: A tool for formal analysis of web services. Proc. CAV, LNCS~3114, pp. 510--514. Springer, 2004.
 
16
 
17
J. E. Hanson, P. Nandi, and D. W. Levine. Conversation-enabled web services for agents and e-business. Proc. IC, pp. 791--796. CSREA, 2002.
 
18
J. E. Johnson, D. E. Langworthy, L. Lamport, and F. H. Vogt. Formal specification of a web services protocol. Proc. WS-FM. Elsevier, 2004.
 
19
S. Nakajima. Model-checking of safety and security aspects in web service flows. Proc. ICWE, LNCS 3140, pp. 488--501. Springer, 2004.
20
 
21
M. Pistore, M. Roveri, and P. Busetta. Requirements-driven verification of web services. Proc. WS-FM. Elsevier, 2004.
22
 
23
 
24

CITED BY  10

Collaborative Colleagues:
Dirk Beyer: colleagues
Arindam Chakrabarti: colleagues
Thomas A. Henzinger: colleagues