An Ontology for the Materials Design Domain

06/13/2020 ∙ by Huanyu Li, et al. ∙ Linköping University 0

In the materials design domain, much of the data from materials calculations are stored in different heterogeneous databases. Materials databases usually have different data models. Therefore, the users have to face the challenges to find the data from adequate sources and integrate data from multiple sources. Ontologies and ontology-based techniques can address such problems as the formal representation of domain knowledge can make data more available and interoperable among different systems. In this paper, we introduce the Materials Design Ontology (MDO), which defines concepts and relations to cover knowledge in the field of materials design. MDO is designed using domain knowledge in materials science (especially in solid-state physics), and is guided by the data from several databases in the materials design field. We show the application of the MDO to materials data retrieved from well-known materials databases.

READ FULL TEXT VIEW PDF
POST COMMENT

Comments

There are no comments yet.

Authors

page 1

page 2

page 3

page 4

This week in AI

Get the week's most popular data science and artificial intelligence research sent straight to your inbox every Saturday.

1 Introduction

More and more researchers in the field of materials science have realized that data-driven techniques have the potential to accelerate the discovery and design of new materials. Therefore, a large number of research groups and communities have developed data-driven workflows, including data repositories (for an overview see [lambrix2018big]) and task-specific analytical tools. Materials design is a technological process with many applications. The goal is often to achieve a set of desired materials properties for an application under certain limitations in e.g., avoiding or eliminating toxic or critical raw materials. The development of condensed matter theory and materials modeling, has made it possible to achieve quantum mechanics-based simulations that can generate reliable materials data by using computer programs [lejaeghere2016reproducibility]. For instance, in [armiento2019database] a flow of databases-driven high-throughput materials design in which the database is used to find materials with desirable properties, is shown. A global effort, the Materials Genome Initiative111https://www.mgi.gov/, has been proposed to govern databases that contain both experimentally-known and computationally-predicted material properties. The basic idea of this effort is that searching materials databases with desired combinations of properties could help to address some of the challenges of materials design. As these databases are heterogeneous in nature, there are a number of challenges to using them in the materials design workflow. For instance, retrieving data from more than one database means that users have to understand and use different application programming interfaces (APIs) or even different data models to reach an agreement. Nowadays, materials design interoperability is achieved mainly via file-based exchange involving specific formats and, at best, some partial metadata, which is not always adequately documented as it is not guided by an ontology. The second author is closely involved with another ongoing effort, the Open Databases Integration for Materials Design (OPTIMADE222https://www.optimade.org/) project which aims at making materials databases interoperational by developing a common API. Also this effort would benefit from semantically enabling the system using an ontology, both for search as well as for integrating information from the underlying databases.

These issues relate to the FAIR principles (Findable, Accessible, Interoperable, and Reusable), with the purpose of enabling machines to automatically find and use the data, and individuals to easily reuse the data [wilkinson2016fair]. Also in the materials science domain, recently, an awareness regarding the importance of such principles for data storage and management is developing and research in this area is starting [draxl2018nomad].

To address these challenges and make data FAIR, ontologies and ontology-based techniques have been proposed to play a significant role. For the materials design field there is, therefore, a need for an ontology to represent solid-state physics concepts such as materials’ properties, microscopic structure as well as calculations, which are the basis for materials design. Thus, in this paper, we present the Materials Design Ontology (MDO). The development of MDO was guided by the schemas of OPTIMADE as they are based on a consensus reached by several of the materials database providers in the field. Further, we show the use of MDO for data obtained via the OPTIMADE API and via database-specific APIs in the materials design field.

The paper is organized as follows. We introduce some well-known databases and existing ontologies in the materials science domain in Section 2. In Section 3, we present the development of MDO and introduce the concepts, relations and the axiomatization of the ontology. In Section 4, we introduce the envisioned usage of MDO as well as a current implementation. In Section 5, we discuss such things as the impact, availability and extendability of MDO as well as future work. Finally, the paper concludes in Section 6 with a small summary.

Availability: MDO is developed and maintained on a GitHub repository333https://github.com/huanyu-li/Materials-Design-Ontology, and is available from a permanent w3id URL444https://w3id.org/mdo.

2 Related Work

In this section we discuss briefly well-known databases as well as ontologies in the materials science field. Further, we briefly introduce OPTIMADE.

2.1 Data and Databases in Materials Design Domain

