REST has gained popularity not only as an alternative approach to building Web Services, but it also has now become a buzzword that is often used to denote a lightweight and loosely coupled approach to design and implement Service-Oriented Architectures. In this book we are focusing on applying REST beyond public Web applications (e.g., in enterprise environments), and on reusing established and well-understood design patterns when doing so. The goal is to establish a good understanding of what REST is about, and the constraints it focuses on as an architectural style. The reader will be able to understand how RESTful systems can be designed and deployed, and what the results are in terms of benefits and challenges encountered in the process.
Since REST is relatively new as an approach for designing Web Services, the more advanced part of the book collects a number of challenges to some of the assumptions and constraints of REST, and looks at current research work on how REST can be extended and applied to scenarios that often are considered not to be a good match for RESTful architectures.
In summary, the goal of the book is to allow readers to come to a deeper understanding of REST on a practical as well as on an advanced level, and to provide an outlook what research on REST is currently working on. The main aim of the book is thus to serve as a starting point for people looking for a deeper principled understanding of REST, its applications, its limitations, and current research work in the area. It is intended for information and service architects and designers who are interested to learn about REST, how it is applied, and how it is being advanced.
Topics of Interest
We are seeking high quality contributions with chapters on, but not limited to, the following topic areas:
Interested researchers and practitioners are encouraged to submit on or before September 19th, 2010 a 1-2 page chapter proposal clearly explaining the content of the proposed chapter through the easychair on: http://www.easychair.org/conferences/?conf=rest2011
The proposal should contain the following information:
Authors of accepted proposals will be notified by September 20th, 2010 about the status of their proposal. Full chapters (up to 20 pages in Springer format) will be due by October 15th, 2010. All submitted chapters will be reviewed for technical correctness and clarity by at least 3 reviewers. Selected contributors may also be requested to serve as reviewers for this book project. Once reviewed, the final chapters have to be delivered by November 22nd 2010 in order to ensure that the book can be published in the first quarter of 2011.