<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Ontologies - A Report</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Felix Engel</string-name>
          <email>felix.engel@tib.eu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sören Auer</string-name>
          <email>soeren.auer@tib.eu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Ontologies, Semantic Web, Sustainability, Visualization, Standardization</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Technische Informationsbibliothek (TIB)</institution>
          ,
          <addr-line>Welfengarten 1B, 30167 Hannover</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <abstract>
        <p>Supply chains are vulnerable and inherently complex processes. In-creasing the resilience of supply chains is realised, if the stakeholders involved have agreed on a clear language. Only this enables a comprehensive, unambiguous and fast exchange of information. Ontologies serve as a powerful formal tool to realize an appropriate communication framework. They are designed to make communication and information exchange between stakeholders and machines unambiguous and thus eficient. This paper addresses the challenges and solutions associated with the fact that ontologies need to reflect agreed definitions of a domain, as we face them in the SC3 and CoyPu projects.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The number of interlocking, disparate organizations and teams involved in a supply chain
quickly become an unmanageable extent. This collection of involved groups may include
various engineering teams, finance teams, production shippers, retail site and warehouse staf,
or shipping and logistics teams required to manufacture and distribute a product. Behind these
organizations and teams are decision makers who must communicate efectively with each
other. Even small misunderstandings in communication between decision makers can quickly
lead to far reaching consequences. Unambiguous and precise language is therefore the key
to a resilient supply chains. As an example [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], in 1999 the destruction of the Mars Orbit
Climater happened, because engineers have not clearly communicated between engineering
teams. One of the components was jointly constructed between a US and a UK team. While
some adopted metric units, others used English units. The damage amounted to 125 Mill USD.
As another example [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], in a transdisciplinary project result discussion with technical terms and
indicators, speaking about micro and macro nutrients. Soil scientists will discuss about nitrogen,
phosphorus, potassium, calcium, magnesium and sulphur. Nutritionists in turn will discuss
about carbohydrates, protein and fat. Even though the introduced examples are very striking,
they are representative of the obvious problem of miscommunication large and small. They
vividly illustrate the importance of agreeing on a commonly understood language throughout
all participants of the supply chain, that we will call a designated community. As a designated
community, we will use the ISO14721 definition [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]: An identified group of potential Consumers
who should be able to understand a particular set of information. Application ontologies for the
precise exchange of information, within and across designated community boundaries promises
to provide a remedy or at least relief. However, the creation and uptake of ontologies are not
trivial tasks, within this paper we will highlight reasons and introduce solutions from two
research projects that address these challenges.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Challenges of working on Ontologies</title>
      <p>An ontology is a tool that provides a formal representation of information to support its
automated exchange between machines. However, the creation, extension and adaptation of
the ontology is not a trivial task. In our opinion, the following four reasons are foundation for
this statement:
1. The work on comprehensive and expressive ontologies must take place in close
cooperation between domain experts and knowledge workers. Domain experts bring the
necessary knowledge about the domain in focus and knowledge workers their expertise
in creating high quality and hence usable ontologies. In order to ensure efective
collaboration, the communication between these two stakeholder groups must be considered in
a suitable form.
2. As the introductory example shows, interdisciplinary communities of soil scientists
and nutritionists, among others, have diferent conceptual allocations that make
errorfree communication dificult. The same is true for intraorganizational teams and
interorganizational exchanges. Ontologies are thus always specific to a particular community.
The provision of mappings to other ontologies is therefore an important prerequisite to
communicate across organizations and not to develop another isolated solution.
3. The definitions of terms implemented in the ontology change dynamically over time.</p>
      <p>Consequently, work on ontologies is an active, lengthy, and always ongoing process.
4. The ontology must be accepted and reused by the designated community, to achieve
stability and to be available in the long term. Therefore, they must be advertised and
aligned with existing ontologies.</p>
      <p>The following chapters describe how the challenges presented are addressed in the CoyPu
and SC3 projects. Finally, a summary of the challenges and the solutions presented is given.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Consideration of Diferent Competence Levels</title>
      <p>The first challenge, introduced in section two concerns collaborative work on creating and
