<!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>Exploration of core concepts required for mid- and domain-level ontology development to facilitate explainable-AI-readiness of data and models</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Martin T. Horsch</string-name>
          <email>martin.thomas.horsch@nmbu.no</email>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Silvia Chiacchiera</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ilian T. Todorov</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ana Teresa Correia</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aditya Dey</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Natalia A. Konchakova</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sebastian Scholze</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Simon Stephan</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kristin Tøndel</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arkopaul Sarkar</string-name>
          <xref ref-type="aff" rid="aff6">6</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>M. Hedi Karray</string-name>
          <xref ref-type="aff" rid="aff6">6</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fadi Al Machot</string-name>
          <email>fadi.al.machot@nmbu.no</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Björn Schembera</string-name>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ATB Institut für Angewandte Systemtechnik Bremen GmbH</institution>
          ,
          <addr-line>Wiener Str. 1, 28359 Bremen</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Helmholtz-Zentrum Hereon, Institute of Surface Science</institution>
          ,
          <addr-line>Max-Planck-Str. 1, 21502 Geesthacht</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Norwegian University of Life Sciences, Department of Data Science</institution>
          ,
          <addr-line>Postboks 5003, 1432 Ås</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>RPTU Kaiserslautern, Laboratory of Engineering Thermodynamics</institution>
          ,
          <addr-line>67663 Kaiserslautern</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>UKRI Science and Technology Facilities Council, Scientific Computing Department</institution>
          ,
          <addr-line>Daresbury WA4 4AD</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>University of Stuttgart, Institute of Applied Analysis and Numerical Simulation</institution>
          ,
          <addr-line>70569 Stuttgart</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff6">
          <label>6</label>
          <institution>University of Technology Tarbes Occitanie Pyrénées, Production Engineering Lab</institution>
          ,
          <addr-line>47, av. d'Azereix, Tarbes</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This position paper reports on the initial discussions within the Knowledge Graph Alliance's working group on explainable-AI-ready data and metadata principles, which was created in March 2024. At present, we are taking initial steps toward capturing core concepts related to explanation, grounding, reliance, and trust; the scope also extends to potential dual notions such as explainability, verifiability/reproducibility, reliability, and trustworthiness. These initial steps consist in reviewing core concepts as they are discussed in the literature and exploring what could be practically useful definitions of these most central concepts. One of the conclusions is that the metadata standards will need to be suitable for documenting three kinds of grounding: Grounding of knowledge, grounding of reliance, and grounding of trust. Pre-existing metadata standards at the mid and domain level are presently undergoing a redesign in order to become more modular, computationally tractable, intelligible to humans, and adjustable, which will be needed as we continue our work toward actionable recommendations. The development of this system of lite (OWL 2 EL) ontologies, called MSO-EM: Ontologies for modelling, simulation, optimization (MSO) and epistemic metadata (EM), is carried out on a public repository.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Applied ontology</kwd>
        <kwd>epistemic metadata</kwd>
        <kwd>explainable-AI-ready (XAIR)</kwd>
        <kwd>ontology redesign</kwd>
        <kwd>reliability</kwd>
        <kwd>reproducibility</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        This work is part of ongoing discussions within the Knowledge Graph Alliance’s working group