In the search for designing new materials, the calculation of electronic structures is an important tool. Calculations take data representing the structure and property of materials as input and generate new such data. A common crystallographic data representation that is widely used by researchers and software vendors for materials design, is CIF555Crystallographic Information Framework, https://www.iucr.org/resources/cif. It was developed by the International Union of Crystallography Working Party on Crystallographic Information and was first online in 2006. One of the widely used databases is the Inorganic Crystal Structure Database (ICSD)666https://icsd.products.fiz-karlsruhe.de/. ICSD provides data that is used as an important starting point in many calculations in the materials design domain.

As the size of computed data grows, and more and more machine learning and data mining techniques are being used in materials design, frameworks are appearing that not only provide data but also tools. Materials Project, AFLOW and OQMD are well-known examples of such frameworks that are publicly available.

Materials Project [Jain2013]

is a central program of the Materials Genome Initiative, focusing on predicting the properties of all known inorganic materials through computations. It provides open web-based data access to computed information on materials, as well as tools to design new materials. To make the data publicly available, the Materials Project provides open Materials API and an open-source python-based programming package (pymatgen).

AFLOW [curtarolo2012aflow] (Automatic Flow for Materials Discovery) is an automatic framework for high-throughput materials discovery, especially for crystal structure properties of alloys, intermetallics, and inorganic compounds. AFLOW provides a REST API and a python-based programming package (aflow). OQMD [saal2013materials] (The Open Quantum Materials Database) is also a high-throughput database consisting of over 600,000 crystal structures calculated based on density functional theory777http://oqmd.org. OQMD is designed based on a relational data model. OQMD supports a REST API and a python-based programming package (qmpy).

2.2 Ontologies and Standards

Within the materials science domain, the use of semantic technologies is in its infancy with the development of ontologies and standards. The ontologies have been developed, focusing on representing general materials domain knowledge and specific sub-domains, respectively.

Two ontologies representing general materials domain knowledge and to which our ontology connects are ChEBI and EMMO. ChEBI [degtyarenko2007chebi] (Chemical Entities of Biological Interest) is a freely available data set of molecular entities focusing on chemical compounds. The representation of such molecular entities as atom, molecule ion, etc. is the basis in both chemistry and physics. The ChEBI ontology is widely used and integrated into other domain ontologies. EMMO (European Materials & Modelling Ontology) aims at developing a standard representational ontology framework based on current knowledge of materials modeling and characterization. The EMMO development started from the very bottom level, using the actual picture of the physical world coming from applied sciences, and in particular from physics and material sciences. Although EMMO already covers some sub-domains in materials science, many sub-domains are still lacking, including the domain MDO targets.

Further, a number of ontologies from the materials science domain focus on specific sub-domains (e.g., metals, ceramics, thermal properties, nanotechnology), and have been developed with a specific use in mind (e.g., search, data integration) [lambrix2018big]. For instance, the Materials Ontology [ashino2010materials] was developed for data exchange among thermal property databases, and MatOnto ontology [cheung2008towards] for oxygen ion conducting materials in the fuel cell domain, NanoParticle Ontology [thomas2011nanoparticle] represents properties of nanoparticles with the purpose of designing new nanoparticles, while the eNanoMapper ontology [hastings2015enanomapper] focuses on assessing risks related to the use of nanomaterials from the engineering point of view. Extensions to these ontologies in the nanoparticle domain are presented in [li2019method]. An ontology that represents formal knowledge for simulation, modeling, and optimization in computational molecular engineering is presented in [horsch2019semantic]. Further, an ontology design pattern to model material transformation in the field of sustainable construction, is proposed in [VardemanKCJFHB17].

