### General Overview

A graphical overview of the SAREF4ENVI ontology is provided in Figure 1.

In such figure, grey rectangles are used to denote classes created in the ontology while white rectangles denote reused classes. For all the entities, it is indicated whether they are defined in the extension or in other ontologies by the prefix included before their identifier, that is, if the element is defined in SAREF4ENVI there is no prefix added and if the element is reused from another ontology it is indicated by a prefix according to the Namespace Declarations section.

Arrows are used represent properties between classes and to represent some RDF, RDF-S and OWL constructs, more precisely:

- Plain arrows with white triangles represent the rdfs:subClassOf relation between two classes. The origin of the arrow is the class to be declared as subclass of the class at the destination of the arrow.
- Dashed arrows between two classes indicate a local restriction in the origin class, i.e. that the object property can be instantiated between the classes in the origin and the destination of the arrow. The identifier of the object property is indicated within the arrow.
- Dashed arrows with identifiers between stereotype signs (i.e. "<< >>") refer to OWL constructs that are applied to some ontology elements, that is, they can be applied to classes or properties depending on the OWL construct being used.
- Dashed arrows with no identifier are used to represent the rdf:type relation, indicating that the element in the origin of the arrow is an instance of the class in the destination of the arrow.

Datatype properties are denoted by rectangles attached to the classes, in an UML-oriented way. Dashed boxes represent local restrictions in the class, i.e. datatype properties that can be applied to the class it is attached to.

Individuals are denoted by grey rectangles (or white ones in the case of being reused from other ontologies) in which the identifier is underlined.

The representation of additional property axioms (functional, inverse functional, transitive, and symmetric) that are being used in the diagram is shown in the legend of Figure 1.

Clause 4.2.2 to clause 4.2.7 describe the different parts of the SAREF4ENVI extension describing the different conceptual modules of the ontology.

Figure 1: SAREF4ENVI overview

### Physical Object Hierarchy

In SAREF4ENVI, the SAREF ontology has been extended with various elements to describe different physical objects, devices, and their characteristics.

Apart from extending the saref:Device class with the s4envi:Device class, a hierarchy has been defined also including the classes s4envi:PhysicalObject, s4envi:System and s4envi:Actuator in the upper levels. In order to represent sensors from the light pollution domain, the classes s4envi:Photometer and s4envi:TESS (a specific type of photometer) have been included extending the hierarchy. Such classes are organized in the hierarchy shown in Figure 2.

Figure 2: Physical Object hierarchy

### Devices and Measurements

Devices and measurements are depicted in Figure 3. This model represents an n-ary pattern that allows users to relate different measurements from a given sensor for different properties measured in different units. That is, the saref:Measurement class aims at describing a measurement of a physical quantity (using the saref:hasValue property) for a given saref:Property and according to a given saref:UnitOfMeasure.

This pattern enables to differentiate between properties and the measurements made for such properties and to store measurements for a concrete property in different units of measurement.

Furthermore, it allows adding a timestamp (using the saref:hasTimeStamp property) to identify when the measurement applies to the property, which can be used either for single measurements or for series of measurements (e.g. measurement streams).

It is worth noting that this modelling was included in SAREF 2.0 after the SAREF4ENVI extension was developed. This pattern was first included in the SAREF4ENVI and SAREF4BLDG extensions and then proposed to be extrapolated to SAREF 2.0; this explains why the prefix used for this part of the model refers to SAREF instead of to SAREF4ENVI. However, as its origin is in the SAREF4ENVI and SAREF4BLDG extensions requirements and models, the explanations are kept in the present document.

Figure 3: Sensor and measurement model

### Devices

Figure 4 represents the s4envi:Device class which is extended from saref:Device; therefore, the new class inherits the properties defined in the SAREF ontology for saref:Device, such as saref:hasManufacturer. In addition, the class has been complemented with the properties s4envi:hasFrequencyMeasurement and s4envi:hasTransmissionPeriod in order to model the frequency with which a device makes measurements and its period for transmitting such measurements. Both relationships are represented by n-ary relationships modelled by the classes s4envi:FrequencyMeasurement and s4envi:PeriodMeasurement, which are subclasses of saref:Measurement. The specific value for the frequency and the period is indicated by the datatype property saref:hasValue , which is inherited from the class saref:Measurement.

As the temporal units of measurement are already defined in SAREF by means of the class time:TemporalUnit, there has been no need for defining new units for s4envi:PeriodMeasurement. However, new units of measurement are needed to represent frequencies; therefore, saref:UnitOfMeasure class has been extended with the class s4envi:FrequencyUnit, including the main instances from the OM units of measurement ontology to measure frequency, such as om:hertz, om:reciprocal_second-time, om:reciprocal_hour, om:reciprocal_day, and om:reciprocal_year. It is worth noting that the user is free to use other units of measurement if required.

