@inproceedings{4576,
  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 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.},
  author       = {Beyer, Dirk and Chakrabarti, Arindam and Henzinger, Thomas A},
  booktitle    = {Proceedings of the 14th international conference on World Wide Web},
  isbn         = {9781595930460},
  location     = {Chiba, Japan},
  pages        = {148 -- 159},
  publisher    = {ACM},
  title        = {{Web service interfaces}},
  doi          = {10.1145/1060745.1060770},
  year         = {2005},
}