There are also efforts on building standards for data export from databases and data integration among tools. To some extent the standards formalize the description of materials knowledge and thereby create ontological knowledge. A recent approach is Novel Materials Discovery (NOMAD888https://www.nomad-coe.eu/externals/european-centres-of-excellence) [draxl2019nomad] of which the metadata structure is defined to be independent of specific material science theory or methods that could be used as an exchange format [Ghiringhelli16].

2.3 Open Databases Integration for Materials Design

OPTIMADE aims at enabling interoperability between materials databases through a common REST API. During the development, OPTIMADE takes widely used materials databases such as those introduced in section 2.1 into account. It has a data model that represents basic entities in the materials design domain.

The process of querying OPTIMADE is shown in Figure 1. Users specify the name of a table, the response fields and filtering conditions. OPTIMADE parses the filtering conditions syntactically, and translates the parsing result, the table’s name and response fields into a query to the underlying database back-end (e.g., an SQL or Mongo-DB query).

Figure 1: The query model in OPTIMADE.

3 The Materials Design Ontology (MDO)

3.1 The development of MDO

The development of MDO followed the NeOn ontology engineering methodology [suarez2012neon]. It consists of a number of scenarios mapped from a set of common ontology development activities. In particular, we focused on applying scenario 1 (From Specification to Implementation), scenario 2 (Reusing and re-engineering non-ontological resources), scenario 3 (Reusing ontological resources) and scenario 8 (Restructuring ontological resources

). We used OWL2 DL as representation language for MDO. During the whole process, two knowledge engineers, and one domain expert from the materials design domain were involved. In the remainder of this section, we introduce the key aspects of the development of MDO.

3.1.1 Requirements Analysis.

During this step, we clarified the requirements by proposing Use Cases (UC), Competency Questions (CQ) and additional restrictions.

The use cases, which were identified through literature study and discussion between the domain expert and the knowledge engineers based on experience with the development of OPTIMADE and the use of materials science databases, are listed below.

  • UC1: MDO will be used for representing knowledge in basic materials science such as solid-state physics and condensed matter theory.

  • UC2: MDO will be used for representing materials calculation and standardizing the publication of the materials calculation data.

  • UC3: MDO will be used as a standard to improve the interoperability among heterogeneous databases in the materials design domain.

  • UC4: MDO will be mapped to OPTIMADE’s schema to improve OPTIMADE’s search functionality.

The competency questions are listed below.

  • CQ1: What are the calculated properties and their values produced by a materials calculation?

  • CQ2: What are the input and output structures of a materials calculation?

  • CQ3: What is the space group type of a structure?

  • CQ4: What is the lattice type of a structure?

  • CQ5: What is the chemical formula of a structure?

  • CQ6: For a series of materials calculations, what are the compositions of materials with a specific range of calculated property (e.g., band gap)?

  • CQ7: For a specific material and a given range of a calculated property (e.g., band gap), what is the lattice type of the structure?

  • CQ8: For a specific material and an expected lattice type of output structure, what are the values of calculated properties of the calculations?

  • CQ9: What is the computational method used in a materials calculation?

  • CQ10: What is the value for a specific parameter (e.g., cutoff energy) of the method used for the calculation?

  • CQ11: Which software produced the result of a calculation?

  • CQ12: Who are the authors of the calculation?

  • CQ13: Which software or code does the calculation run with?

  • CQ14: When was the calculation data published to the database?

Further, we proposed a list of additional restrictions that help in defining concepts. Some examples are shown below. The full list of additional restrictions can be found at the GitHub repository999https://github.com/huanyu-li/Materials-Design-Ontology/blob/master/requirements.md.

  • A materials property can relate to a structure.

  • A materials calculation has exactly one corresponding computational method.

  • A structure corresponds to one specific space group.

  • A materials calculation is performed by some software programs or codes.

3.1.2 Reusing and re-engineering non-ontological resources.

To obtain the knowledge for building the ontology, we followed two steps: (1) the collection and analysis of non-ontological resources that are relevant to the materials design domain, and (2) discussions with the domain expert regarding the concepts and relationships to be modeled in the ontology. The collection of non-ontological resources comes from: (1) the dictionaries of CIF and International Tables for Crystallography; (2) the APIs from different databases (e.g., Materials Project, AFLOW, OQMD) and OPTIMADE.

3.1.3 Modular development aiming at building design patterns.

We identified a pattern related to provenance information in the repository of Ontology Design Patterns (ODP) that could be reused or re-engineered for MDO. This has led to the reuse of entities in PROV-O [lebo2013prov]. Further, we built MDO in modules considering the possibility for each module to be an ontology design pattern, e.g., the calculation module.

3.1.4 Connection and Integration of Existing Ontologies.

MDO is connected to EMMO by reusing the concept ‘Material’, and to ChEBI by reusing the concept ‘atom’. Further, concepts from PROV-O are used. We use the metadata terms from the Dublin Core Metadata Initiative (DCMI)101010http://purl.org/dc/terms/ to represent the metadata of MDO.

3.2 Description of MDO

MDO consists of one basic module, Core, and two domain-specific modules, Structure and Calculation, importing the Core module. In addition, the Provenance module, which also imports Core, models the provenance information of materials calculations. In total, the OWL2 DL representation of the ontology contains 33 classes, 25 object properties, and 37 data properties. Figure 6 shows an overview of the ontology while Figures 25 show the different modules. Figure 7 shows the description logic axioms for MDO. The ontology specification is also publicly accessible at w3id.org111111 https://w3id.org/mdo/full/1.0. The competency questions can be answered using the concepts and relations in the different modules (CQ1 and CQ2 by Core, CQ3 to CQ8 by Structure, CQ9 and CQ10 by Calculation, and CQ11 to CQ14 by Provenance).

The Core module (Figure 2) consists of the top-level concepts and relations of MDO, which are also reused in other modules. The module represents general information of materials calculations. The concepts Calculation and Structure represent materials calculations and materials’ structures, respectively, while Property represents materials properties. Property is specialized into the disjoint concepts CalculatedProperty and PhysicalProperty (Core1, Core2, Core3 in Figure 7). When a calculation is applied on materials structures, each calculation takes some structures and properties as input, and may output structures and calculated properties (Core4, Core5). Further, we use EMMO’s concept Material and state that each structure is related to some material (Core6)). Properties are also related to structures (Core7).

