Search Results for "web services architecture"

Abstract The Semantic Web Services Initiative Architecture Committee (SWSA) proposes the following architectural and protocol abstractions as a foundation for supporting Semantic Web Service technologies on the World Wide Web. This document is based on a review of requirements gathered from a number of different environments to identify the scope and potential requirements for this Semantic Web Services architecture. Introduction The Semantic Web Services Initiative (SWSI) is an 'ad hoc' initiative of academic and industrial researchers, many

Introduction Previous attempts at distributed computing (CORBA, Distributed Smalltalk, Java RMI) have yielded systems where the coupling between various components in a system is too tight to be effective for low-overhead, ubiquitous B2B e-business over the Internet. These approaches require too much agreement and shared context among business systems from different organizations to be reliable for open, low-overhead B2B e-business. Meanwhile, the current trend in the application space is moving away from tightly coupled monolithic systems and

Use of the Web Services architecture provides the following benefits: * Promotes interoperability by minimizing the requirements for shared understanding XML-based interface definition language (NASSL), an XML-based service description (WDS) and a protocol of collaboration and negotiation are the only requirements for shared understanding between a service provider and a service requester. By limiting what is absolutely required for interoperability, collaborating Web services can be truly platform and language independent. By limiting what is

Several essential activities need to happen in any service-oriented environment: 1. A Web service needs to be created, and its interfaces and invocation methods must be defined. 2. A Web service needs to be published to one or more intranet or Internet repositories for potential users to locate. 3. A Web service needs to be located to be invoked by potential users. 4. A Web service needs to be invoked to be of any benefit. 5. A Web service may need to be unpublished when it is no longer available or needed. A Web Services architecture then