<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Evaluating the Efect of Semantic Enrichment on Entity Embeddings of IoT Knowledge Graphs</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Roderick van der Weerdt</string-name>
          <email>r.p.vander.weerdt@vu.nl</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Victor de Boer</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Laura Daniele</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ronald Siebes</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>TNO - Netherlands Organization for Applied Scientific Research</institution>
          ,
          <addr-line>The Hague</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Vrije Universiteit Amsterdam</institution>
          ,
          <addr-line>De Boelelaan 1105, 1081 HV Amsterdam</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <abstract>
        <p>IoT devices in Smart homes generate large amounts of data by sending messages to share measurements at frequent intervals. To make this IoT measurement data interoperable, ontologies such as SAREF are used to represent this data as knowledge graphs (KGs). These resulting KGs contain measurements from IoT devices together with the context about those devices, such as the type of measurements, or in which room it is located. Through the use of embedding methods, we learn embedding representations for entities in KGs that can be used to generate prediction models. In this study, we investigate how the structure of the IoT knowledge graph afects the efectiveness of embedding methods for such tasks. Specifically, we look at the efect on embedding quality of enriching IoT KGs by making implicit information such as temporal sequences and measurement value similarity explicit. We perform experiments on two IoT KGs represented using the SAREF ontology. One is in a basic setting, and the other has this information explicitly added. We use RDF2vec to create embeddings, train a classifier, and compare classifier accuracy.</p>
      </abstract>
      <kwd-group>
        <kwd>Knowledge</kwd>
        <kwd>Internet of Things</kwd>
        <kwd>smart homes</kwd>
        <kwd>ontologies</kwd>
        <kwd>SAREF</kwd>
        <kwd>RDF2vec</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        With IoT devices becoming more prevalent in everyday homes, common frameworks in which
IoT devices can interact become more important. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] Some of these frameworks use ontologies to
create a common knowledge representation that can represent all available information that IoT
devices can share. The resulting knowledge graph (KG) contains not only the information from
the IoT devices but also, due to the organization of the ontology, the context of the information.
      </p>
      <p>All this information combined in one KG provides opportunities to learn over the shared
knowledge by using embedding methods that create vector representations of the entities in a
KG, which can be used to train ML models used as forecasters or classifiers. A classifier could,
for example, be used to predict whether the outside temperature is expected to be warm or cold,
which in turn can be used to turn a heater on or of to save energy.</p>
      <p>
        However, the ontologies that are used in these frameworks were instead developed to optimize
embedding methods to learn from them, they were developed in a manner that: “facilitates the
matching of existing assets in the smart applications domain”. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] Explicitly adding implicitly
available information could potentially improve the quality of entity representations that are
created with the embedding methods. In this research, we investigated the efect that semantic
enrichment of a KG has on the quality of entity embeddings learned from it. This was tested by
taking existing IoT KGs and creating new IoT KGs by semantically enriching them, through the
addition of new properties and entities for each measurement. Classifiers are trained with the
respective entity embeddings and the accuracy of these classifiers was used to determine the
quality of the entity embeddings.
      </p>
      <p>Before the experiment is described in more detail, the next section will give an overview of
relevant research and use it to define some concepts we used in this work.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <p>In this section, we will give a short overview of existing work that is relevant to our research.
The first part explains what we define as IoT KGs, while the second part provides background
to embedding methods and specific methods that will be used in our experiments.</p>
      <sec id="sec-2-1">
        <title>2.1. IoT Knowledge Graphs</title>
        <p>
          We define IoT KGs as KGs specifically created to represent measurement data from IoT devices.