Figure 2: Concepts and relations in the Core module.

The Structure (Figure 3) module represents the structural information of materials. Each structure has exact one composition which represents what chemical elements compose the structure and the ratio of elements in the structure (Struc1). The composition has different representations of chemical formulas. The occupancy of a structure relates the sites with the species, i.e. the specific chemical elements, that occupy the site (Struc2 - Struc5). Each site has no more than one representation of coordinates in Cartesian format and one in fractional format (Struc6, Struc7). The spatial information regarding structures is essential to reflect physical characteristics such as melting point and strength of materials. To represent this spatial information, we state that each structure is represented by some bases and a (periodic) structure can also be represented by one or more lattices (Struc8). Each basis and each lattice can be identified by one

axis-vectors

set or one length triple together with one angle triple (Struc9, Struc10). In crystallography, point groups and space groups are used to represent information of the symmetry of a structure. The space group represents a symmetry group of patterns in three dimensions of a structure and the point group represents a group of linear mappings which correspond to the group of motions in space to determine the symmetry of a structure. Each structure has one corresponding space group (Struc11). Based on the definition from International Tables for Crystallography, each space group also has some corresponding point groups (Struc12).

Figure 3: Concepts and relations in the Structure module.

The Calculation module (Figure 4) represents the classification of different computational methods. Each calculation is achieved by a specific computational method (Cal1). Each computational method has some parameters (Cal2). In the current version of this module, we represent two different methods, the density functional theory method and the Hartree-Fock method (Cal3, Cal4). In particular, the density functional theory method is frequently used in materials design to investigate the electronic structure. Such method has at least one corresponding exchange correlation energy functional (Cal5) which is used to calculate exchange–correlation energy of a system. There are different kinds of functionals to calculate exchange–correlation energy (Cal6 - Cal11).

Figure 4: Concepts and relations in the Calculation module.

The Provenance module (Figure 5) represents the provenance information of materials data and calculation. We reuse part of PROV-O and defined a new concept ReferenceAgent as a sub-concept of PROV-O’s agent (Prov1). We state that each structure and property can be published by reference agents which could be databases or publications (Prov2, Prov3). Each calculation is produced by a specific software (Prov4).

Figure 5: Concepts and relations in the Provenance module.
Figure 6: Ontological Entities in MDO. The four modules, Core, Structure, Calculation and Provenance are shown with different colors, bold content shows the connections to other ontologies.

(Core1) CalculatedProperty Property
(Core2) PhysicalProperty Property
(Core3) CalculatedProperty PhysicalProperty
(Core4) Calculation hasInputStructure.Structure hasInputStructure.Structure
      hasOutputStructure.Structure
(Core5) Calculation hasInputProperty.Property hasInputProperty.Property
      hasOutputCalculatedProperty.CalculatedProperty
(Core6) Structure relatedToMaterial.Material relatedToMaterial.Material
(Core7) Property relatesToStructure.Structure
(Struc1) Structure = 1 hasComposition.Composition
      hasComposition.Composition
(Struc2) Structure hasOccupancy.Occupancy hasOccupancy.Occupancy
(Struc3) Occupancy hasSpecies.Species hasSpecies.Species
(Struc4) Occupancy hasSite.Site hasSite.Site
(Struc5) Species = 1 hasElement.Atom
(Struc6) Site 1 hasCartesianCoordinates.CoordinateVector
      hasCartesianCoordinates.CoordinateVector
