3.4 Engineering Applications and Validation
45
aspects directly correspond to the ETCT text fields [18], except that as an ontology,
the MMTO permits the incorporation of semantically characterized content from the
semantic web. A business case can represent any purely economic consideration or
an optimization problem at the management level, whereas an IC refers to an industrial engineering problem or an optimization problem at the technical or research
and development level. Within the translation process, a suitable approach based on
modelling and simulation is identified and carried out; subsequently, the outcome is
translated back to support an actionable decision at the BC and IC levels. Thus, the
MMTO is also a tool for representing exchange of information during translation
processes (e.g. employing KPIs as logical variables), which may be represented by
workflow graphs following the MODA and/or LDT workflow notations [20, 27].
The VIMMP Validation Ontology (VIVO) categorizes assessments
(i.e. evaluations) of computational resource requirements and benchmarking as
well as customer feedback on various kinds of entities,
11 which can be provided
subsequent to transactions at the VIMMP marketplace [14]. Thereby, users support each other mututally, evaluating contents and providers, while the marketplace platform itself remains neutral and equally open and accessible to everybody. A matrix with subclasses of evmpo:assessment, indicating how marketplace users can evaluate what sort of objects, is shown in Fig. 3.11. Rows correspond to classes of entities that are subjected to an assessment such that a
vivo:data_infrastructure_assessment is an evmpo:assessment that vivo:evaluates an
evmpo:data_infrastructure, and a vivo:meta_assessment is an evmpo:assessment
that vivo:evaluates an evmpo:assessment. Columns correspond to different ways in
which entities can be evaluated, e.g. by reporting an observation on the relative quantitative accuracy (vivo:relative_accuracy_assessment) or by issuing a recommendation (evmpo:endorsement_assessment). Not all theoretically conceivable combinations are allowed—e.g. memory requirements can be stated for software, but not for
projects. Using VIVO, in particular, error analyses and estimates can be attributed to
models, simulation workflows and to data items obtained from repositories or other
platforms (Fig. 3.6).
Selected concepts from the MMTO and from VIVO:
• vivo:assertion: a claim or proposition (e.g. as part of an assessment). Subclasses
include vivo:accuracy_assertion, evmpo:material_property_information and vivo:
requirement_assertion.
• mmto:business_decision_support_system: a decision support system that is
applied to a business case. Analogous: mmto:industrial_decision_support_system,
mmto:translation_decision_support_system.
• vivo:certificate: a validation statement by which an assessment is stated.
• vivo:computational_time_requirement: a requirement assessment concerning the
computational (CPU time) requirements of a simulation workflow.
11 VIVO: https://purl.vimmp.eu/semantics/vivo/vivo.ttl (non-resolvable IRI),
mirrored at http://www.molmod.info/semantics/vivo.ttl (resolvable URL).
45
aspects directly correspond to the ETCT text fields [18], except that as an ontology,
the MMTO permits the incorporation of semantically characterized content from the
semantic web. A business case can represent any purely economic consideration or
an optimization problem at the management level, whereas an IC refers to an industrial engineering problem or an optimization problem at the technical or research
and development level. Within the translation process, a suitable approach based on
modelling and simulation is identified and carried out; subsequently, the outcome is
translated back to support an actionable decision at the BC and IC levels. Thus, the
MMTO is also a tool for representing exchange of information during translation
processes (e.g. employing KPIs as logical variables), which may be represented by
workflow graphs following the MODA and/or LDT workflow notations [20, 27].
The VIMMP Validation Ontology (VIVO) categorizes assessments
(i.e. evaluations) of computational resource requirements and benchmarking as
well as customer feedback on various kinds of entities,
11 which can be provided
subsequent to transactions at the VIMMP marketplace [14]. Thereby, users support each other mututally, evaluating contents and providers, while the marketplace platform itself remains neutral and equally open and accessible to everybody. A matrix with subclasses of evmpo:assessment, indicating how marketplace users can evaluate what sort of objects, is shown in Fig. 3.11. Rows correspond to classes of entities that are subjected to an assessment such that a
vivo:data_infrastructure_assessment is an evmpo:assessment that vivo:evaluates an
evmpo:data_infrastructure, and a vivo:meta_assessment is an evmpo:assessment
that vivo:evaluates an evmpo:assessment. Columns correspond to different ways in
which entities can be evaluated, e.g. by reporting an observation on the relative quantitative accuracy (vivo:relative_accuracy_assessment) or by issuing a recommendation (evmpo:endorsement_assessment). Not all theoretically conceivable combinations are allowed—e.g. memory requirements can be stated for software, but not for
projects. Using VIVO, in particular, error analyses and estimates can be attributed to
models, simulation workflows and to data items obtained from repositories or other
platforms (Fig. 3.6).
Selected concepts from the MMTO and from VIVO:
• vivo:assertion: a claim or proposition (e.g. as part of an assessment). Subclasses
include vivo:accuracy_assertion, evmpo:material_property_information and vivo:
requirement_assertion.
• mmto:business_decision_support_system: a decision support system that is
applied to a business case. Analogous: mmto:industrial_decision_support_system,
mmto:translation_decision_support_system.
• vivo:certificate: a validation statement by which an assessment is stated.
• vivo:computational_time_requirement: a requirement assessment concerning the
computational (CPU time) requirements of a simulation workflow.
11 VIVO: https://purl.vimmp.eu/semantics/vivo/vivo.ttl (non-resolvable IRI),
mirrored at http://www.molmod.info/semantics/vivo.ttl (resolvable URL).