SAREF [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] was created to enable interoperability between IoT devices, it was designed to be
able to represent any information coming from IoT devices, serving as a common “language”
to share information with any other device. In Figure 1, we show an example of a SAREF
graph, four of the six properties of a s a r e f : M e a s u r e m e n t entity1 connect to an entity that
connects to every measurement made by that device, connecting to the same s a r e f : D e v i c e
s a r e f : F e a t u r e O f I n t e r e s t , s a r e f : P r o p e r t y and U n i t O f M e a s u r e m e n t entities, with the other two
properties relating to literals. So when walking through this graph, every measurement is
reachable within two steps.
        </p>
        <p>
          As seen in Figure 1, there are a few entities, such as s a r e f : D e v i c e or s a r e f : P r o p e r t y , that are
connected to the much larger amount of measurement entities. This disproportionate imbalance
between many measurement entities, and a few other entities is what we consider to define
a IoT KG. As stated in [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], the New York entity in DBpedia is specifically highly connected
because from it half of all other entities can be reached within two steps. This high connectivity
is also characteristic for IoT KGs, but instead of it being a specific characteristic of one entity,
this holds for every entity in the graph. Section 3.4 describes how the datasets we used follow
this structure.
        </p>
        <p>
          When examining the Web of Things ontology a similar structure can be observed, with the
w o t : p r o p e r t y entity acting as the s a r e f : M e a s u r e m e n t entity. [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] Similarly the Semantic Sensor
1To be consistent in our terminology we keep referring to these as entities, but for RDF purposes these are resources.
SAREF:Device
        </p>
        <p>SAREF:Task
SAREF:FeatureOfInterest</p>
        <p>SAREF:Property</p>
        <p>SAREF:UnitOfMeasurement
SAREF:Measurement1</p>
        <p>SAREF:Measurement2</p>
        <p>SAREF:Measurement3</p>
        <p>
          Network ontology uses s s n : o b s e r v a t i o n . [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] Earlier research by Moreira et al. [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] has shown
that, with minimal mappings, most properties of IoT data can be represented by both SSN and
SAREF. In our experiments, we focus on KGs that were modeled with SAREF, but based on
similarities between all discussed ontologies we expect our results to also be representative for
KGs modeled with the other ontologies.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Embedding algorithms</title>
        <p>
          The purpose of embedding models is to create a numerical representation for specific entities.
Word2vec learns embeddings for words based on with which other words they co-occur in
sentences. [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] RDF2vec uses random or directed walks to mimic sentences, working under
the assumption that good representations for nodes can be learned based on with which other
nodes they co-occur in random walks. [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] Research has shown that this assumption holds for
many graphs, such as DBpedia or Wikidata.
        </p>
        <p>
          In [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] the authors describe multiple variants of RDF2vec methods, which are all evaluated
on diferent KGs. These graphs were generated based on specific characteristics that a KG can
have, such as cardinality restrictions or relations to particular individuals. Similar to their work
we research the efect of KG characteristics on the quality of RDF2vec embeddings. However,
our characteristics are based on graphs that are used in practice, instead of very specific logical
definitions.
        </p>
        <p>
          Adding new information to a graph based on implicit information can have an adverse efect,
