Databases Reference
In-Depth Information
storage feature for replicating parts of the knowledge base on the mobile device. Hence,
a crucial part of OntoWiki Mobile is the advanced conflict resolution for RDF stores.
The approach is based on a combination of the EvoPat [132] method for data evolution
and ontology refactoring along with a versioning system inspired by distributed version
control systems like Git. OntoWiki Mobile is a generic, application domain agnostic
tool, which can be utilized in a wide range of very di
erent usage scenarios ranging
from instance acquisition to browsing of semantic data on the go. Typical OntoWiki
Mobile usage scenarios are settings where users need to author and access semantically
structured information on the go or in settings where users are away from regular power
supply and restricted to light-weight equipment (e. g. scientific expeditions).
ff
Semantics-Based Requirements Engineering.
Semantic interoperability, linked data,
and a shared conceptual foundation become increasingly important prerequisites in soft-
ware development projects that are characterized by spatial dispersion, large numbers
of stakeholders, and heterogeneous development tools. The SoftWiki OntoWiki exten-
sion [93] focuses specifically on semantic collaboration with respect to requirements
engineering. Potentially very large and spatially distributed groups of stakeholders, in-
cluding developers, experts, managers, and average users, shall be enabled to collect,
semantically enrich, classify, and aggregate software requirements. OntoWiki is used
to support collaboration as well as interlinking and exchange of requirements data. To
ensure a shared conceptual foundation and semantic interoperability, we developed the
SoftWiki Ontology for Requirements Engineering (SWORE) that defines core concepts
of requirement engineering and the way they are interrelated. For instance, the ontol-
ogy defines frequent relation types to describe requirements interdependencies such as
details, conflicts, related to, depends on, etc. The flexible SWORE design allows for
easy extension. Moreover, the requirements can be linked to external resources, such as
publicly available domain knowledge or company-specific policies. The whole process
is called semantification of requirements. It is envisioned as an evolutionary process:
The requirements are successively linked to each other and to further concepts in a
collaborative way, jointly by all stakeholders. Whenever a requirement is formulated,
reformulated, analyzed, or exchanged, it might be semantically enriched by the respec-
tive participant.
5
Linking
The fourth Linked Data Principle, i.e., “Include links to other URIs, so that they can
discover more things” (cf. section 2) is the most important Linked Data principle as it
enables the paradigm change from data silos to interoperable data distributed across the
Web. Furthermore, it plays a key role in important tasks such as cross-ontology ques-
tion answering [22,94], large-scale inferences [151,99] and data integration [95,19].
Yet, while the number of triples in Linked Data sources increases steadily and has sur-
passed 31 billions
11
, links between knowledge bases still constitute less than 5% of
these triples. The goal of linking is to tackle this sparseness so as to transform the Web
into a platform for data and information integration as well as for search and querying.