extending ontologies. A decisive factor here is the collaboration between the domain experts
themselves and the knowledge engineers. The domain experts are familiar with the domain and
contribute with their knowledge to the unambiguous definition of a resource of this domain.
This through a reasoning process until a consensus is defined in the named community. The
knowledge engineer can guide the process; he/she has knowledge about the structure and
implementation of the ontology following various Semantic Web specifications and the tools to
realise the ontology. In order to facilitate these processes of agreement between the domain
experts, as well as the communication of the domain experts with the knowledge engineer, we
see the need for tools that translate the modelled information for diferent expert levels.</p>
      <p>It is precisely in this regard that we are working in the Semantically Connected Semiconductor
Supply Chains (SC3) communication and support action that is funded by the European
Commission on a communication framework as a solution to this challenge. The main use case of the
SC3 project concerns the creation of a unique framework for communication in semiconductor
supply chains. The potential for miscommunication is very high in this environment. The
SC3 project is therefore working on a lingua franca (DR, the digital reference ontology) to
promote semantic interoperability between semiconductor companies and other industries. To
support the collaborative work challenge of domain experts and knowledge engineer, in this
project we are working on a portal for validation, visualization, mapping, and customization
of DR-compliant developments. This environment is a web-based portal that enables visual
translation of the ontology content between diferent visualization types and serves as an
intuitive means to bridge the gap between diferent levels of knowledge and experience of
involved domain experts and knowledge engineers. Within this platform, we distinguish three
types of users. The Expert User is a knowledge engineer who knows how to build ontology
based on the project requirements, but does not have knowledge in a particular domain. The
Advanced User, on the other hand, has some knowledge in ontology developing implementation,
but not enough to make full of usage expert systems tools such as Protégé. The Novice User, on
the other hand, has no knowledge of how to use Semantic Web standards and tools for ontology
development.</p>
      <p>Our assumption is that expert users must most likely be knowledge workers. These workers
are interested in a fully comprehensive and accurate information representation. Therefore,
we provide formal visual representations for these stakeholders in expert mode. These are a
UML-based and a text-based representation of the ontology. The advanced users of our portal,
on the other hand, may already have experience with Semantic Web technologies and may have
some initial experience with tools such as Protégé. For this user group, we therefore provide
tree- and widget-based visualizations of ontologies. These forms of visualization can be used
to query information, while still keeping the overview relatively simple. Finally, there is the
Novice User. For this user, we have provided rather simple graph-based visualizations that focus
on visualizing direct relationships of definitions of resources of the domain. To simplify these
very diferent collaborative editing requirements, our system uses the Relation Resource Model
(RRM). This model serves as a neutral representation format and as such allows the ontology
to be represented in all of these diferent formats mentioned. Our thesis is that these diferent
visualization types enable and stimulate collaborative work on ontology development by serving
as translators that translate the information encoded in an ontology between diferent levels of
performance.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Ontology Take Up and Reuse</title>
      <p>
        Projects that aim to create or revise ontologies face the challenges 2 – 4. An inherent interest of