as shown by [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. In their paper, experiments are performed to test the efect of additional
Semantic
Enrichment
        </p>
        <p>Step I</p>
        <sec id="sec-2-2-1">
          <title>Enriched</title>
        </sec>
        <sec id="sec-2-2-2">
          <title>Graph</title>
          <p>Embedding
Model
Step II
Step II</p>
        </sec>
        <sec id="sec-2-2-3">
          <title>Entity</title>
        </sec>
        <sec id="sec-2-2-4">
          <title>Embeddings</title>
        </sec>
        <sec id="sec-2-2-5">
          <title>Entity</title>
        </sec>
        <sec id="sec-2-2-6">
          <title>Embeddings</title>
          <p>Classification
Task
Step III
Step III</p>
        </sec>
        <sec id="sec-2-2-7">
          <title>Accuracy</title>
          <p>compare</p>
        </sec>
        <sec id="sec-2-2-8">
          <title>Accuracy</title>
          <p>implicit information, but the quality of the embeddings actually declines. They hypothesize that
the initial absence of the implicit information was in itself a signal. Our semantic enrichment
approach similarly utilizes implicit knowledge, but in the case of IoT KGs, the implicit
information is used to create new relations because the current relations are insuficiently connecting
relevant entities.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Method</title>
      <p>In order to expose the efect that semantically enriching IoT KGs has on entity embeddings,
the following experiments were created. The experimental pipeline is depicted in Figure 2.
Each experiment consists of two graphs: an IoT graph (basic graph), and a copy of that first IoT
graph that has been semantically enriched (enriched graph). For the second step an embedding
method is used to create embeddings for specific entities in each graph, and step three uses these
entity embeddings to train a classifier. Comparing the accuracy of the classifier trained with
embeddings from the basic graph, with the accuracy of the classifier trained with embeddings
from the enriched graph will show the efect of the semantic enrichment.</p>
      <p>Each step is described in more detail in the following subsections. All the code used in these
experiments is available in our GitHub repository.2</p>
      <p>To investigate whether the amount of devices afects the embeddings, the experiments were
performed with three diferent quantities of devices. We used either all the measurements of:
one device, all the devices from one home, or all the devices from all the homes in the dataset.</p>
      <sec id="sec-3-1">
        <title>3.1. Step I: Semantic Enrichment</title>
        <p>In order to perform the semantic enrichment of the graph we created three new entities based
on implicit knowledge in the graph.</p>
        <p>Rounded value (red line in Figure 3) Each measurement entity has a measurement value,
which is used to create a new entity based on the rounded value of the measurement. In this
2https://github.com/RoderickvanderWeerdt/semantic-enrichment-of-IoT-graphs
SAREF:Device</p>
        <p>SAREF:Task
SAREF:FeatureOfInterest</p>
        <p>SAREF:Property</p>
        <p>SAREF:UnitOfMeasurement
SAREF:Measurement1</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Step II: Embedding creation</title>
        <p>
          For the embedding step of our experiment, we use the pyRDF2vec implementation of RDF2vec.
[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] This is an implementation of RDF2vec light, which only creates embeddings for specific
entities in KGs, specifically timestamp entities, not for all nodes. Timestamps were selected to
be embedded because they correspond with the classification task, which is described is 3.3.
This also provided the freedom to add and remove devices and measurements without having
to adjust the pipeline, keeping it as similar as possible between experiments. All experiments
used the reverse function of pyRDF2vec.
        </p>
        <p>An initial experiment compares diferent settings for the following hyperparameters: number
of walks per entity, length of the walks, and number of epochs the embeddings are trained.
A subset of the dataset described in Section 3.4 was used that only included 2000 time points,
to decrease the time it takes to train the embedding model. Based on the results of this first
experiment settings were selected to run the remaining experiments.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Step III: Evaluation Task</title>
        <p>The evaluation of the embeddings quality is a classification task, classifying each timestamp as
either hot or cold. The timestamps were labeled by dividing the dataset in two by sorting the
timestamps from hot to cold and labeling the first half as warm, and the second half as cold.</p>
        <p>The classification was performed with a Multilayer perceptron (MLP) implementation written
using PyTorch [11], consisting of two hidden layers with 512 ReLU activation nodes. These
were used as the default hyperparameters. The input to the MLP was the embeddings of the
timestamp, and the output was the hot or cold label.</p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Datasets</title>
        <p>At the moment of writing, we were not able to find open IoT KGs, which is likely due to the
privacy concerns of making people’s IoT device data publicly, therefore we created these ourselves,
using an energy consumption dataset on device level containing real device measurement data.
We created the IoT KGs following the mapping procedure detailed in [12]. Templates were
created for each device in the dataset, mapping each measurement to the graph together with
related properties.</p>
        <p>In order to create the entity files for the embedding step the timestamps of a dataset were
collected and used to connect with the outside temperature at that location at the specific time.
From those temperatures, the hot and cold labels were created. The outside temperature values
were retrieved through worldweatheronline.com.</p>
        <p>OPSD Household data The OPSD Household 1hour dataset [13] consists of energy
consumption measurements from devices in diferent types of buildings, of which we use only the
six residential homes since this is closest to the type of measurements we want to investigate.
Table 2 shows the distributions of the diferent device types over each separate residence. 3</p>
        <p>The dataset contains measurements taken over a five years duration, but not every device
recorded measurements for the entire period. In order to have a complete dataset we chose to
extract a subset of ten months where all devices had recorded measurements, by removing only
two devices (the freezer from residence 2, and the grid export from residence 6), if we would
have included these the measurements would only be available for two months.</p>
        <p>The final manipulation of the data was transforming the energy consumption
measurement from its original value of accumulated consumption from the startpoint, to accumulated
consumption over the last hour. This manipulation was performed to ensure that the
measurement values in the graph would be recurring, which would not be the case for accumulated
measurement values because those would only increase.</p>
        <p>The final graph represents 8133 timestamp entities linking to measurements from 37 devices
from ten device types, spread out over six residences. Three diferent versions of this graph
were created in order to be able to distinguish between the efects of adding more devices from
within the same home, and adding devices from other homes. The following shorthand is used
to refer to diferent compositions of the graph:</p>
        <p>res1dev1: this graph uses only measurements of one device. this is the heatpump from
residence 4. This graph contains 89477 triples.</p>
        <p>res1devA: this graph uses all measurements from all devices in one home, in this case, all
devices from residence 4. This graph contains 715,765 triples.</p>
        <p>resAdevA: this graph uses all measurements from all devices in all available homes that are
available. It contains 3,220,912 triples.
3The IoT KGs can be found at: https://github.com/RoderickvanderWeerdt/SAREFized-OPSD-household-graph
Semantically Enriched data After the semantic enrichment described in Section 3.1 was
performed on the OPSD dataset the KGs grew:
res1dev1: This graph contains 122,007 triples.
res1devA: This graph contains 976,005 triples.
resAdevA: This graph contains 4,391,992 triples.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Results</title>
      <p>In this section, the results of the experiments are reported. The hyperparameter selection uses
the subset with the 2000 hottest and coldest time points of the OPSD dataset, while the full
OPSD dataset is used in Section 4.2.</p>
      <sec id="sec-4-1">
        <title>4.1. Hyperparameter Selection</title>
        <p>The intention of the hyperparameter selection experiment was to find a combination of short
training time and ideally accuracies that were representable for the quality of the embeddings
learned from each graph, not to optimize for the highest accuracy possible.</p>
        <p>Table 3 displays accuracies and training times achieved with the resAdevA-2000 KGs, for
multiple hyperparameter settings. Each combination was trained for 40 epochs.</p>
        <p>After removing the options that were ended prematurely due to an expected training time of
at least 50 hours, marked here with a ‘x’, the grid was reduced into two directions to explore,
increasing either the number of walks or the walk length. By increasing the walk length the
diference in accuracy between using the basic or enriched graph grows, but the training time
also grows extensively. Alternatively increasing the number of walks had a similar efect on the
accuracy, but the time to train only grew slightly between diferent settings.</p>
        <p>We attribute this diference in training time to the increase of entities that were needed to be
retrieved during training of the models with an increased walk length. As discussed earlier in
Section 2.1, IoT KGs require only a few steps through the graph to reach all entities in the graph.
By increasing the walk length more entities are included that are connected to many entities,
increasing the possible unique walks greatly. To handle this more compute time is required.</p>
        <p>Based on our requirements of short training time and distinct accuracies the best option is a
walklength of 2 and 25 walks per entity, since the time increase is limited, and the accuracy
increase allows for more range between the embedding quality of basic and enriched IoT KGs.</p>
        <p>In order to determine the efects of the number of epochs the embeddings model is trained,
we trained six embedding models, one for each version of the basic and the enriched IoT KG.
The training and test accuracy were calculated after each epoch, for a total of 40 epochs. The
results are visualized in Figure 4. Training accuracies are portrayed with dashed lines, test
accuracies with solid lines.</p>
        <p>All training accuracies reach 100% after 10 epochs, except res1dev1-basic, which takes 20
epochs. Two out of three test accuracies for basic IoT KGs never increase above ±50% and are
therefore not taken into account. The enriched IoT KGs test accuracies remain consistent after
20 epochs.</p>
        <p>Based on these findings we trained the model for the next experiment for 20 epochs, this is
enough to reach the plateau of resAdevA enriched and res1devA enriched, but will also avoid
overfitting by not training too long.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Basic vs Enriched</title>
        <p>The results of the experiment have been visualized in Figure 5. For both datasets and for any
amount of devices being used, the classifier trained on the enriched graph always outperforms
the classifier trained on the basic graph. The smallest diference occurred with res1dev1 of the
OPSD data, and even then the accuracy was still significantly diferent ( p=0.00766).</p>
        <p>Accuracies of classifiers trained on basic IoT KGs were, with the exception of res1dev1, always
close to 50%. This indicates that these embeddings did not contain any information that the
classifier was able to learn from since only two possible classes exist and therefore always
picking the same class yields an accuracy of 50%. The exception being the classifier trained
on the res1dev1 graph. A possible explanation is that because this is a singular device, all
measurements values that were available as literals were enough for the embedding model to
learn a signal because that one device by itself happens to be a very good indicator for what
was being classified, the energy consumption of a heatpump to predict the outside temperature.</p>
        <p>Accuracies of classifiers trained on enriched IoT KGs were highest when learning from
res1dev1. As with the classifiers trained on basic IoT KGs, this could be explained by the fact
that this device is a good indicator for the classes. When more devices from the same residence
were added (res1devA) the accuracy of classifiers reduced, which might be explained by all the
additional devices, and therefore measurements, that were added, are not providing more, or
the right, information for the embeddings, causing the classifiers accuracy to decrease. For
example, a dishwasher would not be a good predictor of the outside temperature.</p>
        <p>Classifiers trained with embeddings from resAdevA had a significantly higher accuracy
(p=0.00099) than classifiers trained with embeddings from res1devA. The diference in relation
to res1devA and res1dev1 being that not only other devices were added, but other devices
from diferent homes were added, which include new devices that are good indicators for the
classification labels.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <p>During this research, some unexpected observations were made, which are presented in this
section. They serve as a way to explain our process, but also to suggest some possibilities for
future research.</p>
      <sec id="sec-5-1">
        <title>5.1. Data Validity</title>
        <p>For now, only energy consumption measurements were used, primarily because this was the
only public data we could acquire at the time. More heterogeneous measurements could have a
diferent efect of the embedding methods. Additional measurements could for example include
CO2 levels or room occupancy.</p>
        <p>In Section 2.1 we explained why we expect our results to generalize to IoT KGs created with
diferent ontologies, based on the similarities in their design. Additional research could explore
the diferences, to determine if semantic enrichment has a bigger or smaller efect.</p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Enrichment Choices</title>
        <p>The rounded values were now always rounded to one decimal, using more decimals would result
in more rounded value entities, each having fewer connections with measurements, since fewer
measurement values would be rounded to the same rounded value. But rounding to too many
decimals runs the risk of becoming too specific, with a “rounded” value for every measurement
value. How much rounding is applied could be an interesting parameter for future research.</p>
        <p>Even though all the measurements were about energy consumption, they were made by many
diferent devices. But the rounded values (and literal values) made no distinction between, for
example, a measurement of 0.6 of a freezer, or a measurement of 0.6 of a dryer. Making separate
entities out of these, such as 0 . 6 _ f r e e z e r and 0 . 6 _ d r y e r would allow the embedding method to
learn the diference.</p>
      </sec>
      <sec id="sec-5-3">
        <title>5.3. Evaluation Task</title>
        <p>For now, we used one classifier without any optimization. For the purposes of this experiment
that suficed to compare the accuracies of the classifiers trained on diferent IoT KGs, but other
classifiers could be used to examine if they are diferently afected with diferent IoT KGs.</p>
        <p>The classifiers are overfitting on the training set, as can be observed in Figure 4. This could
be an indication that we need more data, or that the embeddings are creating too specific
representations for the entities. RDF2vec not only embeds similar entities close together, but
it also tries to embed dissimilar entities further away, which could cause all the entities to
be spread out evenly, leaving no generalization to learn for the classification model. Future
research could reimplement this experiment with diferent embedding methods, such as TransE
[14] or GCN [15], which could make the diference in accuracies achieved in the experiment
more clearly distinct.</p>
        <p>In our experiments, we predicted the outside temperature based on a house, but this outside
temperature is the same for all the houses in each dataset because we only have one outside
temperature on city level. Therefore the result that including more houses leads to a higher
accuracy can also mean a more representative house was added, that better represents what is
being classified. Future research should explore the benefits of sharing information between
diferent homes to improve embeddings, but also explore how this afects privacy concerns.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>In this research, we set out to answer the question: What is the efect of semantically enriching a
KG on the quality of entity embeddings learned from it. When we consider the accuracy of the
classifier as an indicator of the quality of the entity embeddings, the results of our experiment
make it clear that semantic enrichment had a positive efect on the entity embedding quality.
The semantically enriched IoT KGs outperformed their corresponding basic IoT KGs in every
instance, regardless of graph size.</p>
      <p>Because the information added by the semantic enrichment is implicitly already available
in the KG, changing the ontology design to add the enrichments would not provide any new
information to the ontology. Instead, we see the semantic enrichment step as an additional part
of preprocessing the graph, to enhance the quality of the embeddings.</p>
      <p>Acknowledgements. This work is part of the InterConnect project (interconnectproject.eu/)
which has received funding from the European Union’s Horizon 2020 research and innovation
program under grant agreement No 857237.
[11] A. Paszke, S. Gross, F. Massa, A. Lerer, J. Bradbury, G. Chanan, T. Killeen, Z. Lin,
N. Gimelshein, L. Antiga, A. Desmaison, A. Kopf, E. Yang, Z. DeVito, M. Raison, A. Tejani,
S. Chilamkurthy, B. Steiner, L. Fang, J. Bai, S. Chintala, Pytorch: An imperative style,
high-performance deep learning library, in: Advances in Neural Information Processing
Systems 32, Curran Associates, Inc., 2019, pp. 8024–8035. URL: http://papers.neurips.cc/
paper/9015-pytorch-an-imperative-style-high-performance-deep-learning-library.pdf.
[12] R. van der Weerdt, V. de Boer, L. Daniele, B. Nouwt, R. Siebes, Making heterogeneous smart
home data interoperable with the SAREF ontology, International Journal of Metadata,
Semantics and Ontologies 15 (2021) 280–293.
[13] Open Power System Data, Data Package Household Data, Version 2020-04-15 https://data.
open-power-system-data.org/household_data/2020-04-15/. (Primary data from various
sources, for a complete list see URL)., 2020.
[14] A. Bordes, N. Usunier, A. Garcia-Duran, J. Weston, O. Yakhnenko, Translating embeddings
for modeling multi-relational data, Advances in neural information processing systems 26
(2013).
[15] T. N. Kipf, M. Welling, Semi-supervised classification with graph convolutional networks,
arXiv preprint arXiv:1609.02907 (2016).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>C.</given-names>
            <surname>Akasiadis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Pitsilis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Spyropoulos</surname>
          </string-name>
          ,
          <article-title>A multi-protocol iot platform based on opensource frameworks</article-title>
          ,
          <source>Sensors</source>
          <volume>19</volume>
          (
          <year>2019</year>
          )
          <fpage>4217</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>L.</given-names>
            <surname>Daniele</surname>
          </string-name>
          , F. den
          <string-name>
            <surname>Hartog</surname>
          </string-name>
          , J. Roes,
          <article-title>Created in Close Interaction with the Industry: the Smart Appliances REFerence (SAREF) Ontology</article-title>
          , in: International Workshop Formal Ontologies Meet Industries, Springer,
          <year>2015</year>
          , pp.
          <fpage>100</fpage>
          -
          <lpage>112</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>J.</given-names>
            <surname>Portisch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Paulheim</surname>
          </string-name>
          ,
          <source>The RDF2vec Family of Knowledge Graph Embedding Methods</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <issue>W3C</issue>
          ,
          <article-title>Web of Things (WoT) Thing Description (</article-title>
          <year>2020</year>
          ). URL: https://www.w3.org/TR/2020/ REC-wot
          <string-name>
            <surname>-</surname>
          </string-name>
          thing-description-
          <volume>20200409</volume>
          /.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Compton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Barnaghi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Bermudez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>GarcíA-Castro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Corcho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Cox</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Graybeal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Hauswirth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Henson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Herzog</surname>
          </string-name>
          , et al.,
          <article-title>The SSN Ontology of the W3C Semantic Sensor Network Incubator Group</article-title>
          ,
          <source>Journal of Web Semantics</source>
          <volume>17</volume>
          (
          <year>2012</year>
          )
          <fpage>25</fpage>
          -
          <lpage>32</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>J.</given-names>
            <surname>Moreira</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Daniele</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. F.</given-names>
            <surname>Pires</surname>
          </string-name>
          , M. van
          <string-name>
            <surname>Sinderen</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Wasielewska</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Szmeja</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          <string-name>
            <surname>Pawlowski</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Ganzha</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Paprzycki</surname>
          </string-name>
          ,
          <article-title>Towards iot platforms' integration semantic translations between w3c ssn and etsi saref</article-title>
          ., in: SEMANTICS workshops,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>T.</given-names>
            <surname>Mikolov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Chen</surname>
          </string-name>
          , G. Corrado,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dean</surname>
          </string-name>
          ,
          <article-title>Eficient estimation of word representations in vector space</article-title>
          ,
          <year>2013</year>
          . URL: https://arxiv.org/abs/1301.3781.
          <source>doi:1 0 . 4 8</source>
          <volume>5 5</volume>
          <fpage>0</fpage>
          <string-name>
            <surname>/ A R X I</surname>
          </string-name>
          <article-title>V . 1 3 0 1 . 3 7 8 1</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>P.</given-names>
            <surname>Ristoski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Rosati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Di</surname>
          </string-name>
          <string-name>
            <surname>Noia</surname>
          </string-name>
          , R. De Leone, H. Paulheim,
          <article-title>Rdf2vec: Rdf graph embeddings and their applications</article-title>
          ,
          <source>Semantic Web</source>
          <volume>10</volume>
          (
          <year>2019</year>
          )
          <fpage>721</fpage>
          -
          <lpage>752</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Iana</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Paulheim</surname>
          </string-name>
          ,
          <article-title>More is not always better: The negative impact of a-box materialization on rdf2vec knowledge graph embeddings</article-title>
          ,
          <source>in: CEUR Workshop Proceedings</source>
          , volume
          <volume>2699</volume>
          ,
          <string-name>
            <surname>RWTH</surname>
          </string-name>
          ,
          <year>2020</year>
          , pp.
          <source>Paper-5.</source>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>G.</given-names>
            <surname>Vandewiele</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Steenwinckel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Agozzino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ongenae</surname>
          </string-name>
          , pyrdf2vec:
          <article-title>A python implementation and extension of rdf2vec</article-title>
          ,
          <source>arXiv preprint arXiv:2205.02283</source>
          (
          <year>2022</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>