<!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>
      <journal-title-group>
        <journal-title>Hersonissos, Greece.
* Corresponding author.
$ jan_martin.keil@dlr.de (J. M. Keil); tobias.koehler@dlr.de (T. Köhler); sirko.schindler@dlr.de (S. Schindler)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Communication in Design-for-Circularity: Requirements to a Knowledge Graph</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jan Martin Keil</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tobias Köhler</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sirko Schindler</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>German Aerospace Center (DLR), Institute of Data Science</institution>
          ,
          <addr-line>Mälzerstraße 3-5, 07745 Jena</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2024</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>In times of potential resource shortages and urgent need of a reduction in CO2 emission, reclaiming resources from end-of-life products becomes more and more relevant. This importance has already resulted in a growing number of legal regulations against the waste of resources and a strong push towards a circular economy. The design of a product has a strong influence on its environmental impact and its recyclability. In the project Methods and Technologies for an intelligent Circularity of Materials (MaTiC-M), we aim to develop a Design-for-Circularity methodology which accounts for product recyclability right from the design phase. However, lack of information for both product developers and recyclers about the entire life cycle of a product impedes recycling-friendly designs and eficient recycling processes. Overcoming this obstacle requires the integration of a wide range of data from diferent sources. Our goal is to develop a knowledge graph to facilitate the exchange of information between product designers and recyclers. In a first step, we analysed the requirements of various stakeholders on such a knowledge graph. In this paper, we present our procedure for the requirements analysis, as well as the resulting catalogue of competency questions.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Circular Economy</kwd>
        <kwd>Competency Questions</kwd>
        <kwd>Knowledge Graph Engineering</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        In the manufacturing industry, we can currently observe two major trends: On the one hand, there is a
strong push towards net-zero emissions as witnessed, e.g., by the European Climate Law, which aims at a
climate-neutral European economy and society by 2050 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. On the other hand, global supply chains are
more and more under pressure due to political tensions, natural disasters but also a growing demand for
various rare resources. Both trends cause a shift from relying solely on primary raw materials towards
an increased use of recycled ones, e.g., from end-of-life products. Besides reducing the dependence
from suppliers, this also lowers CO2 emissions caused by production, processing, and transport of those
materials. The vision is a circular economy in which fewer and fewer resources are disposed of as waste
but instead are reintroduced back into the economic cycle.
      </p>
      <p>The product design and development is of particular importance in this context as it influences the
environmental impact along the entire life cycle of a product: It afects emissions, resource consumption,
and waste generation during manufacturing, the extend of its use (including, e.g., robustness and
durability but also the ability to repair it or replace broken components), and the degree to which its
components can be recycled at its end-of-life. At the moment, product designers often lack proper
information to make informed decisions on many of these sustainability aspects. In the same way,
recyclers currently have little information available about products often causing suboptimal recycling
results with respects to both ecological as well as economic regards as, e.g., rare and valuable materials
cannot be specifically preserved.</p>
      <p>
        In the project Methods and Technologies for an intelligent Circularity of Materials (MaTiC-M) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], we
develop a Design-for-Circularity methodology that already accounts for the recyclability of a product
during its design phase. This allows product designers to make better decisions early on, resulting in
higher recycling rates and thus a lower environmental footprint at the end-of-life or end-of-use of a
product. The methodology is initially developed for a range of demonstrators from the fields of aviation,
energy, and transport. This broad range of domains and the early involvement of various industry
partners will ensure a generic approach and a possible transfer into a wide range of application areas.
      </p>
      <p>A crucial aspect of this methodology is the information exchange between the various involved
stakeholders, including the aforementioned product designers and recyclers but also, e.g., life cycle
analysts, to rate diferent design options based on their environmental impact. In this paper, we report
on the development of the knowledge graph that is at the heart of this information exchange. Here, we
collect and interconnect all relevant information ranging from material characteristics, over life cycle
assessments, to recycling strategies. The goal is to provide a decision support system for both product
designers and recyclers that helps to make more eficient use of available resources, reduce the reliance
on primary raw materials, and thus contribute to meeting the net-zero goals set out by politics.</p>
      <p>This paper is structured as follows: In Section 2, we provide background information on circular
