pax_global_header 0000666 0000000 0000000 00000000064 13666406175 0014530 g ustar 00root root 0000000 0000000 52 comment=8de7e87548dcca8f339ea1607955d058035aa952 saref4ener-issue-6/ 0000775 0000000 0000000 00000000000 13666406175 0014423 5 ustar 00root root 0000000 0000000 saref4ener-issue-6/.gitignore 0000664 0000000 0000000 00000000067 13666406175 0016416 0 ustar 00root root 0000000 0000000 *~ .DS_Store catalog-v001.xml saref-pipeline.jar target saref4ener-issue-6/.gitlab-ci.yml 0000664 0000000 0000000 00000001540 13666406175 0017057 0 ustar 00root root 0000000 0000000 image: openjdk:8-jdk develop: script: - curl -L -o saref-pipeline.jar "https://gitlab.emse.fr/saref/saref-pipeline/-/jobs/artifacts/master/raw/target/saref-pipeline.jar?job=build" - java -jar saref-pipeline.jar develop -s except: - /^prerelease-v/ - /^release-v/ artifacts: when: always paths: - target/site - target/report_output.xml reports: junit: target/report_output.xml release: script: - curl -L -o saref-pipeline.jar "https://gitlab.emse.fr/saref/saref-pipeline/-/jobs/artifacts/master/raw/target/saref-pipeline.jar?job=build" - java -jar saref-pipeline.jar release only: - /^prerelease-v/ - /^release-v/ artifacts: when: always paths: - target/site - target/report_output.xml reports: junit: target/report_output.xml saref4ener-issue-6/.saref-repositories.yml 0000664 0000000 0000000 00000000070 13666406175 0021046 0 ustar 00root root 0000000 0000000 forge.etsi.org/rep/: repos: - saref/saref-core saref4ener-issue-6/LICENSE 0000664 0000000 0000000 00000002703 13666406175 0015432 0 ustar 00root root 0000000 0000000 Copyright 2019 ETSI Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. saref4ener-issue-6/README.md 0000664 0000000 0000000 00000000050 13666406175 0015675 0 ustar 00root root 0000000 0000000 Repository for the SAREF4ENER ontology. saref4ener-issue-6/documentation/ 0000775 0000000 0000000 00000000000 13666406175 0017274 5 ustar 00root root 0000000 0000000 saref4ener-issue-6/documentation/abstract.md 0000664 0000000 0000000 00000000610 13666406175 0021416 0 ustar 00root root 0000000 0000000 The present document is a technical specification of SAREF4ENER, an extension of SAREF [[2]](#[2]) that was created in collaboration with Energy@Home ([http://www.energy-home.it](http://www.energy-home.it)) and EEBus ([http://www.eebus.org/en](http://www.eebus.org/en)), the major Italy- and Germany-based industry associations, to enable the interconnection of their (different) data models. saref4ener-issue-6/documentation/acknowledgements.md 0000664 0000000 0000000 00000000646 13666406175 0023156 0 ustar 00root root 0000000 0000000 The editors would like to thank the ETSI SmartM2M technical committee for providing guidance and expertise. Also, many thanks to the ETSI staff and all other current and former active Participants of the ETSI SmartM2M group for their support, technical input and suggestions that led to improvements to this ontology. Also, special thanks goes to the ETSI SmartM2M Technical Officer Guillemin Patrick for his help. saref4ener-issue-6/documentation/creators.md 0000664 0000000 0000000 00000000126 13666406175 0021437 0 ustar 00root root 0000000 0000000 - [Laura Daniele](https://www.linkedin.com/in/lauradaniele) ([TNO](https://tno.nl/)) saref4ener-issue-6/documentation/description.html 0000664 0000000 0000000 00000023160 13666406175 0022507 0 ustar 00root root 0000000 0000000
An overview of the SAREF4ENER ontology is provided in Figure 1, where rectangles containing an orange circle are used to denote classes created in SAREF4ENER, while rectangles containing a faded orange circle denote classes reused from other ontologies, such as SAREF. For all the entities described in the present document, it is indicated whether they are defined in the SAREF4ENER extension or elsewhere by the prefix included before their identifier, i.e. if the element is defined in SAREF4ENER the prefix is s4ener:, while if the element is reused from another ontology it is indicated in the Namespace Declarations section.
Arrows with white triangles on top 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.
Directed arrows are used to represent properties between classes.
Rectangles that contain a list of values between square brackets denote an enumeration of individuals.
Note that Figure 1 aims at showing a global overview of the main classes of SAREF4ENER and their mutual relations. More details on the different parts of Figure 1 are provided below.
Figure 2 shows the hierarchy of classes and properties defined in SAREF4ENER.
Orange circles represent classes of SAREF4ENER, while faded orange circles represent classes that are reused from other ontologies. Object properties - which are properties between two classes - are denoted by blue rectangles, while datatype properties - which are properties between a class and a data type, such as xsd:string or xsd:dateTime - are denoted by green rectangles. Faded blue and green rectangles denote object properties and datatype properties that are reused from other ontologies.
A s4ener:Device is a subclass of a saref:Device, i.e. it inherits the properties of the more general saref:Device and extends it with additional properties that are specific for SAREF4ENER. The s4ener:Device class is shown in Figure 3.
This clause presents the classes of interest for smart energy management. These classes are used to schedule devices in certain modes and preferred times using power profiles to optimize energy efficiency and accommodate the customer's preferences (i.e. use case 2). These classes are s4ener:PowerProfile, s4ener:Alternative, s4ener:PowerSequence and s4ener:Slot, which are shown in Figure 4.
A s4ener:PowerProfile is a subclass of a saref:Profile, i.e. it inherits the properties of the more general saref:Profile extending it with additional properties that are specific for SAREF4ENER. The s4ener:PowerProfile is used by a s4ener:Device to expose the power sequences that are potentially relevant for the CEM. A s4ener:Device can expose a s4ener:PowerProfile, which consists of one or more alternative plans (s4ener:AlternativesGroup class). A s4ener:AlternativesGroup consists of one or more power sequences (s4ener:PowerSequence class), and a s4ener:PowerSequence consists of one or more slots (s4ener:Slot class). Inversely, a s4ener:Slot belongs to only and exactly one s4ener:PowerSequence, which, in turn, belongs to only and exactly one s4ener:AlternativesGroup, which, in turn, belongs to only and exactly one s4ener:PowerProfile. A s4ener:PowerProfile belongs to only and exactly one s4ener:Device.
The s4ener:AlternativesGroup consists of one or more power sequences (s4ener:PowerSequence class) and, inversely, a s4ener:PowerSequence belongs to only and exactly one s4ener:AlternativesGroup. Figure 5 shows the details of the s4ener:PowerSequence class.
The s4ener:PowerSequence consists of one or more slots (s4ener:Slot class) and, inversely, a s4ener:Slot belongs to only and exactly one s4ener:PowerSequence. Figure 6 shows the details of the s4ener:Slot class.
This clause presents the part of SAREF4ENER that defines how to model events used in, for example, a direct load management and power curtailing scenarios (i.e. use case 4). The classes of interest are s4ener:LoadControlEventData, s4ener:LoadControlEventAction, s4ener:LoadControlStateData and s4ener:LoadControlState, as shown in Figure 7.
The s4ener: LoadControlEventData class is used to represent overload warning severity level and related load control commands to a device. It is characterized by an event ID and a timestamp that represents the time the event information instance was created or received, and the time period that denotes the period of validity of the event. For example, 5 minutes ago an event was received which says that it shall take effect tomorrow from 14:00 to 15:30. In this event the timestamp is "5 minutes ago" and time period is "tomorrow from 14:00 to 15:30".
The s4ener:LoadControlEventAction class expresses the type of actions to be performed as a consequence of a load control event. A s4ener:LoadControlEventAction can be of type "consume" or "produce" to denote consumption or production of energy or power. Values for both consume and produce actions can be s4ener:emergency, s4ener:increase, s4ener:normal, s4ener:pause, s4ener:reduce, s4ener:resume.
The s4ener: LoadControlStateData class expresses the data about the state of an event and is characterized by the same event ID used in the s4ener:LoadControlEventData class, as well as a timestamp, and it is associated to the class s4ener:LoadControlState, which can be of type "consume" or "produce" - analogously to a load control event action – and expresses the possible states of a load control event. Values for both consume and produce load control states can be s4ener:eventAccepted, s4ener:eventStarted, s4ener:eventStopped, s4ener:eventRejected, s4ener:eventCancelled, or s4ener:eventError.
saref4ener-issue-6/documentation/diagrams/ 0000775 0000000 0000000 00000000000 13666406175 0021063 5 ustar 00root root 0000000 0000000 saref4ener-issue-6/documentation/diagrams/Device.png 0000664 0000000 0000000 00000056210 13666406175 0022774 0 ustar 00root root 0000000 0000000 PNG IHDR k _ sRGB gAMA a pHYs .> \IDATx^;H:=X WԉAKT [rIF] RF[`ZL}EVA+2}`1Nh}>L4ulqOَ _\/o2.;