Web Service Composition: A Reality Check
24
Citation
26
Reference
10
Related Paper
Citation Trend
Keywords:
WS-Policy
WS-Addressing
Differentiated services
WS-I Basic Profile
WS-Policy
WS-I Basic Profile
SOAP
WS-Addressing
Services computing
Cite
Citations (38)
Web Services are software applications with a standardized way of giving interoperability between disparate applications. It utilizes an XML messaging system by communicating with each other. In the vast network of web services, it becomes tough for users to differentiate between valid and invalid web services. There are millions of web services available on the internet out of which a small proportion of web services are valid. The primary concept of this paper is invoking proper web services based on their response time. This is achieved by maintaining a registry of services which is validated with certain checkpoints and assertions.
WS-I Basic Profile
WS-Addressing
WS-Policy
SOAP
Services computing
Cite
Citations (0)
One of the newest innovations for the use of the Internet is Web services. Web services allow applications and Internet-enabled devices to easily communicate with one another and combine their functionality to provide services to each other, independent of platform or language. Web services are characterized by SOAP messages used to talk to a Web service, WSDL files that describe a Web service, and the UDDI used to find Web services. Conceptually, Web services are very understandable. They eliminate many of the complexities that have been required when there is a need for computer applications to interact with each other. The question then becomes, is the development of Web services substantially less complex than the prior options available for creating interoperable components? That question is assessed in this paper through the development and annotation of a basic Web service. Software applications like Visual Studio .NET have greatly simplified the creation of Web service and consequently Web services are the future.
WS-I Basic Profile
WS-Policy
WS-Addressing
SOAP
Services computing
Cite
Citations (21)
The field of web services became one of the hottest points of discussion during the last decade, along with the evolving web technology. The possibility of having diverse systems connected to each other has been enormously and successfully achieved with the aid of web services. Despite the fact that web services are built over the concept of web programming, developers must have in mind that there are substantial comparison aspects relevant to creating and hosting a web service. Knowing the procedure of constructing a web service, as well as its architecture and standards being used is highly required and important. This paper is intended to provide web programmers some of the basic concepts regarding two of the most commonly used web services nowadays. These two web services are WSDL (Web Service Description Language) and REST (Representational State Transition). It firstly provides the architecture, standards, and steps on how to create them. The paper then concludes with some findings and observations.
WS-I Basic Profile
WS-Policy
WS-Addressing
Web engineering
SOAP
Cite
Citations (3)
The Web Services Policy 1.5 - Framework provides a general purpose model and corresponding syntax to describe the policies of entities in a Web services-based system. Web Services Policy Framework defines a base set of constructs that can be used and extended by other Web services specifications to describe a broad range of service requirements and capabilities.
WS-Policy
WS-I Basic Profile
WS-Addressing
Services computing
Cite
Citations (138)
PUTTING THE WEB SERVICES SPECIFICATIONS TO REST. Dan R. Olsen III Department of Computer Science Master of Science Web services have become a useful and effective way of sharing information over the World Wide Web. SOAP has become a popular way of providing Web services and has been the focus of the Web Services specifications. The Web Services specifications provide additional capabilities to Web Services such as security and policy exchange. Another popular form of Web services includes light-weight Web or RESTful Web services over HTTP. These light-weight Web services are currently not addressed by the Web Services specifications. In order to provide the same capabilities to RESTful Web services, the Web Services specifications will be used to extend the HTTP protocol to provide the additional capabilities. This work will show how the HTTP protocol can be extended using existing well defined specifications to provide extra capabilities such as security to RESTful Web services.
WS-Policy
WS-I Basic Profile
WS-Addressing
SOAP
Services computing
Cite
Citations (1)
There are two approaches to specifying the composition of Web services: orchestration and choreography. Previous works in Web services selection are mostly based on the orchestration model which focuses on the interactions with a single party. However, in many application scenarios, business goals are achieved by a number of pair-wise interactions among a set of Web services, and there does not exist a single entity that is in charge of selecting Web services for all tasks. Each Web service will autonomously perform Web services selection. In such a choreographic environment, we study the kind of information that each Web service should provide to its partner Web services and how each Web service should perform Web service selection so as to maximize the chance of successfully accomplishing a business goal. The proposed approach is evaluated by simulation, and the experimental results show that our proposed method is close to centralized method and better than the other two distributed Web services selection methods.
WS-Policy
Orchestration
WS-Addressing
WS-I Basic Profile
Cite
Citations (8)
Web services are a complex, emergent technology domain that defines distributed computing that leverages the Web standards of IP, HTTP, and XML. Web services differ from the Web in that the data passed is functional rather than presentation oriented. This chapter describes in detail the principal standard protocols of Web services: SOAP for messaging and WSDL for service descriptions. This chapter also describes how the mobile domain is reacting to this Web services movement: by creating standardization efforts to define Web services interfaces for mobility oriented data such as location and presence and by creating architectures to enable non-SOAP aware terminals act as Web services clients.
SOAP
WS-I Basic Profile
WS-Policy
WS-Addressing
Services computing
Cite
Citations (0)
Progress in the field of Web services has resulted in deployment of a significant number of Web services. Furthermore, it is expected that the number of available Web services will constantly grow in the following years. Due to the high number of available Web services, it is a hard task for developers and business analysts to choose which Web services are most suitable for integration. However, despite the increased academic and commercial interest to Web services, there is currently no survey available analysing most relevant Web services. Moreover, to the best of our knowledge, there is no publicly available study analysing the structure and potential synergy between commercial and governmental Web services. In this paper we target these shortcomings by providing a case study of automated Web service composition for semantically annotated commercial and governmental Web services. We propose a method for identifying most applicable Web services and demonstrate it on a case study. We also analyse interaction and potential synergy between commercial and governmental Web services.
WS-Policy
WS-I Basic Profile
WS-Addressing
Services computing
Web engineering
Cite
Citations (5)