Merge branch 'wastes' into develop-v2.1.1

catalog-v001.xml

saref-pipeline.jar

target

ts

 No newline at end of file

labs.etsi.org/rep/:

  repos:

    - saref/saref-core

    - saref/saref4ener

    - saref/saref4syst

# image: openjdk:8-jdk

# variables:

#     SAREF_DEV_KEY: <my_private_key>

#     SAREF_PORTAL_KEY: <my_private_key>

# before_script:

#   - eval $(ssh-agent -s)

#   - ssh-add <(echo "$SAREF_DEV_KEY")

#   - mkdir -p ~/.ssh

#   - '[[ -f /.dockerenv ]] && echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config'

# stages:

#   - test

#   - build

#   - deploy

# test-develop:

#   stage: test

#   script:

#     - curl -L -o saref-pipeline.jar "https://saref.etsi.org/downloads/saref-pipeline.jar"

#     - java -jar saref-pipeline.jar develop -s && touch target/success

#   allow_failure: true

#   except:

#     - /^prerelease-v/

#     - /^release-v/

#   artifacts:

#     when: always

#     paths:

#       - target/site

#       - target/success

#     reports:

#       junit: target/report_output.xml

# test-prerelease:

#   stage: test

#   script:

#     - curl -L -o saref-pipeline.jar "https://saref.etsi.org/downloads/saref-pipeline.jar"

#     - java -jar saref-pipeline.jar release -t && touch target/success

#   allow_failure: true

#   only:

#     - /^prerelease-v/

#   artifacts:

#     when: always

#     paths:

#       - target/site

#       - target/success

#     reports:

#       junit: target/report_output.xml

# deploy-report:

#   stage: deploy

#   script:

#     - scp -pr target/site saref-dev@saref.etsi.org:~/snapshot/$CI_PIPELINE_ID

#     - echo "SAREF pipeline report  https://saref.etsi.org/snapshot/$CI_PIPELINE_ID/report.html" 

#     - exit $(test -f target/success) $?

#   except:

#     - /^release-v/

# test-release:

#   stage: test

#   script:

#     - curl -L -o saref-pipeline.jar "https://saref.etsi.org/downloads/saref-pipeline.jar"

#     - java -jar saref-pipeline.jar release -t

#   only:

#     - /^release-v/

# trigger-release:

#   stage: deploy

#   only:

#     - /^release-v/

#   variables:

#     SAREF_DEV_KEY: $SAREF_DEV_KEY

#     SAREF_PORTAL_KEY: $SAREF_PORTAL_KEY

#   trigger:

#     project: saref/saref-portal

#     branch: master