these projects therefore is to work towards the long-term availability of the developed ontology.
We see as a core factor for this that care is taken during development to use established ontologies
as much as possible and to build as extensive and active a community as possible. This is the only
way to ensure that work on the ontology will continue after the end of a funding phase. In the
BMBF-funded project Cognitive Economy Intelligence Plattform für die Resilienz wirtschaftlicher
Ökosysteme (CoyPu), research is being conducted on realising an AI based platform to support
economic resilience. This is based on semantic technologies to allow eficient crisis management.
In this project, we are working on a communication framework to find a common language
and understanding in the supply chain environment. In particular, the aim is to identify the
interrelationships of influential events at an early stage, visualize them in the context of other
information, and communicate them in order to define strategies for the further preservation
of the supply chain. Agreeing on a common language for information exchange between
such supply chains is a complex endeavor, which we address by developing COY ontology
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. The COY ontology should help us to visualize the relationships between entities and their
dependencies on events. For example, we may consider environmental events that afect the
transportation infrastructure or political unrest or pandemics that afect the production and
delivery of components of a production. For the development of this ontology, we follow best
practices, as a first step to work with our use case partners in order to develop competency
questions. In a next step, we have evaluated existing ontologies for their applicability to the
challenges arising from the competence questions. The goal here is to achieve as much overlap
as possible with established ontologies in order to achieve a cross-community understanding
(see point 2 of the challenges) of our ontology outside our consortium as well. To address the
problem of reuse and alignment with established ontologies, but also to make our COY ontology
known and accessible to a wide audience (see point 4 of the challenges), we agreed to use a
Terminology Service provided by the NFDI [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] initiative. The Terminology Service (TS) is a
web-based platform that supports the adoption and standardization of ontologies by providing
data and knowledge management capabilities for accessing, maintaining, and subscribing to
domain-specific terminologies. Initially, we plan to use the TS to compile a comprehensive
collection of relevant ontologies so that they are available to all partners in one place. This
enables especially easy search in those ontologies for resources that we can reuse in the COY
ontology. On the other hand, we have also made our COY ontology visible and accessible to other
users of the TS. This is already a first step of the integration of the COY ontology into external
applications. Various external applications are connected to the TS, which query the managed
ontologies and integrate them into external applications using a REST interface. Among other
things, this integrates the COY ontology directly into the browser plugin TermClick [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This
plugin is configured to retrieve concepts from the ontology for a selected text. This can be done
by checking whether a term is used correctly in the corresponding domain by definition, or
simply to view its definition.
      </p>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusions</title>
      <p>In this paper, we introduced and discussed two projects in which the creation of ontologies is
pursued from diferent perspectives. From these projects, we have derived some overlapping
requirements. These requirements are of a general nature and can therefore be transferred to
the work with ontologies in other projects. In general, they concern the interaction between
domain experts and knowledge engineers. Therefore, we need a mean to help these two parties
to gain the same understanding about the information encoded in the ontology. In this context,
we have presented a solution approach that allows meeting the diferent needs on a visual
basis. To this end, we are working on a web-based solution that allows overcoming an existing
communication barrier in a collaborative way and using visual tools. The development of this
solution is currently still in demonstration mode. In addition to the challenge of mediating
between domain experts and knowledge workers, we also see the major challenge of ontologies
being community specific in order to help achieve a common understanding as such. Therefore,
in order to achieve the highest possible level of agreement within this community, we think
that early and comprehensive alignment and harmonization with established ontologies is a
crucial part of development. This is then, of course, conducive to other communities. Because
of this basis other communities can likewise achieve an increasing harmonization with the
COY ontology. We address the above challenges with the help of the TS. This service enables
the unification of the ontology under development by allowing a comparison with established
ontologies. In addition, the TS make the ontology amenable to a larger community, as well as
for use in third-party applications. This is, among other things also a decisive factor, which
it can succeed to keep ontology in active development even beyond a funding period. In this
respect, we also see a great potential for the connection of tools like the TS with the SC3 tools
and WebProtégé.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Acknowledgments</title>
      <p>This work documents results from two projects: The research has received funding from the EU
KDT Joint Undertaking under grant agreement n° 101007312 (project Semantically Connected
Semiconductor Supply Chains - SC3) and by the Federal Ministry for Economic Afairs and
Energy of Germany in the project Cognitive Economy Intelligence Plattform für die Resilienz
wirtschaftlicher Ökosysteme - CoyPu (project number 01MK21007[A-L]).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>I.</given-names>
            <surname>Jordan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Heil</surname>
          </string-name>
          , G. Keding,
          <article-title>Coming to terms with terminology in agriculture-nutrition research projects: an interactive glossary</article-title>
          ,
          <source>Ernahrungs Umschau</source>
          <volume>68</volume>
          (
          <year>2021</year>
          )
          <fpage>198</fpage>
          -
          <lpage>203</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Stewart</surname>
          </string-name>
          ,
          <article-title>Mars orbiter disaster - a failure of data management, 2015</article-title>
          . URL: https://tdan. com
          <article-title>/mars-orbiter-disaster-a-failure-of-data-management/5128.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <article-title>[3] Open archival information system (oais</article-title>
          ),
          <year>2012</year>
          . URL: https://www.iso.org/standard/57284. html.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Coy</surname>
            <given-names>ontology</given-names>
          </string-name>
          ,
          <year>2022</year>
          . URL: https://gitlab.com/coypu-project/coy-ontology.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <source>[5] Nfdi4ing ts</source>
          ,
          <year>2022</year>
          . URL: https://terminology.nfdi4ing.de/ts4ing/index.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Termclick</surname>
          </string-name>
          ,
          <year>2022</year>
          . URL: https://addons.mozilla.org/en-GB/firefox/addon/termclick.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>