Matches in ScholarlyData for { ?s ?p ?o. }
- 21 keyword "HTTP".
- 21 keyword "REST".
- 21 keyword "URI".
- 21 title "Introduction to the Third International Workshop on RESTful Design (WS-REST 2012)".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasLastItem item-3.
- item-1 type ListItem.
- item-1 hasContent rosa-alarcon.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent cesare-pautasso.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent erik-wilde.
- item-3 previous item-2.
- 6 creator christoph-szymanski.
- 6 creator silvia-schreier.
- 6 type InProceedings.
- 6 label "Case Study: Extracting a Resource Model from an Object-Oriented Legacy Application".
- 6 sameAs 6.
- 6 abstract "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.".
- 6 hasAuthorList authorList.
- 6 isPartOf proceedings.
- 6 keyword "Case Study".
- 6 keyword "Legacy System".
- 6 keyword "Resource Design and Granularity".
- 6 title "Case Study: Extracting a Resource Model from an Object-Oriented Legacy Application".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasLastItem item-2.
- item-1 type ListItem.
- item-1 hasContent christoph-szymanski.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent silvia-schreier.
- item-2 previous item-1.
- 7 creator jakob-strauch.
- 7 creator silvia-schreier.
- 7 type InProceedings.
- 7 label "RESTify: From RPCs to RESTful HTTP Design".
- 7 sameAs 7.
- 7 abstract "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.".
- 7 hasAuthorList authorList.
- 7 isPartOf proceedings.
- 7 keyword "hypermedia".
- 7 keyword "iterative method".
- 7 keyword "procedure model".
- 7 keyword "resource design".
- 7 keyword "rest".
- 7 keyword "rpc".
- 7 keyword "soap".
- 7 title "RESTify: From RPCs to RESTful HTTP Design".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasLastItem item-2.
- item-1 type ListItem.
- item-1 hasContent jakob-strauch.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent silvia-schreier.
- item-2 previous item-1.
- 8 creator hiroshi-hosobe.
- 8 creator hyunsun-kim.
- 8 creator julian-padget.
- 8 creator kewei-duan.
- 8 type InProceedings.
- 8 label "Composition of Engineering Web Services with Universal Distributed Data-Flows based on ROA".
- 8 sameAs 8.
- 8 abstract "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.".
- 8 hasAuthorList authorList.
- 8 isPartOf proceedings.
- 8 keyword "RESTful Web services".
- 8 keyword "Web services composition".
- 8 keyword "Web services deployment".
- 8 keyword "engineering Web services".
- 8 keyword "engineering design optimization process".
- 8 keyword "resource oriented architecture".
- 8 keyword "universal distributed data-flows".
- 8 title "Composition of Engineering Web Services with Universal Distributed Data-Flows based on ROA".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasItem item-4.
- authorList hasLastItem item-4.
- item-1 type ListItem.
- item-1 hasContent kewei-duan.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent julian-padget.