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:ConnectionPoint class. If defined, it shall have an English-tagged label (rdfs:label) ending with "Connection Point". The local name of its IRI shall be a camel case form of its English-tagged label.
EXAMPLE 1: ex:ThreePhaseConnectionPoint has English-tagged label "Three-Phase Connection Point"@en
.
A sub-class of the s4syst:ConnectionPoint class shall have an English-tagged comment (rdfs:comment) that defines it in natural language.
EXAMPLE 2: ex:ThreePhaseConnectionPoint has English-tagged comment "A three-phase connection point is a connection point composed of four wires (plus the protective earth): wires R, S, T, for the phases; wire N for the neutral".@en.
A sub-class of the s4syst:ConnectionPoint class may have a universal restriction on the property s4syst:connectsSystemThrough or one of its sub-properties to a sub-class of s4syst:Connection. If so, then the label or the comment of the sub-class of s4syst:ConnectionPoint and the sub-class of s4syst:Connection shall show this relation ostensibly.
A sub-class of the s4syst:ConnectionPoint class may have a universal restriction on the property s4syst:connectionPointOf to a sub-class of s4syst:System. If so, then the label or the comment of the sub-class of s4syst:ConnectionPoint and the sub-class of s4syst:System shall show this relation ostensibly.
EXAMPLE 3: ex:IlluminableZoneFrontierConnectionPoint has a universal restriction on the property s4syst:connectsSystemThrough to the class ex:LightTransmissionSystemConnection, has a universal restriction on the property s4syst:connectionPointOf to the class s4syst ex:IlluminableZoneSystem, and has English-tagged comment "The class of zones frontiers _on_ which one may measure/effect luminosity, and perceive brightness. Illuminable zones are surfaces such as walls, tables, sheer curtains, mirrors, windows. Light may be reflected, absorbed, and transmitted by illuminable zone frontier connection points"@en
.
A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectionPointOf 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 should use the same morpho-syntactic structure as its super-property.
A sub-property of the s4syst:connectionPointOf property shall have an English-tagged comment (rdfs:comment) that describes in natural language how the connected s4syst:System interact.
A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectsAt 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 should use the same morpho-syntactic structure as its super-property.
EXAMPLE 1: ex:connectsPrimarilyAt has English-tagged label "connects primarily at"@en
.
A sub-property of the s4syst:connectsAt property shall have an English-tagged comment (rdfs:comment) that describes in natural language how the connected s4syst:System interact.
EXAMPLE 2: ex:connectsPrimarilyAt has English-tagged comment "Links an electric power transformer system to its primary connection point"@en
.
A sub-class of s4syst:System may be equivalent to an anonymous class having a universal restriction on s4syst:connectsAt or one of its sub-properties to a sub-class of s4syst:ConnectionPoint. If so, then the label or the comment of the sub-class of s4syst:System and the sub-class of s4syst:ConnectionPoint shall show this relation ostensibly.
EXAMPLE 3: ex:USBCommunicationDeviceSystem is equivalent to an anonymous class having a universal restriction on s4syst:connectsAt to the class ex:USBCommunicationConnectionPoint, and has English-tagged comment "The class of communication devices capable of communicating using the USB protocol"@en
.
A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectsSystemThrough 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 should use the same morpho-syntactic structure as its super-property.
EXAMPLE 1: ex:connectsSystemInSNThrough has English-tagged label "connects system in SN through"@en
.
A sub-property of the s4syst:connectsSystemThrough property shall have an English-tagged comment (rdfs:comment) that describes in natural language how the connected s4syst:System interact.
EXAMPLE 2: ex:connectsSystemInSNThrough has English-tagged comment "Links a single phase connection point to a three-phase power bus connection with which it is connected with a SN configuration"@en
A sub-property of the s4syst:connectsSystemThrough property may have an inverse property. If defined, the English-tagged labels and comments of these two properties shall reflect this aspect.
EXAMPLE 3: ex:connectsSystemInSNThrough and ex:connectsSystemInSNAt are inverse properties.
A sub-property of the s4syst:connectsSystemThrough property may be defined as disjoint from other sub-properties of s4syst:connectsSystemThrough.
EXAMPLE 4: The following properties are disjoint: ex:connectsSystemInStarThrough and ex:connectsSystemInTriangleThrough.
A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectsSystemAt 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 should use the same morpho-syntactic structure as its super-property.
EXAMPLE 1: ex:connectsSystemInStarAt has English-tagged label "connects system in star at"@en
.
A sub-property of the s4syst:connectsSystemAt property shall have an English-tagged comment (rdfs:comment) that describes in natural language how the connected s4syst:System interact.
EXAMPLE 2: ex:connectsSystemInStarAt has English-tagged comment "Links a three-phase power bus connection to one of the three-phase connection points it connects with a triangle configuration"@en
.
A sub-class of s4syst:Connection may have an existential or universal restriction on s4syst:connectsSystemAt or one of its sub-properties to a sub-class of s4syst:ConnectionPoint. If so, then the label or the comment of the sub-class of s4syst:Connection and the sub-class of s4syst:ConnectionPoint shall show this relation ostensibly.
EXAMPLE 3: ex:USBCommunicationConnection has a universal restriction on s4syst:connectsSystemAt to the class ex:USBCommunicationConnectionPoint, and has English-tagged comment "The class of USB communication connections between communication devices"@en
.
A sub-property of the s4syst:connectsSystemAt property may have an inverse property. If defined, the English-tagged labels and comments of these two properties shall reflect this aspect.
EXAMPLE 4: ex:connectsSystemInSNAt and ex:connectsSystemInSNThrough are inverse properties.
A sub-property of the s4syst:connectsSystemAt property may be defined as disjoint from other sub-properties of s4syst:connectsSystemThrough.
EXAMPLE 5: The following properties are disjoint: ex:connectsSystemInStarAt and ex:connectsSystemInTriangleAt.