economy and the Linked Open Terms (LOT) methodology. In Section 3, we introduce the method we
applied to determine the requirements for the MaTiC-M knowledge graph. In Section 4, we present the
results of the requirements analysis. In Section 5, we reflect on lessons learned with the requirements
analysis in this projects. In Section 6, we provide a conclusion and give an outlook for the further goals
of the project.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <sec id="sec-2-1">
        <title>2.1. Circular Economy</title>
        <p>
          In this section we provide background information on key concepts for this paper.
A circular economy [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] is a economy model that aims to reduce waste to a minimum. It involves the
maximisation of the use of materials and products by sharing, leasing, reusing, repairing, refurbishing,
and recycling them. The circular economy model is in contrast to the linear economy model, which
relies on cheap, easily accessible materials and energy and that encourages one-time-use of materials
and generation of waste.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Linked Open Terms Methodology</title>
        <p>
          The Linked Open Terms (LOT) methodology [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] is an approach to ontology engineering. It describes a
development process that consist of four main activities: (1) the ontology requirements specification
activity, (2) the ontology implementation activity, (3) the ontology publication activity, and (4) the
ontology maintenance activity. Each activity consists of several sub-activities. For the ontology
requirements specification it defines seven sub-activities: (1.1) the use case specification activity, (1.2)
the data exchange identification activity, (1.3) the purpose and scope identification activity, (1.4) the
functional ontology requirements proposal, (1.5) the functional requirements completion activity, (1.6)
the ontology requirements specification document formalisation, and (1.7) the optional functional
ontology requirements formalisation activity.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Method</title>
      <p>
        An important obstacle to implement a circular economy is the lack of information of all stakeholders
