{"publisher":"ACM","year":"2005","status":"public","citation":{"apa":"Beyer, D., Chakrabarti, A., &#38; Henzinger, T. A. (2005). Web service interfaces (pp. 148–159). Presented at the WWW: World Wide Web Conference, ACM. <a href=\"https://doi.org/10.1145/1060745.1060770\">https://doi.org/10.1145/1060745.1060770</a>","ieee":"D. Beyer, A. Chakrabarti, and T. A. Henzinger, “Web service interfaces,” presented at the WWW: World Wide Web Conference, 2005, pp. 148–159.","ista":"Beyer D, Chakrabarti A, Henzinger TA. 2005. Web service interfaces. WWW: World Wide Web Conference, 148–159.","ama":"Beyer D, Chakrabarti A, Henzinger TA. Web service interfaces. In: ACM; 2005:148-159. doi:<a href=\"https://doi.org/10.1145/1060745.1060770\">10.1145/1060745.1060770</a>","mla":"Beyer, Dirk, et al. <i>Web Service Interfaces</i>. ACM, 2005, pp. 148–59, doi:<a href=\"https://doi.org/10.1145/1060745.1060770\">10.1145/1060745.1060770</a>.","short":"D. Beyer, A. Chakrabarti, T.A. Henzinger, in:, ACM, 2005, pp. 148–159.","chicago":"Beyer, Dirk, Arindam Chakrabarti, and Thomas A Henzinger. “Web Service Interfaces,” 148–59. ACM, 2005. <a href=\"https://doi.org/10.1145/1060745.1060770\">https://doi.org/10.1145/1060745.1060770</a>."},"title":"Web service interfaces","type":"conference","author":[{"first_name":"Dirk","full_name":"Beyer, Dirk","last_name":"Beyer"},{"last_name":"Chakrabarti","full_name":"Chakrabarti, Arindam","first_name":"Arindam"},{"last_name":"Henzinger","id":"40876CD8-F248-11E8-B48F-1D18A9856A87","orcid":"0000−0002−2985−7724","first_name":"Thomas A","full_name":"Thomas Henzinger"}],"date_created":"2018-12-11T12:09:33Z","_id":"4576","date_published":"2005-05-01T00:00:00Z","acknowledgement":"This research was supported in part by the ONR grant N00014-02-1-0671 and by the NSF grants CCR-0234690 and CCR-0225610.","abstract":[{"text":"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 oc- cur in a web service conversation; these are called consis- tency 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 ser- vice 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.","lang":"eng"}],"extern":1,"doi":"10.1145/1060745.1060770","day":"01","publist_id":"132","page":"148 - 159","quality_controlled":0,"conference":{"name":"WWW: World Wide Web Conference"},"date_updated":"2021-01-12T07:59:50Z","publication_status":"published","month":"05"}