Finally, s4envi:Actuator has been added according to the domain expert requirements in order to represent devices that can act (s4envi:affectsProperty) over properties as shown in Figure 4.

Figure 4: Device model

### Systems and Physical Objects

As already observed in Figure 2, according to the requirements extracted from uses cases and domain experts, it was necessary to include more general information about systems and physical objects, which are superclasses of devices, in order to provide a general framework for representing communications, componency, and digital representations. This section focuses on these additional classes included in SAREF4ENVI that model how to access physical objects and their components.

Figure 5 represents the class s4envi:System and its properties. It can observed that a system can be composed of other systems and this is represented by the property s4envi:hasComponent and its inverse s4envi:isComponentOf. A system can also be connected to other systems, represented by the s4envi:isConnectedTo property.

The communication protocol and interface that a system might use are represented by the classes s4envi:CommunicationProtocol and s4envi:CommunicationInterface, respectively.

Figure 5: System model

The model represented in Figure 6 supports the representation of services that allow the access to digital representations of a given physical object (e.g. devices, sensors, etc.). The main entity in this model is s4envi:PhysicalObject that represents a general class for devices and systems and any other entity with a physical representation in order to make the model extensible to other domains. Such object can have digital representations (s4envi:DigitalRepresention) that can be accessed through services (saref:Service).

In addition, the digital representation can be linked back to the physical object that it encapsulates by means of the property s4envi:encapsulates, defined as inverse of s4envi:hasDigitalRepresentation. It is worth noting that s4envi:hasDigitalRepresentation is defined as inverse functional since a digital representation can encapsulate only one object.

Finally, the relation between a physical object and its location is represented by the reused property geo:location. In addition, s4envi:PhysicalObject is declared to be subclass of geo:SpatialThing.

Figure 6: Physical object and digital representation model

### Photometers

A photometer, in general, is an instrument that measures light intensity or optical properties of solutions or surfaces. In general a s4envi:Photometer is an entity that observes some s4envi:LightProperty, in a way of paraphrasing the axiom shown in Figure 7. In such figure, it can also be observed that a particular case of photometer is a s4envi:TESS (Telescope Encoder and Sky Sensor). It is worth noting that other particular photometers could be added by extending the s4envi:Photometer class when reusing this extension.

Furthermore, Figure 7 also shows the main light properties that can be observed by a photometer. These properties are represented as instances, for example s4envi:Luminiscence, of the class s4envi:LightProperty.

Figure 7: Photometer and light property model

### Lampposts, Light Points and Light

Figure 8 represents the model to represent lampposts and their possible light points using the classes s4envi:Lamppost and s4envi:LightPoint. It can also be indicated that a lamppost can have one or more light points by using the s4envi:hasLightPoint object property.

In this model both lampost and light points are allowed to be agents that project light (represented by the property s4envi:projectsLight). In this sense, one lamppost could directly project light or in a more complex scenario a lamppost could have different light points being these light points in charge of projecting the light.

Finally, s4envi:LightPoint has been defined as subclass of geo:Point as it is a point located in a given space and it can inherit the mechanism to express its latitude, altitude and longitude from geo:Point.

Figure 8: Lamppost and light point model

The model depicted in Figure 9 represents the light characteristics. It can be observed that a light is projected in a certain angle, in a given direction and from a given height, represented by the properties s4envi:hasProjectionAngle (datatype property), s4envi:isProjectedInDirection (object property) and s4envi:isProjectedFromHeight (object property), respectively.

The angle is represented by a float indicating the degrees of the cone of light that the light emits. Besides, the direction can be represented by instances of the class s4envi:CompassDirection that could represent values such as North, South, Northwest, etc.

The height from which a light is projected is modelled as a subclass of saref:Measurement, namely s4envi:HeightMeasurement, as in this case it is necessary to indicate the value of such measure, inherited from saref:Measurement, and the unit of measurement used. That is, an n-ary pattern is used here.

The colour of the light emitted is represented by the objet property s4envi:hasColor and its values should be instantiated as individuals of the class s4envi:Color. Similarly, the geometry of a light can be indicated by means of the s4envi:hasGeometry object property and its values would belong to the class s4envi:Geometry.

Finally, it could be indicated whether a light has a flash by using the s4envi:hasFlash datatype property.

Figure 9: Light model

### Observations about S4ENVI

In the following, several observations about potential uses of the SAREF4ENVI ontology are listed.

First of all, it is worth reminding here that a TESS is an example of a particular photometer, other photometers could be included by extending the class s4envi:Photometer.

In addition, in order to include other physical objects or devices related to environmental measurements in other use cases, the different classes included in the ontology could be extended. For example, s4envi:Photometer should be extended to represent CO2 sensors; in that case, the saref:Property hierarchy should be extended with the properties that CO2 sensors might measure following the guidelines presented in this extension.