The primary objective of service-oriented architecture (SOA) is to use information technology to address the key goals of business today: innovation, agility, and market value. Agility in SOA is achieved by use of the principles of encapsulation, modularity, and loose coupling. Loose coupling enables customers to rapidly reuse services in new applications where strong consistency must be maintained to achieve the primary business objectives of the application. When applications are composed of loosely coupled services that are independent i.e. it is owned by different parts of the organization, based on disparate technology assumptions, and evolving on independent schedules and with diverse priorities, the consistency of the composite application can be undermined. This paper examines how consistency can be created and retained in loosely coupled applications. In this context, use of semantic ontology, a technique to achieve and maintain consistency of composite applications using SOA is presented.
Keywords: Service Oriented Architecture (SOA), Agility, Coupling, Cohesion, Semantics, Ontology,
Web Ontology Language (OWL)
[...] The Semantic Annotations for WSDL and XML Schema (SAWSDL) recommendation33 builds upon and refines the concepts introduced in WSDL-S and is the official recommendation of the W3C (World Wide Web Consortium—responsible for many Web standards) for adding semantics to service descriptions, in particular WSDL 1.1 and WSDL An ontology is an exceptionally powerful mechanism for maintaining strong consistency. The ontology, of course, augments the service definition with semantics, helping to identify services that are appropriate. Digitally encoding these semantics enables searching for and validating the most appropriate services for a given need. [...]
[...] Just as a shift in the meaning or performance of a service may move the service away from its original intent, it can also coast toward performing a function more efficiently or more completely SEMANTICS Semantic SOA is standard base, ontology enabled, constraint driven approach that enables automatic service discovery and selection, dynamic information exchange and runtime process orchestration correction and optimization. For example, there may be a dependency on an approval service for completing purchase requests. There may be several approval services listed in the catalog of services that is consulted. [...]
[...] The remainder of this paper explores various aspects of consistency, how consistency can flow and the techniques and practices related to protecting the consistency of loosely coupled, service-based applications SERVICE ORIENTED ARCHITECTURE: OVERVIEW For considering the term service-oriented architecture, it is useful to review the key terms. An architecture is a formal description of a system, defining its purpose, functions, externally visible properties, and interfaces. It also includes the description of the system's internal components and their relationships, along with the principles governing its design, operation, and evolution. [...]
[...] Information Technology terrain in a given business is populated by many services, owned and maintained by different departments and lines of business, built with different underlying languages and technologies, driven by possibly disparate local concerns, registered and published for use across the enterprise, and then composed across distributed networks to orchestrate specific business processes. Several issues raised due to this such as , Building and connecting different services implemented using different technologies. Representing task and objective of each services. Defining and publishing actual capabilities of a service. [...]
[...] Defining precisely the consistency of loosely coupled applications as: ability to preserve the intent and behavior of the application in automating a business objective throughout the life cycle of the services used in the composition of that application.” 4. CONSISTENCY FLOW A frequent problem in loosely coupled systems is that services do not always retain their original be used without examining the semantics of the services that are available. Further, it is possible that the desired service is not called an approval service but rather goes by a completely different name, such as accredit. [...]
using our reader.