appears_in: []
depends_on: []
deprecated: false
description: "The present document is the technical specification of SAREF4SYST, a\
  \ generic extension of [ETSI TS 103 264 SAREF](https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/02.01.01_60/ts_103264v020101p.pdf)\
  \ that defines an ontology pattern which can be instantiated for different domains.\
  \ SAREF4SYST defines Systems, Connections between systems, and Connection Points\
  \ at which systems may be connected. These core concepts can be used generically\
  \ to define the topology of features of interest, and can be specialized for multiple\
  \ domains. The topology of features of interest is highly important in many use\
  \ cases. If a room holds a lighting device, and if it is adjacent with an open window\
  \ to a room whose luminosity is low, then by turning on the lighting device in the\
  \ former room one may expect that the luminosity in the latter room will rise.\n\
  \nThe SAREF4SYST ontology pattern can be instantiated for different domains. For\
  \ example to describe zones inside a building (systems), that share a frontier (connections).\
  \ Properties of systems are typically state variables (e.g. agent population, temperature),\
  \ whereas properties of connections are typically flows (e.g. heat flow).\n\nSAREF4SYST\
  \ has two main aims: on the one hand, to extend SAREF with the capability or representing\
  \ general topology of systems and how they are connected or interact and, on the\
  \ other hand, to exemplify how ontology patterns may help to ensure an homogeneous\
  \ structure of the overall SAREF ontology and speed up the development of extensions.\n\
  \nSAREF4SYST consists both of a core ontology, and guidelines to create ontologies\
  \ following the SAREF4SYST ontology pattern. The core ontology is a lightweight\
  \ OWL-DL ontology that defines 3 classes and 9 object properties.\n\nUse cases for\
  \ ontology patterns are described extensively in  [ETSI TR 103 549 Clauses 4.2 and\
  \ 4.3](https://www.etsi.org/deliver/etsi_tr/103500_103599/103549/01.01.01_60/tr_103549v010101p.pdf).\n\
  \nFor the Smart Energy domain:\n\n- Electric power systems can exchange electricity\
  \ with other electric power systems. The electric energy can flow both ways in some\
  \ cases (from the Public Grid to a Prosumer), or in only one way (from the Public\
  \ Grid to a Load). Electric power systems can be made up of different sub-systems.\
  \ Generic sub-types of electric power systems include producers, consumers, storage\
  \ systems, transmission systems. \n- Electric power systems may be connected one\
  \ to another through electrical connection points. An Electric power system may\
  \ have multiple connection points (Multiple Winding Transformer generally have one\
  \ single primary winding with two or more secondary windings). Generic sub-types\
  \ of electrical connection points include plugs, sockets, direct-current, single-phase,\
  \ three-phase, connection points. \n- An Electrical connection may exist between\
  \ two Electric power systems at two of their respective connection points. Generic\
  \ sub-types of electrical connections include Single-phase Buses, Three-phase Buses.\
  \ A single-phase electric power system can be connected using different configurations\
  \ at a three-phase bus (RN, SN, TN types).\n\nFor the Smart Building domain:\n\n\
  - Buildings, Storeys, Spaces, are different sub-types of Zones. Zones can contain\
  \ sub-zones. Zones can be adjacent or intersect with other zones. \n- Two zones\
  \ may share one or more connections. For example some fresh air may be created inside\
  \ a storey if it has two controllable openings to the exterior at different cardinal\
  \ points. \n\nA graphical overview of the SAREF4SYST ontology is provided in Figure\
  \ 1. In such figure:\n\n- Rectangles are used to denote Classes. The label of the\
  \ rectangle is the identifier of the Class.\n- Plain arrows are used to represent\
  \ Object Properties between Classes. The label of the arrow is the identifier of\
  \ the Object Property. The origin of the arrow is the domain Class of the property,\
  \ and the target of the arrow is the range Class of the property.\n- Dashed arrows\
  \ with identifiers between stereotype signs (i.e. \"`<< >>`\") refer to OWL axioms\
  \ that are applied to some property. Four pairs of properties are inverse one of\
  \ the other; the property `s4syst:connectedTo` is symmetric, and properties `s4syst:hasSubSystem`\
  \ and `s4syst:hasSubSystem` are transitive.\n- A symbol =1 near the target of an\
  \ arrow denotes that the associated property is functional. A symbol ? denotes a\
  \ local existential restriction.\n\n\n![SAREF4SYST overview](diagrams/overview.png)"
example: Connection
example_extras: []
homepage: https://saref.etsi.org/saref4syst/
keywords:
- iot
- nfdi4ing
mappings:
  lov: s4syst
  tib: s4syst
name: 'SAREF4SYST: an extension of SAREF for typology of systems and their inter-connections'
preferred_prefix: saref.system
prefix: saref.system
providers: []
publications: []
synonyms:
- s4syst
uri_format: https://saref.etsi.org/saref4syst/$1
