5.2 Top-Level Ontology
79
by VIPRS, the IRI elements ip, hp, is and hs stand for “is proper part,” “has proper
part,” “is sign” and “has sign,” respectively. Accordingly, the binary chain relations
include
viprs:mereosemiotics_hp_ip ≡ P
−
◦ P,
viprs:mereosemiotics_ip_is ≡ P ◦ S,
viprs:mereosemiotics_ip_hs ≡ P ◦ S
−
, etc.
(5.9)
while the ternary chain relations include
viprs:mereosemiotics_hp_ip_is ≡ P
−
◦ P ◦ S,
viprs:mereosemiotics_hp_ip_hs ≡ P
−
◦ P ◦ S
−
,
viprs:mereosemiotics_ip_is_ip ≡ P ◦ S ◦ P, etc.
(5.10)
With minor exceptions, datatype properties (owl:DatatypeProperty) are absent
from the EMMO [9]; by the domain ontologies, however, datatype properties are
amply employed to associate objects with textual (xs:string), numerical (xs:decimal)
attributes and xs:boolean flags. Figure 5.4 visualizes the hierarchy of top-level
datatype properties introduced in VIPRS. At the highest level, VIPRS categorizes
datatype properties according to their role:
• Identification of an object is positioned below viprs:has_identifier; examples
include otras:has_topic_code, which maps a materials modelling topic
(otras:mm_topic) from OTRAS to a four-digit code. Each topic code uniquely
corresponds to one topic, and its purpose is identification.
• Where an elementary-datatype entry is the content (or part of the content) of an
object, datatype properties below viprs:has_content are used, e.g. this applies to
textual or numerical content of MODA from entries (in OSMO, aspects), corresponding to osmo:has_aspect_text_content and osmo:has_aspect_text_content
[20, 21], cf. Section 3.3.
• Elementary descriptors, specifiers and similar metadata that provide additional,
contingent information on objects, viprs:has_specifier is used, e.g.
otras:has_cited_video_duration_seconds points to a metadata item on the length
of a video. This contributes to our knowledge about the video by specification, while it does not permit its identification; moreover, the video duration is
information about the video content, but it is not itself the content. Therefore,
otras:has_cited_video_duration_seconds viprs:has_specifier.
At the second level, the datatypes are distinguished (string, decimal or Boolean).
Further below, at the third level, the textual datatype properties are further split into
subproperties according to their function (cf. Fig. 5.4).
79
by VIPRS, the IRI elements ip, hp, is and hs stand for “is proper part,” “has proper
part,” “is sign” and “has sign,” respectively. Accordingly, the binary chain relations
include
viprs:mereosemiotics_hp_ip ≡ P
−
◦ P,
viprs:mereosemiotics_ip_is ≡ P ◦ S,
viprs:mereosemiotics_ip_hs ≡ P ◦ S
−
, etc.
(5.9)
while the ternary chain relations include
viprs:mereosemiotics_hp_ip_is ≡ P
−
◦ P ◦ S,
viprs:mereosemiotics_hp_ip_hs ≡ P
−
◦ P ◦ S
−
,
viprs:mereosemiotics_ip_is_ip ≡ P ◦ S ◦ P, etc.
(5.10)
With minor exceptions, datatype properties (owl:DatatypeProperty) are absent
from the EMMO [9]; by the domain ontologies, however, datatype properties are
amply employed to associate objects with textual (xs:string), numerical (xs:decimal)
attributes and xs:boolean flags. Figure 5.4 visualizes the hierarchy of top-level
datatype properties introduced in VIPRS. At the highest level, VIPRS categorizes
datatype properties according to their role:
• Identification of an object is positioned below viprs:has_identifier; examples
include otras:has_topic_code, which maps a materials modelling topic
(otras:mm_topic) from OTRAS to a four-digit code. Each topic code uniquely
corresponds to one topic, and its purpose is identification.
• Where an elementary-datatype entry is the content (or part of the content) of an
object, datatype properties below viprs:has_content are used, e.g. this applies to
textual or numerical content of MODA from entries (in OSMO, aspects), corresponding to osmo:has_aspect_text_content and osmo:has_aspect_text_content
[20, 21], cf. Section 3.3.
• Elementary descriptors, specifiers and similar metadata that provide additional,
contingent information on objects, viprs:has_specifier is used, e.g.
otras:has_cited_video_duration_seconds points to a metadata item on the length
of a video. This contributes to our knowledge about the video by specification, while it does not permit its identification; moreover, the video duration is
information about the video content, but it is not itself the content. Therefore,
otras:has_cited_video_duration_seconds viprs:has_specifier.
At the second level, the datatypes are distinguished (string, decimal or Boolean).
Further below, at the third level, the textual datatype properties are further split into
subproperties according to their function (cf. Fig. 5.4).