doc generated from pipeline

saref-pipeline.jar

target

ts

documentation/ts_*

The preliminary phase was followed by a kick-off workshop in which the experts of EEBus and E@H presented the details of their individual data models, i.e. EEBus (XSDs) and E@H (UML), and also their common data model, the EEBus & E@H (UML+XSDs) model. 

<figure id="Figure_A.1">

<figure>

        <img data-docx-width="15.52cm" src="diagrams/image18.png" alt="Approach"/>

        <figcaption>Figure A.1: Approach</figcaption>

    </figure>

Since the existing EEBus and E@H data models were expressed in different formats, i.e. XSD and UML, and SAREF4ENER had to be expressed in OWL as an extension of SAREF, these data models were first translated into corresponding OWL versions that could be used as intermediate ontologies towards the creation of SAREF4ENER. The transformations UML  OWL and XSD  OWL were performed manually, but existing tools can be used to automate this step (for example, TopBraid Composer™ Maestro Edition). The outcomes of these transformations were the EEBus (OWL) and E@H (OWL) intermediate ontologies in Figure A.1. The reason to create these two separate intermediate ontologies was practical. The common EEBus & E@H data model is a merged model whose parts could be straightforwardly identified as coming either from the EEBus or the E@H data model. Given that the EEBus and E@H experts were not yet (completely) acquainted with ontologies and OWL, their review process was facilitated by separating the generation of an OWL version in two parts. In this way, these experts could focus on their own part, namely EEBus or E@H, instead of having to deal with a single, large and more complex ontology. Moreover, these intermediate ontologies can be reused individually by the two associations if they decide to make use of an OWL version of their own data model in the future.

!!! alert-info "NOTE:"

!!! alert alert-info "NOTE:"

    TopBraid Composer Maestro Edition™ is an example of a suitable product available commercially. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of this product.

# Change history

<table id="Table_id_unknown" data-docx-preferred-width="3.49cm 2.25cm 11.24cm">

<table data-docx-preferred-width="3.49cm 2.25cm 11.24cm">

  <caption>label_unknown</caption>

  <tr>

    <th>Date </th>

### Normative references

# References

## Normative references

* <a id="[0]">[0]</a> [ETSI TS 103 410-1 (V1.2.1)](https://www.etsi.org/deliver/etsi_ts/103400_103499/10341001/01.02.01_60/ts_10341001v010201p.pdf): "SmartM2M;; Extension to SAREF; Part 1: Energy Domain".

* <a id="[1]">[1]</a>	[ETSI TS 103 264 (V3.1.1)](https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/03.01.01_60/ts_103264v030101p.pdf): "SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping".

* <a id="[3]">[3]</a>	[EN 50491-12-2:2022](https://standards.cencenelec.eu/dyn/www/f?p=CENELEC:110:::::FSP_PROJECT,FSP_ORG_ID:69013,1258281&cs=197399B06850C0E168124734149EE5EB5): "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) - Part 12-2: Smart grid - Application specification - Interface and framework for customer - Interface between the Home / Building CEM and Resource manager(s) - Data model and messaging" (produced by CENELEC).

### Informative references

## Informative references

* <a id="[i.1]">[i.1]</a>	TNO, EEBus, Energy@Home: "[SAREF4EE : The extension of SAREF for EEBus and Energy@Home](https://w3id.org/saref4ee)".

* <a id="[i.2]">[i.2]</a>	Energy@home: "[Energy@home Data Model](http://www.energy-home.it/Documents/Technical%20Specifications/E@h_data_model_v2.1.pdf)", v2.1, October 2015.