Explainable-AI-ready data and metadata principles (XAIR principles).1 This working group will develop
recommendations (principles) that, if followed, contribute to making data and models
explainable-AIready (XAIR). This will be supported by metadata standards, specifically, for epistemic metadata, i.e.,
metadata related to the knowledge status of data and models. To our understanding, data and models
are XAIR to the degree that they are semantically enriched in such a way as to facilitate making best
use of explainable learning techniques, broadly understood. That is, first, this does include XAI as
it is commonly understood in a narrow sense, such as techniques based on Shapley values or local
interpretable model-agnostic explanations [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. But it also extends to deductive reasoning, since a logical
or mathematical proof can be considered an explanation of that which is being proven; there, our group
is particularly interested in providing a XAIR documentation to answer set programming as well as
reasoning applied to (fragments of) OWL description logic. Third, our notion of explainable learning also
includes simulation based on models that have some structural agreement with the phenomenon that is
being modelled; there, most saliently, physics-based modelling such as molecular simulation. Eventually,
it is the aim of the working group to advance good practices in data and metadata documentation
that help feeding models and data obtained in all sorts of ways into frameworks where they become
reusable to all these modalities of explainable learning. This means that not only the output from an
explainable learning technique has to become XAIR, but also the input – such as the datasets used for
training, validation, and testing in machine learning, or experimental data that are used to parameterize
and validate a molecular model. It is as of now not yet characterized what exact prerequisites need
to be met to achieve «XAIR status»; instead, this is supposed to be a result from the working group’s
community consultations. We expect it to be centered on model and data documentation through
appropriate metadata, just as it is the case for the FAIR principles [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Accordingly, the recommendations
for explainable-AI-readiness will build on FAIR, and then go beyond it.
      </p>
      <p>
        It is a notorious issue in XAI that core concepts such as explainability, interpretability, etc., are most
often used without any clearly communicated conceptualization of what they would entail [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]; but in a
technical context, clear definitions of technical terms are a necessity, all the more for a task like ours:
Supporting data documentation for XAI-readiness. To our work, central questions at this stage include:
      </p>
      <sec id="sec-1-1">
        <title>1. What properties do objects  and  need to have as a prerequisite for  relying on ?</title>
        <p>
          2. How about  trusting ?
3. What characterizes the diference between trust and reliance?
4. What characterizes the diference between explanations and grounding?
5. What semantic artefacts need to be put in place so that the above can be documented?
The XAIR principles WG has been formed in March 2024, and its work plan for the time being extends
over 40 months, until June 2027. At the present stage, we are engaged with meta-reviewing what
perspectives from the literature need to be taken into account, regarding questions such as those
mentioned above, but also to identify the core concepts to XAI-readiness and explore what definitions
they have been given. The outcome of this exploration will feed into discussions on actionable definitions
of the key concepts that the WG itself will accept; these will then be used for a revision of the previously
developed ontologization of cognitive processes and epistemic metadata [
          <xref ref-type="bibr" rid="ref4 ref9">4</xref>
          ]. First, however, that
preexisting ontology, PIMS-II, needs to be redesigned into a simpler framework to become more amenable
to the planned work. It will for that purpose be split into multiple lite mid- and domain-level OWL 2 EL
ontologies, improving tractability of reasoning tasks as well as intelligibility to developers. Eventually,
as an output from the group’s work, reference ontologies will be provided to users who want to use them
to document models and data in a XAIR way. Nonetheless, «XAIR status» is to be ontology-agnostic,
and users will in no way be required to use these ontologies or give preference to them over others that
support achieving compliance with the recommendations for explainable-AI-readiness equally well.
        </p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. Literature on the core concepts for explainable-AI-readiness</title>
      <p>
        A list of XAIR core concepts has been issued as part of a recent announcement [
        <xref ref-type="bibr" rid="ref10 ref5">5</xref>
        ]. It comprises:
«Explainability and explanation; reproducibility, reliability, and reliance; opacity and transparency,
interpretability and interpretation; DIKW: Data, information, knowledge, and wisdom; responsibility,
trust, trustworthiness, and [. . . ] motivations for trusting; model design, parameterization, and
optimization; holistic validation and unit testing (of models and simulation codes); theoretical virtues (of models);
epistemic agents, vices, and virtues; the four elements of FAIR [. . . ]; simulation; applying and evaluating
models; context awareness, subject matter, and logical subtraction» [
        <xref ref-type="bibr" rid="ref10 ref5">5</xref>
        ]. At present, we are conducting a
preliminary literature analysis on a subset of the above. We call this a meta-review, since the resources
that we are evaluating are themselves already reviews (or other aggregated material). The aim is not to
obtain a complete understanding of how all these matters have been discussed in the literature from
all possible angles, but to sample a variety of perspectives as an initial guidance to discussions about
recommendations for good practice in explainable-AI-ready data and model documentation.
      </p>
      <sec id="sec-2-1">
        <title>2.1. Wisdom hierarchy as reviewed by Rowley</title>
        <p>
          A hierarchy according to which data (D) can be analysed/improved qualitatively first to information (I),
then to knowledge (K), and finally to wisdom (W) has a long tradition in data management and is often
visualized as a DIKW pyramid. This «hierarchy» is not a taxonomy, i.e., wisdom is not understood to
be a subclass of data, or vice versa; instead, D → I → K → W is a kind of value chain or dialectical
sequence. For the present exploration, the review by Rowley [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] is our starting point. The review is
from 2007, but measured by the time scale of progress within epistemology, that means it is recent.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Agency as reviewed by Conte</title>
        <p>
          Within the present framework, we want to keep the concept of agency at a very general level, so that
(almost) anything can be analysed as an agent, similar to the use that is made of the concept of a system
in thermodynamics. Here, if a system has something that can be understood as sensors and actuators
or is by means of some other mechanism capable of perceiving and doing, it can be analysed as an agent.
This makes it all the more important to include a taxonomy of agents as part of an associated mid-level
ontology, since more specific subclasses will be needed to talk about kinds of agents. Our point of
departure in this field is given by the review and the definitions proposed by Conte [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Reproducibility as reviewed by Plesser</title>
        <p>
          Reproducibility is a key component of industry standards, as seen in Quality Management Systems like
ISO 9001, which emphasize reproducibility through consistent quality management practices, requiring
detailed documentation and standardized procedures to ensure reliable process repetition [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Journals
are now encouraging or requiring the submission of data and code alongside published articles to enable
the replication of results, while platforms like the Open Science Framework promote open access to
research materials, enhancing reproducibility by providing researchers with the tools to share their data,
code, and protocols openly [9]. However, the drive for novel results obtained from complicated methods
often leads to practices that hinder reproducibility [10]. A balance is needed to ensure that research
outputs are both innovative and reproducible [11]. Plesser’s concise review [12] is the starting point for
our exploration of frameworks suitable for documenting reproducibility claims and the validation of
such claims; see also Section 3.3, as well as previous work where this was discussed more in depth [13].
        </p>
      </sec>
      <sec id="sec-2-4">
        <title>2.4. Trust as reviewed by Ohlhorst and the ONTrust reference ontology</title>
        <p>Ohlhorst [14], beside making his own philosophical argument on the nature of trust, provides an review
on concepts that are central to his theory, in particular, hinge, entitlement, and virtue. Ohlhorst’s work
and the state of the art summarized therein need to be taken into account for our working group’s
discussions on the relation between explanations and trust in AI systems (Section 3). Attempts at
ontologization can build on the ONTrust reference ontology by Baratella et al. [15].</p>
      </sec>
      <sec id="sec-2-5">
        <title>2.5. Reviews from the OntoCommons and CHEIKHMAT projects</title>
        <p>The Review of Domain Interoperability [16] (RoDI) is a deliverable from the OntoCommons project
(H2020 GA no. 958371) that preceded the formation of the Knowledge Graph Alliance. The purpose
of the RoDI document is to provide a foundation to discussions and technical innovation addressing
domain-level interoperability now that OntoCommons is completed and in its place, the KGA has been
created as a self-sustaining organization. As such, RoDI both reviews and provides recommendations
for designing semantic artefacts. These fit into the OntoCommons ecosystem [ 17] (OCES) that permits
a plurality of foundational ontologies (DOLCE [18], EMMO [19], BFO [20]), and strategies for semantic
heterogeneity and alignment, such as bridge concepts. This approach forms part of the background to
the ongoing ontology redesign (cf. Section 4) within the KGA’s working group on XAIR principles.</p>
        <p>
          In addition, the interoperability requirements matrix from RoDI [16, Section 5.1] develops an
understanding of key concepts that can be related to the wisdom hierarchy, at the level of successfully
communicating knowledge that, in the DIKW pyramid, is referred to as wisdom [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. There, RoDI
distinguishes interoperation of data, humans, software, and organizations, and three interoperability levels:
Syntactic, terminological/semantic, and pragmatic [16]. In addition to this output from OntoCommons,
the CHEIKHMAT project has recently produced a review that very closely connects to our ongoing
survey of key concepts, with a focus specifically on ontology-based and semantics-based XAI [21].
The list of sources and topics included in this first efort is far from suficient. Given the task of the
working group, it urgently has to be expanded by catalogues or reviews of explainability metrics [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ],
since this is a key part of what will need to be documented in practice. As an output by month 10 of the
group’s work plan (December 2024), a Synopsis of XAIR Core Concepts will be delivered, which will take
the form of proceedings from a workshop organized by the projects AI4Work and BatCAT [
          <xref ref-type="bibr" rid="ref10 ref5">5</xref>
          ].
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Exploration of actionable key concepts</title>
      <sec id="sec-3-1">
        <title>3.1. Reliance and reliability</title>
        <p>It does not make sense to speak of an agent  as relying upon something unless it is done in view of
some objective  . In other words, there must be an adverse consequence for the agent if the relationship
fails; namely, that an expected outcome is not achieved. We do not for now require goal-directedness,
i.e.,  is not required to have an awareness or internal representation of  as the agent’s intention; but it
is necessary for  to be goal-oriented, i.e., have an objective (conscious or not). The entity acting as the
subject of a reliance relationship (that which does the relying) must therefore be a goal-oriented agent.</p>
        <p>The reliance relation can be formalized as:
• The ternary predicate « relies on  about », where  is an interlocutor, i.e., another agent (this
can also e.g. be a queriable software running on a machine), and  is the subject matter that the
relationship is about. This realizes itself by  relying upon the following rule: «The antecedent
“agent  asserts , where  is about subject matter ” necessarily implies the consequent .»
• A more general ternary predicate « relies upon rule  for  », where  : □ ℓ( → ) can be any
rule according to which antecedent  necessarily (to the degree ℓ) implies consequent . This is to
be interpreted loosely, e.g.,  and  will usually share free variables, with universal quantification
applied to these variables. For the reliance relationship to work in practice, it is necessary for 
to also rely upon : At some point in time,  may know (or not know, but act as if)  holds, so
the rule can be applied. Otherwise, reliance or non-reliance upon  remain indistinguishable.
The index ℓ of the necessity operator represents the level of necessity at which the rule  is
understood to apply; e.g., in some cases, exceptions may be tolerated, and in some cases, there
may be a margin within which quantitative deviations can be accepted. Descriptors for this can
become complicated, see the discussion of what-you-see-is-what-you-get guarantees in Grote et
al. [22]. For the predicate «relies on», the level ℓ() is understood to be contained in the subject
matter . Here, the notion of aboutness or subject matter can be taken to be that from Yablo [23].
• The even more general ternary predicate « relies upon  for  », where  can be any proposition,
not restricted to a rule. The reliance relationship only makes sense if  somehow causally
contributes to  : It must deliver some contribution to the agent  reaching the goal  .
Rule  : □ ℓ( → ) is reliable whenever it is true, i.e., whenever  implies consequent  to the level ℓ.</p>
        <p>In action, the relationship of reliance is not constituted by the agent  believing or knowing that the
rule holds; i.e., that under all the described conditions,  is actually true. That may or may not be the
case. Instead, the agent  practices reliance upon a rule  by behaving as if  knew that  was reliable,
or in terms that will be clarified further below (Section 3.2), in  emulating an agent ′ such that  is
grounded to . The emulated agent ′ is identical to  in all respects other than about acceptance of 
as knowledge. The relation of relying on someone can accordingly be expanded as
 relies on  about 
≡
≡
 relies upon rule (, ) : □ ℓ() ∀ (( is about  ∧  asserts ) → ) (1)
about (),  emulates ′, who is like , except that ′ knows (, ). (2)
Therein, () refers to the scope of reliance upon . The above does not exclude the case where  really
knows  to be true. In that case, it simply reduces to  = ′; i.e., grounded reliance does not require 
to emulate another hypothetical agent who accepts  as knowledge, since  already is that agent.</p>
        <p>Based on the above, we can characterize agents’ reliability: Interlocutor  is reliable about  whenever
the rule (, ) from the right-hand side of Proposition (1) is reliable, i.e., whenever it is true.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Grounding and explanations</title>
        <p>
          A proposition/rule and the associated reliance relationship is grounded to some agent  if that agent
knows it to be true. The most relevant case of this is applying this definition with  = , i.e., asking
whether the agent who does the relying has suficient knowledge to ground that reliance relationship (if
that is not the case, we can infer that the agent trusts in the relationship, instead of knowing). However,
we can also insert ourselves as ; in this case, the question becomes whether we know the rule that is
relied upon to be true, i.e., whether ’s reliance relationship is grounded to us (only then, we would
say that the rule is reliable). Following this approach, reliance is grounded in knowledge. Accordingly,
ifrst, some information would need to be established as having the status of knowledge – grounding of
reliance presupposes grounding of knowledge. The question of what exactly can ground knowledge,
and how that is to be documented, is at the core of the problem of standardizing epistemic metadata [
          <xref ref-type="bibr" rid="ref4 ref9">4</xref>
          ].
        </p>
        <p>Reliance does not require any grounding, i.e., we can rely on someone or upon something without
knowing that this will be successful and lead to the intended outcome. In that case, we say that we trust.</p>
        <p>Any relationship of trust presupposes that there is a relationship of reliance that is ungrounded to the
trustor , i.e., the relying and trusting agent: Where knowledge would be needed to ground the reliance
relationship, that knowledge is absent. This can be either because the rule that the agent relies upon is
in fact unreliable, or because while it is in fact reliable, that fact is not known to . With Proposition (2)
we can summarize that according to our tentative formalization proposed here, if  trusts in (and,
therefore, does not know) some  , that is realized by  emulating an agent ′ who is like , except
that ′ knows  (and, therefore, does not trust in  ). This emulation is limited to a scope ( ), namely,
the scenarios that the proposition is intended to be applied to, i.e., those that it is about [23].</p>
        <p>Similar to reliance, trust does not require any grounding: An agent can trust blindly in someone or
something without any good reason at all. However, trust can also be grounded [24], i.e., an entitlement
(epistemic warrant) can be provided in many diferent ways [ 14], all of which can be called explanations.
Societal norms and community practices can impose limits on what behaviour around trust is acceptable:
The agent can be held responsible by the community to trust only in appropriate agents or propositions.
In science, naturally, blind trust is not tolerated, while as Koskinen [25] points out, some trust is necessary.
The space between the necessary and the forbidden trust in data-driven modelling would need to be
characterized by a social epistemology that, following Koskinen, still needs to be developed [25].</p>
        <p>For guidelines that advance XAIR models and data, it is therefore a requirement to develop
metadata standards (cf. Section 4) for documenting three kinds of grounding: First, epistemic grounding,
or grounding of knowledge, in line with practices that are accepted as scientific within a scientific
community; second, grounding of reliance by knowledge; and third, grounding of trust by explanations.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Reproducibility and transparency</title>
        <p>Reproducibility ensures the capacity to consistently replicate results under identical conditions,
providing reliability and verification, cf. Section 2.3. Key elements include documentation, standardization,
and data availability; where these are absent, we speak of dark data [26, 27, 28].</p>
        <p>Good practices in research data management avoid dark data and facilitate reproducibility, e.g.,
by complying with suitable documentation and transparency requirements. Transparency involves
providing clear, accessible, and understandable information about processes, enabling scrutiny and
understanding. The key components include clarity, accessibility, accountability, and traceability.</p>
        <p>We remark that the notion of an «implication necessary to level ℓ» proposed in Section 3.1 for rules
upon which agents rely is similar to, and can probably be unified with, the «conditional necessity of  ,
given  » proposed in previous work [13] to formalize the semantics of a reproducibility claim.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Mid- and domain-level ontology redesign</title>
      <p>
        Once the discussions on the core concepts are further progressed, the synopsis has been copiled, and
own definitions of core concepts are suficiently mature, our working group will provide recommended
metadata standards for annotating models and data in a way that improves their XAI-readiness. There
is a major element to this from previous work that will require a redesign: The PIMS-II ontology [
        <xref ref-type="bibr" rid="ref4 ref9">4</xref>
        ]
was developed for cognitive processes (with a focus on research workflows as cognitive processes) and
epistemic metadata (knowledge claims, provenance, and validity claims). This is, however, too broad
for a single ontology to be easily accessible to users; it is even less suitable for a focused discussion of
key concepts, since it will be hard to adjust such a monolithic conceptual scheme to novel perspectives
that might be agreed upon as an outcome from group discussions. In addition, PIMS-II has developed
substantial philosophical overhead (with a FOL axiomatization of its core [29] that distracts from its
purpose and is little accessible to its potential user base), created from an attempt [30] to connect to
the metaphysics underlying the EMMO foundational ontology [19]. However, with the development
of OCES [17, 31], it is no longer needed or even advisable for mid- and domain-level ontologies to
attach themselves to the EMMO so closely, just to interoperate with other EMMO-related ontologies.
OCES and bridge concepts [31] can just as well be used for this purpose [16, 17]. Another element that
might be reused, contingent upon redesign, are (some of) the VIMMP ontologies [32]; the most relevant
ontologies from VIMMP would be OSMO [33, 34], the ontology version of CWA 17284 MODA [35], and
MMTO [36], the ontology version of the EMMC CSA Translation Case Template [37]. The VIMMP
ontologies, specially OSMO, sufer from the same problem as well: Substantial work went into them,
and now, a single ontology addresses too many issues at once, reducing its usefulness for targeted
development tasks; beside, like PIMS-II, the VIMMP ontologies too became complicated through
attempting to conform with preliminary development versions of the EMMO and its metaontological
overhead (and, in the case of OSMO, additionally with MODA). Both PIMS-II and the VIMMP ontologies
also make heavy use of OWL 2 Full semantics and do not prioritize the tractability of reasoning tasks.
      </p>
      <p>Generally speaking, mid- and domain-level ontology redesign should focus on refining and
reorganizing ontological structures to significantly improve clarity, usability, and alignment with domain-specific
requirements, ensuring the ontology accurately represents the required knowledge and relationships
within a domain. This process facilitates better interoperability, data integration, and reasoning
capabilities. Essential considerations in this redesign include achieving conceptual clarity by defining all
concepts and relationships without ambiguity, removing redundancies, and resolving inconsistencies to
enhance the ontology’s functionality and usability [38]. Organizing concepts into a clear hierarchical
structure is critical; this involves not only identifying and establishing natural or logical parent-child
relationships but also ensuring that subcategories are appropriately nested to reflect the true complexity
of the domain [39]. The design should be modular, allowing for easy updates and extensions, which
supports ongoing improvements and adaptability. The ontologies should also be aligned with a
foundational ontology and widely used, or otherwise important, metadata standards from the domain [38]; in
our case, the latter include the reference ontology of trust [15] (cf. Section 2.4), the German NFDI4Ing
project’s Metadata4Ing [40] (m4i), and further domain ontologies as a function of the addressed use case.
Within BatCAT, e.g., EMMO-related domain ontologies such as the BattINFO ontology [41] and the
battery value chain ontology (BVCO). In some domains, BFO-related ontologies would predominate [38].
Here, DOLCE [18] is used as the foundational ontology with which a strong alignment is made, using
DOLCE Lite [42]. DOLCE has been stable for over twenty years and can therefore be relied on as a
building block that will not change in the foreseeable future. In relation to other work, we can rely on
weak alignment based on the SKOS relation skos:closeMatch and additionally benefit from OCES for
connecting to any ontology development that has been done under the BFO and the EMMO [16, 17].</p>
      <p>The redesigned mid- and domain-level ontologies, called MSO-EM: Ontologies for modelling, simulation,
optimization (MSO) and epistemic metadata (EM), are/will be licensed under CC BY-ND 4.0, and their
development is openly accessible through a public github repository.2 The design principles include:
1. The expressivity is restricted to OWL 2 EL, corresponding to ℰ ℒ++ description logic.
2. Each ontology from MSO-EM has at most three taxonomy levels and three concepts at its highest
level. (This does not mean that there will only be three hierarchy levels within MSO-EM as a
whole, but that the tree depth for the concepts defined in a single module TTL file is limited to
three.) Only include concepts that we expect to be directly required in technical practice. Remove
unnecessary concepts in the middle region of the tree, if it is the leaves of the tree that developers
would rather refer to instead.
3. Define few relations, prefer abstract (high-level) relations where possible, and be specific in terms
of the concepts rather than the relations. There is no inherent logical reason to prefer this, but it
is in line with human communication – we tend to use few, comparably generic verbs most of
the time. On the other hand, the nouns we use in speech or writing easily become very specific.
4. Define relations one-way only; where applicable, use the direction that can be used to define
more meaningful restrictions on concepts. Normally, this means that the greater (or whole) entity
should be the subject and the smaller (or part) entity should be the object, i.e., relations of the
type «has part» are preferred over those of the type «is part». This is because OWL EL does not
allow owl:inverseOf, and the greater-to-smaller direction is more frequently used in restrictions.
5. Use strong alignment (rdfs:subClassOf and rdfs:subPropertyOf) only in reference to DOLCE Lite,
not in reference to other ontologies outside the MSO-EM system itself. All concepts from MSO-EM
are subsumed under a concept from DOLCE Lite. Where it can be done, use skos:exactMatch for
strong alignment with DOLCE Lite, m4i, and PIMS-II, but not with any other ontologies.
6. Use weak alignment (skos:closeMatch) where possible for D-SI, EMMO, GPO [43], schema.org,
and any of the legacy ontologies other than PIMS-II; skos:broader and skos:narrower are not used.</p>
      <sec id="sec-4-1">
        <title>At submission time, one of these ontology modules is ready as a demonstrator:</title>
        <p>
          The MSO-EM agency ontology (agency.ttl in the repository2), which implements Conte’s taxonomy [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]
and relations and concepts connected to it; compared to the Agent branch of PIMS-II,3 the taxonomy
was reduced to three hierarchy levels, eliminating e.g. the concept IntelligentAgent for which, there is
little use in concrete practice, since almost always, more specific subclasses would be used instead.
        </p>
        <p>Due to the restrictions imposed on each single ontology, the number of ontologies in this system
will be comparably large, but each of those is expected to be easy to understand. Simplicity in terms
of interconnections and a comparably flat taxonomy will make it possible to adjust definitions to the
outcome of community and group discussion processes; at least, this will be less problematic than in
case of the large monolithic ontologies from previous work such as OSMO and PIMS-II.
2Persistent URL for the MSO-EM ontologies: https://www.purl.org/mso-em. Open-access repository for development:
https://github.com/HE-BatCAT/mso-em. URL with which the system of ontologies can be loaded directly into protégé:
https://batcat.info/semantics/mso-em/ (in protégé: «File» → «Open from URL» → input the URL to the left).
3http://molmod.info/semantics/pims-ii.ttl</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion</title>
      <p>While this position paper reflects the overall perspective from discussions within the KGA working
group on XAIR principles, much of the uptake and further development will depend on the actual use
made of these developments for semantic interoperability, data documentation, and the integration
of models and data into AI-driven systems. The research projects involved in the present efort, so
far, include AI4Work, BatCAT [44], DigiPass CSA, and MaRDI [45].4 Within BatCAT, based on the
project’s requirements analysis [44], plans include to give ontology design principles such as those
from Section 4 the status of a meta-metamodel (M3-model), at the top of a hierarchy in compliance
with the Object Management Group’s ISO standard Meta Object Facility [46] (MOF). Accordingly,
the ontologies themselves become the metamodel (M2-model), below which knowledge graph shapes,
specified through OO-LD, 5 are the model (M1-model). Using MOF helps establish a coherent system
of semantic and technical interoperability, capable of supporting advanced data operations through
integration with other OMG standards such as BPMN, which is also used in the project.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>The work was done within the Knowledge Graph Alliance’s working group on XAIR principles in
collaboration with AI4Work, BatCAT, DigiPass CSA, and MaRDI. The co-authors A. T. Co. and S. Sc.
acknowledge funding from the EU’s Horizon Europe research and innovation programme under GA
no. 101135990: AI4Work. The co-authors F. Al Ma., S. Ch., M. T. Ho., S. St., I. T. To., and K. Tø.
acknowledge funding from Horizon Europe under GA no. 101137725: BatCAT, and the co-authors F. Al Ma.,
M. T. Ho., and N. A. Ko. under GA no. 101138510: DigiPass CSA. The co-author B. Sc. acknowledges
funding from MaRDI, DFG project no. 460135501, within the German national research data infrastructure
(NFDI). The authors acknowledge discussions with Colin W. Glass and Andreas Neumann.
[9] M. R. Munafò, B. A. Nosek, D. V. M. Bishop, K. S. Button, C. D. Chambers, N. Percie du Sert,
U. Simonsohn, E.-J. Wagenmakers, J. J. Ware, J. Ioannidis, A manifesto for reproducible science,
Nature Human Behaviour 1 (2017) 0021. doi:10.1038/s41562-016-0021.
[10] M. Schappals, A. Mecklenfeld, L. Kröger, V. Botan, A. Köster, S. Stephan, E. J. García, G. Rutkai,
G. Raabe, P. Klein, K. Leonhard, C. W. Glass, et al., Round robin study: Molecular simulation of
thermodynamic properties from models with internal degrees of freedom, Journal of Chemical
Theory and Computation 13 (2017) 4270–4280. doi:10.1021/acs.jctc.7b00489.
[11] R. D. Peng, Reproducible research in computational science, Science 334 (2011) 1226–1227.</p>
      <p>doi:10.1126/science.1213847.
[12] H. E. Plesser, Reproducibility vs. replicability: A brief history of a confused terminology, Frontiers
in Neuroinformatics 11 (2018) 76. doi:10.3389/fninf.2017.00076.
[13] M. T. Horsch, S. Chiacchiera, G. Guevara Carrión, M. Kohns, E. A. Müller, D. Šarić, S. Stephan, I. T.</p>
      <p>Todorov, J. Vrabec, B. Schembera, Epistemic metadata for computational engineering information
systems, in: Proc. FOIS 2023, IOS (ISBN 978-1-64368-468-0), 2023, pp. 302–317. doi:10.3233/
faia231136.
[14] J. Ohlhorst, Trust Responsibly, Routledge (ISBN 978-1-032-46098-7), Abingdon, 2024.
[15] R. Baratella, G. Amaral, T. P. Sales, R. Guizzardi, G. Guizzardi, The many facets of trust, in:</p>
      <p>Proc. FOIS 2023, IOS (ISBN 978-1-64368-468-0), 2023, pp. 17–31. doi:10.3233/faia231115.
[16] S. Chiacchiera, A. T. Correia, D. Stokic, E. Sanfilippo, S. Borgo, C. Masolo, A. Sarkar, Y. Le Franc,
J. Haack, C. Weck, J. F. Morgado, G. Goldbeck, et al., Report on the finalized review of domain
interoperability, Deliverable 3.8, OntoCommons CSA, 2023. doi:10.5281/zenodo.10891825.
[17] M. Magas, D. Kiritsis, Industry Commons: An ecosystem approach to horizontal enablers for
sustainable cross-domain industrial innovation, International Journal of Production Research 60
(2022) 479–492. doi:10.1080/00207543.2021.1989514.
[18] S. Borgo, C. Masolo, Ontological foundations of DOLCE, in: R. Poli, M. Healy, A. Kameas (Eds.),
Theory and Applications of Ontology: Computer Applications, Springer (ISBN 978-90-481-8846-8),
Dordrecht, 2010, pp. 279–295. doi:10.1007/978-90-481-8847-5_13.
[19] F. A. Zaccarino, C. Masolo, E. Ghedini, S. Borgo, From causation (and parthood) to time: The case
of EMMO, in: Proc. FOIS 2023, IOS (ISBN 978-1-64368-468-0), 2023, pp. 92–106. doi:10.3233/
faia231120.
[20] R. Arp, B. Smith, A. D. Spear, Building Ontologies with Basic Formal Ontology, MIT Press (ISBN
978-0-262-52781-1), Cambridge, Massachusetts, 2015.
[21] M. R. Naqvi, L. Elmhadhbi, A. Sarkar, B. Archimede, M. H. Karray, Survey on ontology-based
explainable AI in manufacturing, Journal of Intelligent Manufacturing (2024). doi:10.1007/
s10845-023-02304-z.
[22] T. Grote, K. Genin, E. Sullivan, Reliability in machine learning, Philosophy Compass 19 (2024)
e12974. doi:10.1111/phc3.12974.
[23] S. Yablo, Aboutness, Princeton Univ. Press (ISBN 978-0-691-14495-5), 2014.
[24] J. M. Durán, N. Formanek, Grounds for trust: Essential epistemic opacity and computational
reliabilism, Minds and Machines 28 (2018) 645–666. doi:10.1007/s11023-018-9481-6.
[25] I. Koskinen, We have no satisfactory social epistemology of AI-based science, Social Epistemology
(2024). doi:10.1080/02691728.2023.2286253.
[26] P. B. Heidorn, Shedding light on the dark data in the long tail of science, Library Trends 57 (2008)
280–299. doi:10.1353/lib.0.0036.
[27] B. Schembera, J. M. Durán, Dark data as the new challenge for big data science and the
introduction of the scientific data oficer, Philosophy &amp; Technology 33 (2020) 93–115. doi: 10.1007/
s13347-019-00346-x.
[28] B. Schembera, Like a rainbow in the dark: Metadata annotation for HPC applications in the age of
dark data, Journal of Supercomputing 77 (2021) 8946–8966. doi:10.1007/s11227-020-03602-6.
[29] M. T. Horsch, Mereosemiotics: Parts and signs, in: Proc. JOWO 2021, CEUR-WS (CEUR Workshop</p>
      <p>Proceedings no. 2969), 2021, p. FOUST: 3.
[30] M. T. Horsch, S. Chiacchiera, B. Schembera, M. A. Seaton, I. T. Todorov, Semantic interoperability
based on the European Materials and Modelling Ontology and its ontological paradigm:
Mereosemiotics, in: Proc. WCCM-ECCOMAS 2020, Scipedia, 2021, p. 297. doi:10.23967/wccm-eccomas.
2020.297.
[31] A. de Baas, P. Del Nostro, J. Friis, E. Ghedini, G. Goldbeck, I. M. Paponetti, A. Pozzi, A. Sarkar,
L. Yang, F. A. Zaccarini, D. Toti, Review and alignment of domain-level ontologies for materials
science, IEEE Access 11 (2023) 120372–120401. doi:10.1109/access.2023.3327725.
[32] M. T. Horsch, S. Chiacchiera, M. A. Seaton, I. T. Todorov, K. Šindelka, M. Lísal, B.
Andreon, E. Bayro Kaiser, G. Mogni, G. Goldbeck, R. Kunze, G. Summer, et al., Ontologies for
the Virtual Materials Marketplace, Künstliche Intelligenz 34 (2020) 423–428. doi:10.1007/
s13218-020-00648-9.
[33] M. T. Horsch, C. Niethammer, G. Boccardo, P. Carbone, S. Chiacchiera, M. Chiricotto, J. D. Elliott,
V. Lobaskin, P. Neumann, P. Schifels, M. A. Seaton, I. T. Todorov, et al., Semantic interoperability
and characterization of data provenance in computational molecular engineering, Journal of
Chemical &amp; Engineering Data 65 (2020) 1313–1329. doi:10.1021/acs.jced.9b00739.
[34] M. T. Horsch, D. Toti, S. Chiacchiera, M. A. Seaton, G. Goldbeck, I. T. Todorov, OSMO: Ontology
for simulation, modelling, and optimization, in: Proc. JOWO 2021, CEUR-WS (CEUR Workshop
Proceedings no. 2969), 2021, p. FOIS Showcase: 47.
[35] CEN-CENELEC Management Centre, Materials modelling: Terminology, classification and
metadata, CWA 17284:2018 E, CEN, Brussels, 2018.
[36] M. T. Horsch, S. Chiacchiera, M. A. Seaton, I. T. Todorov, B. Schembera, P. Klein, N. A. Konchakova,
Pragmatic interoperability and translation of industrial engineering problems into modelling and
simulation solutions, in: Proc. DAMDID 2020, Springer (ISBN 978-3-030-81199-0), 2021, pp. 45–59.
doi:10.1007/978-3-030-81200-3_4.
[37] M. Pezzotta, J. Friis, G. J. Schmitz, N. Konchakova, D. Höche, D. Hristova-Bogaerds, P. Asinari,
L. Bergamasco, G. Goldbeck, Report on translation case studies describing the gained experience,
Technical report, EMMC CSA, 2021. doi:10.5281/zenodo.4457849.
[38] R. Rudnicki, B. Smith, T. Malyuta, W. Mandrick, Best practices of ontology development, White
paper, CUBRC, 2016.
[39] M. Amir, M. Baruah, M. Eslamialishah, S. Ehsani, A. Bahramali, S. Naddaf-Sh, Zarandioon, Truveta
Mapper: A zero-shot ontology alignment framework, in: Proc. OM 2023, CEUR-WS (CEUR
Workshop Proceedings no. 3591), 2023, pp. 1–12.
[40] D. Iglezakis, D. Terzijska, S. Arndt, S. Leimer, J. Hickmann, M. Fuhrmans, G. Lanza, Modelling
scientific processes with the m4i ontology, in: Proc. CoRDI 2023, NFDI, 2023. doi: 10.52825/
cordi.v1i.271.
[41] S. Clark, F. L. Bleken, S. Stier, E. Flores, C. W. Andersen, M. Marcinek, A. Szczesna-Chrzan,
M. Gaberšček, M. R. Palacin, M. Uhrin, J. Friis, Toward a unified description of battery data,
Advanced Energy Materials 12 (2022) 2102702. doi:10.1002/aenm.202102702.
[42] H. Paulheim, A. Gangemi, Serving DBpedia with DOLCE: More than just adding a cherry on
top, in: Proc. ISWC 2015, part I, Springer (ISBN 978-3-319-25006-9), Cham, 2015, pp. 180–196.
doi:10.1007/978-3-319-25007-6_11.
[43] S. Stier, X. Xu, L. Gold, M. Möckel, Ontology-based battery production dataspace and its
interweaving with artificial intelligence-empowered data analytics, Energy Technology 12 (2024) 2301305.
doi:10.1002/ente.202301305.
[44] M. T. Horsch, D. Romanov, E. Valseth, S. Belouettar, L. E. Córdova López, J. Glutting, M. A.</p>
      <p>Janssen, P. Klein, A. Linhart, M. A. Seaton, E. D. Sødahl, N. Vizcaino, et al., Battery manufacturing
knowledge infrastructure requirements for multicriteria optimization based decision support in
design of simulation, in: Proc. SeMatS 2024, CEUR-WS, 2024.
[45] M. Reidelbach, B. Schembera, M. Weber, Towards a FAIR documentation of workflows and models
in applied mathematics, in: Proc. ICMS 2024, Springer (ISBN 978-3-031-64528-0), 2024, pp. 254–262.
doi:10.1007/978-3-031-64529-7_27.
[46] ISO/IEC JTC 1/SC 32, Information technology: Meta object facility, ISO 19502:2005, ISO, 2005.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M.</given-names>
            <surname>Pawlicki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pawlicka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Uccello</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Szelest</surname>
          </string-name>
          , S. D'Antonio,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kozik</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Choraś, Evaluating the necessity of the multiple metrics for assessing explainable AI: A critical examination</article-title>
          ,
          <source>Neurocomputing</source>
          <volume>602</volume>
          (
          <year>2024</year>
          )
          <article-title>128282</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.neucom.
          <year>2024</year>
          .
          <volume>128282</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M. D.</given-names>
            <surname>Wilkinson</surname>
          </string-name>
          , M. Dumontier, IJsbrand Jan Aalbersberg, G. Appleton,
          <string-name>
            <given-names>M.</given-names>
            <surname>Axton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Baak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Blomberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-W.</given-names>
            <surname>Boiten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. B. da Silva</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. E.</given-names>
            <surname>Bourne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Bouwman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. J.</given-names>
            <surname>Brookes</surname>
          </string-name>
          , et al.,
          <article-title>The FAIR guiding principles for scientific data management and stewardship</article-title>
          ,
          <source>Scientific Data</source>
          <volume>3</volume>
          (
          <year>2016</year>
          )
          <article-title>160018</article-title>
          . doi:
          <volume>10</volume>
          .1038/sdata.
          <year>2016</year>
          .
          <volume>18</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Z. C.</given-names>
            <surname>Lipton</surname>
          </string-name>
          ,
          <article-title>The mythos of model interpretability: In machine learning, the concept of interpretability is both important and slippery</article-title>
          ,
          <source>Queue</source>
          <volume>16</volume>
          (
          <year>2018</year>
          )
          <fpage>31</fpage>
          -
          <lpage>57</lpage>
          . doi:
          <volume>10</volume>
          .1145/3236386.3241340.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Horsch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Schembera</surname>
          </string-name>
          ,
          <article-title>Documentation of epistemic metadata by a mid-level ontology of cognitive processes</article-title>
          ,
          <source>in: Proc. JOWO</source>
          <year>2022</year>
          ,
          <article-title>CEUR-WS (</article-title>
          <source>CEUR Workshop Proceedings no. 3249)</source>
          ,
          <year>2022</year>
          , p.
          <source>CAOS: 2.</source>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>F.</given-names>
            <surname>Al Machot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. E. Córdova</given-names>
            <surname>López</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. T.</given-names>
            <surname>Correia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Horsch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Scholze</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Stephan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Werth</surname>
          </string-name>
          ,
          <string-name>
            <surname>DCLXVI</surname>
          </string-name>
          <year>2024</year>
          ,
          <article-title>call for papers, AI4Work</article-title>
          and BatCAT,
          <year>2024</year>
          . doi:
          <volume>10</volume>
          .5281/zenodo.13142343.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>J.</given-names>
            <surname>Rowley</surname>
          </string-name>
          ,
          <article-title>The wisdom hierarchy: Representations of the DIKW hierarchy</article-title>
          ,
          <source>Journal of Information Systems</source>
          <volume>33</volume>
          (
          <year>2007</year>
          )
          <fpage>163</fpage>
          -
          <lpage>180</lpage>
          . doi:
          <volume>10</volume>
          .1177/0165551506070706.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>R.</given-names>
            <surname>Conte</surname>
          </string-name>
          ,
          <article-title>Rational, goal-oriented agents</article-title>
          , in: R. A.
          <string-name>
            <surname>Meyers</surname>
          </string-name>
          (Ed.),
          <source>Computational Complexity</source>
          ,
          <source>Springer (ISBN 978-1-4614-1799-6)</source>
          , New York,
          <year>2012</year>
          , pp.
          <fpage>2578</fpage>
          -
          <lpage>2593</lpage>
          . doi:
          <volume>10</volume>
          .1007/ 978-1-
          <fpage>4614</fpage>
          -1800-
          <volume>9</volume>
          _
          <fpage>158</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8] ISO/TC 176/SC 2,
          <string-name>
            <surname>Quality</surname>
            <given-names>management</given-names>
          </string-name>
          <source>systems: Requirements, ISO</source>
          <volume>9001</volume>
          :
          <year>2015</year>
          , ISO,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <surname>4AI4Work (HEur</surname>
            <given-names>GA</given-names>
          </string-name>
          101135990): https://ai4work.eu/; BatCAT (HEur GA 101137725): https://batcat.info/;
          <string-name>
            <surname>DigiPass CSA (HEur</surname>
            <given-names>GA</given-names>
          </string-name>
          101138510): https://ms.hereon.de/digipass/;
          <string-name>
            <surname>MaRDI (NFDI - DFG</surname>
            <given-names>ID</given-names>
          </string-name>
          460135501): https://www.mardi4nfdi.de.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>5https://github.com/OO-LD</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>