The present document is the technical specification of SAREF4ENVI, an extension of SAREF [[1]](#[1]) for the environment domain. The extension was created in collaboration with domain experts in the field of light pollution currently working in the STARS4ALL European H2020 project ([http://www.stars4all.eu/index.php/lpi/](http://www.stars4all.eu/index.php/lpi/)). The STARS4ALL project is composed by partners such as Universidad Politécnica de Madrid, Universidad Complutense de Madrid, ESCP Europe, Leibniz Institute of Freshwater Ecology and Inland Fisheries, Instituto de Astrofísica de Canarias, University of Southampton, Europan Crowdfunding Network, and CEFRIEL (Società Consortile a Responsabilita Limitata).

<div class="alert-warning">NOTE: The text in this section is extracted from ETSI TS 103 410-2 (V2.1.1) <a href="#[0]">[0]</a>, and therefore falls inside the <a href="https://www.etsi.org/intellectual-property-rights">ETSI IPR Policy</a></div>

SAREF4ENVI has two main aims: on the one hand, to be the basis for enabling the use of SAREF in the environment domain and, on the other hand, to exemplify how to enable interoperability between environmental devices in cooperation.

SAREF4ENVI is an OWL-DL ontology that extends SAREF with 32 classes (24 defined in SAREF4ENVI and 7 reused from the time, SAREF and geo ontologies), 24 object properties (22 defined in SAREF4ENVI and 2 reused from the SAREF and geo ontologies), 13 data type properties (9 defined in SAREF4ENVI and 4 reused from the SAREF ontology), and 24 individuals (9 defined in SAREF4ENVI and 12 reused from the OM ontology). SAREF4ENVI focuses on extending SAREF for photometers to solve the lack of interoperability between sensors that can measure and share information about light pollution. Such extension involves the following use cases (more details can be found in ETSI TR 103 411 [[i.1]](#[i.1])):

[The technical specification ETSI TS 103 410-2](#[0]) is a technical specification of SAREF4ENVI, an OWL-DL ontology that extends SAREF [[1]](#[1]) for the Environment domain. 

- Use case 1: Monitor light pollution in a city, through the data collected by photometers about the magnitude of the light emitted in a given area.

- Use case 2: Adjust lampposts light intensity due to high pollution, after identifying the most contaminating lampposts and therefore the areas where more energy is being thrown away.

- Use case 3: Register a photometer, in which a new collection of photometers is incorporated into an existing sensor network.

[The technical specification ETSI TS 103 410-2](#[0]) is a major revision of SAREF4ENVI ontology extension, developed in the context of the STF 641 (<a href="https://portal.etsi.org/xtfs/">https://portal.etsi.org/xtfs/#/xTF/641</a>), using updated reference ontology patterns specified in ETSI TS 103 548 [[2]](#[2]) to solve the harmonization needs identified in ETSI TR 103 781 [[i.3]](#[i.3]), with updated development framework and tools defined in ETSI TS 103 673 [[3]](#[3]).

ETSI TS 103 410-2 (V1.1.2) [[i.1]](#[i.1]) was created in collaboration with domain experts in the field of light pollution that worked in the STARS4ALL European H2020 project (<a href="https://cordis.europa.eu/project/id/688135/">https://cordis.europa.eu/project/id/688135</a>/). The STARS4ALL project was composed of partners such as Universidad Politécnica de Madrid, Universidad Complutense de Madrid, ESCP Europe, Leibniz Institute of Freshwater Ecology and Inland Fisheries, Instituto de Astrofísica de Canarias, University of Southampton, Europan Crowdfunding Network, and CEFRIEL (Società Consortile a Responsabilita Limitata). As such, V1.1.2 of [the technical specification ETSI TS 103 410-2](#[0]) focused on extending SAREF for photometers to solve the lack of interoperability between sensors that can measure and share information about light pollution. Such extension involves the following use cases (more details can be found in ETSI TR 103 411 [[i.2]](#[i.2])):

* **Use case 1**: Monitor light pollution in a city, through the data collected by photometers about the magnitude of the light emitted in a given area.

* **Use case 2**: Adjust lampposts light intensity due to high pollution, after identifying the most contaminating lampposts and therefore the areas where more energy is being thrown away.

* **Use case 3**: Register a photometer, in which a new collection of photometers is incorporated into an existing sensor network.

Added in [the technical specification ETSI TS 103 410-2](#[0]) is the covering of the waste management domain, as a collaboration between IMT - Mines Saint-Étienne and the company Compost'Ond, specialized in composting biodegradable waste. The Waste Managment Domain is divided into three modules: Waste, Collection and Treatment. They correspond chronologically to the three stages of waste management systems, from the moment a material becomes waste to the moment it is either transformed into another resource or becomes a final waste:

* The Waste module of the Waste Management Domain covers waste, those who produce it and where, its type, and the containers in which it is disposed before collection.

* The Collection module of the Waste Management Domain covers waste collection, the vehicles used and the journeys made to do so.

* The Treatment module of the Waste Management Domain covers waste processing (pre-treatment, treatment, disposal), the processes that can be used for doing so, the organisations involved, the emissions produced, and the final outputs.

The intention of SAREF4ENVI includes:

* to be the basis for enabling the use of SAREF in the environment domain;

* to exemplify how to enable interoperability between environmental devices in cooperation.

As all the SAREF ontologies, SAREF4ENVI is a dynamic semantic model that is meant to evolve over time. Therefore, the stakeholders in the Environment domain are invited to use, validate and provide feedback on SAREF4ENVI, collaborating with the SAREF ontology experts to improve and evolve SAREF4ENVI in an iterative and interactive manner, so that changes and additions can be incorporated in future releases of [the technical specification ETSI TS 103 410-2](#[0]).

The prefixes and namespaces used in SAREF4ENVI and in [the technical specification ETSI TS 103 410-2](#[0]) are listed in [the Namespace Declarations section](#namespacedeclarations).

For all the entities described in [the technical specification ETSI TS 103 410-2](#[0]), it is indicated whether they are defined in the SAREF4ENVI extension or elsewhere by the prefix included before their identifier, i.e. if the element is defined in SAREF4ENVI, the prefix is s4envi, while if the element is reused from another ontology, it is indicated by a prefix according to [the Namespace Declarations section](#namespacedeclarations). Colour codes also help to distinguish the provenance of entities.

Diagrams are to be interpreted using the Chowlk notation [[3]](#[3]), clause 9.7.2.

[Figure 1](#Figure_1) provides a symbol legend for SAREF4ENVI diagrams.

<figure>

  <img src="diagrams/SAREF4ENVI_figures.SymbologyLegend.png" alt="Symbol legend for diagrams in <a href="#[0]">the technical specification ETSI TS 103 410-2</a>"/>

  <figcaption id="Figure_1">Figure 1: Symbol legend for diagrams in <a href="#[0]">the technical specification ETSI TS 103 410-2</a></figcaption>

</figure>

- [Maxime Lefrançois](http://maxime-lefrancois.info/me#) ([MINES Saint-Étienne](https://www.mines-stetienne.fr/))

- [Audrey Tanguy](https://orcid.org/0000-0002-2094-0572) ([MINES Saint-Étienne](https://www.mines-stetienne.fr/))

- [Fabien Badeig](https://www.linkedin.com/in/fabien-badeig/) ([MINES Saint-Étienne](https://www.mines-stetienne.fr/))

- [Raúl Garcia-Castro](http://www.garcia-castro.com/foaf.rdf#me) ([Universidad Politécnica de Madrid](http://www.oeg-upm.net/))