<!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>Mechanical Testing Ontology for Digital-Twins: a roadmap based on EMMO</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Joana Francisco Morgado</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Emanuele Ghedini</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gerhard Goldbeck</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adham Hashibon</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Georg J. Schmitz</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jesper Friis</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anne F. de Baas</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ACCESS, RWTH Aachen University</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department of Industrial Engineering, University of Bologna</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Fraunhofer Institute for Mechanics of Materials IWM</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Goldbeck Consulting Ltd, St. Johns Innovation Centre</institution>
          ,
          <addr-line>Cambridge CB4 0WS</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Materials and Nanotechnology</institution>
          ,
          <addr-line>SINTEF Industry</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The enormous amount of materials data currently generated by high throughput experiments and computations poses a signi cant challenge in terms of data integration and sharing. A common ontology lays the foundation for solving this issue, enabling semantic interoperability of models, experiments, software and data which is vital for a more rational and e cient development of novel materials. This paper is based on the current e orts by the European Materials Modelling Council (EMMC) on establishing common standards for materials through the European Materials &amp; Modelling Ontology (EMMO) and demonstrates the application of EMMO to the mechanical testing eld. The focus of this paper is to outline the approach to develop EMMO compliant domain ontologies.</p>
      </abstract>
      <kwd-group>
        <kwd>Ontology</kwd>
        <kwd>Materials Science sation</kwd>
        <kwd>Interoperability</kwd>
        <kwd>EMMO</kwd>
        <kwd>Knowledge Base</kwd>
        <kwd>Digitali-</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Materials Science is a well-established discipline essential to provide new
