The technology resolves semantic ambiguities in the descriptions of Web service interfaces by combining information retrieval and semantic Web techniques. Information retrieval techniques are used to resolve the domain-independent relationships. For example, in this approach, semantic similarity is derived using an English thesaurus after "tokenization" and part-of-speech tagging of the names of the elements that describe the interfaces of Web services.
Semantic Web techniques are used to resolve domain-specific similarities. For example, the
Annotation is the process of associating metadata with data. This article presents a Web services API intended as an industry standard for client-server systems designed to facilitate the structured annotation of heterogeneous data. The author presents the goals of the Annotation Web services API and then discusses how those goals motivate the data model around which the API operates. The author also discusses 29 methods that comprise the API including two examples of possible sequences of API calls to create and retrieve annotations.
The Annotation
The members of the METEOR-S project are happy to announce the support for SAWSDL(Semantic Annotations for WSDL)
SAWSDL is a simple extension of WSDL using the extensibility elements. It has two basic types of annotations, the model reference and the schema mapping. The model reference annotation, the same as the WSDL-S model reference, is used to associate interfaces/port types, operations, inputs, outputs, and xml schema elements and attributes with Semantic Concepts. Model reference annotations are used by the METEOR-S framework to support the
Abstract
Web Services Description Language (WSDL) provides a model and an XML format for describing Web services. This document describes a representation of that model in the Resource Description Language (RDF) and in the Web Ontology Language (OWL), and a mapping procedure for transforming particular WSDL descriptions into their RDF form.
Status of this Document
This document is an editors' draft and has no formal standing within W3C, it is submitted for consideration of the Web Services Description Working Group.
This section describes the