38
3 Marketplace-Level Domain Ontologies
from the EMMO [15, 16]. Corresponding domain ontologies: VIVO and VOV,
cf. Sect. 3.4 and Chap. 4.
These categories need not be disjoint, e.g. evmpo:material and evmpo:product overlap, since a material can be manufactured with the intent of selling it as a commodity,
by which it becomes a good, and hence a product.
The common superclass of the paradigmatic categories is evmpo:paradigmatic_entity. Below the fundamental level, the EVMPO also includes non-fundamental
entites as subclasses, e.g. evmpo:simulation as a subclass of evmpo:process and
evmpo:service as a subclass of evmpo:product. Terms which are not closely related
to the materials modelling marketplace paradigm itself, but may occur within a
related knowledge base, are defined to be non-paradigmatic. For this purpose, the
EVMPO includes evmpo:annotation as a twelfth, non-paradigmatic fundamental
category; the EVMPO top relation, parent to both evmpo:paradigmatic_entity and
evmpo:annotation,
is
evmpo:marketplace_related_entity.
The
relation
evmpo:has_annotation can connect any marketplace-related entity to an annotation.
Below this, 12 subproperties are defined, corresponding to the fundamental categories, i.e. evmpo:has_assessment_annotation pointing to annotations of an assessment, etc., and evmpo:has_meta_annotation for annotations of an annotation.
Consistency with the EVMPO, and by implication consistency with the EMMO,
is a requirement for all components and infrastructures that aim at interoperating
within the EVMF. This design ensures that while EVMF-interoperable infrastructures
need to agree on the definition of the most important entities, any platform retains
the option to extend its own semantic base as required. To remain interoperable
within the EVMF, any additional concepts need to be subsumed under fundamental
categories from the EVMPO; cf. Sect. 5.4 for a summary on how the EVMPO and
the marketplace-level domain ontologies are aligned with the EMMO.
3.3 Modelling, Simulation and Computational Resources
The Marketplace-Accessible Computational Resource Ontology (MACRO) deals
with data and hardware-related resources and infrastructures [14]. In particular,
MACRO contains classes and individuals representing file formats expected to occur
on the VIMMP marketplace platform,
8 many of which are obtained by connecting
to the EDAM ontology [25]. High-level concepts from MACRO and their relation
to EVMPO concepts (evmpo:agent, evmpo:annotation, etc.) are shown in Fig. 3.2.
Complementing MACRO, the PaaSPort ontology [26] can be used to describe Platforms as a Service (PaaS).
The Ontology for Simulation, Modelling and Optimization (OSMO) was developed as the ontology version of MODA [20], making workflow representations
8 MACRO: https://purl.vimmp.eu/semantics/macro/macro.ttl (non-resolvable
IRI), mirrored at http://www.molmod.info/semantics/macro.ttl (resolvable URL).
3 Marketplace-Level Domain Ontologies
from the EMMO [15, 16]. Corresponding domain ontologies: VIVO and VOV,
cf. Sect. 3.4 and Chap. 4.
These categories need not be disjoint, e.g. evmpo:material and evmpo:product overlap, since a material can be manufactured with the intent of selling it as a commodity,
by which it becomes a good, and hence a product.
The common superclass of the paradigmatic categories is evmpo:paradigmatic_entity. Below the fundamental level, the EVMPO also includes non-fundamental
entites as subclasses, e.g. evmpo:simulation as a subclass of evmpo:process and
evmpo:service as a subclass of evmpo:product. Terms which are not closely related
to the materials modelling marketplace paradigm itself, but may occur within a
related knowledge base, are defined to be non-paradigmatic. For this purpose, the
EVMPO includes evmpo:annotation as a twelfth, non-paradigmatic fundamental
category; the EVMPO top relation, parent to both evmpo:paradigmatic_entity and
evmpo:annotation,
is
evmpo:marketplace_related_entity.
The
relation
evmpo:has_annotation can connect any marketplace-related entity to an annotation.
Below this, 12 subproperties are defined, corresponding to the fundamental categories, i.e. evmpo:has_assessment_annotation pointing to annotations of an assessment, etc., and evmpo:has_meta_annotation for annotations of an annotation.
Consistency with the EVMPO, and by implication consistency with the EMMO,
is a requirement for all components and infrastructures that aim at interoperating
within the EVMF. This design ensures that while EVMF-interoperable infrastructures
need to agree on the definition of the most important entities, any platform retains
the option to extend its own semantic base as required. To remain interoperable
within the EVMF, any additional concepts need to be subsumed under fundamental
categories from the EVMPO; cf. Sect. 5.4 for a summary on how the EVMPO and
the marketplace-level domain ontologies are aligned with the EMMO.
3.3 Modelling, Simulation and Computational Resources
The Marketplace-Accessible Computational Resource Ontology (MACRO) deals
with data and hardware-related resources and infrastructures [14]. In particular,
MACRO contains classes and individuals representing file formats expected to occur
on the VIMMP marketplace platform,
8 many of which are obtained by connecting
to the EDAM ontology [25]. High-level concepts from MACRO and their relation
to EVMPO concepts (evmpo:agent, evmpo:annotation, etc.) are shown in Fig. 3.2.
Complementing MACRO, the PaaSPort ontology [26] can be used to describe Platforms as a Service (PaaS).
The Ontology for Simulation, Modelling and Optimization (OSMO) was developed as the ontology version of MODA [20], making workflow representations
8 MACRO: https://purl.vimmp.eu/semantics/macro/macro.ttl (non-resolvable
IRI), mirrored at http://www.molmod.info/semantics/macro.ttl (resolvable URL).