SAREF reference ontology patterns

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.

SAREF patterns for procedure executions

NOTE: The text in this page is taken from ETSI TS 103 548, and therefore falls under the ETSI IPR Policy

A saref:ProcedureExecution represents the act of carrying out a procedure.

SAREF Core defines four sub-classes of saref:ProcedureExecution:

  • saref:CommandExecution describes the execution of a command.
  • saref:OperationExecution describes the execution of an operation in a network: the-machine interpretable-description of a communication between devices over the network.
  • saref:Observation is the act of carrying out a procedure to estimate or calculate a value of a property of a feature of interest, or a state of a feature of interest.
  • saref:Actuation is the act of carrying out a procedure to control the state of the world using an actuator. It links to an actuator to describe what made the actuation, and to the controlled feature, property, property of interest, state, or state of interest.

The figure below illustrates the main classes and properties in the SAREF Core patterns for procedure executions.

SAREF Core pattern for Procedure Executions
SAREF Core pattern for Procedure Executions

SAREF extensions should not create specific instances of the class saref:ProcedureExecution or any of its sub-classes, as they are meant to be created by applications.

SAREF extensions and applications shall not define sub-properties of the following properties:

  • saref:madeBy
  • saref:isMadeBy
  • saref:hasResultTime
  • saref:hasPhenomenonTime
  • saref:hasTimestamp