Developing a ReSTful mixed reality web service platform
Proceedings of the First International Workshop on RESTful Design
ICWE'10 Proceedings of the 10th international conference on Web engineering
Experiences in building a RESTful mixed reality web service platform
ICWE'10 Proceedings of the 10th international conference on Web engineering
Proceedings of the Second International Workshop on RESTful Design
Modeling behavioral RESTful web service interfaces in UML
Proceedings of the 2011 ACM Symposium on Applied Computing
Designing level 3 behavioral RESTful web service interfaces
ACM SIGAPP Applied Computing Review
RESTful, resource-oriented architectures: a model-driven approach
WISS'10 Proceedings of the 2010 international conference on Web information systems engineering
Stream management within the cloudminer
ICA3PP'11 Proceedings of the 11th international conference on Algorithms and architectures for parallel processing - Volume Part I
A finite-state machine approach for modeling and analyzing restful systems
Journal of Web Engineering
RESTify: from RPCs to RESTful HTTP design
Proceedings of the Third International Workshop on RESTful Design
Case Study: Extracting a resource model from an object-oriented legacy application
Proceedings of the Third International Workshop on RESTful Design
Model-Driven development of resource-oriented applications
ICSOC'11 Proceedings of the 2011 international conference on Service-Oriented Computing
A concept for generating simplified RESTful interfaces
Proceedings of the 22nd international conference on World Wide Web companion
Architectural Styles for Distributed Interoperability
Information Resources Management Journal
| Hi-index | 0.00 |
Representational State Transfer (ReST) architecture provides a set of constraints that drive design decisions towards architectural properties such as interoperability, evolvability and scalability. Designing a ReSTful service API involves finding resources and their relationships, selecting uniform operations for each resource, and defining data formats for them. It is often a non-trivial exercise to refine a functional specification, expressed in terms of arbitrary actions, to a resource-oriented, descriptive state information content. We argue that this process can be described as a series of model transformations, starting from service functionality and gradually refining the phase products until a ReSTful service API is reached. This paper outlines the process phases, transformations and intermediate models based on our experiences in developing ReSTful services and service APIs at Nokia Research Center. The process captures our understanding on how to systematically transform functional specifications into ReSTful Web service interfaces.