(Struc7) Site 1 hasFractionalCoordinates.CoordinateVector
      hasCartesianCoordinates.CoordinateVector
(Struc8) Structure hasBasis.Basis hasBasis.Basis hasLattice.Lattice
(Struc9) Basis = 1 hasAxisVectors.AxisVectors
      (= 1 hasLengthTriple.LengthTriple = 1 hasAngleTriple.AngleTriple)
(Struc10) Lattice = 1 hasAxisVectors.AxisVectors
      (= 1 hasLengthTriple.LengthTriple = 1 hasAngleTriple.AngleTriple)
(Struc11) Structure = 1 hasSpaceGroup.SpaceGroup hasSpaceGroup.SpaceGroup
(Struc12) SpaceGroup hasPointGroup.PointGroup hasPointGroup.PointGroup
(Cal1) Calculation = 1 hasComputationalMethod.ComputationalMethod
(Cal2) ComputationalMethod hasParameter.ComputationalMethodParameter
      hasParameter.ComputationalMethodParameter
(Cal3) DensityFunctionalTheoryMethod ComputationalMethod
(Cal4) HartreeFockMethod ComputationalMethod
(Cal5) DensityFunctionalTheoryMethod
      hasXCFunctional.ExchangeCorrelationFunctional
      hasXCFunctional.ExchangeCorrelationFunctional
(Cal6) GeneralizedGradientApproximation ExchangeCorrelationFunctional
(Cal7) LocalDensityApproximation ExchangeCorrelationFunctional
(Cal8) metaGeneralizedGradientApproximation ExchangeCorrelationFunctional
(Cal9) HybridFunctional ExchangeCorrelationFunctional
(Cal10) HybridGeneralizedGradientApproximation HybridFunctional
(Cal11) HybridmetaGeneralizedGradientApproximation HybridFunctional
(Prov1) ReferenceAgent Agent
(Prov2) Structure wasAttributedTo.ReferenceAgent
(Prov3) Property wasAttributedTo.ReferenceAgent
(Prov4) Calculation wasAssociatedwith.SoftwareAgent

Figure 7: Description logic axioms for MDO.

4 MDO Usage

In Figure 8, we show the vision for the use of MDO for semantic search over OPTIMADE and materials science databases. By generating mappings between MDO and the schemas of materials databases, we can create MDO-enabled query interfaces. The querying can occur, for instance, via MDO-based query expansion, MDO-based mediation or through MDO-enabled data warehouses.

As a proof of concept (full lines in the figure), we created mappings between MDO and the schemas of OPTIMADE and part of Materials Project. Using the mappings we created an RDF data set with data from Materials project. Further, we built a SPARQL query application which can be used to query the RDF data set using MDO terminology. Examples are given below.

Figure 8: The vision of the use of MDO. The full-lined components in the figure are currently implemented in a prototype.

4.0.1 Instantiating a materials calculation using MDO.

In Figure 9 we exemplify the use of MDO to represent a specific materials calculation and related data in an instantiation. The example is from one of the 85 stable materials published in Materials Project in [faber2016machine]. The calculation is about one kind of elpasolites, with the composition . To not overcrowd the figure, we only show the instances corresponding the calculation’s output structure, and for multiple calculated properties, species and sites, we only show one instance respectively. Connected to the instances of the Core module’s concepts, are instances representing the structural information of the output structure, the provenance information of the output structure and calculated property, and the information about the computational method used for the calculation.

Figure 9: An instantiated materials calculation.

4.0.2 Mapping the data from a materials database to RDF using MDO.

As presented in section 2.1, data from many materials databases are provided through the providers’ APIs. A commonly used format is JSON. Our current implementation mapped all JSON data related to the 85 stable materials from [faber2016machine] to RDF. We constructed the mappings by using SPARQL-Generate [lefranccois2017sparql]. Listing 1 shows a simple example on how to write the mappings on ‘band gap’ which is a CalculatedProperty. The result is shown in Listing 2. The final RDF dataset contains 40,066 triples. The SPARQL-generate script and the RDF dataset are available from the GitHub repository121212https://github.com/huanyu-li/Materials-Design-Ontology/tree/master/mapping_generator. This RDF dataset is used for executing SPARQL queries such as the one presented below.

