@conference {rest:2015:wicsa,
	title = {A conversation based approach for modeling REST APIs},
	booktitle = {12th Working IEEE / IFIP Conference on Software Architecture (WICSA 2015)},
	year = {2015},
	month = {May},
	address = {Montreal, Canada},
	abstract = {Conversations are a well-known concept in service design to describe complex interactions between a client and one or multiple services. The REST architectural style constrains the characteristics of clients, servers and their interactions in REST architectures which consequently has an impact on conversations in such systems. The relation between conversations and REST architectures and how such RESTful conversations can be characterized has not been studied in detail yet. In this paper we discuss the characteristics of conversations in REST architectures and introduce an initial set of commonly used conversation types. Based on this, we propose to use conversations as a modeling tool for the design of REST APIs at a higher level of abstraction. We also introduce a corresponding interaction centric metamodel for REST APIs. The characterization of RESTful conversations enables a new interaction centric viewpoint on REST architectures which can be also applied for modeling REST APIs on an abstraction level that enables users to focus on the essential functionality of their REST API.},
	keywords = {conversation, model-driven engineering, REST, RESTful conversation},
	url = {http://wicsa2015.org/wicsa-sessions.html$\#$WS5},
	author = {Florian Haupt and Frank Leymann and Cesare Pautasso}
}
@conference {www08restsoap,
	title = {RESTful Web Services vs. Big Web Services: Making the Right Architectural Decision},
	booktitle = {17th World Wide Web Conference (WWW 2008)},
	year = {2008},
	month = {April},
	pages = {805-814},
	publisher = {ACM},
	organization = {ACM},
	address = {Beijing, China},
	abstract = {Recent technology trends in the Web Services (WS) domain indicate that a solution eliminating the presumed complexity of the WS-* standards may be in sight: advocates of REpresentational State Transfer (REST) have come to believe that their ideas explaining why the World Wide Web works are just as applicable to solve enterprise application integration problems and to simplify the plumbing required to build service-oriented architectures. In this paper we objectify the WS-* vs. REST debate by giving a quantitative technical comparison based on architectural principles and decisions. We show that the two approaches differ in the number of architectural decisions that must be made and in the number of available alternatives. This discrepancy between freedom-from-choice and freedom-of-choice explains the complexity difference perceived. However, we also show that there are significant differences in the consequences of certain decisions in terms of resulting development and maintenance costs. Our comparison helps technical decision makers to assess the two integration styles and technologies more objectively and select the one that best fits their needs: REST is well suited for basic, ad hoc integration scenarios, WS-* is more flexible and addresses advanced quality of service requirements commonly occurring in enterprise computing. },
	keywords = {architectural decisions, REST, SOAP, Web services},
	doi = {10.1145/1367497.1367606},
	author = {Cesare Pautasso and Olaf Zimmermann and Frank Leymann}
}
