The SAREF reference ontology patterns provide guidelines on how to use and extend SAREF concepts and relationships for the modelling and the description of any kind of applications-related data/information/systems. The SAREF reference ontology patterns can be applied to different verticals to provide the SAREF suite of ontologies a homogeneous and predictable structure, and to achieve higher semantic interoperability.
A specialization of the SAREF4SYST pattern may define a sub-class of the s4syst:System class. If defined, it shall have an English-tagged label (rdfs:label) ending with "System". The local name of its IRI shall be a camel case form of its English-tagged label.
EXAMPLE: ex:ElectricPowerSystem has English-tagged label "Electric Power System".@en
.
It shall have an English-tagged comment (rdfs:comment) that defines it in natural language.
A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:hasSubSystem property or the s4syst:subSystemOf property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property shall use the same morpho-syntactic structure as its super-property.
EXAMPLE 1: ex:subElectricPowerSystemOf with English-tagged label "sub electric power system of".@en
.
A sub-class of s4syst:System shall have an English-tagged comment (rdfs:comment) that describes in natural language how the properties of the sub-system contribute to the properties of the super-system.
EXAMPLE 2: ex:subElectricPowerSystemOf has English-tagged comment that contains "The consumed electricity of an electric power consumer system contributes to the consumed electricity of its super electric power consumer system"@en
.
A sub-class of s4syst:System may be defined as a sub-class or equivalent class of an anonymous class having an existential or universal restriction on the s4syst:hasSubSystem or s4syst:subSystemOf property. If so, the class shall be s4syst:System or one of its sub-classes.
A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectedTo property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label.
EXAMPLE 1: ex:exchangesElectricityWith has English-tagged label "exchanges electricity with".@en
.
It shall have an English-tagged comment (rdfs:comment) that describes in natural language how the connected s4syst:Systems interact.
A sub-property of the s4syst:connectedTo property may be symmetric. If so, it shall define a common domain and range that is s4syst:System or one of its sub-classes. The English-tagged comment shall reflect this symmetry. The comment shall mention the domain and range s4syst:Systems.
EXAMPLE 2: ex:exchangesElectricityWith has English-tagged comment "Links an electric power system to another electric power system with which it may exchange electricity".@en
.
If a sub-property of the s4syst:connectedTo property is not symmetric, then an inverse (owl:inverseOf) of this property may be defined. If defined, the English-tagged labels and comments of these two properties shall reflect this aspect.
EXAMPLE 3: ex:powers has English-tagged comment "Links an electric power system to another electric power system to which it sends electricity".@en
, and ex:isPoweredBy has English-tagged comment "Links an electric power system to another electric power system from which it receives electricity".@en
.