Countering Service Information Challenges in the Internet of Services

Abstract

Business Webs apply the idea of value networks to the WWW. The underlying delivery platform is commonly referred to as the Internet of Services and will certainly have to deal with a great variety and amount of information about services along several service information dimensions. As soon as brokerage, discovery, or community feedback parts are decentralized, there emerge a number of service information challenges (modeling the information in a holistic way, documentation, interlinkage, tool interoperability, distributed querying, inconsistent information, and cooperation of different stakeholders). In this paper, we propose to counter such service information challenges by two artifacts. First, we contribute a Service Ontology based on a sound and rigid foundational ontology. The Service Ontology provides a holistic and consistent way of capturing service information. We apply the recommendations of the W3C Semantic Web Activity whose recent standardization has already opened new possibilities for tool interoperability, interlinkage of information, and distributed querying on the web. However, building and prescribing an ontology in standardized languages is not enough to address all service information challenges. Therefore, as a second contribution, we provide a method around the ontology including a governance framework, guidelines for applying the W3C Semantic Web recommendations, a lifecycle-spanning tool chain, and different levels of applicability. We label our method Semantic Business Web approach, since we build on W3C Semantic Web standards, use and extend them in the Business Web setting. Both artifacts are constructed in an interdisciplinary way by experts participating in the German lighthouse project THESEUS/TEXO. The project's scenario also serves as a proof of concept evaluation of the artifacts

Visual Semantic Analysis to Support Semi-Automatic Modeling of Semantic Service Descriptions

“…facilitates service analysis and semantic extraction. 3. supports semi-automatic modeling of new service description by reusing and adapting the extracted semantics.…”

“…How to support users to deal with the complexity of SD modeling? 3. What is the process model for the VSA?…”

“…The two boxes at the bottom in Figure 2. 3 show binding of the interface of a service. The port/endpoint defines address or connection to a specific endpoint of a service.…”

“…There is redundant information in concept lattice. The two kinds of redundancy can be eliminated from concept lattice without loosing any information as shown in [3]: redundant elements in formal concepts intents and redundant objects in formal concepts extents. Our reduction procedure has 2 steps: elimination of redundant elements from formal concepts intents and elimination of lattice of extents.…”

“…This section gives an overview of concrete requirements as described in sections 4.2.1, 4.2.2, and 4.2. 3. The requirements are grouped to nine requirements categories.…”