PREFIX core: <https://w3id.org/mdo/core/>
GENERATE {
        ?band_gap_node a core:CalculatedProperty;
        core:hasPropertyValue ?band_gap;
        core:hasPropertyName "band_gap";
        core:hasUnit "eV";
}
SOURCE <http://example.com/mp-989579_Rb2LiTlCl6.json>
      AS ?source
WHERE {
  BIND(fun:JSONPath(?source,"$.original_task_id")
      AS ?TASK_ID)
  BIND(fun:JSONPath(?source,"$.band_gap") AS ?band_gap)
  BIND(<{?TASK_ID}_band_gap> AS ?band_gap_node)
}
Listing 1: A simple example of mapping
@prefix core:  <https://w3id.org/mdo/core/> .
        rdf:type core:CalculatedProperty ;
        core:hasPropertyName "band_gap" ;
        core:hasPropertyValue 1.5623e0 ;
        core:hasUnit "eV" ;
Listing 2: RDF data

4.0.3 A SPARQL Query Example.

As example we show a SPARQL query related to CQ6 in Listing 3. The result contains 7 records which are shown in Table 4.0.3. The query is:

  • “What are the materials of which the value of band gap is higher than 5eV?” (The result should contain the formula, and the value of band gap.)

PREFIX core: <https://w3id.org/mdo/core/>
PREFIX structure: <https://w3id.org/mdo/structure/>
SELECT ?formula ?value WHERE {
  ?calculation rdf:type core:Calculation;
               core:hasOutputCalculatedProperty ?Property;
               core:hasOutputStructure ?OutputStructure.
  ?Property core:hasPropertyValue ?value;
            core:hasPropertyName ?name.
  ?OutputStructure structure:hasComposition ?Composition.
  ?Composition structure:hasDescriptiveFormula ?formula.
  FILTER (?value>5 && ?name="band_gap")
}
Listing 3: A SPARQL query example on Materials Project’s dataset
Table 1: The result of the query
formula value
5.3759999999999994
5.939299999999999
5.4629
5.2687
5.5428
5.9026
6.0426

We show more SPARQL query examples and the corresponding result in the GitHub repository131313https://github.com/huanyu-li/Materials-Design-Ontology/tree/master/sparql_query.

5 Discussion and Future Work

To our knowledge, MDO is the first OWL ontology representing solid-state physics concepts, which are the basis for materials design.

The ontology fills a need for semantically enabling access to and integration of materials databases, and for realizing FAIR data in the materials design field. This will have a large impact on the effectiveness and efficiency of finding relevant materials data and calculations, thereby augmenting the speed and the quality of the materials design process. Through our connection with OPTIMADE and because of the fact that we have created mappings between MDO and some major materials databases, the potential for impact is large.

The development of MDO followed well-known practices from the ontology engineering point of view (NeOn methodology, modular design, and the use of ODPs). Further, we reused concepts from PROV-O, ChEBI, and EMMO.

A permanent URL is reserved from w3id.org for MDO. MDO is maintained on a GitHub repository from where the ontology in OWL2 DL, visualizations of the ontology and modules, UCs, CQs and restrictions are available. It is licensed via an MIT license141414 https://github.com/huanyu-li/Materials-Design-Ontology/blob/master/LICENSE.

Due to our modular approach MDO can be extended with other modules, for instance, regarding different types of calculations and their specific properties. We identified, for instance, the need for an X Ray Diffraction module to model the experimental data of the diffraction used to explore the structural information of materials, and an

Elastic Tensor

module to model data in a calculation that represents a structure’s elasticity. We may also refine the current ontology. For instance, it may be interesting to model workflows containing multiple calculations. We will also consider to publish modules as ODPs as they have encoded the practice of modeling the knowledge in the domain.

6 Conclusion

In this paper, we presented MDO, an ontology which defines concepts and relations to cover the knowledge in the field of materials design and which reuses concepts from other ontologies. We discussed the ontology development process showing use cases and competency questions. Further, we showed the use of MDO for semantically enabling materials database search. As a proof of concept, we mapped MDO to OPTIMADE and part of Materials Project and showed querying functionality using SPARQL on a dataset from Materials Project.

Acknowledgements.

This work has been financially supported by the Swedish e-Science Research Centre (SeRC), the Swedish National Graduate School in Computer Science (CUGS), and the Swedish Research Council (Vetenskapsrådet, dnr 2018-04147).

References