Countering Service Information Challenges in the Internet of Services

Abstract

The Internet of Services is commonly referred to as the underlying platform for realizing ad-hoc value networks in the web. In the case of decentralized service discovery, brokerage, or community feedback, there emerge a number of service information challenges that have to be addressed. In this paper, we propose to counter such service information challenges by two artifacts. First, we contribute a Service Ontology as a consistent and holistic way of capturing service information. The ontology is constructed in an interdisciplinary and collaborative way and formalized with W3C Semantic Web recommendations. Second, we provide for the methodological aspects around the ontology including a governance framework and guidelines for interlinking information.

A unified description language for human to automated services

“…Although differing in its main notions, they present ontological foundations of service science modeled according to the basic principles of ontological analysis. In turn, this reference ontology forms the core part of the TEXO Service Ontology [25]. In addition, it features ontology modules for pricing, legal, innovation, or rating information.…”

Towards a Commitment-Based Reference Ontology for Services

“…RELATED WORK OWL-S [40] and WSMO [41] are Semantic Web Service ontologies that focus mainly on technological aspects and are usually applied for automating tasks such as service discovery and composition [42]. These ontologies are not based on foundational ontologies and none of them addresses the notion of commitments.…”

“…The Service Ontology proposed [42] is structured in such way that the core modules span several application domains, such as healthcare, and automotive, and are also grounded by the upper level model, which consists of a concise foundational ontology (DOLCE [21]). By that, we consider this ontology as core reference ontology.…”

A novel SLA-aware approach for web service composition

“…Computational independent workflows are designed using graphical notations such as BPMN 2.0 [9], UML AD [10], USDL [11].…”