@proceedings{wsrest2010, title = "First International Workshop on RESTful Design (WS-REST 2010)", booktitle = "First International Workshop on RESTful Design (WS-REST 2010)", editor = "Cesare Pautasso and Erik Wilde and Alexandros Marinos", address = "Raleigh, North Carolina", key = "First International Workshop on RESTful Design (WS-REST 2010)", month = apr, year = 2010, uri = "http://ws-rest.org/" } @inproceedings{pau10a, crossref = "wsrest2010", author = "Cesare Pautasso and Erik Wilde and Alexandros Marinos", title = "First International Workshop on RESTful Design (WS-REST 2010)", pages = "1-3", abstract = "Over the past few years, the discussion between the two major architectural styles for designing and implementing Web services, the RPC-oriented approach and the resource-oriented approach, has been mainly held outside of traditional research communities. Mailing lists, forums and developer communities have seen long and fascinating debates around the assumptions, strengths, and weaknesses of these two approaches. The First International Workshop on RESTful Design (WS-REST 2010) has the goal of getting more researchers involved in the debate by providing a forum where discussions around the resource-oriented style of Web services design take place. Representational State Transfer (REST) is an architectural style and as such can be applied in different ways, can be extended by additional constraints, or can be specialized with more specific interaction patterns. WS-REST is the premier forum for discussing research ideas, novel applications and results centered around REST at the World Wide Web conference, which provides a great setting to host this first edition of the workshop dedicated to research on the architectural style underlying the Web." } @inproceedings{ric10, crossref = "wsrest2010", author = "Leonard Richardson", title = "Developers Like Hypermedia, But They Don't Like Web Browsers ", pages = "4-9", abstract = {Although desktop developers often have trouble consciously understanding RESTful concepts like "hypermedia as the engine of application state", this does not prevent them from intuitively understanding client-side tools based on these concepts. However, I encountered unexpected developer resistance after implementing a security protocol I and other web developers had thought uncontroversial: the most common mechanism for authorizing OAuth request tokens. This developer resistance has implications for many web services that share their authentication credentials with a corresponding website.} } @inproceedings{had10, crossref = "wsrest2010", author = "Marc Hadley and Santiago Pericas-Geertsen and Paul Sandoz", title = "Exploring Hypermedia Support in Jersey", pages = "10-15", abstract = "This paper describes a set of experimental extensions for Jersey that aim to simplify server-side creation and client-side consumption of hypermedia-driven services. We introduce the concept of action resources that expose workflow-related operations on a parent resource." } @inproceedings{par10, crossref = "wsrest2010", author = "Savas Parastatidis and Jim Webber and Guilherme Silveira and Ian Robinson", title = "The Role of Hypermedia in Distributed System Development", pages = "16-22", abstract = "This paper discusses the role of the Representational State Transfer (REST) architectural style in the development of distributed applications. It also gives an overview of how RESTful implementations of distributed business processes and structures can be supported by a framework such as Restfulie." } @inproceedings{kel10, crossref = "wsrest2010", author = "Mike Kelly and Michael Hausenblas", title = "Using HTTP Link: Header for Gateway Cache Invalidation", pages = "23-26", abstract = "Gateway caches are intermediary components for reducing demands on destination servers, and therefore operational costs of a system. At scale, particularly with the advent of on-demand infrastructures such as EC2, etc., maximising cache efficiency translates into cost efficiency, resulting in a competitive advantage. In this position paper, we initially discuss advantages and limitations of HTTP caching mechanisms. We then propose to use HTTP Link: headers to maximise the efficiency of gateway (or reverse proxy) caching mechanisms and discuss early findings. " } @inproceedings{eng10, crossref = "wsrest2010", author = "Charles Engelke and Craig Fitzgerald", title = "Replacing Legacy Web Services with RESTful Services", pages = "27-30", abstract = "In this paper, we describe issues encountered in designing and implementing a set of RESTful services to extend and replace web services that have been in commercial use since 1998. Applicability of REST to the service requirements, suitability of available tools, and interoperability between multiple clients and servers are discussed. " } @inproceedings{fer10, crossref = "wsrest2010", author = "Federico Fernandez and Jaime Nav\'on", title = "Towards a Practical Model to Facilitate Reasoning about REST Extensions and Reuse", pages = "31-38", abstract = "We believe that there is a need for a practical model to visualize the structure and design rationale of REST, so researchers can study more easily the reutilization of this architectural style or parts of it, to the design of software solutions with different requirements than those of the early WWW. In this work we propose the utilization of extended influence diagrams to represent the structure and design rationale of an architectural style. The model is evaluated qualitatively by showing how a diagram of REST, populated with information extracted from the doctoral dissertation that introduced the term, is helpful to gain a better understanding of the properties and limitations of this style, and to reason about potential modifications for applications with different goals than those of the early WWW." } @inproceedings{gar10, crossref = "wsrest2010", author = "Antonio Garrote Hern\'andez, Mar\'\i{}a N. Moreno Garc\'\i{}a", title = "A Formal Definition of RESTful Semantic Web Services", pages = "39-45", abstract = "In this article a formal model applying REST architectural principles to the description of semantic web services is introduced, including the discussion of its syntax and operational semantics. RESTful semantic resources are described using the concept of tuple spaces being manipulated by HTTP methods that are related to classical tuple space operations. On the other hand, RESTful resources creation, destruction and other dynamic aspects of distributed HTTP computations involving coordination between HTTP agents and services are modeled using process calculus style named channels and message passing mechanisms. The resulting model allows for a complete and rigorous description of resource based web systems, where agents taking part in a computation publish data encoded according to semantic standards through public triple repositories identified by well known URIs. The model can be used to describe complex interaction scenarios where coordination and composition of resources are required. One of such scenarios taken from the literature about web services choreography is analyzed from the point of view of the proposed model. Finally, possible extensions to the formalism, such as the inclusion of a description logics based type system associated to the semantic resources or possible extensions to HTTP operations are briefly explored." } @inproceedings{jac10, crossref = "wsrest2010", author = "Ian Jacobi and Alexey Radul", title = "A RESTful Messaging System for Asynchronous Distributed Processing", pages = "46-53", abstract = "Traditionally, distributed computing problems have been solved by partitioning data into chunks small enough to be handled by commodity hardware. However, such partitioning is not possible in cases where there are a high number of dependencies or high dimensionality, such as in reasoning and expert systems, rendering such problems less tractable for distributed systems. By instead partitioning the problem, rather than the data, we can achieve a more general application of distributed computing. Partitioning the problem rather than the data may require tighter communication between members of the network, even though many networks can only be assumed to be weakly-connected. We believe that a decentralized implementation of propagator networks may resolve the problem. By placing several constraints on the merging of data transmitted over the network, we can easily synchronize information and achieve eventual convergence without implementing mechanisms needed for serialization. To this end, we present the design of a RESTful messaging mechanism, currently in the process of being implemented, that allows distributed propagator networks to be created, using mechanisms that result in eventual convergence of knowledge across a weakly-connected network. By utilizing a RESTful design of the mechanism, we can also achieve a reduction of bandwidth usage during synchronization through the use of caching." } @inproceedings{sel10, crossref = "wsrest2010", author = "Petri Selonen and Petros Belimpasakis and Yu You", title = "Developing a RESTful Mixed Reality Web Service Platform", pages = "54-61", abstract = "This paper discusses the development of a RESTful Web Service platform for serving Mixed Reality content at Nokia Research Center. The paper gives an overview of the Mixed Reality domain, the requirements for the platform and its implementation. We further outline a method for developing resource oriented web services, beginning with high-level requirements, formalizing them as UML models and refining them to a RESTful API specification. The approach is demonstrated with detailed examples of designing one particular API subset for Mixed Reality annotations. " } @inproceedings{sti10, crossref = "wsrest2010", author = "Vlad Stirbu", title = "A RESTful Architecture for Adaptive and Multi-device Application Sharing", pages = "62-66", abstract = "In this paper we introduce a practical approach to share the user interface of MVC compatible interactive applications with remote devices that have the ability to adapt the user interface to their specific look and feel. We present the system architecture and the methodology to model the user interface as a set of RESTful resources. The remote user interface and the application state are synchronized using an Web-based event-driven system." }