5.4 VIMMP-EMMO Alignment
85
Table 5.2 Alignment between selected relations from the VIMMP marketplace-level ontologies
(source ontology S) introduced in Sects. 3.3 (top), 3.4 (middle) and 3.5 (bottom) and VIPRS in
combination with the EMMO (target ontology T )
source-ontology relation
target-ontology relation a,b,c,d
osmo:has aspect
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
osmo:has aspect object content
P
− ◦ S
macro:has channel member
emmo-holistic:hasParticipant
macro:has granularity
(S
− ◦ P
− ) (S ◦ P
− ◦ S
− )
osmo:has value
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
osmo:has variable unit
emmo-metrology:hasReferenceUnit
macro:is io format of
S ◦ viprs:p loc and roc, cf. note a
osmo:is linked to
viprs:mutual requirement, cf. notes b and c
macro:provides access to
(S ◦ P
− ) viprs:satisfies requirement of, cf. note c
mmto:considers business case
P
− ◦ P ◦ S
−
mmto:describes product
S
vivo:evaluates
S
vivo:has assertion
P
−
vivo:has error statement
P
−
mmto:has tca pe type
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
vivo:has unit
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
vivo:is quantity kind
S
−
vivo:states assessment
P
−
viprs:enables, cf. note d
vico:contains
P
−
vico:follows
S viprs:is enabled by, cf. note d
vico:has affiliation
P
vico:has author
viprs:is enabled by, cf. note d
otras:has offered course
S ◦ P
−
otras:has specifier
S
− ◦ P
−
vico:is certifier of
viprs:satisfies requirement of, cf. note c
otras:is narrower than
S ◦ S −
otras:is part of course
P
a Modal statement I viprs:p_loc_and_roc J (read p_loc_and_roc as “possibly, the left occurs
and the right occurs”): It is possible for the left-hand argument I and the right-hand argument J to
occur jointly, i.e. ♦(occ[I ] ∧ occ[J ]).
b The modal relation viprs:mutual_requirement is defined by equivalence with the relational
intersection
viprs:satisfies_ requirement_of viprs:satisfies_requirement_of
− .
c I viprs:satisfies_requirement_of J implies that for some conceptualization K I of I , it is necessary that an instantiation I of K I occurs or that J does not occur
I viprs:satisfies_requirement_of J =⇒
(5.13)
∃K I : K I C I ∧
: (K I C I
) ∧ (occ[J ] → occ[I
]));
e.g. if J is a simulation with a code that requires XML input, I might be a particular XML file,
satisfying a requirement of J , while K I might be the XML file format. Then it is not the occurrence
of I itself that is strictly required for J to occur, but the occurrence of the more generic object K I .
However, occ[I ] necessarily implies occ[K I ]. By comparing Eqs. (5.6) and (5.13), with K J = J ,
we observe
viprs:satisfies_requirement_of viprs:n_loc_cor_rnoc.
(5.14)
d The modal relation viprs:is_enabled_by is defined by equivalence with the relational intersection viprs:p_loc_and_roc viprs:satisfies_requirement_of
− , the inverse relation of which
is given by viprs:enables ≡ viprs:p_loc_and_roc viprs:satisfies_requirement_of
85
Table 5.2 Alignment between selected relations from the VIMMP marketplace-level ontologies
(source ontology S) introduced in Sects. 3.3 (top), 3.4 (middle) and 3.5 (bottom) and VIPRS in
combination with the EMMO (target ontology T )
source-ontology relation
target-ontology relation a,b,c,d
osmo:has aspect
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
osmo:has aspect object content
P
− ◦ S
macro:has channel member
emmo-holistic:hasParticipant
macro:has granularity
(S
− ◦ P
− ) (S ◦ P
− ◦ S
− )
osmo:has value
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
osmo:has variable unit
emmo-metrology:hasReferenceUnit
macro:is io format of
S ◦ viprs:p loc and roc, cf. note a
osmo:is linked to
viprs:mutual requirement, cf. notes b and c
macro:provides access to
(S ◦ P
− ) viprs:satisfies requirement of, cf. note c
mmto:considers business case
P
− ◦ P ◦ S
−
mmto:describes product
S
vivo:evaluates
S
vivo:has assertion
P
−
vivo:has error statement
P
−
mmto:has tca pe type
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
vivo:has unit
S
− ◦ (P
−
• emmo-perceptual:Symbolic)
vivo:is quantity kind
S
−
vivo:states assessment
P
−
viprs:enables, cf. note d
vico:contains
P
−
vico:follows
S viprs:is enabled by, cf. note d
vico:has affiliation
P
vico:has author
viprs:is enabled by, cf. note d
otras:has offered course
S ◦ P
−
otras:has specifier
S
− ◦ P
−
vico:is certifier of
viprs:satisfies requirement of, cf. note c
otras:is narrower than
S ◦ S −
otras:is part of course
P
a Modal statement I viprs:p_loc_and_roc J (read p_loc_and_roc as “possibly, the left occurs
and the right occurs”): It is possible for the left-hand argument I and the right-hand argument J to
occur jointly, i.e. ♦(occ[I ] ∧ occ[J ]).
b The modal relation viprs:mutual_requirement is defined by equivalence with the relational
intersection
viprs:satisfies_ requirement_of viprs:satisfies_requirement_of
− .
c I viprs:satisfies_requirement_of J implies that for some conceptualization K I of I , it is necessary that an instantiation I of K I occurs or that J does not occur
I viprs:satisfies_requirement_of J =⇒
(5.13)
∃K I : K I C I ∧
: (K I C I
) ∧ (occ[J ] → occ[I
]));
e.g. if J is a simulation with a code that requires XML input, I might be a particular XML file,
satisfying a requirement of J , while K I might be the XML file format. Then it is not the occurrence
of I itself that is strictly required for J to occur, but the occurrence of the more generic object K I .
However, occ[I ] necessarily implies occ[K I ]. By comparing Eqs. (5.6) and (5.13), with K J = J ,
we observe
viprs:satisfies_requirement_of viprs:n_loc_cor_rnoc.
(5.14)
d The modal relation viprs:is_enabled_by is defined by equivalence with the relational intersection viprs:p_loc_and_roc viprs:satisfies_requirement_of
− , the inverse relation of which
is given by viprs:enables ≡ viprs:p_loc_and_roc viprs:satisfies_requirement_of