n/a
n/a
Olaf Zimmermann
Olaf Zimmermann
Olaf
Zimmermann
5103c81b7657299492aa4826125e4613f4f31f5f
Nokia
Nokia
Subbu Allamaraju
Subbu Allamaraju
Subbu
Allamaraju
6a84ebb2e0e32d4018751907c921b53b6883bd0a
Ghent University
Ghent University
Aldo Gangemi
Aldo
Gangemi
Joaquim Gabarro
Joaquim Gabarro
Joaquim
Gabarro
7250d9213c1ecbe41fc0bfeab1648bb87464c3c8
amundsen.com, inc.
amundsen.com, inc.
Jan Algermissen
Jan Algermissen
Jan
Algermissen
ca10d65178213d05d8c12f192f525c5e3d24f059
Nokia Corporation
Nokia Corporation
Alexandros Marinos
Alexandros Marinos
Alexandros
Marinos
9c72aee259c7b4e4830b2018b69bef645c866ed6
Ian Robinson
Ian Robinson
Ian
Robinson
e95160bc77cd0e2fed106fc437759ea48badd329
Duncan Cragg
Duncan Cragg
Duncan
Cragg
7934175e713b545f083f42097e0fd2f12e3a465a
Thomas Steiner
Thomas Steiner
Thomas
Steiner
08e16fa0ce4602315e959303c0f2f0b26a7cd4c2
Digital Enterprise Research Institute (DERI), NUI Galway
Digital Enterprise Research Institute (DERI), NUI Galway
Benjamin Carlyle
Benjamin Carlyle
Benjamin
Carlyle
e81d20fd6c8230f35402fa4dc04bad8bff6072c4
ThoughtWorks
ThoughtWorks
ecc013db98426b445011d56370e785edafaea5e2
Mike
Amundsen
Mike Amundsen
Mike Amundsen
Institute of Architecture of Application Systems
Institute of Architecture of Application Systems
Cesare Pautasso
Cesare Pautasso
Cesare
Pautasso
af2308705bed94be9df42b32943d498bb21a48d7
ThoughtWorks (UK) Ltd
ThoughtWorks (UK) Ltd
University of California, Irvine
University of California, Irvine
Many companies have invested in legacy applications and want to benefit from the interoperability that the architectural style Representational State Transfer (REST) offers without redeveloping their software. One of the crucial parts when adding a REST interface to an existing application is creating an appropriate resource model. Utilizing any available model of the legacy application can accelerate development significantly because existing domain knowledge, data, and business process implementations can be reused. Despite the maturity of the architectural style, there is still little record of creating a resource model from existing object-oriented applications. This article presents a lightweight modeling process: First we harvest an existing object model for resource candidates, afterwards the resulting model is enhanced incrementally until a suitable resource model emerges. The process is illustrated by a case study that highlights interesting challenges, such as a comprehensive domain model and long running processes, as well as pragmatic solutions for these challenges. The paper demonstrates that it is feasible to add a RESTful interface to a legacy application even in a process rich environment.
Case Study: Extracting a Resource Model from an Object-Oriented Legacy Application
Resource Design and Granularity
Case Study
Legacy System
Case Study: Extracting a Resource Model from an Object-Oriented Legacy Application
Valentina Presutti
Valentina
Presutti
University of Bath
University of Bath
IBM Research GmbH
IBM Research GmbH
Red Hat
Red Hat
Cornelia Davis
Cornelia Davis
Cornelia
Davis
7ac5dd24bfdadd023a03f53123d8758697aaeeb8
Yu You
Yu You
Yu
You
efa7aa6c69ae0bd59132078de0f3f17768b393c7
SAP AG
SAP AG
Markus Lanthaler
Markus Lanthaler
Markus
Lanthaler
deb84ad4ddc60b9fb853de65fc4cef03c9ed05ee
University of Hagen
University of Hagen
Yahoo Inc.
Yahoo Inc.
Silvia Schreier
Silvia Schreier
Silvia
Schreier
b0e679e36ef349ef182e1ae8926e0efec16cc5b5
Pontificia Universidad Católica de Chile
Pontificia Universidad Católica de Chile
Davy Van Deursen
Davy Van Deursen
Davy
Van Deursen
20ce3b0262f51732189cf73813162ecc5c98cab9
Kewei Duan
Kewei Duan
Kewei
Duan
dbf4014e3effea1a59752ed2d0edd6bfd4743cb8
procedure model
hypermedia
soap
rest
resource design
Starting a REST design is a difficult task - even more if the designer has a RPC or object-oriented background. There are patterns and best practices for a RESTful design, but they do not help in cases of previous knowledge in the field of RPCs.To support the adaption from RPC- to REST-oriented thinking, we propose RESTify, a straightforward procedure model to redesign a RPC-oriented interface into a hypermedia-enabled REST interface. RESTfiy uses a WSDL document of an existing SOAP service and consists of three iterations. The result of each iteration is an enhanced version of the preceding one concerning the REST constraints and is meant to be implemented as a HTTP service. Beside the technical result of the process and the design of a RESTful interface, the developer becomes acquainted to the main elements of a RESTful design, the constraints and their application. The results of the evaluation, using a prototypical web application and public SOAP services, are promising.
RESTify: From RPCs to RESTful HTTP Design
iterative method
RESTify: From RPCs to RESTful HTTP Design
rpc
University of Lugano, Switzerland
University of Lugano, Switzerland
Rik Van De Walle
Rik Van De Walle
Rik
Van De Walle
209af6a5da064a4a0f0cb89a336bfeb0ebcc196d
Bill Burke
Bill Burke
Bill
Burke
fd83e8c693c31443308e8601dd372b2a5995cc00
UC Berkeley
UC Berkeley
Joe Gregorio
Joe Gregorio
Joe
Gregorio
ad7039cbaf2bf89fd96b902236f5f0cb05f18d2f
Hiroshi Hosobe
Hiroshi Hosobe
Hiroshi
Hosobe
458d5c244fbdde711ab8cb2573dd85ee3a3dcf25
Jakob Strauch
Jakob Strauch
Jakob
Strauch
4984bfad9356b52d2509c6cdd2b555b7eee25540
Rosa Alarcon
Rosa Alarcon
Rosa
Alarcon
4aa578c1b66b36b8d9fb8e276aa90891d0c54d2b
Web services composition
engineering Web services
engineering design optimization process
universal distributed data-flows
The problem of staging data in workflows has received much attention over the last decade, with a variety of user-directed and automatic solutions. The latter are the focus of the first contribution in this paper, where we propose a simple peer-to-peer solution adapted to the needs of RESTful services. The second contribution, is the combination of the data staging mechanism with a simple service deployment mechanism, that is designed to allow applications developed for the command-line to function as (RESTful) services without modification or (in some cases) recompilation. Thus, the aim of this paper is to describe the design and implementation of: (i) a peer-to-peer data-staging mechanism, that is itself RESTful, and (ii) a service deployment mechanism, also following REST design principles, which together form the Universal Distributed Data-flows framework, for the support of data-intensive (RESTful) workflows. We evaluate the framework by means of an engineering workflow developed for multi-disciplinary design optimization. The workflow itself is specified in Taverna, which is a conventional centralized data-staging enactment system. However, by virtue of the underlying services and staging mechanisms described here, the resulting enactment is peer-to-peer (for data), which furthermore permits asynchronous staging, with potential benefits for network utilization and end-to-end execution time.
RESTful Web services
Composition of Engineering Web Services with Universal Distributed Data-Flows based on ROA
resource oriented architecture
Web services deployment
Composition of Engineering Web Services with Universal Distributed Data-Flows based on ROA
(unknown)
(unknown)
National Institute of Informatics
National Institute of Informatics
NORD Software Consulting
NORD Software Consulting
Dataset about ws-rest2012.
Tue May 03 19:04:56 CEST 2016
Stuart Charlton
Stuart Charlton
Stuart
Charlton
af59ebc829379c474ca0f9defd673eeda851dfa4
Graz University of Technology
Graz University of Technology
University of Surrey
University of Surrey
Erik
Wilde
cdee7ba2e53e5c97d302fe5e107715e9d271f6d5
Erik Wilde
Erik Wilde
Christian Guetl
Christian Guetl
Christian
Guetl
36c422dc0cb56532856b1bf7130413754622626d
Julian Padget
Julian Padget
Julian
Padget
25e30218961b2bc39e83f4fe37707279a00686d5
Functional Descriptions as the Bridge between Hypermedia APIs and the Semantic Web
REST
Web APIs
API descriptions
hypermedia
Semantic Web
Web services
Functional Descriptions as the Bridge between Hypermedia APIs and the Semantic Web
The early visions for the Semantic Web, from the infamous 2001 Scientific American article by Berners-Lee et al., feature intelligent agents that can autonomously perform tasks like discovering information, scheduling events, finding execution plans for complex operations, and in general, use reasoning techniques to come up with sense-making and traceable decisions. While today – more than ten years later – the building blocks (1) resource-oriented rest infrastructure, (2) Web apis, and (3) Linked Data are in place, the envisioned intelligent agents have not landed yet. In this paper, we explain why capturing functionality is the connection between these three building blocks, and introduce the functional api description format RESTdesc that creates this bridge between rest apis and the Semantic Web. Rather than adding yet another component to the Semantic Web stack, RESTdesc offers instead concise descriptions that reuse existing vocabularies to guide hypermedia-driven agents. Its versatile capabilities are illustrated by a real-life agent use case for Web browsers wherein we demonstrate that RESTdesc functional descriptions are capable of fulfilling the promise of autonomous agents on the Web.
Service descriptions
Michael Hausenblas
Michael Hausenblas
Michael
Hausenblas
327b61f3721afbd39dceadf5e5b4fc2d79d5dcc8
Vlad Stirbu
Vlad Stirbu
Vlad
Stirbu
b3933dd733655e749cbb8dbfb03e97f27b679342
Verivue
Verivue
Ruben Verborgh
Ruben Verborgh
Ruben
Verborgh
fb22bc1100f1f5b282380024f58bf4e906fd3e69
Stefan Tilkov
Stefan Tilkov
Stefan
Tilkov
0d6002bff7329ebda2f3c49e7510ef0aed64f4d8
Yves Lafon
Yves Lafon
Yves
Lafon
dc78438fdc2eaad39f0500db20e452636b96129d
Google
Google
Anna Lisa Gentile
Anna Lisa
Gentile
Invensys Rail
Invensys Rail
Hyunsun Kim
Hyunsun Kim
Hyunsun
Kim
15bdee0c301b94f4e8fc9b428f6b15f8c0df041f
user interface
mirror world
Experiences Designing Hypermedia-Driven and Self-Adaptive Web-Based AR Authoring Tools
Experiences Designing Hypermedia-Driven and Self-Adaptive Web-Based AR Authoring Tools
In this paper we present our experiences on developing generic and adaptive web-based content authoring tools for augmented and mixed reality applications. Our approach uses hypermedia to convey the capabilities of content servers and to load on demand only the functionality needed to interact with the corresponding content server. The mechanism allows the web application to provide an optimized user experience by adapting to the environment where it is used.
hypermedia
FH Aachen
FH Aachen
Usability
HTTP
Web Services
From APIs to Affordances: A New Paradigm for Web Services
REST
Evolvability
Hypermedia
WWW
SOA
The ecosystem of services on the Web continues to grow and evolve while, at the same time, the number and diversity of connected devices increases; challenges lie ahead for both providers and consumers of Web services. This paper is presented as a ‘what-if’ proposal; an alternate paradigm for dealing with an increasingly heterogeneous network.Drawing from diverse sources including physical architecture, industrial design, the psychology of perception, and cross-cultural mono-myth, a new implementation paradigm is proposed to help software architects and developers meet these challenges; one that invites participants to shift their mental model from that of programming network devices to programming the network to which those devices are connected.To accomplish this goal an “affordance-rich message” is proposed; one that is based on shared understanding through network-oriented affordances instead of device-oriented APIs. A working model based on this approach is offered, examples given, and areas of related work identified.
From APIs to Affordances: A New Paradigm for Web Services
Andrea Giovanni Nuzzolese
Andrea Giovanni
Nuzzolese
Sam Coppens
Sam Coppens
Sam
Coppens
d13779a648af2d2d2da34f2d758084f5624debd0
Frank Leymann
Frank Leymann
Frank
Leymann
16347d64323354dec32ca0cbc2a78f4e92794a37
Ghent University - IBBT - ELIS - Multimedia Lab
Ghent University - IBBT - ELIS - Multimedia Lab
Canadian Pacific Railway
Canadian Pacific Railway
HTTP
REST
URI
Introduction to the Third International Workshop on RESTful Design (WS-REST 2012)
tbd
Introduction to the Third International Workshop on RESTful Design (WS-REST 2012)
Christoph Szymanski
Christoph Szymanski
Christoph
Szymanski
79bead2f4720d4326cd5c4a3d2863d9a92d68428
principles
What if the Web Were Not RESTful?
REST
What if the Web Were Not RESTful?
fail
education
So called RESTful services are in widespread use both on the web, and increasingly, in large enterprises. We say “so called” because in reality, most of these services are not very RESTful. Those active in the REST community know well where these interfaces fail to meet REST principles, however, true understanding remains in this relatively small community. Unfortunately, the result is a set of interfaces that are ultimately limited in their use, and the deficiencies are not usually recognized until it is too late to make the necessary changes. Our experience has shown that individuals are not being deliberately neglectful, rather, they simply do not know what they do not know. Everyone thinks they “get REST”; after all, using HTTP to move XML or JSON payloads over the network is very simple. We have found that most individuals begin to understand the nuances of REST when they are explained and they almost always ask for resources that further explain these concepts. There most certainly are materials available, however the best ones are rather substantial in size lessening the chance that many people will read them.In this paper we take a fresh approach to explaining the core principles of REST, by describing a World Wide Web that fails to meet these tenets. We look at each key element, resource orientation, the uniform interface, media types and hyperlinking, and imagine the consequences of not abiding by the REST architectural style on the end user or tools developer of the web. We then do the same analysis in the context of web services and programmatic consumers. We examine each REST characteristic and examine the disadvantages when not followed and the advantages gained what the architectural guidance is followed. We have found that in discussions, the analogy of the World Wide Web has been very effective at explaining REST and we hope the same will hold true with this paper.
Universitat Politecnica de Catalunya
Universitat Politecnica de Catalunya
Richard Taylor
Richard Taylor
Richard
Taylor
a2f16b60071182b050de394bb16111292ad986aa
Steve Vinoski
Steve Vinoski
Steve
Vinoski
41c9a17b89f645e0063508a30317a80b60e3cf58
Web services
REST
Web of Things
Semantic Web
On Using JSON-LD to Create Evolvable RESTful Services
As the amount of data and devices on the Web experiences exponential growth issues on how to integrate such hugely heterogeneous components into a scalable system become increasingly important. REST has proven to be a viable solution for such large-scale information systems. It provides a set of architectural constraints that, when applied as a whole, result in benefits in terms of loose coupling, maintainability, evolvability, and scalability. Unfortunately some of REST’s constraints such as the ones that demand self-descriptive messages or require the use of hypermedia as the engine of application state are rarely implemented correctly. This results in tightly coupled and thus brittle systems. To solve these and other issues, we present JSON-LD, a community effort to standardize a media type targeted to machine-to-machine communication with inherent hypermedia support and rich semantics. Since JSON-LD is 100% compatible to traditional JSON, developers can continue to use their existing tools and libraries. As we show in the paper, JSON-LD can be used to build truly RESTful services that, at the same time, integrate the exposed data into the Semantic Web. The required additional design costs are significantly outweighed by the achievable benefits in terms of loose coupling, evolvability, scalability, self-descriptiveness, and maintainability.
Linked Data
On Using JSON-LD to Create Evolvable RESTful Services
JSON-LD
W3C
W3C
EMC
EMC