materials that can cope with the current environmental challenges and that can enhance
sustainability. The industrial materials development cycle is highly dependent
on large volumes of data continuously generated from experiments,
characterisation and simulations. Unfortunately, a considerable part of this data ends up
unutilised and, in some cases, even discarded leading to loss of opportunities for
added value creation. One of the reasons behind this is known as the \silo
problem" in data management which basically means a lack of data interconnection
and interoperability. This lack hinders full data access and therefore the ability
to build new knowledge. The silos are mostly driven by large amount of data
being kept in disparate and isolated data sources, heterogeneity of data formats
and types and poor curation practices( e.g. data from di erent microstructure
modelling generated by commercial software and inhouse codes with no common
standards). As reported in a PricewaterhouseCoopers (PwC) study [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], the
nonexistence of ndable, accessible, interoperable and reusable (FAIR) data invokes
costs to the European economy of at least e10.2 billion per year and has
significant impacts on manufacturing [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        Digitalisation of materials is playing a vital role in opening data silos and
making them exploitable. However, to maximise bene t and to succeed in the
digital transformation, all components required to establish a material digital
twin must be available [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Already existing and mature materials modelling
approaches [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] (digital model and data representation) along with the materials
data from characterisation and experiments (data from the tangible object: the
material) are not su cient. The information needs also to be formalised and
combined [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. Hence, interoperability of models, software and data is needed to
facilitate an integrated approach to materials design and product improvement
[
        <xref ref-type="bibr" rid="ref22 ref9">9, 22</xref>
        ].
      </p>
      <p>
        Interoperability can be achieved by a common standardised representation of
knowledge in the form of an ontology. An ontology consists of a formal, shared,
explicit knowledge representation with a common vocabulary which can be used
by di erent people { and machines { to share information within a certain
domain and which has interlinked concepts (classes) and individuals (instances)
based on a xed logic formalism (axioms, relationships and subclassi cation).
An ontology is conceptually important to establish a standard or \common
language" but also a practical necessity in data knowledge and data management.
It provides rich machine processable semantic descriptions that enable complex
search terms. An ontology increases the performance of searches [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] in
particular as semantic reasoning allows to derive new information using inference
and Arti cial Intelligence (AI). By leveraging available information, new
synergies and knowledge can be produced that can support building better materials,
more robust processes and eventually smarter industries and science based on
well-informed and well-reasoned decisions.
      </p>
      <p>
        Attempts to develop ontologies have been made for the materials science
eld [
        <xref ref-type="bibr" rid="ref28 ref5 ref6 ref7">7, 28, 5, 6</xref>
        ]. However, these e orts mostly focus on a speci c application
and do not always go beyond a taxonomy. Besides an agreed terminology, an
ontology requires conceptualisation of logical relations and a set of functional
and actionable axioms. To address the interoperability issue, the EMMC has
developed the EMMO that provides a common semantic framework for describing
materials, models and data with the possibility of extension and adaptation to
other domains of interest in the applied sciences. This article is a step towards
demonstrating an application of the EMMO to the eld of mechanical testing.
It is by no means intended to be either complete or to show a complete domain
ontology, but rather to show ongoing e orts towards a coherent bottom up and
top down ontology development.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Methodology</title>
      <p>Ongoing e orts to establish a practical ontology for the materials eld and in
particular for mechanical testing based on the European Materials &amp; Modelling
Ontology (EMMO) are presented within two main sections: EMMO foundations
and EMMO domain application development.
2.1</p>
      <sec id="sec-2-1">
        <title>EMMO foundations</title>
        <p>
          EMMO is a top and middle level [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] ontology developed by the EMMC which
aims at paving the road for semantic interoperability providing a generic
common ground for describing materials, models and data that can be extended to
and adapted by all domains of science and engineering. To satisfy the
representational needs of the complex and multidisciplinary domain of materials science,
EMMO is (i) solidly based in physical sciences, (ii) consistent with
fundamental theories such as classical physics and quantum mechanics and (iii) based on
existing standards for materials modelling (Review of Materials Modelling [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ],
CEN Workshop Agreement [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] including the MODA template [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], and other
international standards such as the SI Brochure [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] and JCGM200:2008. [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]).
        </p>
        <p>
          Moreover, to the best of our knowledge, EMMO is the only materials
science ontology able to explicitly capture all granularity levels of description of
process and materials. These granularity levels can be described in a
reductionistic perspective, and this is done via the introduction of the \direct parthood"
relation in EMMO. With this relation physicals (the class that contains all the
individuals that stand for real world objects that interact physically with the
ontologist) [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ] can be represented by a strict hierarchy of direct parts down
to an elementary level. Direct parthood is a concept in Mereotopology, a
combination between mereology and topology used to represent the parthood and
spatial-temporal relationships, respectively. EMMO makes extensive use of
concepts and relations of mereotopology. Additionally, EMMO has a strong basis in
analytical philosophy and relies on causality (physics) and on semiotics.
Semiotics reduces the complexity of a physical thing to a sign(model) [
          <xref ref-type="bibr" rid="ref22 ref9">9, 22</xref>
          ]. The
semiotic relationship \standsFor" is the general basis for linking models to
reality and this is expressed in the statement \Model standsFor RealThing". In
its formalisation, EMMO is based on description logic, and its axiomatisation is
expressed using the Web Ontology Language (OWL).
        </p>
        <p>
          EMMO relies on four main layers: (1) a top level which contains the most
fundamental concepts; (2) a middle level that includes representations of generic
cross-domain concepts such as materials, units and processes; (3) a domain level
for a particular branch of science which is more specialised and speci c to
concepts and entities relevant within that particular branch of science and
engineering; an example is mechanical testing and (4) the application level which
should deal only with concepts that are not reused in other applications; an
example is concepts speci c to a user case such as the name of the measurement
device. These layers put into the ontology have to strike a balance between
being a highly expressive, (thus heavy) ontology or being a lighter, incomplete but
highly e cient ontology. This is the reusability-usability trade-o problem [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
        <p>
          Especially for measurement processes, having the right unit ontology that
addresses the main focus of the community [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ], EMMO includes a metrology
module at its middle level, used to represent the units and their interlinking
with physical quantities. The EMMO with its top and middle level ontology,
can be interpreted as the glue combining di erent domains by providing the
root concepts and sockets to plug-in new ontology branches or existing domain
and application ontologies.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>EMMO domain application development</title>
        <p>
          The process of ontology development is a thoroughly iterative process with
several feedback loops. In fact, it is open-ended since our perception of knowledge
changes continuously [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. Therefore, it is important to adopt a systematic
ontology development approach to accompany the knowledge dynamics, capture
e ectively the complexity of the domains and to follow the ontology
stakeholders [
          <xref ref-type="bibr" rid="ref13 ref21 ref23 ref4">4, 13, 21, 23</xref>
          ]. EMMO-compliant domain ontologies are developed using the
EMMO top and middle level, which gives the advantage of having already a
semantic framework in place that provides common standard EMMO concepts
as well as established formalized axioms that can be used as root and adapted
to the particular purpose.
        </p>
        <p>
          The presented ontology development methodology follows the common
practices in ontology development which consists of the following ve phases
described by Sure et al. [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]: (1) feasibility study; (2) kicko ; (3) re nement; (4)
evaluation and (5) application and evolution.
        </p>
        <p>
          The development of EMMO domain ontologies starts with the feasibility
study, phase (1), which relies on the identi cation of the domain of interest. The
kicko phase (2) is the most extensive phase and will be the focus of the present
paper together with the evaluation phase (4). The former aims at producing
the baseline taxonomy which involves the identi cation of the key terms and
concepts to represent the domain of interest in a semi-formal way mostly by the
aid of simpler and comprehensive diagrams (e.g.: UML or even pen and paper
diagrams). In this phase, a classi cation of the domain based on subclassi cation
relationships (class and subclass) is realized. The conceptualization guided by
the EMMO framework should also take place at this stage. It is very important
to understand how the main concepts such as process or material are described in
EMMO to ensure full compliance of the taxonomy with EMMO notions. EMMO
and the domain ontology are then combined by ensuring there is an equivalent
EMMO class or suitable EMMO parent class. This consistency in concept
enables then an integration between the EMMO and the new domain which starts
with the placement of the new concepts as subclass of EMMO classes through
a bottom up approach. In the re nement phase (3), the taxonomy hierarchy is
formalized using an ontology representation language. In the present paper the
ontology is coded using OWL via the open-source ontology editor Protege [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]
and the FaCT++ reasoner [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ]. The taxonomy is further enhanced with new
concepts (classes) and relations (other than isA) compliant with the EMMO logical
constructs are added between the concepts. To comply with the modular design
of EMMO a new module (or OWL le) needs to be created per domain which
imports not only the EMMO-top and middle level classes and especially EMMO
relations but also any other relevant EMMO compliant module and domain.
Usually the evaluation phase is parallel to the re nement due to the need for
constant veri cation and validation with respect to the semantics incorporated,
accuracy and completeness [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. The evaluation (phase 4) of the ontology requires
collaboration with both ontology and domain experts which is supported by
using the full capabilities of the EMMO open-access GitHub repository [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ]. The
fth and last phase, comprising the application and evolution is not addressed
within this paper. However, it is important to note that any ontology requires
maintenance to be able to respond to the continuous changes in the domain. The
maintenance is mostly accomplished by the realization of phases (2)-(4) by the
person in charge of gathering and implementing the feedback from the ontology
users and applications. A more detailed schematic of the engineering ontology
methodology used in the development of EMMO compliant ontologies is
represented in Fig. 1. The development steps will be explored further in the following
section using the current e orts on the mechanical testing representation as use
case.
The main focus of this paper is on how to do the organisation of domain
ontologies. We will present the development approach and the discussion of issues
related to the identi cation of commonalities and determination of boundaries
between the domains. Ongoing e orts on the mechanical testing EMMO-compliant
domain ontology are presented as an example.
        </p>
        <p>Mechanical testing covers a wide range of tests that are carried out to
determine the mechanical properties of materials. The purpose is to ensure that their
material response to a given action makes the material suitable for the intended
application. The methodology for formalising this domain in an EMMO
compliant ontology is carried out following the six main steps identi ed in the green
(right) part of Fig. 1
1. Feasibility study: The domain of interest of this paper is mechanical testing.
2. To satisfy the aim of the ontology, the semantic model should support the
representation of a process that can be used to represent the mechanical
tests and the material de ned by its properties before,during and after the
tests. This is shown in Fig. 2.
3. Identi cation of classes and relationships: Based on the main concepts of
process, material and properties the initial ontology structure as represented
in Fig. 2 can be built and is further enhanced by the addition of new classes
and EMMO-compliant logic constructs.</p>
        <p>Each object and relation is discussed and it is determined to which EMMO
perspective it belongs (holistic, physics or reductionistic. e.g. hasParticipant
and hasRole are emmo-relationships speci c to physicals represented in an
\holistic perspective" that focusses on the role of the participants Fig. 2.
The formalisation of the classes and relationships in OWL is realised in
parallel together with the constant veri cation of the ontology consistency.
This is the key step in the ontology development procedure since it maps
the real-world entities/objects with their ontological representations.
Note that to achieve completeness, the developed ontology should just
contain enough concepts, classes and relationships to respond to the desired
competency questions.
4. Categorization of domains and applications: The level of genericness of each
concept needs to be discussed and it needs to be decided whether the concept
belongs to a domain or an application level. The class MechanicalTestX that
represents a speci c type of mechanical test is application-speci c knowledge
and it is a subclass of the domain notion MechanicalTest (Fig. 2). Please note
that this is true because the MechanicalTestX class refers here to a variant
of a mechanical test (e.g.: tensile test or indentation test part of the domain
level) that is speci c to a certain Lab X. More general concepts such as the
classes properties, process and material are part of the EMMO middle level.
5. Creation of new modules for each domain/application: EMMO compliant
ontologies are sliced in several modules which are used to separate
domain and application-speci c knowledge. This ensures the design of a
modular ontology which facilitates its progress and gradual enrichment. Fig. 3
shows an example of three modules that need to be developed to represent
the mechanical test: mechanical-test-x, mechanical-test-y and
mechanicaltesting. The modules mechanical-test-x, mechanical-test-y are part of the
application layer and contain concepts that are speci c to each of these
tests (not shared among them) e.g. the name of the operator or name of
the measurement device whereas the module mechanical testing, which is
part of the EMMO domain layer contains more generic concepts that are
used in both mechanical-test-x and mechanical-test-y modules. Concepts
represented in Fig. 3 other than MechanicalTestX, MechanicalTestY and
MechanicalTest are part of other modules at the middle and top levels
of EMMO. It is worth mentioning that the practice is adopted to make
each of this modules correspond to an OWL le with a speci c namespace
e.g.\http://emmo.info/emmo/application/mechanical-test-x".</p>
        <p>To get the domain/application ontologies accepted as an ontology based on
EMMO using the o cial EMMO repository, the end-user needs to submit a
proposal to the EMMO Governance Committee. Once approved, a Domain
Ontology Task Group will be established by the EMMC for the maintenance
and development of the designated ontology.</p>
        <p>
          The integration of these modules and the placement in the di erent emmo
levels (top, middle, domain and application) is represented in Fig. 4 where
the yellow rectangle represents the top and middle layers (core framework)
that are the building block for all EMMO compliant ontologies. This work
was based on the currently available EMMO v1.0.0-alpha2 version on GitHub.com.
6. Collaboration: The development of a harmonious, coherent, common
standard in an application eld is achieved by using the emmo top and middle
level ontology and by engaging the whole mechanical testing stakeholder
community from material science, industry and research in its development.
Hence, to ensure the participation of all interested communities, this
application domain ontology is open-source and relies on its open-access repository
in GitHub for development [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ].
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>This paper supports the current Industry 4.0 e orts to move towards integrated
knowledge. The paper presents EMMO as a basis to document material science
by establishing a ontology engineering methodology and demonstrating this via
an application of EMMO in the eld of mechanical testing . The presented
building blocks are vital to bridge the gap between the modern experimental,
simulation and characterisation elds. The presented integration is shown to
result into actionable knowledge that can support intelligent and well-informed
decision-making along development of novel materials solutions.
5</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgements</title>
      <p>This paper is supported by European Union's Horizon 2020 research and
innovation programme: MARKETPLACE project, Grant Agreement No. 814492;
FORCE project, Grant Agreement No. 721027 and OYSTER project, Grant
Agreement No. 760287.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. CEN workshop agreement - CWA 17284
          <article-title>- materials modelling - terminology, classi cation and metadata</article-title>
          . https://ftp.cencenelec.eu/CEN/TCandWorkshops/Workshops/WS/%20MODA/CWA 17284.pdf,
          <volume>04</volume>
          -
          <fpage>03</fpage>
          -2020
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. MODA template. https://moda-app.eu/, 04-
          <fpage>03</fpage>
          -2020
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. 200:
          <year>2008</year>
          , J.:
          <article-title>International vocabulary of metrology | basic and general concepts and associated terms (</article-title>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Ameri</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Urbanovsky</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McArthur</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>A systematic approach to developing ontologies for manufacturing service modeling</article-title>
          .
          <source>In: Proceedings of the workshop on ontology and semantic web for manufacturing</source>
          . vol.
          <volume>14</volume>
          .
          <string-name>
            <surname>Citeseer</surname>
          </string-name>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Ashino</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Materials ontology: An infrastructure for exchanging materials information and knowledge</article-title>
          .
          <source>Data Science Journal</source>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bhat</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shah</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Das</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kulkarni</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghaisas</surname>
            ,
            <given-names>S.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reddy</surname>
            ,
            <given-names>S.S.</given-names>
          </string-name>
          :
          <article-title>Premap- knowledge driven design of materials and engineering process</article-title>
          . In: ICoRD'
          <volume>13</volume>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Cheung</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Drennan</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hunter</surname>
          </string-name>
          , J.:
          <article-title>Towards an ontology for data-driven discovery of new materials</article-title>
          .
          <source>In: AAAI Spring Symposium: Semantic Scientic Knowledge Integration</source>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>De Baas</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>What makes a material function. Let Me Compute the Ways</article-title>
          . . .
          <article-title>Modelling in H2020 LEIT-NMBP Programme Materials</article-title>
          and
          <string-name>
            <given-names>Nanotechnology</given-names>
            <surname>Projects</surname>
          </string-name>
          .
          <article-title>Luxembourg: Publications O ce of the European Union (</article-title>
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Goldbeck</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghedini</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hashibon</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmitz</surname>
            ,
            <given-names>G.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Friis</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A reference language and ontology for materials modelling and interoperability</article-title>
          .
          <source>In: Proceedings NAFEMS World Congress</source>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Goldbeck</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Court</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>The economic impact of materials modelling</article-title>
          (
          <year>Jan 2016</year>
          ). https://doi.org/10.5281/zenodo.44780, https://doi.org/10.5281/zenodo.44780
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Goldbeck</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Simperler</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Strategies for industry to engage in materials modelling</article-title>
          (
          <year>Dec 2019</year>
          ). https://doi.org/10.5281/zenodo.3564455, https://doi.org/10.5281/zenodo.3564455
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Himanen</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Geurts</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Foster</surname>
            ,
            <given-names>A.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rinke</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Data-driven materials science: Status, challenges, and perspectives</article-title>
          .
          <source>Advanced Science</source>
          <volume>6</volume>
          (
          <issue>21</issue>
          ),
          <volume>1900808</volume>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. Jarvenpaa,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Siltala</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            ,
            <surname>Hylli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            ,
            <surname>Lanz</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.:</surname>
          </string-name>
          <article-title>The development of an ontology for describing the capabilities of manufacturing resources</article-title>
          .
          <source>Journal of Intelligent Manufacturing</source>
          <volume>30</volume>
          (
          <issue>2</issue>
          ),
          <volume>959</volume>
          {
          <fpage>978</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Kritzinger</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Traar</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Henjes</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sihn</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Digital twin in manufacturing: A categorical literature review and classi cation</article-title>
          .
          <source>IFAC-PapersOnLine</source>
          <volume>51</volume>
          (
          <issue>11</issue>
          ),
          <volume>1016</volume>
          {
          <fpage>1022</fpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Lahmann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Probst</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parlitz</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Bene ts management - transformation assurance</article-title>
          .
          <source>Tech. rep. (</source>
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. des Poids et Mesures,
          <string-name>
            <surname>B.I.:</surname>
          </string-name>
          <article-title>The international system of units (si) (</article-title>
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Morbach</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marquardt</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Ontocape|a large-scale ontology for chemical process engineering</article-title>
          .
          <source>Engineering applications of arti cial intelligence</source>
          <volume>20</volume>
          (
          <issue>2</issue>
          ),
          <volume>147</volume>
          {
          <fpage>161</fpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Musen</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>The protege project: a look back and a look forward</article-title>
          .
          <source>AI</source>
          matters
          <volume>1</volume>
          (
          <issue>4</issue>
          ),
          <volume>4</volume>
          {
          <fpage>12</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Ocker</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paredis</surname>
            ,
            <given-names>C.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vogel-Heuser</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Applying knowledge bases to make factories smarter</article-title>
          .
          <source>at-Automatisierungstechnik</source>
          <volume>67</volume>
          (
          <issue>6</issue>
          ),
          <volume>504</volume>
          {
          <fpage>517</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Rudnicki</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malyuta</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mandrick</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Best Practices of Ontology Development (</article-title>
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Sack</surname>
          </string-name>
          , H.:
          <article-title>Knowledge engineering with semantic web technologies</article-title>
          . https://open.hpi.de/courses/semanticweb2015,
          <fpage>04</fpage>
          -
          <lpage>03</lpage>
          -2020
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Schmitz</surname>
            ,
            <given-names>G.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goldbeck</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghedini</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hashibon</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Friis</surname>
          </string-name>
          , J.:
          <article-title>Towards an icme methodology in europe { nomenclature, taxonomies, ontologies, and marketplaces</article-title>
          .
          <source>In: Proceedings NAFEMS World Congress</source>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Staab</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Studer</surname>
          </string-name>
          , R.: Handbook on Ontologies. Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Steinberg</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schindler</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Keil</surname>
            ,
            <given-names>J.M.:</given-names>
          </string-name>
          <article-title>Owl: Experiences and directions{reasoner evaluation</article-title>
          .
          <source>OWL: Experiences and Directions{Reasoner Evaluation</source>
          . (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Sure</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Staab</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Studer</surname>
          </string-name>
          , R.:
          <article-title>Ontology engineering methodology</article-title>
          . In: Handbook on ontologies, pp.
          <volume>135</volume>
          {
          <fpage>152</fpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26. EMMO:
          <article-title>European Materials and Modelling Ontology (EMMO) repository template</article-title>
          . https://github.com/emmo-repo
          <source>/EMMO</source>
          ,
          <fpage>04</fpage>
          -
          <lpage>03</lpage>
          -2020
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <article-title>FaCT: The FaCT system</article-title>
          . http://www.cs.man.ac.uk/ horrocks/FaCT/, 04-
          <fpage>03</fpage>
          - 2020
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          :
          <article-title>Semantic query on materials data based on mapping matml to an owl ontology</article-title>
          .
          <source>Data Science Journal</source>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>