Bringing semantics to web services: the OWL-S approach
06 Jul 2004-pp 26-42
TL;DR: This paper shows how to use OWL-S in conjunction with Web service standards, and explains and illustrates the value added by the semantics expressed in OWl-S.
Abstract: Service interface description languages such as WSDL, and related standards, are evolving rapidly to provide a foundation for interoperation between Web services. At the same time, Semantic Web service technologies, such as the Ontology Web Language for Services (OWL-S), are developing the means by which services can be given richer semantic specifications. Richer semantics can enable fuller, more flexible automation of service provision and use, and support the construction of more powerful tools and methodologies. Both sets of technologies can benefit from complementary uses and cross-fertilization of ideas. This paper shows how to use OWL-S in conjunction with Web service standards, and explains and illustrates the value added by the semantics expressed in OWL-S.
Citations
More filters
01 Jan 2002
TL;DR: Knowledge management systems, Knowledge management systems , مرکز فناوری اطلاعات و اصاع رسانی, کδاوρزی
Abstract: Knowledge management systems , Knowledge management systems , مرکز فناوری اطلاعات و اطلاع رسانی کشاورزی
416 citations
TL;DR: This article establishes a consolidated analysis framework that advances the fundamental understanding of Web service composition building blocks in terms of concepts, models, languages, productivity support techniques, and tools and reviews the state of the art in service composition from an unprecedented, holistic perspective.
Abstract: Web services are a consolidated reality of the modern Web with tremendous, increasing impact on everyday computing tasks. They turned the Web into the largest, most accepted, and most vivid distributed computing platform ever. Yet, the use and integration of Web services into composite services or applications, which is a highly sensible and conceptually non-trivial task, is still not unleashing its full magnitude of power. A consolidated analysis framework that advances the fundamental understanding of Web service composition building blocks in terms of concepts, models, languages, productivity support techniques, and tools is required. This framework is necessary to enable effective exploration, understanding, assessing, comparing, and selecting service composition models, languages, techniques, platforms, and tools. This article establishes such a framework and reviews the state of the art in service composition from an unprecedented, holistic perspective.
277 citations
Cites background from "Bringing semantics to web services:..."
...It includes preconditions and (conditional) effects in the description of the Web services, as well as enriched semantic representations of Web service inputs and outputs [Martin et al. 2005]....
[...]
28 Feb 2005
TL;DR: This paper argues that the full richness of the Grid vision, with its application in e-Science, e-Research, or e-Business, requires the Semantic Grid, an extension of the current Grid in which information and services are given well-defined meaning.
Abstract: Grid computing offers significant enhancements to our capabilities for computation, information processing, and collaboration, and has exciting ambitions in many fields of endeavor. We argue that the full richness of the Grid vision, with its application in e-Science, e-Research, or e-Business, requires the "Semantic Grid." The Semantic Grid is an extension of the current Grid in which information and services are given well-defined meaning, better enabling computers and people to work in cooperation. To this end, we outline the requirements of the Semantic Grid, discuss the state of the art in achieving them, and identify the key research challenges in realizing this vision.
257 citations
Additional excerpts
...To this end, the Web Ontology Language for Services (OWL-S) [24] encodes rich semantic service descriptions [25] in a way that builds naturally upon OWL....
[...]
TL;DR: This article summarizes the SWSA committee's findings, emphasizing its review of requirements gathered from several different environments, and identifies the scope and potential requirements for a semantic Web services architecture.
Abstract: The semantic Web services initiative architecture (SWSA) committee has created a set of architectural and protocol abstractions that serve as a foundation for semantic Web service technologies. This article summarizes the committee's findings, emphasizing its review of requirements gathered from several different environments. We also identify the scope and potential requirements for a semantic Web services architecture.
250 citations
23 Jan 2006
TL;DR: This paper proposes the language grid to create composite language services for various communities to increase the accessibility and usability of online language services.
Abstract: To increase the accessibility and usability of online language services, this paper proposes the language grid to create composite language services for various communities. The language grid is called "horizontal," when the grid connects the standard languages of nations, or "vertical," when the grid combines the language services generated by communities. Semantic Web service technologies are applied in a human-centered fashion, to create composite language services through the collaboration of users and agents. Three example scenarios are given to illustrate how the language grid organizes standard and community language services for intercultural collaboration activities.
229 citations
References
More filters
01 Jan 2004
TL;DR: This document provides an introduction to OWL by informally describing the features of each of the sublanguages of OWL, the Web Ontology Language by providing additional vocabulary along with a formal semantics.
Abstract: The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. OWL facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL has three increasingly-expressive sublanguages: OWL Lite, OWL DL, and OWL Full. This document is written for readers who want a first impression of the capabilities of OWL. It provides an introduction to OWL by informally describing the features of each of the sublanguages of OWL. Some knowledge of RDF Schema is useful for understanding this document, but not essential. After this document, interested readers may turn to the OWL Guide for more detailed descriptions and extensive examples on the features of OWL. The normative formal definition of OWL can be found in the OWL Semantics and Abstract Syntax. Status of this document OWL Web Ontology Language Overview https://www.w3.org/TR/owl-features/ 1 de 14 09/05/2017 08:32 a.m. This document has been reviewed by W3C Members and other interested parties, and it has been endorsed by the Director as a W3C Recommendation. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. This is one of six parts of the W3C Recommendation for OWL, the Web Ontology Language. It has been developed by the Web Ontology Working Group as part of the W3C Semantic Web Activity (Activity Statement, Group Charter) for publication on 10 February 2004. The design of OWL expressed in earlier versions of these documents has been widely reviewed and satisfies the Working Group's technical requirements. The Working Group has addressed all comments received, making changes as necessary. Changes to this document since the Proposed Recommendation version are detailed in the change log. Comments are welcome at public-webont-comments@w3.org (archive) and general discussion of related technology is welcome at www-rdf-logic@w3.org (archive). A list of implementations is available. The W3C maintains a list of any patent disclosures related to this work. This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
4,147 citations
"Bringing semantics to web services:..." refers background in this paper
...In particular, the authors of this paper, members of the OWL-S Coalition, are developing the Ontology Web Language for Services (OWL-S) [25], which seeks to provide the building blocks for encoding rich semantic service descriptions, in a way that builds naturally upon OWL [19], the Semantic Web language undergoing standardization at the W3C....
[...]
Book•
05 Oct 2004
TL;DR: This book focuses on executable processes and comes back to abstract processes in Chapter 4, which can be used to replace sets of rules usually expressed in natural language, which is often ambiguous.
Abstract: processes are rarely used. The most common scenario is to use them as a template to define executable processes. Abstract processes can be used to replace sets of rules usually expressed in natural language, which is often ambiguous. In this book, we will first focus on executable processes and come back to abstract processes in Chapter 4. 21 This material is copyright and is licensed for the sole use by Encarnacion Bellido on 20th February 2006 Via Alemania, 10, bajos, , Palma de Mallorca, Baleares, 07006
3,772 citations
09 Jun 2002
TL;DR: In this article, the authors propose a solution based on DAML-S, a DAMLbased language for service description, and show how service capabilities are presented in the Profile section of a DAMl-S description and how a semantic match between advertisements and requests is performed.
Abstract: The Web is moving from being a collection of pages toward a collection of services that interoperate through the Internet. The first step toward this interoperation is the location of other services that can help toward the solution of a problem. In this paper we claim that location of web services should be based on the semantic match between a declarative description of the service being sought, and a description of the service being offered. Furthermore, we claim that this match is outside the representation capabilities of registries such as UDDI and languages such as WSDL.We propose a solution based on DAML-S, a DAML-based language for service description, and we show how service capabilities are presented in the Profile section of a DAML-S description and how a semantic match between advertisements and requests is performed.
2,412 citations
TL;DR: The authors propose the markup of Web services in the DAML family of Semantic Web markup languages, which enables a wide variety of agent technologies for automated Web service discovery, execution, composition and interoperation.
Abstract: The authors propose the markup of Web services in the DAML family of Semantic Web markup languages. This markup enables a wide variety of agent technologies for automated Web service discovery, execution, composition and interoperation. The authors present one such technology for automated Web service composition.
1,978 citations
01 Jan 2003
TL;DR: The BPEL4WS specification defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intracorporate and the business-to-business spaces.
Abstract: This document defines a notation for specifying business process behavior based on Web Services. This notation is called Business Process Execution Language for Web Services (abbreviated to BPEL4WS in the rest of this document). Processes in BPEL4WS export and import functionality by using Web Service interfaces exclusively. Business processes can be described in two ways. Executable business processes model actual behavior of a participant in a business interaction. Business protocols, in contrast, use process descriptions that specify the mutually visible message exchange behavior of each of the parties involved in the protocol, without revealing their internal behavior. The process descriptions for business protocols are called abstract processes. BPEL4WS is meant to be used to model the behavior of both executable and abstract processes. BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web services interaction model and enables it to support business transactions. BPEL4WS defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intracorporate and the business-to-business spaces. Status of this Document This is an initial public draft release of the BPEL4WS specification. We anticipate a number of extensions to the feature set of BPEL4WS that are discussed briefly at the end of the document. BPEL4WS represents a convergence of the ideas in the XLANG and WSFL specifications. Both XLANG and WSFL are superseded by the BPEL4WS specification. BPEL4WS and related specifications are provided as-is and for review and evaluation only. BEA, IBM and Microsoft hope to solicit your contributions and suggestions in the near future. BEA, IBM and Microsoft make no warrantees or representations regarding the specifications in any manner whatsoever.
1,910 citations
"Bringing semantics to web services:..." refers background or methods in this paper
...Other matching algorithms, such as in [28], [8], [2], and also again [13], assume that capabilities are described by the state transformation produced by the Web service....
[...]
...Nevertheless, other work on discovery does not assume OWL-S, most notably [2] which bases Web service descriptions on the MIT Process Handbook [12]....
[...]
...While OWL-S does not make such strong assumptions on the ontologies needed for discovery, when those assumptions are known to hold, results similar to those obtained in [2] can be obtained by using the matching processes suggested for OWL-S, by first selecting Web services with a given capability and then selecting those services whose process model satisfies the temporal constraint....
[...]