along the product life cycle. In particular, product developers often can not assess the implications of
certain design decisions for the sustainability and recyclability of the product. Vice versa, recyclers
lack information on the individual parts and materials used in a product to select the optimal recycling
strategy. In MaTiC-M we aim to address this obstacle with an RDF knowledge graph that supports
the exchange of the required information. RDF supports us in the integration processes of the tool
landscapes of the involved stakeholders, e.g., via a rather seamless transition in communication protocols
using JSON-LD [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Further, RDF allows for an easy integration with and reuse of large knowledge bases
like ChEBI [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Finally by using RDF as the base for information storage and exchange, we encourage
adherence to the FAIR principles [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] with prospects of, e.g., FAIR Digital Twins [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] as a later use case.
      </p>
      <p>
        For the development of the MaTiC-M knowledge graph, we apply the Linked Open Terms (LOT)
methodology [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], a current and yet widespread methodology for ontology engineering. However, we
needed to slightly adapt the process to account for the conditions of the project framework and we
skipped the optional functional ontology requirements formalisation activity:
      </p>
      <sec id="sec-3-1">
        <title>3.1. Use Case Specification</title>
        <p>Based on an internal preliminary study, the use cases have been outlined in the MaTiC-M project plan:
1. provide information on recycling capabilities to enable an assessment of the recyclability of a
product during its design as part of a Design-for-Circularity methodology,
2. provide information about designs and materials to enable the selection of an optimal
decomposition and recycling at the end of life of a product.</p>
        <p>However, as the Design-for-Circularity methodology itself is developed during the project, we expect
further refinement of the use case specifications over the course of the project.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Data Exchange Identification</title>
        <p>
          Interviews were conducted with domain experts, to identify the file formats currently used for storing
or exchanging data between stakeholders along the product life cycle. These interviews revealed a
range of relevant data formats, including tabular data stored in CSV and Excel files. Furthermore, 3D
models of the product designs must be analysed by several stakeholders. However, these analyses
require diferent computer-aided design ( CAD) data formats. The standard for the exchange of product
model data (STEP) format [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] enables to derive 3D data in all other required formats. Therefore, we
selected the STEP format as the format for the exchange of 3D data. Unfortunately, some software tools
do not export all relevant information into STEP, although it is the broadly accepted baseline format
for CAD data. This makes some workarounds necessary to ensure comprehensive data integration.
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Purpose And Scope Identification</title>
        <p>The purpose and scope of the knowledge graph is already outlined in the project proposal. However,
the specific methods the knowledge graph needs to support are still under active development. As
a consequence, the purpose and scope definition could not be detailed so far. This is a unavoidable
deviation from the LOT methodology. Therefore, the following knowledge graph development is based
on the outlined assumptions, which might change to a certain degree over the course of the project,
though. Nevertheless, some decisions have already been made. For example, the primary language of
the knowledge graph was decided to be English, supplemented by German as secondary language.</p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Functional Ontology Requirements Proposal</title>
        <p>We specified the functional ontology requirements in the form of competency questions ( CQs). In a
ifrst step, all involved domain experts were asked to provide CQs that are relevant for the use cases
in their domain and area of expertise. Overall, 14 domain experts from seven institutes of diferent
domains within the German Aerospace Center (DLR) contributed to the collection of CQs. To prepare
the domain experts for the task, example questions were provided along with an introduction of the
purpose of the CQs. This resulted in several independent list of CQs (one per stakeholder or group of
stakeholders involved in the project; in total seven independent lists). However, the level of granularity
and compliance with the question format difered. In particular, we experienced a clear diference
between domain experts with and without prior experience in developing or using knowledge graphs.
Initially, the CQs were collected and edited in German.</p>
        <p>In a second step, we consolidated the collected CQs into a single list. During this consolidation and
in close collaboration with the domain experts, we also clarified and aligned the CQs. This included the
following activities:</p>
        <sec id="sec-3-4-1">
          <title>Ensure Question Format</title>
          <p>Some initial CQs were only single keywords instead of full questions or the questions were
consecutive questions that are understandable only in the context of the previous ones. We
rephrased these CQs to comply with the intended question format and to be unambiguous and
independent of one another.</p>
        </sec>
        <sec id="sec-3-4-2">
          <title>Split Complex Questions</title>
          <p>Some initial CQs were rather long or complex and involved a multitude of independent aspects.</p>
          <p>We split these CQs into multiple CQs to obtain a more even level of granularity.</p>
        </sec>
        <sec id="sec-3-4-3">
          <title>Highlight Important Terms</title>
          <p>Each CQ contains important terms. We highlighted these important terms to identify relevant
concepts. Further, this helps to keep an overview during the question consolidation.</p>
        </sec>
        <sec id="sec-3-4-4">
          <title>Group Questions</title>
          <p>We noticed that there is couple of central topics among the CQs. Therefore, we grouped the CQs
based on their main topic of concern. This activity is merely for organisational purposes and
does not imply any priority or rating among the CQs. It helps to keep an overview during the
question consolidation and we expect it to help during the ontology implementation, too.</p>
        </sec>
        <sec id="sec-3-4-5">
          <title>Merge Duplicated Questions</title>
          <p>Some equivalent or very similar questions were part of or derived from multiple initial CQ lists.</p>
          <p>We merged these CQs to avoid redundancy.</p>
        </sec>
        <sec id="sec-3-4-6">
          <title>Align Terminology</title>
          <p>
            We identified terminology gaps between diferent domains and contributors and clarified the
meaning of used terms. For example, we decided that we consider (a) the term “material” as the
chemical composition and structure of things like in “materials science” and therefore rejected
the interpretation as things that are used to produce another thing like in a “bill of material” [
            <xref ref-type="bibr" rid="ref10">10</xref>
            ],
(b) the term “part” as a thing that is not assembled of other things and therefore rejected the
interpretation as a thing that is (meant to be) assembled into an assembly, (c) the term “component”
instead of the term “part” as a thing that is (meant to be) assembled into an assembly and thereby
has a special role in this context, (d) the term “product” as a part or assembly that is (meant to be)
sold and thereby has a special role in this context and therefore rejecting the interpretation as a
thing that can be sold to a consumer. These linguistic ambiguities apply to German and English
in a similar way.
          </p>
          <p>During these activities, we maintained the links between initial CQs and their according consolidated
CQs to track the provenance of the latter. Due to splitting and merging during the consolidation,
there is a many-to-many relation between initial and consolidated CQs. The provenance of each CQ
helped to ensure that all initial CQs have been considered entirely in the consolidated CQs and that
the consolidated CQs do not extend the scope of the initial CQs. Further, it eased the validation of
consolidated CQs in the next step. These activities resulted in a CQ catalogue draft.</p>
        </sec>
      </sec>
      <sec id="sec-3-5">
        <title>3.5. Functional Requirements Completion</title>
        <p>To complete the CQ catalogue, we conducted a verification of the catalogue draft. All involved domain
experts were asked to check whether the consolidated CQs cover all their information needs and that</p>
        <p>Topic
material
scrap
collection
disassembly
recycling
202 individual part / assembly / product
301 connection / joining
material source
manufacturing / production
What properties (e.g., tensile strength, thermal
conductivity, heat capacity, density) does a material have?
Which parts and assemblies does an assembly / product
consist of?
Which connections of which connection type / which
joining method exist between two components?
In what amount is a material available from a primary /
secondary material source?
How much electrical energy does a production process /
manufacturing process require per workpiece or amount
of material?
What material does an amount of scrap consist of?
What personnel is required for the collection of the scrap of
a product or assembly?
Which disassembly steps are to be carried out for a product?
How much electrical energy does a recycling step require
per product or component or amount of material?
What is the lifespan of a device?
How many person hours with which qualifications does a
personnel requirement comprise?
none of their intents was misinterpreted. This revealed a few gaps in the consolidated CQs that have
subsequently been addressed. In one case, one of several alternative concepts in a question was missing.
In other cases, the links between the initial CQs and the consolidated CQs were incorrect.</p>
      </sec>
      <sec id="sec-3-6">
        <title>3.6. Ontology Requirements Specification Document Formalisation</title>
        <p>To produce the ontology requirements specification document (ORSD), we decided to create a table
containing the consolidated CQs, stored as a CSV file. As the non-functional requirements can not
be comprehensively specified yet due to the project’s setup, this is suficient to store the known
requirements. Each CQ is stored both in German as well as in English. We used the translation service
DeepL Pro1 to generate a draft translation from German into English, which was manually reviewed
and corrected afterwards. Further, we assigned a numeric identifier to each CQ.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Results</title>
      <p>
        At this stage of development, we identified a total number of 97 CQs that are grouped regarding their
central concepts into 11 topic groups: Material contains questions around characteristics of individual
materials employed. Individual part / assembly / product centres around which components make a final
product whereas connection / joining includes question of how they are assembled. Material source and
manufacturing / production provide necessary information for the life cycle assessment [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] during the
creation of a product. Scrap and collection describe the collection of products at their end-of-life and
end-of-use phase. Finally, disassembly and recycling hold CQs for recycling processing while appliance
/ machine and personnel requirements do so for the resources required for processes along the whole
product life cycle. Table 1 shows one example CQ per topic. The CQs are recorded in tabular form
including translations in both English and German. The topics list illustrates the broad range of domains
that need to be involved in the Design-for-Circularity methodology.
      </p>
      <p>
        Unfortunately, we can not publish all consolidated CQs for now to protect intellectual property rights
of our project partners. Therefore, we omitted or generalised some of the question in the consolidated
CQ table for publishing. The resulting table contains 65 CQs. It is publicly available [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] and licensed
under a permissive CC BY 4.0 license2.
      </p>
    </sec>
    <sec id="sec-5">
      <title>5. Lessons Learned</title>
      <p>As mentioned in Section 3, we had to adapt the LOT methodology according to the framework of
the project. Even though very helpful, it did not fit perfectly in our situation, where the application
environment of the knowledge graph is not yet largely defined. In such case, a less linear but more
agile methodology might be a better option.</p>
      <p>Maintaining the provenance of CQs turned out to be very helpful for later activities during the
requirements specification. But as we used a wiki platform to collect and consolidate the CQs, maintaining
the links between initial CQs and consolidated CQs was a rather cumbersome manual task.</p>
      <p>During the collection of the initial CQs we experienced several misconceptions regarding their purpose
and form. In particular, there was a misconception that the CQs are about information needed within
the project as opposed to information needed to apply the Design-for-Circularity methodology. We also
noticed a clear diference between domain experts with and without prior experience in developing or
using knowledge graphs. As a take-away, we need to put more emphasis on the introduction of the
requirements specification activities to the domain experts in future projects.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>The implementation of a circular economy requires stakeholders along a product life cycle to exchange
information about the product. For instance, product designers need more information about the
processes at the end-of-life/end-of-use of a product, to ease the product recycling and recyclers have to
know the structure and involved materials of a product to decide for an optimal recycling strategy. We
investigated the requirements for a knowledge graph that supports product designers and recyclers to
increase the recyclability and the actual recycling rate of products on the path to a circular economy.
Based on the identified requirements, we will develop the MaTiC-M knowledge graph to support
the Design-for-Circularity methodology currently under development. We intend to make extensive
use of existing ontologies and knowledge graphs to (a) reduce the development efort and (b) ensure
compatibility with other eforts in the domain.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>Many thanks to Mohamad Abdallah (DLR Institute of Vehicle Concepts), Elmar Beeh (DLR Institute of
Vehicle Concepts), Katrin Bugelnig (DLR Institute of Materials Research), Jan Haubrich (DLR Institute of
Materials Research), Sree Sameer Kumtamukkula (DLR Institute of Vehicle Concepts), Tom Lorenz (DLR
Institute of Low-Carbon Industrial Processes), Miriam Löbbecke (DLR Institute of Materials Research),
Nicole Carina Neumann (DLR Institute of Future Fuels), Korbinian Nottensteiner (DLR Institute of
Robotics and Mechatronics), Diana Peters (DLR Institute of Data Science), Robert Reiser (DLR Institute
of System Dynamics and Control), Ismael Valentin Rodriguez Brena (DLR Institute of Robotics and
Mechatronics), Ralf Sturm (DLR Institute of Vehicle Concepts), Bernhard Thiele (DLR Institute of System
Dynamics and Control), and Sven Torstrick-von der Lieth (DLR Institute of Lightweight Systems) for
their valuable contributions to the requirements analysis.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Regulation</surname>
          </string-name>
          (EU)
          <year>2021</year>
          /
          <article-title>1119 of the European Parliament and of the Council of 30 June 2021 establishing the framework for achieving climate neutrality and amending Regulations (EC) No 401/2009 and</article-title>
          (EU)
          <year>2018</year>
          /1999 ('European Climate Law'), in: Oficial Journal, L
          <volume>243</volume>
          ,
          <year>2021</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          . URL: http://data.europa.eu/eli/reg/2021/1119/oj.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Keil</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Peters</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Lorenz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schindler</surname>
          </string-name>
          ,
          <article-title>Digital knowledge exchange for circularity of materials</article-title>
          ,
          <source>in: DLRK</source>
          <year>2023</year>
          ,
          <year>2023</year>
          , p.
          <fpage>1</fpage>
          . URL: https://elib.dlr.de/197942/.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>European</given-names>
            <surname>Parliament</surname>
          </string-name>
          ,
          <article-title>Circular economy: definition, importance</article-title>
          and benefits,
          <year>2023</year>
          . URL: https://www.europarl.europa.eu/topics/en/article/20151201STO05603/ circular
          <article-title>-economy-definition-importance-and-</article-title>
          <string-name>
            <surname>benefits</surname>
          </string-name>
          , Accessed:
          <fpage>2024</fpage>
          -02-28.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Poveda-Villalón</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Fernández-Izquierdo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Fernández-López</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.</surname>
          </string-name>
          <article-title>García-Castro, LOT: An industrial oriented ontology engineering framework</article-title>
          ,
          <source>Engineering Applications of Artificial Intelligence</source>
          <volume>111</volume>
          (
          <year>2022</year>
          )
          <article-title>104755</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.engappai.
          <year>2022</year>
          .
          <volume>104755</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>G.</given-names>
            <surname>Kellogg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.-A.</given-names>
            <surname>Champin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Longley</surname>
          </string-name>
          ,
          <article-title>JSON-LD 1.1 - A JSON-based Serialization for Linked Data</article-title>
          ,
          <source>W3C Recommendation</source>
          ,
          <year>2020</year>
          . URL: https://www.w3.org/TR/2020/REC-json-ld11-
          <volume>20200716</volume>
          /.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>K.</given-names>
            <surname>Degtyarenko</surname>
          </string-name>
          , P. de Matos,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ennis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hastings</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zbinden</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>McNaught</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Alcantara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Darsow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Guedj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ashburner</surname>
          </string-name>
          ,
          <article-title>Chebi: a database and ontology for chemical entities of biological interest</article-title>
          ,
          <source>Nucleic Acids Research</source>
          <volume>36</volume>
          (
          <year>2007</year>
          )
          <fpage>D344</fpage>
          -
          <lpage>D350</lpage>
          . doi:
          <volume>10</volume>
          .1093/nar/gkm791.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M. D.</given-names>
            <surname>Wilkinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumontier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I. J.</given-names>
            <surname>Aalbersberg</surname>
          </string-name>
          , 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>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Clark</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Crosas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Dillo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Dumon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Edmunds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. T.</given-names>
            <surname>Evelo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Finkers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gonzalez-Beltran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. J.</given-names>
            <surname>Gray</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Groth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Goble</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. S.</given-names>
            <surname>Grethe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Heringa</surname>
          </string-name>
          , P. A. '
          <string-name>
            <surname>t Hoen</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Hooft</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Kok</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Kok</surname>
            ,
            <given-names>S. J.</given-names>
          </string-name>
          <string-name>
            <surname>Lusher</surname>
            ,
            <given-names>M. E.</given-names>
          </string-name>
          <string-name>
            <surname>Martone</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Mons</surname>
            ,
            <given-names>A. L.</given-names>
          </string-name>
          <string-name>
            <surname>Packer</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Persson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Rocca-Serra</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Roos</surname>
            , R. van Schaik,
            <given-names>S.-A.</given-names>
          </string-name>
          <string-name>
            <surname>Sansone</surname>
            , E. Schultes,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Sengstag</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Slater</surname>
            , G. Strawn,
            <given-names>M. A.</given-names>
          </string-name>
          <string-name>
            <surname>Swertz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Thompson</surname>
            ,
            <given-names>J. van der</given-names>
          </string-name>
          <string-name>
            <surname>Lei</surname>
            , E. van Mulligen,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Velterop</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Waagmeester</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Wittenburg</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Wolstencroft</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Mons</surname>
          </string-name>
          ,
          <article-title>The fair guiding principles for scientific data management and stewardship</article-title>
          ,
          <source>Scientific Data</source>
          <volume>3</volume>
          (
          <year>2016</year>
          ). doi:
          <volume>10</volume>
          .1038/sdata.
          <year>2016</year>
          .
          <volume>18</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>D.</given-names>
            <surname>Peters</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schindler</surname>
          </string-name>
          ,
          <article-title>Fair for digital twins</article-title>
          ,
          <source>CEAS Space Journal</source>
          <volume>16</volume>
          (
          <year>2023</year>
          )
          <fpage>367</fpage>
          -
          <lpage>374</lpage>
          . doi:
          <volume>10</volume>
          .1007/ s12567-023-00506-y.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <source>[9] ISO 10303-1</source>
          :
          <fpage>2024</fpage>
          ,
          <article-title>Industrial automation systems and integration - Product dara representation and exchange - Part 1: Overview and fundamental principles</article-title>
          , Standard, International Organization for Standardization,
          <year>2024</year>
          . URL: https://www.iso.org/standard/83105.html.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>H.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Abd Nikooie Pour</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lindecrantz</surname>
          </string-name>
          , E. Blomqvist,
          <string-name>
            <given-names>P.</given-names>
            <surname>Lambrix</surname>
          </string-name>
          ,
          <article-title>A survey of general ontologies for the cross-industry domain of circular economy</article-title>
          ,
          <source>in: Companion Proceedings of the ACM Web Conference</source>
          <year>2023</year>
          , WWW '23 Companion, Association for Computing Machinery, New York, NY, USA,
          <year>2023</year>
          , p.
          <fpage>731</fpage>
          -
          <lpage>741</lpage>
          . doi:
          <volume>10</volume>
          .1145/3543873.3587613.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>M. Z. Hauschild</surname>
            ,
            <given-names>R. K.</given-names>
          </string-name>
          <string-name>
            <surname>Rosenbaum</surname>
            ,
            <given-names>S. I.</given-names>
          </string-name>
          Olsen (Eds.),
          <source>Life Cycle Assessment: Theory and Practice</source>
          , Springer International Publishing,
          <year>2018</year>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -56475-3.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>J. M. Keil</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Abdallah</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Beeh</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Bugelnig</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Haubrich</surname>
            ,
            <given-names>S. S.</given-names>
          </string-name>
          <string-name>
            <surname>Kumtamukkula</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Lorenz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Löbbecke</surname>
            ,
            <given-names>N. C.</given-names>
          </string-name>
          <string-name>
            <surname>Neumann</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Nottensteiner</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Peters</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Reiser</surname>
            ,
            <given-names>I. V.</given-names>
          </string-name>
          <string-name>
            <surname>Rodriguez</surname>
            <given-names>Brena</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sturm</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Thiele</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          <article-title>Torstrick-von der</article-title>
          <string-name>
            <surname>Lieth</surname>
          </string-name>
          ,
          <string-name>
            <surname>MaTiC-M Knowledge Graph Competency Questions</surname>
          </string-name>
          ,
          <year>2024</year>
          . doi:
          <volume>10</volume>
          .5281/zenodo.10730784.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>