Principled design of the modern Web architecture
ACM Transactions on Internet Technology (TOIT)
Developing web services choreography standards: the case of REST vs. SOAP
Decision Support Systems - Special issue: Web services and process management
Microformats: a pragmatic path to the semantic web
Proceedings of the 15th international conference on World Wide Web
Reference Architecture for Lending Industry in ULS Systems
ULS '07 Proceedings of the International Workshop on Software Technologies for Ultra-Large-Scale Systems
From representations to computations: the evolution of web architectures
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Restful web services
Scaling up software architecture evaluation processes
ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
RESTful Web service composition with BPEL for REST
Data & Knowledge Engineering
Towards a practical model to facilitate reasoning about REST extensions and reuse
Proceedings of the First International Workshop on RESTful Design
Hi-index | 0.00 |
REpresentational State Transfer (REST) and the resource-oriented viewpoint are considered to be the guiding principles behind the WWW ULS ecosystem. RESTful principles are responsible for many of the desirable ULS quality attributes achieved, such as loose-coupling, reliability, data visibility and interoperability. However, many exiting Web-based or service-oriented applications (WSDL/SOAP-based) only use WWW/HTTP as a tunneling protocol or abuse URL and POX (Plain Old XML) by encoding method semantics in them. These applications are designed as fine-grained distributed Remote Procedure Calls (RPC), breaking many of the REST principles, and are subsequently harmful to the overall ULS system health. The debate on REST versus SOAP-based "Big" Web services has been raging in the industry. We observe that the main problems lie in two areas: 1) conceptually modeling process-centric business applications using a "resource-oriented" viewpoint promoted by the REST principles; and 2) decentralizing a workflow-based business process (e.g. BPEL) into distributed and dynamic process fragments. In this paper, we propose a solution to these two problems. Our approach aligns process-intensive applications with the basic Web principles and promotes dynamic and distributed process coordination.