Serveur d'exploration Cyberinfrastructure

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.

Search Techniques for the Web of Things: A Taxonomy and Survey

Identifieur interne : 000131 ( Pmc/Corpus ); précédent : 000130; suivant : 000132

Search Techniques for the Web of Things: A Taxonomy and Survey

Auteurs : Yuchao Zhou ; Suparna De ; Wei Wang ; Klaus Moessner

Source :

RBID : PMC:4883291

Abstract

The Web of Things aims to make physical world objects and their data accessible through standard Web technologies to enable intelligent applications and sophisticated data analytics. Due to the amount and heterogeneity of the data, it is challenging to perform data analysis directly; especially when the data is captured from a large number of distributed sources. However, the size and scope of the data can be reduced and narrowed down with search techniques, so that only the most relevant and useful data items are selected according to the application requirements. Search is fundamental to the Web of Things while challenging by nature in this context, e.g., mobility of the objects, opportunistic presence and sensing, continuous data streams with changing spatial and temporal properties, efficient indexing for historical and real time data. The research community has developed numerous techniques and methods to tackle these problems as reported by a large body of literature in the last few years. A comprehensive investigation of the current and past studies is necessary to gain a clear view of the research landscape and to identify promising future directions. This survey reviews the state-of-the-art search methods for the Web of Things, which are classified according to three different viewpoints: basic principles, data/knowledge representation, and contents being searched. Experiences and lessons learned from the existing work and some EU research projects related to Web of Things are discussed, and an outlook to the future research is presented.


Url:
DOI: 10.3390/s16050600
PubMed: 27128918
PubMed Central: 4883291

Links to Exploration step

PMC:4883291

Le document en format XML

<record>
<TEI>
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">Search Techniques for the Web of Things: A Taxonomy and Survey</title>
<author>
<name sortKey="Zhou, Yuchao" sort="Zhou, Yuchao" uniqKey="Zhou Y" first="Yuchao" last="Zhou">Yuchao Zhou</name>
<affiliation>
<nlm:aff id="af1-sensors-16-00600">Institute for Communication Systems (ICS), University of Surrey, Guildford GU2 7XH, UK;
<email>s.de@surrey.ac.uk</email>
(S.D.);
<email>k.moessner@surrey.ac.uk</email>
(K.M.)</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="De, Suparna" sort="De, Suparna" uniqKey="De S" first="Suparna" last="De">Suparna De</name>
<affiliation>
<nlm:aff id="af1-sensors-16-00600">Institute for Communication Systems (ICS), University of Surrey, Guildford GU2 7XH, UK;
<email>s.de@surrey.ac.uk</email>
(S.D.);
<email>k.moessner@surrey.ac.uk</email>
(K.M.)</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Wang, Wei" sort="Wang, Wei" uniqKey="Wang W" first="Wei" last="Wang">Wei Wang</name>
<affiliation>
<nlm:aff id="af2-sensors-16-00600">Department of Computer Science and Software Engineering, Xi’an Jiaotong-Liverpool University, Ren’ai Road Dushu Lake Higher Education Town SIP, Suzhou 215123, China;
<email>Wei.Wang03@xjtlu.edu.cn</email>
</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Moessner, Klaus" sort="Moessner, Klaus" uniqKey="Moessner K" first="Klaus" last="Moessner">Klaus Moessner</name>
<affiliation>
<nlm:aff id="af1-sensors-16-00600">Institute for Communication Systems (ICS), University of Surrey, Guildford GU2 7XH, UK;
<email>s.de@surrey.ac.uk</email>
(S.D.);
<email>k.moessner@surrey.ac.uk</email>
(K.M.)</nlm:aff>
</affiliation>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">PMC</idno>
<idno type="pmid">27128918</idno>
<idno type="pmc">4883291</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4883291</idno>
<idno type="RBID">PMC:4883291</idno>
<idno type="doi">10.3390/s16050600</idno>
<date when="2016">2016</date>
<idno type="wicri:Area/Pmc/Corpus">000131</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title xml:lang="en" level="a" type="main">Search Techniques for the Web of Things: A Taxonomy and Survey</title>
<author>
<name sortKey="Zhou, Yuchao" sort="Zhou, Yuchao" uniqKey="Zhou Y" first="Yuchao" last="Zhou">Yuchao Zhou</name>
<affiliation>
<nlm:aff id="af1-sensors-16-00600">Institute for Communication Systems (ICS), University of Surrey, Guildford GU2 7XH, UK;
<email>s.de@surrey.ac.uk</email>
(S.D.);
<email>k.moessner@surrey.ac.uk</email>
(K.M.)</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="De, Suparna" sort="De, Suparna" uniqKey="De S" first="Suparna" last="De">Suparna De</name>
<affiliation>
<nlm:aff id="af1-sensors-16-00600">Institute for Communication Systems (ICS), University of Surrey, Guildford GU2 7XH, UK;
<email>s.de@surrey.ac.uk</email>
(S.D.);
<email>k.moessner@surrey.ac.uk</email>
(K.M.)</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Wang, Wei" sort="Wang, Wei" uniqKey="Wang W" first="Wei" last="Wang">Wei Wang</name>
<affiliation>
<nlm:aff id="af2-sensors-16-00600">Department of Computer Science and Software Engineering, Xi’an Jiaotong-Liverpool University, Ren’ai Road Dushu Lake Higher Education Town SIP, Suzhou 215123, China;
<email>Wei.Wang03@xjtlu.edu.cn</email>
</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Moessner, Klaus" sort="Moessner, Klaus" uniqKey="Moessner K" first="Klaus" last="Moessner">Klaus Moessner</name>
<affiliation>
<nlm:aff id="af1-sensors-16-00600">Institute for Communication Systems (ICS), University of Surrey, Guildford GU2 7XH, UK;
<email>s.de@surrey.ac.uk</email>
(S.D.);
<email>k.moessner@surrey.ac.uk</email>
(K.M.)</nlm:aff>
</affiliation>
</author>
</analytic>
<series>
<title level="j">Sensors (Basel, Switzerland)</title>
<idno type="eISSN">1424-8220</idno>
<imprint>
<date when="2016">2016</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<textClass></textClass>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">
<p>The Web of Things aims to make physical world objects and their data accessible through standard Web technologies to enable intelligent applications and sophisticated data analytics. Due to the amount and heterogeneity of the data, it is challenging to perform data analysis directly; especially when the data is captured from a large number of distributed sources. However, the size and scope of the data can be reduced and narrowed down with search techniques, so that only the most relevant and useful data items are selected according to the application requirements. Search is fundamental to the Web of Things while challenging by nature in this context, e.g., mobility of the objects, opportunistic presence and sensing, continuous data streams with changing spatial and temporal properties, efficient indexing for historical and real time data. The research community has developed numerous techniques and methods to tackle these problems as reported by a large body of literature in the last few years. A comprehensive investigation of the current and past studies is necessary to gain a clear view of the research landscape and to identify promising future directions. This survey reviews the state-of-the-art search methods for the Web of Things, which are classified according to three different viewpoints: basic principles, data/knowledge representation, and contents being searched. Experiences and lessons learned from the existing work and some EU research projects related to Web of Things are discussed, and an outlook to the future research is presented.</p>
</div>
</front>
<back>
<div1 type="bibliography">
<listBibl>
<biblStruct>
<analytic>
<author>
<name sortKey="Guinard, D" uniqKey="Guinard D">D. Guinard</name>
</author>
<author>
<name sortKey="Trifa, V" uniqKey="Trifa V">V. Trifa</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Zeng, D" uniqKey="Zeng D">D. Zeng</name>
</author>
<author>
<name sortKey="Guo, S" uniqKey="Guo S">S. Guo</name>
</author>
<author>
<name sortKey="Cheng, Z" uniqKey="Cheng Z">Z. Cheng</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Evans, D" uniqKey="Evans D">D. Evans</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="De, S" uniqKey="De S">S. De</name>
</author>
<author>
<name sortKey="Christophe, B" uniqKey="Christophe B">B. Christophe</name>
</author>
<author>
<name sortKey="Moessner, K" uniqKey="Moessner K">K. Moessner</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Sun, W" uniqKey="Sun W">W. Sun</name>
</author>
<author>
<name sortKey="Yang, Z" uniqKey="Yang Z">Z. Yang</name>
</author>
<author>
<name sortKey="Zhang, X" uniqKey="Zhang X">X. Zhang</name>
</author>
<author>
<name sortKey="Liu, Y" uniqKey="Liu Y">Y. Liu</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Pozza, R" uniqKey="Pozza R">R. Pozza</name>
</author>
<author>
<name sortKey="Nati, M" uniqKey="Nati M">M. Nati</name>
</author>
<author>
<name sortKey="Georgoulas, S" uniqKey="Georgoulas S">S. Georgoulas</name>
</author>
<author>
<name sortKey="Moessner, K" uniqKey="Moessner K">K. Moessner</name>
</author>
<author>
<name sortKey="Gluhak, A" uniqKey="Gluhak A">A. Gluhak</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Villaverde, B C" uniqKey="Villaverde B">B.C. Villaverde</name>
</author>
<author>
<name sortKey="De Paz Alberola, R" uniqKey="De Paz Alberola R">R. de Paz Alberola</name>
</author>
<author>
<name sortKey="Jara, A J" uniqKey="Jara A">A.J. Jara</name>
</author>
<author>
<name sortKey="Fedor, S" uniqKey="Fedor S">S. Fedor</name>
</author>
<author>
<name sortKey="Das, S K" uniqKey="Das S">S.K. Das</name>
</author>
<author>
<name sortKey="Pesch, D" uniqKey="Pesch D">D. Pesch</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Romer, K" uniqKey="Romer K">K. Romer</name>
</author>
<author>
<name sortKey="Ostermaier, B" uniqKey="Ostermaier B">B. Ostermaier</name>
</author>
<author>
<name sortKey="Mattern, F" uniqKey="Mattern F">F. Mattern</name>
</author>
<author>
<name sortKey="Fahrmair, M" uniqKey="Fahrmair M">M. Fahrmair</name>
</author>
<author>
<name sortKey="Kellerer, W" uniqKey="Kellerer W">W. Kellerer</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Broring, A" uniqKey="Broring A">A. Bröring</name>
</author>
<author>
<name sortKey="Echterhoff, J" uniqKey="Echterhoff J">J. Echterhoff</name>
</author>
<author>
<name sortKey="Jirka, S" uniqKey="Jirka S">S. Jirka</name>
</author>
<author>
<name sortKey="Simonis, I" uniqKey="Simonis I">I. Simonis</name>
</author>
<author>
<name sortKey="Everding, T" uniqKey="Everding T">T. Everding</name>
</author>
<author>
<name sortKey="Stasch, C" uniqKey="Stasch C">C. Stasch</name>
</author>
<author>
<name sortKey="Liang, S" uniqKey="Liang S">S. Liang</name>
</author>
<author>
<name sortKey="Lemmens, R" uniqKey="Lemmens R">R. Lemmens</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Zhang, D" uniqKey="Zhang D">D. Zhang</name>
</author>
<author>
<name sortKey="Yang, L T" uniqKey="Yang L">L.T. Yang</name>
</author>
<author>
<name sortKey="Huang, H" uniqKey="Huang H">H. Huang</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Guinard, D" uniqKey="Guinard D">D. Guinard</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Fielding, R T" uniqKey="Fielding R">R.T. Fielding</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Mockapetris, P" uniqKey="Mockapetris P">P. Mockapetris</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Bormann, C" uniqKey="Bormann C">C. Bormann</name>
</author>
<author>
<name sortKey="Castellani, A P" uniqKey="Castellani A">A.P. Castellani</name>
</author>
<author>
<name sortKey="Shelby, Z" uniqKey="Shelby Z">Z. Shelby</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Coria, J A G" uniqKey="Coria J">J.A.G. Coria</name>
</author>
<author>
<name sortKey="Castellanos Garz N, J A" uniqKey="Castellanos Garz N J">J.A. Castellanos-Garzón</name>
</author>
<author>
<name sortKey="Corchado, J M" uniqKey="Corchado J">J.M. Corchado</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Wu, C I" uniqKey="Wu C">C.-I. Wu</name>
</author>
<author>
<name sortKey="Kung, H Y" uniqKey="Kung H">H.-Y. Kung</name>
</author>
<author>
<name sortKey="Chen, C H" uniqKey="Chen C">C.-H. Chen</name>
</author>
<author>
<name sortKey="Kuo, L C" uniqKey="Kuo L">L.-C. Kuo</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Wang, W" uniqKey="Wang W">W. Wang</name>
</author>
<author>
<name sortKey="De, S" uniqKey="De S">S. De</name>
</author>
<author>
<name sortKey="Cassar, G" uniqKey="Cassar G">G. Cassar</name>
</author>
<author>
<name sortKey="Moessner, K" uniqKey="Moessner K">K. Moessner</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Wang, W" uniqKey="Wang W">W. Wang</name>
</author>
<author>
<name sortKey="Yao, F" uniqKey="Yao F">F. Yao</name>
</author>
<author>
<name sortKey="De, S" uniqKey="De S">S. De</name>
</author>
<author>
<name sortKey="Moessner, K" uniqKey="Moessner K">K. Moessner</name>
</author>
<author>
<name sortKey="Sun, Z" uniqKey="Sun Z">Z. Sun</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Aberer, K" uniqKey="Aberer K">K. Aberer</name>
</author>
<author>
<name sortKey="Hauswirth, M" uniqKey="Hauswirth M">M. Hauswirth</name>
</author>
<author>
<name sortKey="Salehi, A" uniqKey="Salehi A">A. Salehi</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Calbimonte, J P" uniqKey="Calbimonte J">J.-P. Calbimonte</name>
</author>
<author>
<name sortKey="Sarni, S" uniqKey="Sarni S">S. Sarni</name>
</author>
<author>
<name sortKey="Eberle, J" uniqKey="Eberle J">J. Eberle</name>
</author>
<author>
<name sortKey="Aberer, K" uniqKey="Aberer K">K. Aberer</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Le Phuoc, D" uniqKey="Le Phuoc D">D. Le-Phuoc</name>
</author>
<author>
<name sortKey="Nguyen Mau, H Q" uniqKey="Nguyen Mau H">H.Q. Nguyen-Mau</name>
</author>
<author>
<name sortKey="Parreira, J X" uniqKey="Parreira J">J.X. Parreira</name>
</author>
<author>
<name sortKey="Hauswirth, M" uniqKey="Hauswirth M">M. Hauswirth</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Soldatos, J" uniqKey="Soldatos J">J. Soldatos</name>
</author>
<author>
<name sortKey="Kefalakis, N" uniqKey="Kefalakis N">N. Kefalakis</name>
</author>
<author>
<name sortKey="Hauswirth, M" uniqKey="Hauswirth M">M. Hauswirth</name>
</author>
<author>
<name sortKey="Serrano, M" uniqKey="Serrano M">M. Serrano</name>
</author>
<author>
<name sortKey="Calbimonte, J P" uniqKey="Calbimonte J">J.-P. Calbimonte</name>
</author>
<author>
<name sortKey="Riahi, M" uniqKey="Riahi M">M. Riahi</name>
</author>
<author>
<name sortKey="Aberer, K" uniqKey="Aberer K">K. Aberer</name>
</author>
<author>
<name sortKey="Jayaraman, P P" uniqKey="Jayaraman P">P.P. Jayaraman</name>
</author>
<author>
<name sortKey="Zaslavsky, A" uniqKey="Zaslavsky A">A. Zaslavsky</name>
</author>
<author>
<name sortKey="Zarko, I P" uniqKey="Zarko I">I.P. Žarko</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Kansal, A" uniqKey="Kansal A">A. Kansal</name>
</author>
<author>
<name sortKey="Nath, S" uniqKey="Nath S">S. Nath</name>
</author>
<author>
<name sortKey="Jie, L" uniqKey="Jie L">L. Jie</name>
</author>
<author>
<name sortKey="Feng, Z" uniqKey="Feng Z">Z. Feng</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Ostermaier, B" uniqKey="Ostermaier B">B. Ostermaier</name>
</author>
<author>
<name sortKey="Romer, K" uniqKey="Romer K">K. Romer</name>
</author>
<author>
<name sortKey="Mattern, F" uniqKey="Mattern F">F. Mattern</name>
</author>
<author>
<name sortKey="Fahrmair, M" uniqKey="Fahrmair M">M. Fahrmair</name>
</author>
<author>
<name sortKey="Kellerer, W" uniqKey="Kellerer W">W. Kellerer</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Tan, C C" uniqKey="Tan C">C.C. Tan</name>
</author>
<author>
<name sortKey="Sheng, B" uniqKey="Sheng B">B. Sheng</name>
</author>
<author>
<name sortKey="Wang, H" uniqKey="Wang H">H. Wang</name>
</author>
<author>
<name sortKey="Li, Q" uniqKey="Li Q">Q. Li</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Wang, H" uniqKey="Wang H">H. Wang</name>
</author>
<author>
<name sortKey="Tan, C C" uniqKey="Tan C">C.C. Tan</name>
</author>
<author>
<name sortKey="Li, Q" uniqKey="Li Q">Q. Li</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Yang, X" uniqKey="Yang X">X. Yang</name>
</author>
<author>
<name sortKey="Song, W" uniqKey="Song W">W. Song</name>
</author>
<author>
<name sortKey="De, D" uniqKey="De D">D. De</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Jara, A J" uniqKey="Jara A">A.J. Jara</name>
</author>
<author>
<name sortKey="Martinez Julia, P" uniqKey="Martinez Julia P">P. Martinez-Julia</name>
</author>
<author>
<name sortKey="Skarmeta, A" uniqKey="Skarmeta A">A. Skarmeta</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Kamilaris, A" uniqKey="Kamilaris A">A. Kamilaris</name>
</author>
<author>
<name sortKey="Papakonstantinou, K" uniqKey="Papakonstantinou K">K. Papakonstantinou</name>
</author>
<author>
<name sortKey="Pitsillides, A" uniqKey="Pitsillides A">A. Pitsillides</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Jara, A J" uniqKey="Jara A">A.J. Jara</name>
</author>
<author>
<name sortKey="Lopez, P" uniqKey="Lopez P">P. Lopez</name>
</author>
<author>
<name sortKey="Fernandez, D" uniqKey="Fernandez D">D. Fernandez</name>
</author>
<author>
<name sortKey="Castillo, J F" uniqKey="Castillo J">J.F. Castillo</name>
</author>
<author>
<name sortKey="Zamora, M A" uniqKey="Zamora M">M.A. Zamora</name>
</author>
<author>
<name sortKey="Skarmeta, A F" uniqKey="Skarmeta A">A.F. Skarmeta</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Ding, Z" uniqKey="Ding Z">Z. Ding</name>
</author>
<author>
<name sortKey="Chen, Z" uniqKey="Chen Z">Z. Chen</name>
</author>
<author>
<name sortKey="Yang, Q" uniqKey="Yang Q">Q. Yang</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Jirka, S" uniqKey="Jirka S">S. Jirka</name>
</author>
<author>
<name sortKey="Broring, A" uniqKey="Broring A">A. Bröring</name>
</author>
<author>
<name sortKey="Stasch, C" uniqKey="Stasch C">C. Stasch</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Nath, S" uniqKey="Nath S">S. Nath</name>
</author>
<author>
<name sortKey="Liu, J" uniqKey="Liu J">J. Liu</name>
</author>
<author>
<name sortKey="Zhao, F" uniqKey="Zhao F">F. Zhao</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Liang, S H" uniqKey="Liang S">S.H. Liang</name>
</author>
<author>
<name sortKey="Huang, C Y" uniqKey="Huang C">C.-Y. Huang</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Bauer, M" uniqKey="Bauer M">M. Bauer</name>
</author>
<author>
<name sortKey="Longo, S" uniqKey="Longo S">S. Longo</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Zhou, Y" uniqKey="Zhou Y">Y. Zhou</name>
</author>
<author>
<name sortKey="De, S" uniqKey="De S">S. De</name>
</author>
<author>
<name sortKey="Wang, W" uniqKey="Wang W">W. Wang</name>
</author>
<author>
<name sortKey="Moessner, K" uniqKey="Moessner K">K. Moessner</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="De, S" uniqKey="De S">S. De</name>
</author>
<author>
<name sortKey="Elsaleh, T" uniqKey="Elsaleh T">T. Elsaleh</name>
</author>
<author>
<name sortKey="Barnaghi, P" uniqKey="Barnaghi P">P. Barnaghi</name>
</author>
<author>
<name sortKey="Meissner, S" uniqKey="Meissner S">S. Meissner</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Barnaghi, P" uniqKey="Barnaghi P">P. Barnaghi</name>
</author>
<author>
<name sortKey="Wang, W" uniqKey="Wang W">W. Wang</name>
</author>
<author>
<name sortKey="Dong, L" uniqKey="Dong L">L. Dong</name>
</author>
<author>
<name sortKey="Wang, C" uniqKey="Wang C">C. Wang</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Fredj, S B" uniqKey="Fredj S">S.B. Fredj</name>
</author>
<author>
<name sortKey="Boussard, M" uniqKey="Boussard M">M. Boussard</name>
</author>
<author>
<name sortKey="Kofman, D" uniqKey="Kofman D">D. Kofman</name>
</author>
<author>
<name sortKey="Noirie, L" uniqKey="Noirie L">L. Noirie</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Mayer, S" uniqKey="Mayer S">S. Mayer</name>
</author>
<author>
<name sortKey="Guinard, D" uniqKey="Guinard D">D. Guinard</name>
</author>
<author>
<name sortKey="Trifa, V" uniqKey="Trifa V">V. Trifa</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Timpner, J" uniqKey="Timpner J">J. Timpner</name>
</author>
<author>
<name sortKey="Schurmann, D" uniqKey="Schurmann D">D. Schurmann</name>
</author>
<author>
<name sortKey="Wolf, L" uniqKey="Wolf L">L. Wolf</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Timpner, J" uniqKey="Timpner J">J. Timpner</name>
</author>
<author>
<name sortKey="Wolf, L" uniqKey="Wolf L">L. Wolf</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Ahull, J P" uniqKey="Ahull J">J.P. Ahulló</name>
</author>
<author>
<name sortKey="L Pez, P G" uniqKey="L Pez P">P.G. López</name>
</author>
<author>
<name sortKey="Artigas, M S" uniqKey="Artigas M">M.S. Artigas</name>
</author>
<author>
<name sortKey="Skarmeta, A F G" uniqKey="Skarmeta A">A.F.G. Skarmeta</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Christophe, B" uniqKey="Christophe B">B. Christophe</name>
</author>
<author>
<name sortKey="Verdot, V" uniqKey="Verdot V">V. Verdot</name>
</author>
<author>
<name sortKey="Toubiana, V" uniqKey="Toubiana V">V. Toubiana</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Du, C" uniqKey="Du C">C. Du</name>
</author>
<author>
<name sortKey="Zhou, Z" uniqKey="Zhou Z">Z. Zhou</name>
</author>
<author>
<name sortKey="Shu, L" uniqKey="Shu L">L. Shu</name>
</author>
<author>
<name sortKey="Jia, X" uniqKey="Jia X">X. Jia</name>
</author>
<author>
<name sortKey="Wang, Q" uniqKey="Wang Q">Q. Wang</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Ebrahimi, M" uniqKey="Ebrahimi M">M. Ebrahimi</name>
</author>
<author>
<name sortKey="Shafieibavani, E" uniqKey="Shafieibavani E">E. ShafieiBavani</name>
</author>
<author>
<name sortKey="Wong, R K" uniqKey="Wong R">R.K. Wong</name>
</author>
<author>
<name sortKey="Fong, S" uniqKey="Fong S">S. Fong</name>
</author>
<author>
<name sortKey="Fiaidhi, J" uniqKey="Fiaidhi J">J. Fiaidhi</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Patni, H" uniqKey="Patni H">H. Patni</name>
</author>
<author>
<name sortKey="Henson, C" uniqKey="Henson C">C. Henson</name>
</author>
<author>
<name sortKey="Sheth, A" uniqKey="Sheth A">A. Sheth</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Chun, S" uniqKey="Chun S">S. Chun</name>
</author>
<author>
<name sortKey="Seo, S" uniqKey="Seo S">S. Seo</name>
</author>
<author>
<name sortKey="Oh, B" uniqKey="Oh B">B. Oh</name>
</author>
<author>
<name sortKey="Lee, K H" uniqKey="Lee K">K.-H. Lee</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Henson, C A" uniqKey="Henson C">C.A. Henson</name>
</author>
<author>
<name sortKey="Pschorr, J K" uniqKey="Pschorr J">J.K. Pschorr</name>
</author>
<author>
<name sortKey="Sheth, A P" uniqKey="Sheth A">A.P. Sheth</name>
</author>
<author>
<name sortKey="Thirunarayan, K" uniqKey="Thirunarayan K">K. Thirunarayan</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Pschorr, J" uniqKey="Pschorr J">J. Pschorr</name>
</author>
<author>
<name sortKey="Henson, C A" uniqKey="Henson C">C.A. Henson</name>
</author>
<author>
<name sortKey="Patni, H K" uniqKey="Patni H">H.K. Patni</name>
</author>
<author>
<name sortKey="Sheth, A P" uniqKey="Sheth A">A.P. Sheth</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Battle, R" uniqKey="Battle R">R. Battle</name>
</author>
<author>
<name sortKey="Kolas, D" uniqKey="Kolas D">D. Kolas</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Quilitz, B" uniqKey="Quilitz B">B. Quilitz</name>
</author>
<author>
<name sortKey="Leser, U" uniqKey="Leser U">U. Leser</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Acosta, M" uniqKey="Acosta M">M. Acosta</name>
</author>
<author>
<name sortKey="Vidal, M E" uniqKey="Vidal M">M.-E. Vidal</name>
</author>
<author>
<name sortKey="Lampo, T" uniqKey="Lampo T">T. Lampo</name>
</author>
<author>
<name sortKey="Castillo, J" uniqKey="Castillo J">J. Castillo</name>
</author>
<author>
<name sortKey="Ruckhaus, E" uniqKey="Ruckhaus E">E. Ruckhaus</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Gorlitz, O" uniqKey="Gorlitz O">O. Görlitz</name>
</author>
<author>
<name sortKey="Staab, S" uniqKey="Staab S">S. Staab</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Schwarte, A" uniqKey="Schwarte A">A. Schwarte</name>
</author>
<author>
<name sortKey="Haase, P" uniqKey="Haase P">P. Haase</name>
</author>
<author>
<name sortKey="Hose, K" uniqKey="Hose K">K. Hose</name>
</author>
<author>
<name sortKey="Schenkel, R" uniqKey="Schenkel R">R. Schenkel</name>
</author>
<author>
<name sortKey="Schmidt, M" uniqKey="Schmidt M">M. Schmidt</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Zhou, Y" uniqKey="Zhou Y">Y. Zhou</name>
</author>
<author>
<name sortKey="De, S" uniqKey="De S">S. De</name>
</author>
<author>
<name sortKey="Moessner, K" uniqKey="Moessner K">K. Moessner</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Buil Aranda, C" uniqKey="Buil Aranda C">C. Buil-Aranda</name>
</author>
<author>
<name sortKey="Arenas, M" uniqKey="Arenas M">M. Arenas</name>
</author>
<author>
<name sortKey="Corcho, O" uniqKey="Corcho O">O. Corcho</name>
</author>
<author>
<name sortKey="Polleres, A" uniqKey="Polleres A">A. Polleres</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Calbimonte, J P" uniqKey="Calbimonte J">J.-P. Calbimonte</name>
</author>
<author>
<name sortKey="Jeung, H Y" uniqKey="Jeung H">H.Y. Jeung</name>
</author>
<author>
<name sortKey="Corcho, O" uniqKey="Corcho O">O. Corcho</name>
</author>
<author>
<name sortKey="Aberer, K" uniqKey="Aberer K">K. Aberer</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Barbieri, D F" uniqKey="Barbieri D">D.F. Barbieri</name>
</author>
<author>
<name sortKey="Braga, D" uniqKey="Braga D">D. Braga</name>
</author>
<author>
<name sortKey="Ceri, S" uniqKey="Ceri S">S. Ceri</name>
</author>
<author>
<name sortKey="Valle, E D" uniqKey="Valle E">E.D. Valle</name>
</author>
<author>
<name sortKey="Grossniklaus, M" uniqKey="Grossniklaus M">M. Grossniklaus</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Anicic, D" uniqKey="Anicic D">D. Anicic</name>
</author>
<author>
<name sortKey="Fodor, P" uniqKey="Fodor P">P. Fodor</name>
</author>
<author>
<name sortKey="Rudolph, S" uniqKey="Rudolph S">S. Rudolph</name>
</author>
<author>
<name sortKey="Stojanovic, N" uniqKey="Stojanovic N">N. Stojanovic</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Le Phuoc, D" uniqKey="Le Phuoc D">D. Le-Phuoc</name>
</author>
<author>
<name sortKey="Dao Tran, M" uniqKey="Dao Tran M">M. Dao-Tran</name>
</author>
<author>
<name sortKey="Parreira, J X" uniqKey="Parreira J">J.X. Parreira</name>
</author>
<author>
<name sortKey="Hauswirth, M" uniqKey="Hauswirth M">M. Hauswirth</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Shin, J" uniqKey="Shin J">J. Shin</name>
</author>
<author>
<name sortKey="Eom, S" uniqKey="Eom S">S. Eom</name>
</author>
<author>
<name sortKey="Lee, K H" uniqKey="Lee K">K.-H. Lee</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Perera, C" uniqKey="Perera C">C. Perera</name>
</author>
<author>
<name sortKey="Zaslavsky, A" uniqKey="Zaslavsky A">A. Zaslavsky</name>
</author>
<author>
<name sortKey="Liu, C H" uniqKey="Liu C">C.H. Liu</name>
</author>
<author>
<name sortKey="Compton, M" uniqKey="Compton M">M. Compton</name>
</author>
<author>
<name sortKey="Christen, P" uniqKey="Christen P">P. Christen</name>
</author>
<author>
<name sortKey="Georgakopoulos, D" uniqKey="Georgakopoulos D">D. Georgakopoulos</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Shah, M" uniqKey="Shah M">M. Shah</name>
</author>
<author>
<name sortKey="Sardana, A" uniqKey="Sardana A">A. Sardana</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Pfisterer, D" uniqKey="Pfisterer D">D. Pfisterer</name>
</author>
<author>
<name sortKey="Romer, K" uniqKey="Romer K">K. Romer</name>
</author>
<author>
<name sortKey="Bimschas, D" uniqKey="Bimschas D">D. Bimschas</name>
</author>
<author>
<name sortKey="Kleine, O" uniqKey="Kleine O">O. Kleine</name>
</author>
<author>
<name sortKey="Mietz, R" uniqKey="Mietz R">R. Mietz</name>
</author>
<author>
<name sortKey="Truong, C" uniqKey="Truong C">C. Truong</name>
</author>
<author>
<name sortKey="Hasemann, H" uniqKey="Hasemann H">H. Hasemann</name>
</author>
<author>
<name sortKey="Kroller, A" uniqKey="Kroller A">A. Kroller</name>
</author>
<author>
<name sortKey="Pagel, M" uniqKey="Pagel M">M. Pagel</name>
</author>
<author>
<name sortKey="Hauswirth, M" uniqKey="Hauswirth M">M. Hauswirth</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Truong, C" uniqKey="Truong C">C. Truong</name>
</author>
<author>
<name sortKey="Romer, K" uniqKey="Romer K">K. Romer</name>
</author>
<author>
<name sortKey="Chen, K" uniqKey="Chen K">K. Chen</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Elahi, B M" uniqKey="Elahi B">B.M. Elahi</name>
</author>
<author>
<name sortKey="Romer, K" uniqKey="Romer K">K. Romer</name>
</author>
<author>
<name sortKey="Ostermaier, B" uniqKey="Ostermaier B">B. Ostermaier</name>
</author>
<author>
<name sortKey="Fahrmair, M" uniqKey="Fahrmair M">M. Fahrmair</name>
</author>
<author>
<name sortKey="Kellerer, W" uniqKey="Kellerer W">W. Kellerer</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Michel, J" uniqKey="Michel J">J. Michel</name>
</author>
<author>
<name sortKey="Julien, C" uniqKey="Julien C">C. Julien</name>
</author>
<author>
<name sortKey="Payton, J" uniqKey="Payton J">J. Payton</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Qian, X" uniqKey="Qian X">X. Qian</name>
</author>
<author>
<name sortKey="Che, X" uniqKey="Che X">X. Che</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Mietz, R" uniqKey="Mietz R">R. Mietz</name>
</author>
<author>
<name sortKey="Romer, K" uniqKey="Romer K">K. Romer</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Mayer, S" uniqKey="Mayer S">S. Mayer</name>
</author>
<author>
<name sortKey="Guinard, D" uniqKey="Guinard D">D. Guinard</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Comer, D" uniqKey="Comer D">D. Comer</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Guttman, A" uniqKey="Guttman A">A. Guttman</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Navas, J C" uniqKey="Navas J">J.C. Navas</name>
</author>
<author>
<name sortKey="Imielinski, T" uniqKey="Imielinski T">T. Imielinski</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Taylor, K" uniqKey="Taylor K">K. Taylor</name>
</author>
<author>
<name sortKey="Parsons, E" uniqKey="Parsons E">E. Parsons</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Jaiswal, D" uniqKey="Jaiswal D">D. Jaiswal</name>
</author>
<author>
<name sortKey="Dey, S" uniqKey="Dey S">S. Dey</name>
</author>
<author>
<name sortKey="Dasgupta, R" uniqKey="Dasgupta R">R. Dasgupta</name>
</author>
<author>
<name sortKey="Mukherjee, A" uniqKey="Mukherjee A">A. Mukherjee</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Oguz, D" uniqKey="Oguz D">D. Oguz</name>
</author>
<author>
<name sortKey="Ergenc, B" uniqKey="Ergenc B">B. Ergenc</name>
</author>
<author>
<name sortKey="Yin, S" uniqKey="Yin S">S. Yin</name>
</author>
<author>
<name sortKey="Dikenelli, O" uniqKey="Dikenelli O">O. Dikenelli</name>
</author>
<author>
<name sortKey="Hameurlain, A" uniqKey="Hameurlain A">A. Hameurlain</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Compton, M" uniqKey="Compton M">M. Compton</name>
</author>
<author>
<name sortKey="Barnaghi, P" uniqKey="Barnaghi P">P. Barnaghi</name>
</author>
<author>
<name sortKey="Bermudez, L" uniqKey="Bermudez L">L. Bermudez</name>
</author>
<author>
<name sortKey="Garcia Castro, R" uniqKey="Garcia Castro R">R. GarcíA-Castro</name>
</author>
<author>
<name sortKey="Corcho, O" uniqKey="Corcho O">O. Corcho</name>
</author>
<author>
<name sortKey="Cox, S" uniqKey="Cox S">S. Cox</name>
</author>
<author>
<name sortKey="Graybeal, J" uniqKey="Graybeal J">J. Graybeal</name>
</author>
<author>
<name sortKey="Hauswirth, M" uniqKey="Hauswirth M">M. Hauswirth</name>
</author>
<author>
<name sortKey="Henson, C" uniqKey="Henson C">C. Henson</name>
</author>
<author>
<name sortKey="Herzog, A" uniqKey="Herzog A">A. Herzog</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Malhotra, K" uniqKey="Malhotra K">K. Malhotra</name>
</author>
<author>
<name sortKey="Gardner, S" uniqKey="Gardner S">S. Gardner</name>
</author>
<author>
<name sortKey="Patz, R" uniqKey="Patz R">R. Patz</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Pelekis, N" uniqKey="Pelekis N">N. Pelekis</name>
</author>
<author>
<name sortKey="Frentzos, E" uniqKey="Frentzos E">E. Frentzos</name>
</author>
<author>
<name sortKey="Giatrakos, N" uniqKey="Giatrakos N">N. Giatrakos</name>
</author>
<author>
<name sortKey="Theodoridis, Y" uniqKey="Theodoridis Y">Y. Theodoridis</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Frentzos, E" uniqKey="Frentzos E">E. Frentzos</name>
</author>
<author>
<name sortKey="Gratsias, K" uniqKey="Gratsias K">K. Gratsias</name>
</author>
<author>
<name sortKey="Theodoridis, Y" uniqKey="Theodoridis Y">Y. Theodoridis</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Schmidt, M" uniqKey="Schmidt M">M. Schmidt</name>
</author>
<author>
<name sortKey="Gorlitz, O" uniqKey="Gorlitz O">O. Görlitz</name>
</author>
<author>
<name sortKey="Haase, P" uniqKey="Haase P">P. Haase</name>
</author>
<author>
<name sortKey="Ladwig, G" uniqKey="Ladwig G">G. Ladwig</name>
</author>
<author>
<name sortKey="Schwarte, A" uniqKey="Schwarte A">A. Schwarte</name>
</author>
<author>
<name sortKey="Tran, T" uniqKey="Tran T">T. Tran</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Bassi, A" uniqKey="Bassi A">A. Bassi</name>
</author>
<author>
<name sortKey="Bauer, M" uniqKey="Bauer M">M. Bauer</name>
</author>
<author>
<name sortKey="Fiedler, M" uniqKey="Fiedler M">M. Fiedler</name>
</author>
<author>
<name sortKey="Kramp, T" uniqKey="Kramp T">T. Kramp</name>
</author>
<author>
<name sortKey="Kranenburg, R" uniqKey="Kranenburg R">R. Kranenburg</name>
</author>
<author>
<name sortKey="Lange, S" uniqKey="Lange S">S. Lange</name>
</author>
<author>
<name sortKey="Meissner, S" uniqKey="Meissner S">S. Meissner</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Meyer, S" uniqKey="Meyer S">S. Meyer</name>
</author>
<author>
<name sortKey="Ruppen, A" uniqKey="Ruppen A">A. Ruppen</name>
</author>
<author>
<name sortKey="Magerkurth, C" uniqKey="Magerkurth C">C. Magerkurth</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Christophe, B" uniqKey="Christophe B">B. Christophe</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="De, S" uniqKey="De S">S. De</name>
</author>
<author>
<name sortKey="Cassar, G" uniqKey="Cassar G">G. Cassar</name>
</author>
<author>
<name sortKey="Christophe, B" uniqKey="Christophe B">B. Christophe</name>
</author>
<author>
<name sortKey="Fredj, S B" uniqKey="Fredj S">S.B. Fredj</name>
</author>
<author>
<name sortKey="Bauer, M" uniqKey="Bauer M">M. Bauer</name>
</author>
<author>
<name sortKey="Santos, N" uniqKey="Santos N">N. Santos</name>
</author>
<author>
<name sortKey="Jacobs, T" uniqKey="Jacobs T">T. Jacobs</name>
</author>
<author>
<name sortKey="Zeybek, E" uniqKey="Zeybek E">E. Zeybek</name>
</author>
<author>
<name sortKey="De Las Heras, R" uniqKey="De Las Heras R">R. de las Heras</name>
</author>
<author>
<name sortKey="Martin, G" uniqKey="Martin G">G. Martín</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Jin, X" uniqKey="Jin X">X. Jin</name>
</author>
<author>
<name sortKey="Chun, S" uniqKey="Chun S">S. Chun</name>
</author>
<author>
<name sortKey="Jung, J" uniqKey="Jung J">J. Jung</name>
</author>
<author>
<name sortKey="Lee, K H" uniqKey="Lee K">K.-H. Lee</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Tonjes, R" uniqKey="Tonjes R">R. Tönjes</name>
</author>
<author>
<name sortKey="Reetz, E S" uniqKey="Reetz E">E.S. Reetz</name>
</author>
<author>
<name sortKey="Moessner, K" uniqKey="Moessner K">K. Moessner</name>
</author>
<author>
<name sortKey="Barnaghi, P M" uniqKey="Barnaghi P">P.M. Barnaghi</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="review-article">
<pmc-dir>properties open_access</pmc-dir>
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Sensors (Basel)</journal-id>
<journal-id journal-id-type="iso-abbrev">Sensors (Basel)</journal-id>
<journal-id journal-id-type="publisher-id">sensors</journal-id>
<journal-title-group>
<journal-title>Sensors (Basel, Switzerland)</journal-title>
</journal-title-group>
<issn pub-type="epub">1424-8220</issn>
<publisher>
<publisher-name>MDPI</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="pmid">27128918</article-id>
<article-id pub-id-type="pmc">4883291</article-id>
<article-id pub-id-type="doi">10.3390/s16050600</article-id>
<article-id pub-id-type="publisher-id">sensors-16-00600</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Review</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Search Techniques for the Web of Things: A Taxonomy and Survey</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Zhou</surname>
<given-names>Yuchao</given-names>
</name>
<xref ref-type="aff" rid="af1-sensors-16-00600">1</xref>
<xref rid="c1-sensors-16-00600" ref-type="corresp">*</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>De</surname>
<given-names>Suparna</given-names>
</name>
<xref ref-type="aff" rid="af1-sensors-16-00600">1</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Wang</surname>
<given-names>Wei</given-names>
</name>
<xref ref-type="aff" rid="af2-sensors-16-00600">2</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Moessner</surname>
<given-names>Klaus</given-names>
</name>
<xref ref-type="aff" rid="af1-sensors-16-00600">1</xref>
</contrib>
</contrib-group>
<contrib-group>
<contrib contrib-type="editor">
<name>
<surname>Sun</surname>
<given-names>Yunchuan</given-names>
</name>
<role>Academic Editor</role>
</contrib>
<contrib contrib-type="editor">
<name>
<surname>Jara</surname>
<given-names>Antonio</given-names>
</name>
<role>Academic Editor</role>
</contrib>
<contrib contrib-type="editor">
<name>
<surname>Wang</surname>
<given-names>Shengling</given-names>
</name>
<role>Academic Editor</role>
</contrib>
</contrib-group>
<aff id="af1-sensors-16-00600">
<label>1</label>
Institute for Communication Systems (ICS), University of Surrey, Guildford GU2 7XH, UK;
<email>s.de@surrey.ac.uk</email>
(S.D.);
<email>k.moessner@surrey.ac.uk</email>
(K.M.)</aff>
<aff id="af2-sensors-16-00600">
<label>2</label>
Department of Computer Science and Software Engineering, Xi’an Jiaotong-Liverpool University, Ren’ai Road Dushu Lake Higher Education Town SIP, Suzhou 215123, China;
<email>Wei.Wang03@xjtlu.edu.cn</email>
</aff>
<author-notes>
<corresp id="c1-sensors-16-00600">
<label>*</label>
Correspondence:
<email>yuchao.zhou@surrey.ac.uk</email>
; Tel.: +44-750-088-9377</corresp>
</author-notes>
<pub-date pub-type="epub">
<day>27</day>
<month>4</month>
<year>2016</year>
</pub-date>
<pub-date pub-type="collection">
<month>5</month>
<year>2016</year>
</pub-date>
<volume>16</volume>
<issue>5</issue>
<elocation-id>600</elocation-id>
<history>
<date date-type="received">
<day>18</day>
<month>1</month>
<year>2016</year>
</date>
<date date-type="accepted">
<day>21</day>
<month>4</month>
<year>2016</year>
</date>
</history>
<permissions>
<copyright-statement>© 2016 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2016</copyright-year>
<license>
<license-p>
<pmc-comment>CREATIVE COMMONS</pmc-comment>
This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC-BY) license (
<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0/">http://creativecommons.org/licenses/by/4.0/</ext-link>
).</license-p>
</license>
</permissions>
<abstract>
<p>The Web of Things aims to make physical world objects and their data accessible through standard Web technologies to enable intelligent applications and sophisticated data analytics. Due to the amount and heterogeneity of the data, it is challenging to perform data analysis directly; especially when the data is captured from a large number of distributed sources. However, the size and scope of the data can be reduced and narrowed down with search techniques, so that only the most relevant and useful data items are selected according to the application requirements. Search is fundamental to the Web of Things while challenging by nature in this context, e.g., mobility of the objects, opportunistic presence and sensing, continuous data streams with changing spatial and temporal properties, efficient indexing for historical and real time data. The research community has developed numerous techniques and methods to tackle these problems as reported by a large body of literature in the last few years. A comprehensive investigation of the current and past studies is necessary to gain a clear view of the research landscape and to identify promising future directions. This survey reviews the state-of-the-art search methods for the Web of Things, which are classified according to three different viewpoints: basic principles, data/knowledge representation, and contents being searched. Experiences and lessons learned from the existing work and some EU research projects related to Web of Things are discussed, and an outlook to the future research is presented.</p>
</abstract>
<kwd-group>
<kwd>search</kwd>
<kwd>Web of Things</kwd>
<kwd>Internet of Things</kwd>
<kwd>linked data</kwd>
<kwd>streaming data</kwd>
<kwd>observation and measurement data</kwd>
<kwd>sensors</kwd>
<kwd>entities</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="sec1-sensors-16-00600">
<title>1. Introduction</title>
<p>The Web of Things (WoT) paradigm envisions an interoperable infrastructure for enabling communications among physical world objects and data access to create future Internet of Things (IoT) applications through existing Web standards [
<xref rid="B1-sensors-16-00600" ref-type="bibr">1</xref>
,
<xref rid="B2-sensors-16-00600" ref-type="bibr">2</xref>
]. In recent years, low price and easy deployment of sensors and wireless sensor networks, the development of communication techniques, and the emergence of various smart objects, have led to increasing numbers of physical objects being connected. Cisco Systems predicts the number of connected objects to increase to 50 billion by 2020 [
<xref rid="B3-sensors-16-00600" ref-type="bibr">3</xref>
]. As a consequence, massive amount of data (e.g., data describing the objects or data captured from the physical or social worlds) is expected to be generated continuously by these connected objects.</p>
<p>In WoT, the physical objects are deployed in different geographical locations and managed by different organisations; and the captured data is represented in different formats and its quality is subject to various uncertainties. Currently, the data is collected and processed by different brokers or middleware, stored in distributed datasets or clouds, and often made available through specialised Application Programming Interfaces (APIs). This implies a key obstacle in developing innovative applications in the WoT, which is, multiple sources of data are required to be blended to detect useful patterns and discover valuable information. As not all data is relevant to an application’s needs and requirements, efficient and effective search methods are needed to find the most relevant and useful data sources (
<italic>i.e.</italic>
, the sources that produce the data) or data items.</p>
<p>In contrast to searching documents on the Web, search in WoT manifests several additional challenges. For example, WoT objects can have complex descriptions; and their produced data can have properties represented along the thematic, spatial, and temporal dimensions. The status of the WoT objects may change unexpectedly, for instance, loss of communication, malfunctioning of the wireless sensor nodes, opportunistic presence of the mobile sensors, and change of the measurement targets. All of these characteristics indicate that traditional search techniques built on relatively static indexing structures are not sufficient for WoT applications.</p>
<p>A notable research direction is on device and service discovery on the IoT. A number of EU research initiatives have focussed on developing device and service resolution frameworks for the IoT. The IoT-A [
<xref rid="B4-sensors-16-00600" ref-type="bibr">4</xref>
] project provides semantic description models for services and entities to enable scalable lookup and discovery of resources (devices, sensors), real world entities and their associations [
<xref rid="B5-sensors-16-00600" ref-type="bibr">5</xref>
]. IoT@Work [
<xref rid="B6-sensors-16-00600" ref-type="bibr">6</xref>
] also provides a directory service that enables access to services and devices through a variety of protocols and tools. The VITAL project [
<xref rid="B7-sensors-16-00600" ref-type="bibr">7</xref>
] aims to enable semantic discovery of Internet-connected objects and services agnostic of the underlying IoT platform. Research in this line in fact targets searching objects of different types (e.g., devices, sensors, and services) which generate data. There is also research on IoT discovery at the lower layers of the IP stack, focusing on connection and access, for example, neighbour discovery in Wireless Sensor Networks [
<xref rid="B8-sensors-16-00600" ref-type="bibr">8</xref>
] and opportunistic IoT scenarios [
<xref rid="B9-sensors-16-00600" ref-type="bibr">9</xref>
]. Service discovery for constrained machine-to-machine communications is reviewed in [
<xref rid="B10-sensors-16-00600" ref-type="bibr">10</xref>
]. In contrast, this study investigates the search problems on the WoT from a data-centric perspective.</p>
<p>Currently, there are only a limited number of studies that survey the search techniques for the WoT. One such study reviews research in searching for entities [
<xref rid="B11-sensors-16-00600" ref-type="bibr">11</xref>
], however, search for sensors and Observation and Measurement (O&M) data is not included. O&M data represents values of any observed or measured quantity (e.g., indoor temperature). Since sensor networks have been increasingly deployed to monitor environments all around the world, sensors and their O&M data are becoming more and more important in the Web of Things. Nevertheless, in order to utilise sensors and O&M data for different WoT applications, a coherent infrastructure is needed for sharing, finding, and accessing sensors and their O&M data, due to the heterogeneity of protocols supported by the various sensors from a huge number of sensor manufacturers [
<xref rid="B12-sensors-16-00600" ref-type="bibr">12</xref>
]. Formal representations of both sensor model (such as SensorML [
<xref rid="B13-sensors-16-00600" ref-type="bibr">13</xref>
]) and data model (such as Observations and Measurements XML Schema [
<xref rid="B14-sensors-16-00600" ref-type="bibr">14</xref>
]) are required for such an infrastructure. Another survey [
<xref rid="B2-sensors-16-00600" ref-type="bibr">2</xref>
] presents search techniques according to a simple classification on the type of data aggregation (push- or pull-based). It does not provide a clear view of different facets of search techniques. In [
<xref rid="B15-sensors-16-00600" ref-type="bibr">15</xref>
], search systems are compared along multiple dimensions, however, a classification that allows a better understanding of the research is missing. Overall, the existing studies only focus on some specific aspects and are insufficient to offer a holistic and clear view of the state-of-the-art. This paper aims to provide a comprehensive survey which identifies the different perspectives that mirror the development of the search techniques. It defines a taxonomy, shown in
<xref ref-type="fig" rid="sensors-16-00600-f001">Figure 1</xref>
, that classifies the search techniques for WoT from three perspectives: (1) fundamental search principles; (2) data/knowledge representation, focusing on Linked Data and streaming data; and (3) contents being searched (e.g., Observation and Measurement data, sensors, and entities in the WoT). It should be noted that the techniques classified according to these three perspectives overlap with each other to some extent.</p>
<p>The contributions of this paper can be summarised as follows. (1) A comprehensive, qualitative comparison of different search techniques for the WoT, which enables the readers to gain a clear picture of the current research landscape; (2) a classification based on (a) fundamental search principles, which provides the readers a better understanding of the enabling techniques, (b) data/knowledge representation, which enables the readers to understand how different knowledge representation formalisms contribute to the search in WoT, (c) contents being searched, which enables the readers to understand how the variety of data impacts effective and efficient design of search methods; (3) a critical discussion of the lessons and experiences gained from this study and the authors’ involvement in some of the large EU research projects on WoT and IoT; and (4) observation of the trends and promising future research directions based on the review of the literature.</p>
<p>The remainder of this paper is organised as follows: in
<xref ref-type="sec" rid="sec2-sensors-16-00600">Section 2</xref>
we provide some background information on the WoT system model and relevant applications. Metrics used for comparing the search techniques are introduced in
<xref ref-type="sec" rid="sec3-sensors-16-00600">Section 3</xref>
.
<xref ref-type="sec" rid="sec4-sensors-16-00600">Section 4</xref>
,
<xref ref-type="sec" rid="sec5-sensors-16-00600">Section 5</xref>
and
<xref ref-type="sec" rid="sec6-sensors-16-00600">Section 6</xref>
detail the different techniques that fit into the classification model: basic principles, data/knowledge representation, and content of data, respectively. A critical discussion on the limitations, best practices and opportunities are provided in
<xref ref-type="sec" rid="sec7-sensors-16-00600">Section 7</xref>
.
<xref ref-type="sec" rid="sec8-sensors-16-00600">Section 8</xref>
gives an outlook for future research and
<xref ref-type="sec" rid="sec9-sensors-16-00600">Section 9</xref>
concludes the paper.</p>
</sec>
<sec id="sec2-sensors-16-00600">
<title>2. WoT System Model and Applications</title>
<p>The Web of Things provides an Application Layer that simplifies the creation of Internet of Things applications. For this study, we adopt the WoT system model proposed in [
<xref rid="B16-sensors-16-00600" ref-type="bibr">16</xref>
] (shown in
<xref ref-type="fig" rid="sensors-16-00600-f002">Figure 2</xref>
). Applications can be built based on four other layers, namely, Accessiblity Layer, Findability Layer, Sharing Layer, and Composition Layer. The Accessibility Layer deals with the problem of “how can we, from an application point of view, enable a consistent access to all kinds of connected objects?” [
<xref rid="B16-sensors-16-00600" ref-type="bibr">16</xref>
]. This can be enabled by providing Smart Gateway, RESTful API [
<xref rid="B17-sensors-16-00600" ref-type="bibr">17</xref>
], as well as the Domain Name System (DNS) [
<xref rid="B18-sensors-16-00600" ref-type="bibr">18</xref>
] and Constrained Application Protocol (CoAP) [
<xref rid="B19-sensors-16-00600" ref-type="bibr">19</xref>
] standards on web-accessible objects. The Findability Layer aims to solve the problem of “given an ecosystem of billions of smart things, how do we find their services to integrate them into composite applications?” [
<xref rid="B16-sensors-16-00600" ref-type="bibr">16</xref>
],
<italic>i.e.</italic>
, to enable searching and finding relevant services and data. The focus of our paper is to survey the state-of-the-art research corresponding to this layer. The Sharing Layer focuses on privacy and security issues and the Composition Layer is concerned with composing applications based on discovered services, e.g., automated business process composition [
<xref rid="B20-sensors-16-00600" ref-type="bibr">20</xref>
] and sensor data augmented with data aggregation [
<xref rid="B21-sensors-16-00600" ref-type="bibr">21</xref>
]. For more detailed discussion on these two layers please refer to [
<xref rid="B16-sensors-16-00600" ref-type="bibr">16</xref>
].</p>
<p>According to the WoT system model, the Findability Layer is the bridge between Web-accessible objects and their services to applications. This implies the significance of efficient and effective search technologies for WoT applications. Guinard
<italic>et al.</italic>
identify several challenges for providing search on WoT [
<xref rid="B16-sensors-16-00600" ref-type="bibr">16</xref>
], for example, smart objects do not have many indexable properties (in contrast to textual information for searching documents); smart objects always contain contextual information, such as their geographical locations (coordinates), descriptive positions (e.g., Room B on Floor 1), or current owner; mobility of smart objects, such as movement of smartphones, will lead to continuously changing contextual information; fast-changing data is not suitable for scheduled indexing as in traditional search engines.</p>
<p>WoT applications have different objectives, purposes and scope, which can be translated into different requirements for search techniques. To provide the readers a better overview of the search techniques, we provide a mapping of the search requirements and techniques with the WoT domains and applications, as shown in
<xref ref-type="table" rid="sensors-16-00600-t001">Table 1</xref>
. The classification of the applications is based on the W3C Web of Things Interest Group’s unofficial report [
<xref rid="B22-sensors-16-00600" ref-type="bibr">22</xref>
]. In this article, we review, categorise and analyse the existing search techniques for different applications in the WoT and discuss how they address the requirements and challenges. Furthermore, we examine the recent trends and point out some of the future research directions.</p>
</sec>
<sec id="sec3-sensors-16-00600">
<title>3. Metrics for Evaluating Search Techniques</title>
<p>The WoT is a highly dynamic and evolving organism composed of billions of interconnected “Things”, consequently, the scope of the research in search techniques for the WoT is broad. Individual research work may just focus on a narrow aspect of this broad area, e.g., scalability, knowledge representation (to enable semantic search), stream handling, dynamicity
<italic>etc.</italic>
To gain a quick while in-depth overview of the research, it would be better to define some prominent metrics or dimensions against which the existing works can be compared. These metrics are explained as follows:
<list list-type="simple">
<list-item>
<p>
<italic>Data format</italic>
: indicates representation of the data.</p>
</list-item>
<list-item>
<p>
<italic>Access approach</italic>
: refers to how clients of the search functionality can access the search results.</p>
</list-item>
<list-item>
<p>
<italic>Search type</italic>
: refers to the fundamental search techniques based on which the search systems are developed, such as keyword-based search, Structured Query Language (SQL)-like query, indexing, spatial search, or continuous query. The core techniques employed are important in determining the efficacy of the search.</p>
</list-item>
<list-item>
<p>
<italic>Scale of experiments</italic>
: indicates the scale of the experiments performed in a particular research work, e.g., the number of sensors and entities, or the amount of data,
<italic>etc.</italic>
, if the information is available.</p>
</list-item>
<list-item>
<p>
<italic>Dynamicity</italic>
: the term refers to the factors which have direct or indirect impact on the status, states or values generated by the “Things”, such as device registration, mobility (change of geographical locations), or sensor hardware fault [
<xref rid="B23-sensors-16-00600" ref-type="bibr">23</xref>
,
<xref rid="B24-sensors-16-00600" ref-type="bibr">24</xref>
]. It is used to indicate whether a search mechanism provides support to handle the problems caused by the highly dynamic WoT environment. In the WoT, the objects’ status and the values they produce may change rapidly. New incoming data may cause the mechanism to undergo extensive computations (leading to progressive performance degradation) or repeated changes in its underlying infrastructure (e.g., the index structures).</p>
</list-item>
<list-item>
<p>
<italic>Architecture</italic>
: points out whether a search platform is designed or the experiments are performed in a centralised or distributed manner (or both).</p>
</list-item>
<list-item>
<p>
<italic>Implementation</italic>
: indicates which programming languages/models are used to implement the search techniques or systems.</p>
</list-item>
</list>
</p>
<p>Other than the metrics mentioned above, some researchers also compare aggregation type and security support of search [
<xref rid="B15-sensors-16-00600" ref-type="bibr">15</xref>
], query time, query accuracy, entity mobility and status, as well as targeted users [
<xref rid="B11-sensors-16-00600" ref-type="bibr">11</xref>
]. For this paper, these characteristics are not considered as they do not apply to most of the reviewed techniques. </p>
<p>
<xref ref-type="table" rid="sensors-16-00600-t002">Table 2</xref>
,
<xref ref-type="table" rid="sensors-16-00600-t003">Table 3</xref>
and
<xref ref-type="table" rid="sensors-16-00600-t004">Table 4</xref>
provide a summary of the surveyed works against the metrics. As can be seen, various data formats have been used to model the WoT objects. Among them, many choose data formats that support semantics, which enables interoperability and automated reasoning, at the cost of some additional complexity. With respect to access method, REpresentational State Transfer (HTTP REST) and SPARQL Protocol And RDF Query Language (SPARQL) are the two most popular approaches due to their simplicity of implementation. The reviewed techniques employ many different search techniques, varying from keyword-based search to spatial search, semantic query,
<italic>etc.</italic>
More than half of the studied works aim at providing search functionalities on a global scale. It is interesting to see that many search techniques have taken dynamicity into consideration in their design, implying that the research community has been well aware of the distinctive charateristics of search on WoT.</p>
<p>Both centralised and distributed architectures (or combinations) are prevalent in the existing systems: a centralised architecture is efficient in process control at a single point whereas distributed architectures fit the characteristics of WoT best. Another notable finding is that most systems are implemented in Java, this can be largely attributed to the availability of many Java-based open source tools and APIs.</p>
</sec>
<sec id="sec4-sensors-16-00600">
<title>4. Classification Viewpoint—Basic Principles</title>
<p>Search as a topic has been investigated for decades; but existing techniques cannot be directly applied and need to be adapted to support search in the WoT. This section provides a classification that focuses on the underlying techniques and principles essential for search in WoT. Two broad categories of methods can be identified according to this classification,
<italic>i.e.</italic>
, indexing and clustering.</p>
<sec id="sec4dot1-sensors-16-00600">
<title>4.1. Indexing</title>
<p>Indexing is a technique that organises search key values and addresses of objects into catalogues to enable efficient lookup. The search functionality is provided by scanning the catalogue first and then locating the desired objects via the addresses in the catalogue. In the WoT, data objects are usually described according to a pre-defined knowledge representation model. Such descriptions contain useful textual information e.g., functionalities or geographical locations. Two main types of indexing approaches can be identified: text indexing and spatial indexing.</p>
<sec id="sec4dot1dot1-sensors-16-00600">
<title>4.1.1. Text Indexing</title>
<p>Text-based search techniques originate from the field of information retrieval. The overall search process can be roughly divided into two steps: indexing and searching. Indexing is used to scan all the words in documents (which can be done offline) to create an inverted index. Each term is linked to addresses pointing to the locations of the documents or the occurrences of the terms in the documents. During the search step, the index is first scanned; once the desired term is found in the list, the address of the documents can then be located. To reduce the size of the index and to improve the search efficiency, in practice, some specialised indexing data structures (such as the B-tree [
<xref rid="B82-sensors-16-00600" ref-type="bibr">82</xref>
]) are used.</p>
<p>Data and objects in the WoT are usually annotated with textual descriptions according to some carefully designed knowledge representation models. The descriptions can include valuable information related to functionalities, environment, location, performance (with keywords such as “tolerant to noise” or “high resolution”), and other context information of the objects. These kind of textual descriptions can be crawled and indexed to build simple, text-based search systems. For example, Global Sensor Networks (GSN) [
<xref rid="B25-sensors-16-00600" ref-type="bibr">25</xref>
], SenseWeb [
<xref rid="B29-sensors-16-00600" ref-type="bibr">29</xref>
], OSIRIS [
<xref rid="B38-sensors-16-00600" ref-type="bibr">38</xref>
], Dyser [
<xref rid="B30-sensors-16-00600" ref-type="bibr">30</xref>
], Microsearch [
<xref rid="B31-sensors-16-00600" ref-type="bibr">31</xref>
], Snoogle [
<xref rid="B32-sensors-16-00600" ref-type="bibr">32</xref>
], and IoT-SVK [
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
] (which is a hybrid real-time search engine framework for the Internet of Things based on Spatial-Temporal, Value-based, and Keyword-based Conditions), all apply text based indexing and searching. Techniques for text indexing can also be used for indexing values, e.g., LiveWeb [
<xref rid="B33-sensors-16-00600" ref-type="bibr">33</xref>
] and IoT-SVK [
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
] apply such indexing techniques for sensor values and provide search functionalities over the given values.</p>
<p>In addition, text-based indexing can also be combined with existing standards to provide search or discovery of smart objects over the Web. For example, the Domain Name System (DNS) [
<xref rid="B18-sensors-16-00600" ref-type="bibr">18</xref>
] can be utilised and extended with indexing techniques for searching smart objects [
<xref rid="B34-sensors-16-00600" ref-type="bibr">34</xref>
,
<xref rid="B35-sensors-16-00600" ref-type="bibr">35</xref>
,
<xref rid="B36-sensors-16-00600" ref-type="bibr">36</xref>
]. The HyperCat [
<xref rid="B83-sensors-16-00600" ref-type="bibr">83</xref>
] server also manages and stores catalogues to offer search with simple criteria, lexicographic range search with sortable string format,
<italic>etc.</italic>
These approaches exploit the existing Internet infrastructure, hence support large-scale deployments. However, it is difficult to embed complex descriptions and rich semantics to the WoT objects through these standards, which may restrict the functionalities of WoT applications built on them.</p>
<p>Research initiatives such as GSN [
<xref rid="B25-sensors-16-00600" ref-type="bibr">25</xref>
] provide APIs for users to publish sensors with descriptions. This approach offloads the annotation efforts for describing sensors to sensor publishers. However, since the descriptions are added by individual users manually, sometimes they tend to be inconsistent with each other and the accuracy cannot be guaranteed. Overall, text indexing is extremely easy to implement and can be used in most of the situations, but the most obvious limitation is the low search precision due to ambiguous descriptions.</p>
</sec>
<sec id="sec4dot1dot2-sensors-16-00600">
<title>4.1.2. Spatial Indexing</title>
<p>WoT objects and data have a strong focus on locality; this implies that spatial information is vital for description and search. In some cases, spatial information and other features of objects and data are separated to provide search services [
<xref rid="B23-sensors-16-00600" ref-type="bibr">23</xref>
,
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
,
<xref rid="B38-sensors-16-00600" ref-type="bibr">38</xref>
,
<xref rid="B39-sensors-16-00600" ref-type="bibr">39</xref>
,
<xref rid="B40-sensors-16-00600" ref-type="bibr">40</xref>
,
<xref rid="B41-sensors-16-00600" ref-type="bibr">41</xref>
,
<xref rid="B42-sensors-16-00600" ref-type="bibr">42</xref>
]. Spatial information is typically represented by latitude and longitude coordinates (sometimes including altitude as well). The two-dimensional data cannot be effectively processed by text-based indexing structures as the latitude and longitude values tend to be different even for objects located near to each other.</p>
<p>Two or more dimensional data can be mapped to and indexed by one-dimensional keys by using space filling curves. Two such examples are GeoCENS [
<xref rid="B40-sensors-16-00600" ref-type="bibr">40</xref>
] using peano curve to search for events and Zhou
<italic>et al.</italic>
work [
<xref rid="B42-sensors-16-00600" ref-type="bibr">42</xref>
] using Geohash (Z-order curve) to search for O&M data and objects. The technique used in the latter work enables both historical and near real time search for data generated by both fixed and mobile objects.</p>
<p>Objects or data points can also be indexed by tree-like data structures based on spatial indexing techniques. For example, R-tree [
<xref rid="B84-sensors-16-00600" ref-type="bibr">84</xref>
] is often used for indexing ranges. Approaches implementing R-tree based technique and its variants [
<xref rid="B23-sensors-16-00600" ref-type="bibr">23</xref>
,
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
,
<xref rid="B38-sensors-16-00600" ref-type="bibr">38</xref>
,
<xref rid="B39-sensors-16-00600" ref-type="bibr">39</xref>
,
<xref rid="B41-sensors-16-00600" ref-type="bibr">41</xref>
] index the Minimum Bounding Rectangles (MBR), which enclose the location range of all the children of a node. The nodes whose range intersects with the location in the query are retrieved. A known drawback of the R-tree based methods is the limited scalability; when a large number of locations of the physical entities are indexed, the MBR are likely to change frequently, which may negatively affect the indexing and query performance. The work in Wang
<italic>et al.</italic>
[
<xref rid="B23-sensors-16-00600" ref-type="bibr">23</xref>
] alleviates this problem by indexing the gateways (in which semantic repositories are implemented to store the sensor descriptions) instead of individual sensors. Thus, changes of individual sensors (e.g., geographical properties) are constrained within the bounds of the gateway. This eliminates the necessity of frequent updates on the spatial indexing structures.</p>
</sec>
</sec>
<sec id="sec4dot2-sensors-16-00600">
<title>4.2. Clustering</title>
<p>Clustering-based search techniques first group the “things” or data into clusters, usually in an offline phase, and then execute queries in the selected cluster. Since the number of things or the amount of data in one cluster is relatively smaller, the overall query process is reasonably efficient. With location being a key property for objects and data in the WoT, geographical information or relative location plays a substantial role in clustering-based discovery methods.</p>
<sec id="sec4dot2dot1-sensors-16-00600">
<title>4.2.1. Location-Based Clustering</title>
<p>Recent research on IoT semantic modelling and knowledge engineering emphasises the importance of location [
<xref rid="B43-sensors-16-00600" ref-type="bibr">43</xref>
] by defining semantic relations between IoT services and geographical locations (e.g., global location, local location and geographical coordinates). This modelling approach enables IoT service discovery based on the linked IoT data [
<xref rid="B44-sensors-16-00600" ref-type="bibr">44</xref>
].</p>
<p>An indoor location-based (room, building, floor,
<italic>etc.</italic>
) search mechanism is proposed by [
<xref rid="B45-sensors-16-00600" ref-type="bibr">45</xref>
] in which a hierarchy of semantic gateways is implemented. The gateways encapsulate semantic service descriptions of IoT objects within their geographic scope. Scalable search is provisioned through routing tables (constructed by recursive clustering of the semantic descriptions) which perform request matching and forwarding. However, this approach does not consider the cost of routing table maintenance (
<italic>i.e.</italic>
, update of service descriptions) due to the potential mobility of IoT objects. Mayer
<italic>et al.</italic>
[
<xref rid="B46-sensors-16-00600" ref-type="bibr">46</xref>
] consider logical identifiers for places aiming to structure nodes in a hierarchy, with interactions restricted to direct communication between neighbourhood nodes to ensure scalability. The search process can be performed either at a local node or a distant node (based on query routing).</p>
<p>The geocasting-based approaches [
<xref rid="B47-sensors-16-00600" ref-type="bibr">47</xref>
,
<xref rid="B48-sensors-16-00600" ref-type="bibr">48</xref>
,
<xref rid="B49-sensors-16-00600" ref-type="bibr">49</xref>
,
<xref rid="B85-sensors-16-00600" ref-type="bibr">85</xref>
] provide capability of sending a query to nodes within a range of location in a distributed architecture. These approaches do not have concrete clusters thus are more flexible for mobile nodes, and are often used in Vehicular Networks [
<xref rid="B47-sensors-16-00600" ref-type="bibr">47</xref>
,
<xref rid="B48-sensors-16-00600" ref-type="bibr">48</xref>
]. However, the reliability of the query is hard to be guaranteed as available services cannot be known through geocasting techniques only. In addition, query response may need extra techniques to send messages to the query sender, especially mobile ones [
<xref rid="B47-sensors-16-00600" ref-type="bibr">47</xref>
,
<xref rid="B48-sensors-16-00600" ref-type="bibr">48</xref>
].</p>
<p>Location is one of three themes (the other two are thematic and temporal aspects) considered in [
<xref rid="B5-sensors-16-00600" ref-type="bibr">5</xref>
] to associate IoT services to real-world physical entities. The authors propose a geographically distributed, federated architecture of cooperating nodes with local reasoning capabilities to manage the large number of IoT devices.</p>
</sec>
<sec id="sec4dot2dot2-sensors-16-00600">
<title>4.2.2. Non-Location-Based Clustering</title>
<p>Location-based clusters can be inflexible on many occasions due to mobility of objects. Other than location-based clusters, Christophe
<italic>et al.</italic>
[
<xref rid="B50-sensors-16-00600" ref-type="bibr">50</xref>
] cluster query requests into application invoked query and human accessed query. By specifying different requirements on the two categories, the system provides different services to the search functionality. In [
<xref rid="B51-sensors-16-00600" ref-type="bibr">51</xref>
], the authors provide clustering of IoT services based on the Google Similarity Distance. In conjunction with a skewness-aware clustering tree for spatial query and a one-dimensional index for temporal feature, a compounded query for IoT services is enabled. However, the evaluation results of the clustering process show that the method does not scale well as the number of IoT services increases to certain values. Ebrahimi
<italic>et al.</italic>
[
<xref rid="B52-sensors-16-00600" ref-type="bibr">52</xref>
] provide Sensor Semantic Overlay Networks (SSONs) for sensor search. SSONs cluster sensors based on their context information, which is defined based on the Semantic Sensor Network (SSN) Ontology. The authors propose an ant clustering algorithm, AntClust, for building clusters. User queries are sent to the most similar cluster for obtaining results. An adaptive strategy with changing threshold is used to maintain performance in the dynamic IoT environment and to control when to re-initiate the clustering process. As clustering techniques often require a time-consuming offline computing phase, they are more suitable for objects with relatively static structures, or within a specific scope. They are also vulnerable to dynamicity, e.g., a large amount of new incoming data due to changes in surrounding environments, which may lead to the clusters being frequently re-computed.</p>
</sec>
</sec>
</sec>
<sec id="sec5-sensors-16-00600">
<title>5. Classification Viewpoint—Data/Knowledge Representation</title>
<p>The Web of Things aims at making information about the objects and data generated by the objects accessible through Web standards. The Semantic Web aims at providing semantics and interoperability for any type of resource on the Web to build a Web of Data. The research communities have recognised the importance of Semantic Web techniques (e.g., knowledge representation formalism and automated reasoning to derive new knowledge) in realising intelligent services with connected objects in the IoT and WoT [
<xref rid="B44-sensors-16-00600" ref-type="bibr">44</xref>
,
<xref rid="B53-sensors-16-00600" ref-type="bibr">53</xref>
,
<xref rid="B54-sensors-16-00600" ref-type="bibr">54</xref>
]. In this section, search techniques are explored from the perspective of data/knowledge representation, with a particular focus on the use of the Semantic Web technologies,
<italic>i.e.</italic>
, Linked Data and semantic streaming data.</p>
<sec id="sec5dot1-sensors-16-00600">
<title>5.1. Search and Query on Linked Data</title>
<p>Linked Data is an important concept for the vision of a Web of Data. Sir Tim Berners-Lee proposed the Linked Data principles, which suggest to publish data in standard formats (such as in Resource Description Framework (RDF) [
<xref rid="B86-sensors-16-00600" ref-type="bibr">86</xref>
]) and to access it through existing Web standards (Hypertext Transfer Protocol (HTTP) look up and SPARQL query [
<xref rid="B87-sensors-16-00600" ref-type="bibr">87</xref>
]). More importantly, the data items should be linked to each other and to other resources wherever applicable, to add semantics to the original data [
<xref rid="B88-sensors-16-00600" ref-type="bibr">88</xref>
]. Linked Data offers the capability of linking data items with their Uniform Resource Identifiers (URIs), making it possible to build interlinked and distributed datasets. This subsection discusses centralised and federated (distributed) approaches to access the Linked Data in the WoT.</p>
<sec id="sec5dot1dot1-sensors-16-00600">
<title>5.1.1. Centralised Approaches</title>
<p>This class of methods publishes semantic descriptions of the objects in the WoT as linked data in a centralised fashion. For example, the work in [
<xref rid="B53-sensors-16-00600" ref-type="bibr">53</xref>
,
<xref rid="B55-sensors-16-00600" ref-type="bibr">55</xref>
,
<xref rid="B56-sensors-16-00600" ref-type="bibr">56</xref>
] merges sensor description information into a centralised repository, and provides SPARQL endpoints for accessing the datasets. The semantic descriptions can be linked to other data sources that contain geographical information to enable simple spatial search, for example, all sensors near to the points of interest in a city. The limitation is that the spatial search functionality can only support keyword-based search through filters in the SPARQL query at coarse levels.</p>
<p>As locations become increasingly important for objects and data in the WoT [
<xref rid="B89-sensors-16-00600" ref-type="bibr">89</xref>
], some researchers extend the SPARQL language with spatial search capabilities [
<xref rid="B57-sensors-16-00600" ref-type="bibr">57</xref>
,
<xref rid="B59-sensors-16-00600" ref-type="bibr">59</xref>
,
<xref rid="B60-sensors-16-00600" ref-type="bibr">60</xref>
]. These works either add a spatial ontology (such as World Geodetic System 1984 (WGS84) ontology [
<xref rid="B90-sensors-16-00600" ref-type="bibr">90</xref>
]) or spatial properties (geom:geometry [
<xref rid="B57-sensors-16-00600" ref-type="bibr">57</xref>
]) into the original ontology. They then use built-in functions of the triple store (such as OpenLink’s Virtuoso [
<xref rid="B91-sensors-16-00600" ref-type="bibr">91</xref>
]) or build external functions to enable spatial search at finer levels, such as ‘within a region’. The search process can directly run SPARQL queries on the endpoints to get objects satisfying semantic restrictions as well as spatial constraints. Spatial index structures, such as R-tree, can be introduced to make the search even more efficient. A comparison of different semantic Web tools for spatial query is provided in [
<xref rid="B92-sensors-16-00600" ref-type="bibr">92</xref>
].</p>
<p>Centralised approaches enable fast response to queries, however, they require the data to be stored in a centralised repository. This introduces a number of limitations, for example, single point of failure, duplication of data (which introduces difficulties in maintaining the status of all objects and data), and poor scalability.</p>
</sec>
<sec id="sec5dot1dot2-sensors-16-00600">
<title>5.1.2. Federated Approaches</title>
<p>One benefit of Linked Data is that it allows the data storage to be distributed over the Web while maintaining semantic links between the resources. Obviously, centralised approaches do not take full advantage of Linked Data. One can utilise federated query techniques to enable transparent query over distributed repositories.</p>
<p>In federated search, the original query is decomposed into a number of sub-queries, and the search system helps determine which source or dataset can provide potential answers for a sub-query. The sub-queries are sent to the relevant repositories to retrieve intermediate results, which are finally federated to compose the final results. Processing of the sub-queries is unlikely to be efficient without a proper execution plan. Existing implementations [
<xref rid="B61-sensors-16-00600" ref-type="bibr">61</xref>
,
<xref rid="B62-sensors-16-00600" ref-type="bibr">62</xref>
,
<xref rid="B63-sensors-16-00600" ref-type="bibr">63</xref>
,
<xref rid="B64-sensors-16-00600" ref-type="bibr">64</xref>
,
<xref rid="B65-sensors-16-00600" ref-type="bibr">65</xref>
] provide different query optimisation techniques for the query process, for example, optimisation based on complete knowledge and statistics of datasets (DARQ [
<xref rid="B61-sensors-16-00600" ref-type="bibr">61</xref>
], ANAPSID [
<xref rid="B62-sensors-16-00600" ref-type="bibr">62</xref>
], SPLENDID [
<xref rid="B63-sensors-16-00600" ref-type="bibr">63</xref>
]), or heuristic ([
<xref rid="B65-sensors-16-00600" ref-type="bibr">65</xref>
], FedX [
<xref rid="B64-sensors-16-00600" ref-type="bibr">64</xref>
]).</p>
<p>It is worth noting that most of the above implementations are based on SPARQL 1.0. The newer version, SPARQL 1.1 [
<xref rid="B66-sensors-16-00600" ref-type="bibr">66</xref>
] supports federated query capability by expressing queries across diverse datasets, and has been approved as a W3C recommendation (for more information about the syntax of SPARQL 1.1, please refer to [
<xref rid="B67-sensors-16-00600" ref-type="bibr">67</xref>
]). In addition to the previous query constructs, it uses the
<italic>SERVICE</italic>
statement to declare a remote SPARQL endpoint. The work in ANAPSID [
<xref rid="B62-sensors-16-00600" ref-type="bibr">62</xref>
] extends SPARQL 1.1 by providing the
<italic>agjoin</italic>
and
<italic>adjoin</italic>
operators to further reduce execution time, enabling a query to be answered even when a source is blocked.</p>
<p>Federated search addresses some of the limitations of the centralised search. The challenge is how to design appropriate query optimisation techniques to enable efficient distributed queries. Furthermore, its performance is subject to transmission delays and network bandwidth. Related challenges and future directions are discussed in [
<xref rid="B93-sensors-16-00600" ref-type="bibr">93</xref>
], for example, metadata management, caching results, and adaptive query processing in federated search.</p>
</sec>
</sec>
<sec id="sec5dot2-sensors-16-00600">
<title>5.2. Search over Streaming Data</title>
<p>WoT comprises of both static and dynamic data, for example, metadata describing sensors or objects is relatively static and changes infrequently; while data generated by sensors and objects are dynamic and of streaming nature. Streaming data has its own characteristics, for example, the speed at which data is generated may change (because of change of the application requirements), or the data flow may stop and recover occasionally (recurrence). In some delay-tolerant networking applications, data might not arrive in order, or arrive later in bursts. Therefore, it requires specialised techniques that can quickly process the continuously generated data for indexing and querying. Moreover, the data values are always tagged with time stamps and (often with) spatial information as well. This subsection presents the recent works on searching over streaming data through relational database mapping and semantic modelling.</p>
<sec id="sec5dot2dot1-sensors-16-00600">
<title>5.2.1. Relational Database Mapping Approaches</title>
<p>Data Stream Management Systems (DSMS) aim to provide functionalities for managing streaming data based on traditional relational database systems. In the context of WoT, the research mainly focuses on providing languages and facilities to support continuous queries [
<xref rid="B25-sensors-16-00600" ref-type="bibr">25</xref>
,
<xref rid="B68-sensors-16-00600" ref-type="bibr">68</xref>
].</p>
<p>The GSN framework [
<xref rid="B25-sensors-16-00600" ref-type="bibr">25</xref>
] is a DSMS that offers ad-hoc data access APIs to virtual sensors stored in the GSN system. The queries allow sliding windows through explicitly defined temporal parameters. SenseWeb [
<xref rid="B29-sensors-16-00600" ref-type="bibr">29</xref>
] supports queries for sensor data streams based on type, location and descriptions of sensors. Ontology-based query of live sensor data is presented in [
<xref rid="B68-sensors-16-00600" ref-type="bibr">68</xref>
]. The authors use the R2RML language (RDB-to-RDF mapping language) for mapping streams stored in relational databases to ontological schemas. The virtual RDF streams can be queried using an extended SPARQL language that supports time windows. The authors also validate their method by using query mapping to retrieve data from existing DSMSs such as ESPER [
<xref rid="B94-sensors-16-00600" ref-type="bibr">94</xref>
], GSN and Xively [
<xref rid="B95-sensors-16-00600" ref-type="bibr">95</xref>
].</p>
<p>While these works provide a useful approach for ontology-based query of sensor O&M time-series data, the actual query processing and O&M data collection/storage is delegated to the DSMS. The functionalities offered by this class of methods are generally limited to those provided by the underlying relational databases.</p>
</sec>
<sec id="sec5dot2dot2-sensors-16-00600">
<title>5.2.2. Semantic Modelling Approaches</title>
<p>An alternative approach is presented in [
<xref rid="B44-sensors-16-00600" ref-type="bibr">44</xref>
], where semantically annotated sensor O&M data is transformed to streams and is assigned a unique identifier. The naming mechanism is based on the location, quality and start time of the measurement. To deal with the large amount of annotated data, a K-means clustering algorithm is applied to distribute the data among different repositories. Resolution is done by finding the nearest cluster to identify the repositories that are likely to contain the data sought by the queries. However, queries requiring time window and data aggregation functions are not supported.</p>
<p>As a lot of streaming data has been published as RDF data [
<xref rid="B44-sensors-16-00600" ref-type="bibr">44</xref>
], efforts to extend the SPARQL language to answer continuous queries for streaming data have been undertaken. Some of the examples include C-SPARQL [
<xref rid="B69-sensors-16-00600" ref-type="bibr">69</xref>
], EP-SPARQL [
<xref rid="B70-sensors-16-00600" ref-type="bibr">70</xref>
], CQELS [
<xref rid="B71-sensors-16-00600" ref-type="bibr">71</xref>
] and SPARQLstream [
<xref rid="B68-sensors-16-00600" ref-type="bibr">68</xref>
]. Among them, SPARQLstream and C-SPARQL store data in DSMS, and provide translation services to enable continuous queries. In contrast, CQELS uses its own native processing model in the query engine, which can dynamically adapt to changes in the input data. Linked Sensor Middleware (LSM) [
<xref rid="B27-sensors-16-00600" ref-type="bibr">27</xref>
] is an application based on CQELS. LSM is also integrated with eXtended Global Sensor Networks (XGSN) [
<xref rid="B26-sensors-16-00600" ref-type="bibr">26</xref>
] in OpenIoT [
<xref rid="B28-sensors-16-00600" ref-type="bibr">28</xref>
].</p>
<p>Semantic modelling based methods add rich semantics to the WoT data and provide more powerful reasoning capabilities than relational databases. However, the data model is relatively more complex and requires extra computation during runtime. To alleviate the problem, Shin
<italic>et al.</italic>
[
<xref rid="B72-sensors-16-00600" ref-type="bibr">72</xref>
] propose query adaptive techniques to filter out semantic streaming data that is not related to registered query to reduce both the size of storage and the query response time.</p>
</sec>
</sec>
</sec>
<sec id="sec6-sensors-16-00600">
<title>6. Classification Viewpoint—Contents Being Searched</title>
<p>This section provides a review to the search techniques for WoT from the content perspective as different content types entail different search methods. Due to the importance of sensors and sensor networks to WoT and IoT, this section focuses on the following three types which form the basic contents of the WoT: information about sensors (
<italic>i.e.</italic>
, the descriptive and contextual information for sensors), Observation and Measurement data (
<italic>i.e.</italic>
, data produced by different kinds of sensors), and information about entities (information objects in the WoT, e.g., city, point of interest, patient, or smart home). From an object-oriented or semantic modelling view, a sensor is also a kind of entity in the WoT; however, the discussion in this section distinguishes sensors from entities due to their particular importance.</p>
<sec id="sec6dot1-sensors-16-00600">
<title>6.1. Search for Observation and Measurement Data</title>
<p>O&M search aims to find the desired measurement data based on pre-defined requirements, for example, within a specific time range in a particular location. One approach is to perform a sensor search first and then retrieve the O&M data from selected sensors. However, it may not be effective for mobile sensors, whose spatial values might change frequently over time. Another approach is to perform direct search in streaming databases which store large amounts of O&M data collected from sensors. The requirements for real-time streaming data and historical data are considered separately in this subsection. Search techniques for streaming data have also been discussed in
<xref ref-type="sec" rid="sec5dot2-sensors-16-00600">Section 5.2</xref>
. Most of them can support short-term historical data queries (bounded by the given time windows), but normally not long-term historical data.</p>
<sec id="sec6dot1dot1-sensors-16-00600">
<title>6.1.1. Instantaneous Data</title>
<p>Real-time data is important for many applications; for instance, users may need to know the availability of meeting rooms or the nearest car parks with available parking space. A lot of research has been undertaken in designing and developing real-time O&M data search. The work in SensorMap [
<xref rid="B39-sensors-16-00600" ref-type="bibr">39</xref>
] allows users to first search sensors on a location map by specifying the sensor type. Once the matching sensors are found, the latest values generated by those sensors are retrieved. Liveweb [
<xref rid="B33-sensors-16-00600" ref-type="bibr">33</xref>
] creates an index on real-time data in a tree structure to enable efficient search. GeoCENS [
<xref rid="B40-sensors-16-00600" ref-type="bibr">40</xref>
] applies space filling curve on the spatial information of sensors, and implements a hybrid Peer-to-Peer (P2P) architecture to support spatial search for sensors. The O&M data is then obtained from the selected sensors. IoT-SVK [
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
] integrates and symbolises sampling values into keywords, then applies Value-Symbolized Keyword B
<sup>+</sup>
-tree to support O&M value queries. However, due to transmission delays or communication failure, real time data services sometimes cannot guarantee data freshness, especially in time-critical applications. The work in [
<xref rid="B71-sensors-16-00600" ref-type="bibr">71</xref>
] combines search techniques with a short-term prediction algorithm to mitigate this problem.</p>
</sec>
<sec id="sec6dot1dot2-sensors-16-00600">
<title>6.1.2. Historical Data</title>
<p>Historical data may not seem important in day-to-day lives, but they are vital for data analytics and predictive modelling. The work in LSM [
<xref rid="B27-sensors-16-00600" ref-type="bibr">27</xref>
] provides facilities and services for storage and query of historical data. These search services generally assume that the context of O&M data is static and not likely to change frequently. IoT-SVK [
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
] indexes both O&M values and time stamps to support historical data search.</p>
<p>Spatial information is one of the most important context information crucial to the retrieval of O&M data. As sensors and smart devices are increasingly attached to mobile objects (buses, humans,
<italic>etc.</italic>
), spatial information of O&M data may change frequently. Traditional methods cannot provide effective search services for O&M data generated by mobile objects. To address this issue, Zhou
<italic>et al.</italic>
[
<xref rid="B42-sensors-16-00600" ref-type="bibr">42</xref>
] provide a data-centric framework which encodes spatial features into the O&M data and stores it into a cloud based time-series database. The framework enables search for historical and near real-time data collected from both static and mobile sensing sources. A potential challenge is the storage of O&M data as it is continuously generated from an increasingly large number of static and mobile objects. One future research direction is the design of more effective information abstraction methods for real-time streaming data, which largely preserve the valuable information contained in the original data and at the same time reduce the needs for large storage space. The recent research on NoSQL databases and cloud-based storage can also be used to alleviate the problem.</p>
</sec>
</sec>
<sec id="sec6dot2-sensors-16-00600">
<title>6.2. Search for Sensor Information</title>
<p>In many applications, especially those that need continuous data, it is computationally expensive and time-consuming to search for O&M data directly and repeatedly. A much more efficient approach is to identify the best sources which can provide the needed data and to subscribe to them. The objective of sensor search is to find the right sources which can provide the O&M data (preferably high quality, or with less computation cost) needed in an application. The existing methods can be categorised into two groups: context-based (e.g., search based on locations and types of sensors); or content-based, (e.g., search sensors that generate certain values).</p>
<sec id="sec6dot2dot1-sensors-16-00600">
<title>6.2.1. Context-Based Sensor Search</title>
<p>Context-based sensor search relies on various type of contextual information available in the descriptions of sensors and services. Microsearch [
<xref rid="B31-sensors-16-00600" ref-type="bibr">31</xref>
] and Snoogle [
<xref rid="B32-sensors-16-00600" ref-type="bibr">32</xref>
] offer search services for sensor nodes by indexing the sensor descriptions. Jirka
<italic>et al.</italic>
[
<xref rid="B38-sensors-16-00600" ref-type="bibr">38</xref>
] provide sensor search based on keywords as well as indexed geographical locations. The works in [
<xref rid="B53-sensors-16-00600" ref-type="bibr">53</xref>
,
<xref rid="B56-sensors-16-00600" ref-type="bibr">56</xref>
] publish sensor data (sensor descriptions and sensed data) following the Linked Data principles. The published data is also linked to concepts in existing datasets, such as GeoNames [
<xref rid="B96-sensors-16-00600" ref-type="bibr">96</xref>
], to extend the original descriptions with geographical information. This allows users to discover sensors based on named locations.</p>
<p>Other than location and type, context may include information related to quality of service of sensors, such as accuracy, reliability, delay,
<italic>etc.</italic>
CASSARAM [
<xref rid="B73-sensors-16-00600" ref-type="bibr">73</xref>
] proposes search and selection of sensors based on user expectations and priorities over quality of service related information. Sensors are modelled with contextual properties based on the Semantic Sensor Network Ontology (SSN Ontology) [
<xref rid="B97-sensors-16-00600" ref-type="bibr">97</xref>
]. A weighted Euclidean distance based indexing technique is used to measure how similar the description of a sensor is to the user requirements. The authors also apply an optimised parallel processing method to enable distributed search over different server nodes to acquire highly ranked sensors. Shah
<italic>et al.</italic>
[
<xref rid="B74-sensors-16-00600" ref-type="bibr">74</xref>
] provide a search service based on multiple features in a P2P network, which consist of distance, energy level, communication cost, computation cost,
<italic>etc.</italic>
Selection of the sensors is based on the Euclidian distance of weighted features of sensors and the user requirements.</p>
<p>Sensor search techniques based on context information are effective in retrieving a list of potentially useful sensors. However, the limitation lies in the availability of the contextual information. For example, while geographical information can be obtained in straightforward ways, quality of service related information is often difficult to capture for individual sensors. Furthermore, carefully designed ranking algorithms are needed to select the best ones from all the retrieved sensors.</p>
</sec>
<sec id="sec6dot2dot2-sensors-16-00600">
<title>6.2.2. Content-Based Sensor Search</title>
<p>Content-based search aims to find sensors based on the values generated by sensors. The work by Elahi
<italic>et al.</italic>
[
<xref rid="B77-sensors-16-00600" ref-type="bibr">77</xref>
] leverages human periodic behaviour and predicts the sensor output at future points. The results are then used to estimate the probability that a sensor matches the query requirements. The work by Truong
<italic>et al.</italic>
[
<xref rid="B76-sensors-16-00600" ref-type="bibr">76</xref>
] calculate the similarity scores between sensors and a given sensor (used as a query) with the output of sensors. The matched sensors are further ranked based on the fuzzy set theory. Although research in this line is not as popular as context-based one, it represents a useful approach in some applications, for instance, monitoring whether sensors are functioning properly, identifying sensors that need maintenance, deploying new sensors, or defining new services based on particular sensors.</p>
</sec>
</sec>
<sec id="sec6dot3-sensors-16-00600">
<title>6.3. Search for Entity Information</title>
<p>Entity search has potential usage in a wide range of human-centric applications whose primary tasks are to facilitate interactions between human users and intelligent systems. As sensor is a particular type of entity or object, it is not surprising that techniques used for searching entities are similar to those designed for sensor search in many ways. In almost all applications, sensors and various kinds of entities (e.g., a parking lot, smart office, or a patient) are always associated to each other. The work in Dyser [
<xref rid="B30-sensors-16-00600" ref-type="bibr">30</xref>
] and SPITFIRE [
<xref rid="B75-sensors-16-00600" ref-type="bibr">75</xref>
] in fact provides both sensor search and entity search. The existing research on searching entities is also classified into context-based and content-based.</p>
<sec id="sec6dot3dot1-sensors-16-00600">
<title>6.3.1. Context-Based Entity Search</title>
<p>Knowledge representation plays important roles in searching both sensors and entities. In sensor search, contextual information about sensors can be represented by using the widely used models, such as the SSN ontology [
<xref rid="B97-sensors-16-00600" ref-type="bibr">97</xref>
], or Sensor Model Language (SensorML) [
<xref rid="B13-sensors-16-00600" ref-type="bibr">13</xref>
]; however, currently, there is no standard knowledge representation models for entities, which might introduce some interoperability problems in the search systems in the WoT.</p>
<p>DiscoWoT [
<xref rid="B81-sensors-16-00600" ref-type="bibr">81</xref>
] is a general semantic discovery service for Web-enabled things. The descriptions of the things can be created by arbitrary users through a given Web-based interface according to its internal description structures, which contain the basic, contextual and product-related information about the resources. Qian
<italic>et al.</italic>
[
<xref rid="B79-sensors-16-00600" ref-type="bibr">79</xref>
] provide an IoT Search Engine to enable search for Radio-Frequency IDentification (RFID) objects in real-time. The engine consists of several modules: an index, update module, query module, and security module. The index module implements a distributed indexing and storage component. The update module can handle different update operations (
<italic>i.e.</italic>
, add, delete, and modify). The query module provides an interface to handle query requests and representation of results. The security module applies the Elliptic Curve Cryptography-based algorithm [
<xref rid="B98-sensors-16-00600" ref-type="bibr">98</xref>
] for encryption and decryption, providing authentication and protection of vital entities. Gander [
<xref rid="B78-sensors-16-00600" ref-type="bibr">78</xref>
] is a middleware for pervasive computing environment that is able to capture the context of data items and to provide real-time search capability for nearby entities. It applies sampling on the spatiotemporal information through peer-to-peer methods. The context used for search includes relationships among data items and their surrounding environments.</p>
<p>Compared to sensors, entities significantly vary in size, scope, type and capabilities. It is difficult to design a comprehensive knowledge representation model for all kinds of entities in the WoT. A general model (e.g., an upper-level ontology) is not able to capture more specific knowledge of the various entities in different domains. Therefore, applications implementing entity search are usually limited in terms of domain and scope (e.g., specificity).</p>
</sec>
<sec id="sec6dot3dot2-sensors-16-00600">
<title>6.3.2. Content-Based Entity Search</title>
<p>Content-based entity search can find entities based on their states or status. Different from content-based sensor search which directly searches through raw O&M data, content-based entity search requires entities’ states or status to be derived from the O&M data first.</p>
<p>Dyser [
<xref rid="B30-sensors-16-00600" ref-type="bibr">30</xref>
] supports searching real-world entities that are in some specific states, e.g., available parking slot. In Dyser, an index is first created based on the metadata of sensors and entities. During the query process, a number of sensors relevant to the entity of interest are retrieved first, and then the state of the entity is derived based on the values collected from its associated sensors. The matched entities are sorted by the ranking technique proposed in the authors’ previous work [
<xref rid="B77-sensors-16-00600" ref-type="bibr">77</xref>
]. The search process stops when enough (top k) matched entities are found. The prediction model used in Dyser periodically computes the states of entities based on the measurement data from sensors. The work in Mietz
<italic>et al.</italic>
[
<xref rid="B80-sensors-16-00600" ref-type="bibr">80</xref>
] applies Bayesian Network to automatically infer the states of the entities. SPITFIRE [
<xref rid="B75-sensors-16-00600" ref-type="bibr">75</xref>
] infers states of things from the embedded sensors based on their semantic descriptions. One notable feature of this work is that it employs a short-term prediction model. Because of the dynamicity of the WoT, the status of the returned entities may even change due to transmission delays. The short-term prediction can resolve this issue effectively.</p>
</sec>
</sec>
</sec>
<sec id="sec7-sensors-16-00600">
<title>7. Discussion</title>
<p>This section presents lessons learnt from the comparison of the existing work and the experiences gained from the authors’ involvement in some of the large EU research projects on WoT and IoT. The discussion is provided following the classification of the existing search techniques.</p>
<sec id="sec7dot1-sensors-16-00600">
<title>7.1. The Basic Principles Perspective</title>
<p>Traditional spatial indexing techniques are good at indexing static objects; however, sensors and smart objects are increasingly becoming mobile, e.g., smart phones, buses equipped with sensors,
<italic>etc.</italic>
These mobile sensors lead to opportunistic sensing, which provide sensing data in extended areas. However, very few spatial search mechanisms consider mobile objects, e.g., trajectory search [
<xref rid="B99-sensors-16-00600" ref-type="bibr">99</xref>
,
<xref rid="B100-sensors-16-00600" ref-type="bibr">100</xref>
]. As mobile sensors and opportunistic sensing become more and more prevalent, search methods for the WoT applications need to pay special attention to them.</p>
<p>Searching based on existing standards is a good practice in designing search systems in WoT and shows a promising direction, for example, the DNS-based approaches can exploit the current Internet infrastructure, in which Web crawlers can be designed to collect descriptions of IoT devices. Existing Web standards are used mainly for resources and devices discovery, which is based on proposed or existing registries deployed on the Web. These registries manage identifiers and metadata of sensors, entities, and their services, offering simple search functionalities (such as keyword match) within the scope of registries. Distributed search on a large scale relies on peer-to-peer overlays covering these registries. More complex search services may require additional search techniques, such as Elasticsearch [
<xref rid="B101-sensors-16-00600" ref-type="bibr">101</xref>
], to be integrated.</p>
<p>Due to the dynamicity (e.g., changing physical environment factors, mobility, device failure, and opportunistic sensing scenarios) and open tasks (local area data analytics, personalised smart services,
<italic>etc.</italic>
), search in the WoT should be implemented along multiple dimensions,
<italic>i.e.</italic>
, temporal, spatial, and thematic. This is one of the most significant differences to other traditional search applications. The work in [
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
] follows this principle by combining different indexing techniques and designing a search method based on time, locations and values, and reports encouraging results. It shows that developing search methods exploiting the temporal, spatial and thematic properties of the WoT objects and data simultaneously is a promising direction.</p>
<p>Most of the reviewed works implement middlewares based on the basic search principles for easy deployment, such as OpenIoT [
<xref rid="B28-sensors-16-00600" ref-type="bibr">28</xref>
], GSN [
<xref rid="B25-sensors-16-00600" ref-type="bibr">25</xref>
], GeoCENS [
<xref rid="B40-sensors-16-00600" ref-type="bibr">40</xref>
], Geospatial Indexing [
<xref rid="B23-sensors-16-00600" ref-type="bibr">23</xref>
]. The middleware platforms hide the comlexity and heterogeneity of the representation of and communication among objects and sensors, and offer easy-to-use search functionality based on stardard service interfaces. However, evaluation and comparison of the existing methods are difficult. We have done a lot of investigation on the possibility of performing such evaluation and comparison among all surveyed works: we checked if the systems in the reviewed papers are still accessible through the provided Uniform Resource Locators (URLs) or SPARQL endpoints and have clear input specification (so we could perform some experiments to measure the throughput and scalability). Unfortunately, we only got a very small number, which makes the comparison and evaluation insignificant. Another difficulty is that most of the works are performed in a closed environment and the datasets are not publicly available. Moreover, the reviewed works implement different methods and use different data formats and datasets.</p>
</sec>
<sec id="sec7dot2-sensors-16-00600">
<title>7.2. The Data/Knowledge Representation Perspective</title>
<p>Although this study differentiates the centralised and distributed methods, the line between them diminishes in real systems. Based on the review of the related work, it is straightforward to see that a combination of both methods has clear advantages. A good practice is to maintain metadata on WoT objects and data in a relatively more centralised repository and to store the more dynamic, streaming data in distributed storages. The metadata can be published as linked data, which links to other data items in different sources (e.g., domain knowledge bases and existing linked data cloud).</p>
<p>With respect to evaluation strategies, centralised, federated, and streaming based approaches need to be considered differently. Even methods falling into the same category might be difficult to compare, for example, most centralised approaches extend the Linked Data query with geospatial functionalities, e.g., LinkedGeoData [
<xref rid="B57-sensors-16-00600" ref-type="bibr">57</xref>
], OWLIM-SE [
<xref rid="B59-sensors-16-00600" ref-type="bibr">59</xref>
], GeoSPARQL [
<xref rid="B60-sensors-16-00600" ref-type="bibr">60</xref>
]. However, the internal knowledge representations of these research works are different and cannot be directly compared without translating one representation to another. Federated approaches evaluate queries on distributed datasets (DARQ [
<xref rid="B61-sensors-16-00600" ref-type="bibr">61</xref>
], ANAPSID [
<xref rid="B62-sensors-16-00600" ref-type="bibr">62</xref>
], SPLENDID [
<xref rid="B63-sensors-16-00600" ref-type="bibr">63</xref>
], FedX [
<xref rid="B64-sensors-16-00600" ref-type="bibr">64</xref>
], Federated Query Implementation [
<xref rid="B65-sensors-16-00600" ref-type="bibr">65</xref>
]). Fedbench [
<xref rid="B102-sensors-16-00600" ref-type="bibr">102</xref>
] provides a benchmark test for response time in federated approaches. A comparison study on response time is provided in SPLENDID against DARQ and FedX. It is reported that in that particular experiment, FedX outperforms others in most queries and SPLENDID performs competitively. Streaming based approaches are concerned with continuous analysis over sensor streams (e.g., C-SPARQL [
<xref rid="B69-sensors-16-00600" ref-type="bibr">69</xref>
], EP-SPARQL [
<xref rid="B70-sensors-16-00600" ref-type="bibr">70</xref>
], CQELS [
<xref rid="B71-sensors-16-00600" ref-type="bibr">71</xref>
]). CQELS provides a benchmark for continuous query and compares the results against C-SPARQL and ETALIS (EP-SPARQL). In [
<xref rid="B71-sensors-16-00600" ref-type="bibr">71</xref>
], it is reported that CQELS outperforms the others and its performance is stable during the experiment.</p>
<p>As the size of the streaming data is likely to be much larger than the size of the metadata of WoT objects, efficient search remains a challenge. The work in CQELS [
<xref rid="B71-sensors-16-00600" ref-type="bibr">71</xref>
] presents a promising approach for searching semantic streaming data, which is independent of the DSMS and has the potential to make use of the full capacity of semantic representation and reasoning. However, in the vision of the “Big Data”, the current efforts are far not enough. One of the trends is to leverage the recent development in big data processing platforms in designing search techniques for the big streaming data of WoT.</p>
</sec>
<sec id="sec7dot3-sensors-16-00600">
<title>7.3. The Content Perspective</title>
<p>From the review of the existing research, one can see that search techniques for Observation & Measurement data, sensors and entities tend to converge, especially for some WoT applications that need different ways to access data generated about the physical world. However, as the contents being searched are significantly different, we are not able to find any comprehensive evaluation for the methods under this category, which remains as a future research topic. The review also highlights the importance of the semantic models (in particular, the lightweight models) in knowledge representation. Besides the ontologies designed for sensors, the IoT Domain ontology provided in IoT-A Reference Model [
<xref rid="B103-sensors-16-00600" ref-type="bibr">103</xref>
] is becoming more and more popular and finds its application in diverse areas such as business process modelling [
<xref rid="B104-sensors-16-00600" ref-type="bibr">104</xref>
], dynamic association derivation between ICT and real-world objects [
<xref rid="B5-sensors-16-00600" ref-type="bibr">5</xref>
,
<xref rid="B105-sensors-16-00600" ref-type="bibr">105</xref>
], service discovery [
<xref rid="B41-sensors-16-00600" ref-type="bibr">41</xref>
,
<xref rid="B106-sensors-16-00600" ref-type="bibr">106</xref>
], service selection and ranking [
<xref rid="B107-sensors-16-00600" ref-type="bibr">107</xref>
] and test case derivation for IoT service lifecycle management [
<xref rid="B108-sensors-16-00600" ref-type="bibr">108</xref>
].</p>
<p>Current research on derivation of entity status mostly employs simple methods (e.g., to detect if a room is hot/cold for humans). The conclusion drawn from the sensor measurement data sometimes may be too coarse as the prediction methods do not take the differences of individual users or applications into consideration. The future research in entity and sensor search needs to look into the personalisation problem, which entails more sophisticated machine learning based methods. In particular, the research needs to pay more attention to the accuracy of the prediction, especially for time-critical applications.</p>
</sec>
</sec>
<sec id="sec8-sensors-16-00600">
<title>8. Outlook</title>
<p>The study presented in the previous sections shows that many techniques from different research fields, e.g., information retrieval, semantic Web, database, and knowledge management, have been applied to the development of search methods in WoT applications. The major differences between “search in the WoT” and “search on the Web” are well understood in most of the research works. The research community has also recognised the complex nature of the search problems in WoT, for instance, dynamicity of the things and data (while documents on the Web are relatively much more static); the uncertainty (while status of documents is relatively much more stable); spatial and temporal properties (while these are not the primary concern of Web documents). To address these problems, researchers have applied different techniques, such as semantic modelling and description, spatial indexing, federated and peer-to-peer search. However, these efforts are far from being sufficient, especially with the pressure of challenges of the overwhelming amount of data produced by the sensors and smart objects in the WoT. Obviously, the data produced on the WoT is a kind of big data. To this end, the following future research directions can be identified:</p>
<p>
<italic>Big Data Search</italic>
: the term is used to indicate the need for designing and developing more effective and efficient techniques for searching the big WoT data. Although the existing research has built solid frameworks for search services, it has not seriously taken into account the potential problems introduced by the volume, velocity and variety of the big data, which are compounded by the dynamicity of the WoT. For example, the MapReduce programming model, which is fundamental to the existing big data processing platforms such as Hadoop [
<xref rid="B109-sensors-16-00600" ref-type="bibr">109</xref>
] and SPARK [
<xref rid="B110-sensors-16-00600" ref-type="bibr">110</xref>
], requires that a computation task should be expressed as computing sums of functions over the whole dataset. This often involves a lot of repeated and frequent inter-machine communications. The input to the sum functions are a large number of key-value pairs in which the keys need to have fixed representations. However, this is not practical and extremely inefficient for applications in the WoT with high degree of dynamicity, e.g., the spatial and temporal properties and associated objects of a sensing device may change frequently, making it difficult or impossible to compute a key for the O&M data from that sensing device. To make the big WoT search more efficient, some of the existing underlying building blocks in searching the WoT infrastructure might need to be redesigned by leveraging the innovative technologies developed in the big data research. The complexity of searching big data lies in not only the design of search methods, but also the methods for distributed storage, abstraction, processing and analytics. This direction interleaves with other research directions, which are explained in the following.</p>
<p>
<italic>Distributed Intelligence</italic>
: it is not possible to collect all the information available on the WoT, build a centralised index and provide the search functionalities. This is fundamentally different to the development of Web search engines, in which most of the Web documents can be crawled and processed in a powerful, centralised data centre. The concept of distributed intelligence in this context implies a framework in which search functionalities are implemented on distributed, autonomous units that can cooperate to provide transparent search services to end users or applications. The most notable advantage is that each individual distributed unit applies intelligent processing mechanisms locally to hide the effects introduced by uncertain and dynamic factors pervasive in WoT. Another advantage is that after the distributed processing, quality of the data can be guaranteed (e.g., missing values can be estimated through regression analysis, data items can be ranked based on the local criteria, or inaccurate values can be eliminated) and volume of the data can be significantly reduced.</p>
<p>
<italic>Information Abstraction</italic>
: Besides providing search for entities and O&M data, future WoT search techniques may also support the search for abstract data objects, which encodes richer information in compact representation. Such abstraction can be implemented on different levels of a search system, for example, data from different sources can be aggregated based on the spatial or temporal dimensions to create high quality data series; missing values can be approximated by data collected from similar sources nearby. With proper inference techniques, information abstraction techniques can help extract patterns or events, which are useful for many data mining and machine learning algorithms, as well as for developing knowledge oriented search (
<italic>i.e.</italic>
, semantic search) functionalities.</p>
<p>
<italic>Personalisation</italic>
: many WoT applications, such as smart cities and smart home, are in line with the concept of human-centric computing. The ultimate objective of such applications is to provide intelligent assistance to human beings to make their life quality better. However, the current research is mainly intelligence-centric and pays less attention to the differences between each individual human user. Geographical information has been used to develop some sort of personalised, location-based search services in some of the existing research works (e.g., to constrain the search scope by searching restaurants within 500 m to the user’s location). However, more personalised search mechanisms need to be developed by exploiting not only the spatial information, but also temporal information and individual’s preferences. Furthermore, personalisation also allows automated adaptation of the search results without requiring users to explicitly specify the search criteria.</p>
</sec>
<sec id="sec9-sensors-16-00600">
<title>9. Conclusions</title>
<p>The complex nature of the WoT entails specialised search techniques for not only the physical or virtual “Things”, but also the data produced by those things. During the past few years, many techniques have been developed, covering a multitude of functionalities and dimensionalities. In this survey, a taxonomy for these existing techniques is defined, which allows the readers to gain a better picture of the research landscape. The state-of-the-art is reviewed and the existing techniques are compared from different viewpoints. The paper does not compare the search techniques through benchmark evaluations, due to the unavailability of benchmarks that can handle all kinds of search techniques included in this survey. The review is followed by a critical discussion on the current limitations, best practices as well as some of the lessons learned. The paper also proposes several promising future research directions under the emergent challenges of big data on the WoT. The study will benefit the research community in understanding the state-of-the-art on search techniques in WoT and gaining insights into the future research challenges and directions.</p>
</sec>
</body>
<back>
<ack>
<title>Acknowledgments</title>
<p>This work is supported by the collaborative European Union and Ministry of Internal Affairs and Communication (MIC), Japan, Research and Innovation action, ‘‘iKaaS” under EU Grant number 643262.</p>
</ack>
<notes>
<title>Author Contributions</title>
<p>All the authors were involved in designing the taxonomy as well as writing and reviewing this manuscript.</p>
</notes>
<notes>
<title>Conflicts of Interest</title>
<p>The authors declare no conflict of interest.</p>
</notes>
<glossary>
<title>Abbreviations</title>
<p>The following abbreviations are used in this manuscript:
<array>
<tbody>
<tr>
<td rowspan="1" colspan="1">AJAX</td>
<td rowspan="1" colspan="1">Asynchronous JavaScript and XML</td>
</tr>
<tr>
<td rowspan="1" colspan="1">APIs</td>
<td rowspan="1" colspan="1">Application Programming Interfaces</td>
</tr>
<tr>
<td rowspan="1" colspan="1">CoAP</td>
<td rowspan="1" colspan="1">Constrained Application Protocol</td>
</tr>
<tr>
<td rowspan="1" colspan="1">DNS</td>
<td rowspan="1" colspan="1">Domain Name System</td>
</tr>
<tr>
<td rowspan="1" colspan="1">DNS-SD</td>
<td rowspan="1" colspan="1">DNS Service Directory</td>
</tr>
<tr>
<td rowspan="1" colspan="1">DPWS</td>
<td rowspan="1" colspan="1">Devices Profile for Web Services</td>
</tr>
<tr>
<td rowspan="1" colspan="1">DSMS</td>
<td rowspan="1" colspan="1">Data Stream Management Systems</td>
</tr>
<tr>
<td rowspan="1" colspan="1">FUTS</td>
<td rowspan="1" colspan="1">Frequently Updated Timestamped and Structured</td>
</tr>
<tr>
<td rowspan="1" colspan="1">GSN</td>
<td rowspan="1" colspan="1">Global Sensor Networks</td>
</tr>
<tr>
<td rowspan="1" colspan="1">HTML</td>
<td rowspan="1" colspan="1">HyperText Markup Language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">HTTP</td>
<td rowspan="1" colspan="1">Hypertext Transfer Protocol</td>
</tr>
<tr>
<td rowspan="1" colspan="1">IoT</td>
<td rowspan="1" colspan="1">Internet of Things</td>
</tr>
<tr>
<td rowspan="1" colspan="1">JSI</td>
<td rowspan="1" colspan="1">Java Spatial Index</td>
</tr>
<tr>
<td rowspan="1" colspan="1">JSON</td>
<td rowspan="1" colspan="1">JavaScript Object Notation</td>
</tr>
<tr>
<td rowspan="1" colspan="1">LSM</td>
<td rowspan="1" colspan="1">Linked Sensor Middleware</td>
</tr>
<tr>
<td rowspan="1" colspan="1">O&M</td>
<td rowspan="1" colspan="1">Observation and Measurement</td>
</tr>
<tr>
<td rowspan="1" colspan="1">O&M-S</td>
<td rowspan="1" colspan="1">Semantically annotated O&M</td>
</tr>
<tr>
<td rowspan="1" colspan="1">OGC</td>
<td rowspan="1" colspan="1">Open Geospatial Consortium</td>
</tr>
<tr>
<td rowspan="1" colspan="1">OWL</td>
<td rowspan="1" colspan="1">Web Ontology Language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">OWL-DL</td>
<td rowspan="1" colspan="1">OWL- Description Logics</td>
</tr>
<tr>
<td rowspan="1" colspan="1">OWL-S</td>
<td rowspan="1" colspan="1">Semantic Markup for Web Services</td>
</tr>
<tr>
<td rowspan="1" colspan="1">P2P</td>
<td rowspan="1" colspan="1">Peer-to-Peer</td>
</tr>
<tr>
<td rowspan="1" colspan="1">RDB</td>
<td rowspan="1" colspan="1">Relational Database</td>
</tr>
<tr>
<td rowspan="1" colspan="1">RDB-to-RDF mapping language</td>
<td rowspan="1" colspan="1">R2RML language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">RDF</td>
<td rowspan="1" colspan="1">Resource Description Framework</td>
</tr>
<tr>
<td rowspan="1" colspan="1">RDFS</td>
<td rowspan="1" colspan="1">RDF Schema</td>
</tr>
<tr>
<td rowspan="1" colspan="1">REST</td>
<td rowspan="1" colspan="1">REpresentational State Transfer</td>
</tr>
<tr>
<td rowspan="1" colspan="1">RFID</td>
<td rowspan="1" colspan="1">Radio-Frequency IDentification</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SenML</td>
<td rowspan="1" colspan="1">Sensor Markup Language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SensorML</td>
<td rowspan="1" colspan="1">Sensor Model Language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SML-S</td>
<td rowspan="1" colspan="1">Semantically annotated SensorML</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SOAP</td>
<td rowspan="1" colspan="1">Simple Object Access Protocol</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SOS</td>
<td rowspan="1" colspan="1">Sensor Observation Service</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SPARQL</td>
<td rowspan="1" colspan="1">SPARQL Protocol And RDF Query Language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SQL</td>
<td rowspan="1" colspan="1">Structured Query Language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SSN</td>
<td rowspan="1" colspan="1">Semantic Sensor Network</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SSONs</td>
<td rowspan="1" colspan="1">Sensor Semantic Overlay Networks</td>
</tr>
<tr>
<td rowspan="1" colspan="1">SWE</td>
<td rowspan="1" colspan="1">Sensor Web Enablement</td>
</tr>
<tr>
<td rowspan="1" colspan="1">URIs</td>
<td rowspan="1" colspan="1">Uniform Resource Identifiers</td>
</tr>
<tr>
<td rowspan="1" colspan="1">URLs</td>
<td rowspan="1" colspan="1">Uniform Resource Locators</td>
</tr>
<tr>
<td rowspan="1" colspan="1">WADL</td>
<td rowspan="1" colspan="1">Web Application Description Language</td>
</tr>
<tr>
<td rowspan="1" colspan="1">WGS84</td>
<td rowspan="1" colspan="1">World Geodetic System 1984</td>
</tr>
<tr>
<td rowspan="1" colspan="1">WoT</td>
<td rowspan="1" colspan="1">Web of Things</td>
</tr>
<tr>
<td rowspan="1" colspan="1">XGSN</td>
<td rowspan="1" colspan="1">eXtended Global Sensor Networks</td>
</tr>
<tr>
<td rowspan="1" colspan="1">XML</td>
<td rowspan="1" colspan="1">eXtensible Markup Language</td>
</tr>
</tbody>
</array>
</p>
</glossary>
<ref-list>
<title>References</title>
<ref id="B1-sensors-16-00600">
<label>1.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Guinard</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Trifa</surname>
<given-names>V.</given-names>
</name>
</person-group>
<article-title>Towards the web of things: Web mashups for embedded devices</article-title>
<source>Proceedings of the International World Wide Web Conferences (WWW)</source>
<conf-loc>Madrid, Spain</conf-loc>
<conf-date>20–24 April 2009</conf-date>
</element-citation>
</ref>
<ref id="B2-sensors-16-00600">
<label>2.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zeng</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Guo</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Cheng</surname>
<given-names>Z.</given-names>
</name>
</person-group>
<article-title>The web of things: A survey</article-title>
<source>J. Commun.</source>
<year>2011</year>
<volume>6</volume>
<fpage>424</fpage>
<lpage>438</lpage>
<pub-id pub-id-type="doi">10.4304/jcm.6.6.424-438</pub-id>
</element-citation>
</ref>
<ref id="B3-sensors-16-00600">
<label>3.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Evans</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>The Internet of Things: How the Next Evolution of the Internet is Changing Everything</article-title>
<source>CISCO White Paper</source>
<publisher-name>CISCO</publisher-name>
<publisher-loc>San Jose, CA, USA</publisher-loc>
<year>2011</year>
</element-citation>
</ref>
<ref id="B4-sensors-16-00600">
<label>4.</label>
<element-citation publication-type="webpage">
<article-title>Internet of Things Architecture (IoT-A)</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.iot-a.eu/public">http://www.iot-a.eu/public</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B5-sensors-16-00600">
<label>5.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>De</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Christophe</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Moessner</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Semantic enablers for dynamic digital–physical object associations in a federated node architecture for the Internet of Things</article-title>
<source>Ad Hoc Netw.</source>
<year>2014</year>
<volume>18</volume>
<fpage>102</fpage>
<lpage>120</lpage>
<pub-id pub-id-type="doi">10.1016/j.adhoc.2013.02.003</pub-id>
</element-citation>
</ref>
<ref id="B6-sensors-16-00600">
<label>6.</label>
<element-citation publication-type="webpage">
<article-title>IoT@Work</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="https://www.iot-at-work.eu/">https://www.iot-at-work.eu/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B7-sensors-16-00600">
<label>7.</label>
<element-citation publication-type="webpage">
<article-title>Virtualized Programmable InTerfAces for Smart, Secure and Cost-Effective IoT depLoyments in Smart Cities (VITAL)</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://vital-iot.eu/project">http://vital-iot.eu/project</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B8-sensors-16-00600">
<label>8.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sun</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>Y.</given-names>
</name>
</person-group>
<article-title>Energy-Efficient Neighbor Discovery in Mobile Ad Hoc and Wireless Sensor Networks: A Survey</article-title>
<source>IEEE Commun. Surv. Tutor.</source>
<year>2014</year>
<volume>16</volume>
<fpage>1448</fpage>
<lpage>1459</lpage>
<pub-id pub-id-type="doi">10.1109/SURV.2013.012414.00164</pub-id>
</element-citation>
</ref>
<ref id="B9-sensors-16-00600">
<label>9.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pozza</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Nati</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Georgoulas</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Moessner</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Gluhak</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Neighbor Discovery for Opportunistic Networking in Internet of Things Scenarios: A Survey</article-title>
<source>IEEE Access</source>
<year>2015</year>
<volume>3</volume>
<fpage>1101</fpage>
<lpage>1131</lpage>
<pub-id pub-id-type="doi">10.1109/ACCESS.2015.2457031</pub-id>
</element-citation>
</ref>
<ref id="B10-sensors-16-00600">
<label>10.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Villaverde</surname>
<given-names>B.C.</given-names>
</name>
<name>
<surname>de Paz Alberola</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Jara</surname>
<given-names>A.J.</given-names>
</name>
<name>
<surname>Fedor</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Das</surname>
<given-names>S.K.</given-names>
</name>
<name>
<surname>Pesch</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>Service Discovery Protocols for Constrained Machine-to-Machine Communications</article-title>
<source>IEEE Commun. Surv. Tutor.</source>
<year>2014</year>
<volume>16</volume>
<fpage>41</fpage>
<lpage>60</lpage>
<pub-id pub-id-type="doi">10.1109/SURV.2013.102213.00229</pub-id>
</element-citation>
</ref>
<ref id="B11-sensors-16-00600">
<label>11.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Romer</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Ostermaier</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Mattern</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Fahrmair</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Kellerer</surname>
<given-names>W.</given-names>
</name>
</person-group>
<article-title>Real-Time Search for Real-World Entities: A Survey</article-title>
<source>Proc. IEEE</source>
<year>2010</year>
<volume>98</volume>
<fpage>1887</fpage>
<lpage>1902</lpage>
<pub-id pub-id-type="doi">10.1109/JPROC.2010.2062470</pub-id>
</element-citation>
</ref>
<ref id="B12-sensors-16-00600">
<label>12.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Bröring</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Echterhoff</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Jirka</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Simonis</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Everding</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Stasch</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Liang</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Lemmens</surname>
<given-names>R.</given-names>
</name>
</person-group>
<article-title>New Generation Sensor Web Enablement</article-title>
<source>Sensors</source>
<year>2011</year>
<volume>11</volume>
<fpage>2652</fpage>
<lpage>2699</lpage>
<pub-id pub-id-type="doi">10.3390/s110302652</pub-id>
<pub-id pub-id-type="pmid">22163760</pub-id>
</element-citation>
</ref>
<ref id="B13-sensors-16-00600">
<label>13.</label>
<element-citation publication-type="webpage">
<person-group person-group-type="author">
<collab>Open Geospatial Consortium</collab>
</person-group>
<article-title>OGC® SensorML: Model and XML Encoding Standard</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.opengeospatial.org/standards/sensorml">http://www.opengeospatial.org/standards/sensorml</ext-link>
</comment>
<date-in-citation>(accessed on 26 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B14-sensors-16-00600">
<label>14.</label>
<element-citation publication-type="webpage">
<person-group person-group-type="author">
<collab>Open Geospatial Consortium</collab>
</person-group>
<article-title>OpenGIS® Observations and Measurements—XML Implementation</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.opengeospatial.org/standards/om">http://www.opengeospatial.org/standards/om</ext-link>
</comment>
<date-in-citation>(accessed on 26 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B15-sensors-16-00600">
<label>15.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>L.T.</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>H.</given-names>
</name>
</person-group>
<article-title>Searching in Internet of Things: Vision and Challenges</article-title>
<source>Proceedings of 2011 IEEE 9th International Symposium on Parallel and Distributed Processing with Applications (ISPA)</source>
<conf-loc>Busan, Korea</conf-loc>
<conf-date>26–28 May 2011</conf-date>
</element-citation>
</ref>
<ref id="B16-sensors-16-00600">
<label>16.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Guinard</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>A Web of Things Application Architecture-Integrating the Real-World into the Web</article-title>
<source>Ph.D. Thesis</source>
<publisher-name>ETH Zurich</publisher-name>
<publisher-loc>Switzerland</publisher-loc>
<year>2011</year>
</element-citation>
</ref>
<ref id="B17-sensors-16-00600">
<label>17.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Fielding</surname>
<given-names>R.T.</given-names>
</name>
</person-group>
<article-title>Architectural Styles and the Design of Network-Based Software Architectures</article-title>
<source>Ph.D. Thesis</source>
<publisher-name>University of California</publisher-name>
<publisher-loc>Irvine, Irvine, CA, USA</publisher-loc>
<year>2000</year>
</element-citation>
</ref>
<ref id="B18-sensors-16-00600">
<label>18.</label>
<element-citation publication-type="webpage">
<person-group person-group-type="author">
<name>
<surname>Mockapetris</surname>
<given-names>P.</given-names>
</name>
</person-group>
<article-title>Domain Names—Concepts and Facilities</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="https://www.ietf.org/rfc/rfc1035.txt">https://www.ietf.org/rfc/rfc1035.txt</ext-link>
</comment>
<date-in-citation>(accessed on 26 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B19-sensors-16-00600">
<label>19.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Bormann</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Castellani</surname>
<given-names>A.P.</given-names>
</name>
<name>
<surname>Shelby</surname>
<given-names>Z.</given-names>
</name>
</person-group>
<article-title>Coap: An application protocol for billions of tiny internet nodes</article-title>
<source>IEEE Internet Comput.</source>
<year>2012</year>
<volume>16</volume>
<fpage>62</fpage>
<lpage>67</lpage>
<pub-id pub-id-type="doi">10.1109/MIC.2012.29</pub-id>
</element-citation>
</ref>
<ref id="B20-sensors-16-00600">
<label>20.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Coria</surname>
<given-names>J.A.G.</given-names>
</name>
<name>
<surname>Castellanos-Garzón</surname>
<given-names>J.A.</given-names>
</name>
<name>
<surname>Corchado</surname>
<given-names>J.M.</given-names>
</name>
</person-group>
<article-title>Intelligent business processes composition based on multi-agent systems</article-title>
<source>Expert Syst. Appl.</source>
<year>2014</year>
<volume>41</volume>
<fpage>1189</fpage>
<lpage>1205</lpage>
<pub-id pub-id-type="doi">10.1016/j.eswa.2013.08.003</pub-id>
</element-citation>
</ref>
<ref id="B21-sensors-16-00600">
<label>21.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wu</surname>
<given-names>C.-I.</given-names>
</name>
<name>
<surname>Kung</surname>
<given-names>H.-Y.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>C.-H.</given-names>
</name>
<name>
<surname>Kuo</surname>
<given-names>L.-C.</given-names>
</name>
</person-group>
<article-title>An intelligent slope disaster prediction and monitoring system based on WSN and ANP</article-title>
<source>Expert Syst. Appl.</source>
<year>2014</year>
<volume>41</volume>
<fpage>4554</fpage>
<lpage>4562</lpage>
<pub-id pub-id-type="doi">10.1016/j.eswa.2013.12.049</pub-id>
</element-citation>
</ref>
<ref id="B22-sensors-16-00600">
<label>22.</label>
<element-citation publication-type="webpage">
<article-title>Use Cases and Requirements for the Web of Things</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://w3c.github.io/wot/wot-ucr.html">http://w3c.github.io/wot/wot-ucr.html</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B23-sensors-16-00600">
<label>23.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wang</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>De</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Cassar</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Moessner</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>An Experimental Study on Geospatial Indexing for Sensor Service Discovery</article-title>
<source>Expert Syst. Appl.</source>
<year>2015</year>
<volume>42</volume>
<fpage>3528</fpage>
<lpage>3538</lpage>
<pub-id pub-id-type="doi">10.1016/j.eswa.2014.11.058</pub-id>
</element-citation>
</ref>
<ref id="B24-sensors-16-00600">
<label>24.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wang</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Yao</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>De</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Moessner</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Sun</surname>
<given-names>Z.</given-names>
</name>
</person-group>
<article-title>A ranking method for sensor services based on estimation of service access cost</article-title>
<source>Inf. Sci.</source>
<year>2015</year>
<volume>319</volume>
<fpage>1</fpage>
<lpage>17</lpage>
<pub-id pub-id-type="doi">10.1016/j.ins.2015.05.029</pub-id>
</element-citation>
</ref>
<ref id="B25-sensors-16-00600">
<label>25.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Aberer</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Hauswirth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Salehi</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Infrastructure for data processing in large-scale interconnected sensor networks</article-title>
<source>Proceedings of the 2007 International Conference on Mobile Data Management</source>
<conf-loc>Mannheim, Germany</conf-loc>
<conf-date>7–11 May 2007</conf-date>
</element-citation>
</ref>
<ref id="B26-sensors-16-00600">
<label>26.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Calbimonte</surname>
<given-names>J.-P.</given-names>
</name>
<name>
<surname>Sarni</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Eberle</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Aberer</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>XGSN: An open-source semantic sensing middleware for the web of things</article-title>
<source>Proceedings of the 7th International Workshop on Semantic Sensor Networks</source>
<conf-loc>Riva del Garda, Italy</conf-loc>
<conf-date>19–23 October 2014</conf-date>
</element-citation>
</ref>
<ref id="B27-sensors-16-00600">
<label>27.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Le-Phuoc</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Nguyen-Mau</surname>
<given-names>H.Q.</given-names>
</name>
<name>
<surname>Parreira</surname>
<given-names>J.X.</given-names>
</name>
<name>
<surname>Hauswirth</surname>
<given-names>M.</given-names>
</name>
</person-group>
<article-title>A middleware framework for scalable management of linked streams</article-title>
<source>Web Semantics Sci. Ser. Agents World Wide Web</source>
<year>2012</year>
<volume>16</volume>
<fpage>42</fpage>
<lpage>51</lpage>
<pub-id pub-id-type="doi">10.1016/j.websem.2012.06.003</pub-id>
</element-citation>
</ref>
<ref id="B28-sensors-16-00600">
<label>28.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Soldatos</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Kefalakis</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Hauswirth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Serrano</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Calbimonte</surname>
<given-names>J.-P.</given-names>
</name>
<name>
<surname>Riahi</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Aberer</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Jayaraman</surname>
<given-names>P.P.</given-names>
</name>
<name>
<surname>Zaslavsky</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Žarko</surname>
<given-names>I.P.</given-names>
</name>
<etal></etal>
</person-group>
<article-title>OpenIoT: Open Source Internet-of-Things in the Cloud</article-title>
<source>Interoperability and Open-Source Solutions for the Internet of Things</source>
<person-group person-group-type="editor">
<name>
<surname>Podnar Žarko</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Pripužić</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Serrano</surname>
<given-names>M.</given-names>
</name>
</person-group>
<publisher-name>Springer International Publishing</publisher-name>
<publisher-loc>Cham, Switzerland</publisher-loc>
<year>2015</year>
<fpage>13</fpage>
<lpage>25</lpage>
</element-citation>
</ref>
<ref id="B29-sensors-16-00600">
<label>29.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kansal</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Nath</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Jie</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Feng</surname>
<given-names>Z.</given-names>
</name>
</person-group>
<article-title>SenseWeb: An Infrastructure for Shared Sensing</article-title>
<source>IEEE MultiMed.</source>
<year>2007</year>
<volume>14</volume>
<fpage>8</fpage>
<lpage>13</lpage>
<pub-id pub-id-type="doi">10.1109/MMUL.2007.82</pub-id>
</element-citation>
</ref>
<ref id="B30-sensors-16-00600">
<label>30.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Ostermaier</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Romer</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Mattern</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Fahrmair</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Kellerer</surname>
<given-names>W.</given-names>
</name>
</person-group>
<article-title>A real-time search engine for the web of things</article-title>
<source>Proceedings of the IEEE Internet of Things (IOT)</source>
<conf-loc>Tokyo, Japan</conf-loc>
<conf-date>29 November–1 December 2010</conf-date>
</element-citation>
</ref>
<ref id="B31-sensors-16-00600">
<label>31.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Tan</surname>
<given-names>C.C.</given-names>
</name>
<name>
<surname>Sheng</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>Q.</given-names>
</name>
</person-group>
<article-title>Microsearch: A search engine for embedded devices used in pervasive computing</article-title>
<source>ACM Trans. Embed. Comput. Syst.</source>
<year>2010</year>
<volume>9</volume>
<fpage>1</fpage>
<lpage>29</lpage>
<pub-id pub-id-type="doi">10.1145/1721695.1721709</pub-id>
</element-citation>
</ref>
<ref id="B32-sensors-16-00600">
<label>32.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wang</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Tan</surname>
<given-names>C.C.</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>Q.</given-names>
</name>
</person-group>
<article-title>Snoogle: A Search Engine for Pervasive Environments</article-title>
<source>IEEE Trans. Parallel Distrib. Syst.</source>
<year>2010</year>
<volume>21</volume>
<fpage>1188</fpage>
<lpage>1202</lpage>
<pub-id pub-id-type="doi">10.1109/TPDS.2009.145</pub-id>
</element-citation>
</ref>
<ref id="B33-sensors-16-00600">
<label>33.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yang</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Song</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>De</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>LiveWeb: A Sensorweb Portal for Sensing the World in Real-Time</article-title>
<source>Tsinghua Sci. Technol.</source>
<year>2011</year>
<volume>16</volume>
<fpage>491</fpage>
<lpage>504</lpage>
<pub-id pub-id-type="doi">10.1016/S1007-0214(11)70068-2</pub-id>
</element-citation>
</ref>
<ref id="B34-sensors-16-00600">
<label>34.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Jara</surname>
<given-names>A.J.</given-names>
</name>
<name>
<surname>Martinez-Julia</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Skarmeta</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Light-weight multicast DNS and DNS-SD (lmDNS-SD): IPv6-based resource and service discovery for the Web of Things</article-title>
<source>Proceedings of the Sixth IEEE International Conference on Innovative Mobile and Internet Services in Ubiquitous Computing (IMIS)</source>
<conf-loc>Palermo, Italy</conf-loc>
<conf-date>4–6 July 2012</conf-date>
</element-citation>
</ref>
<ref id="B35-sensors-16-00600">
<label>35.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Kamilaris</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Papakonstantinou</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Pitsillides</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Exploring the Use of DNS as a Search Engine for the Web of Things</article-title>
<source>Proceedings of the 2014 IEEE World Forum on Internet of Things (WF-IoT)</source>
<conf-loc>Seoul, Korea</conf-loc>
<conf-date>6–8 March 2014</conf-date>
</element-citation>
</ref>
<ref id="B36-sensors-16-00600">
<label>36.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Jara</surname>
<given-names>A.J.</given-names>
</name>
<name>
<surname>Lopez</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Fernandez</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Castillo</surname>
<given-names>J.F.</given-names>
</name>
<name>
<surname>Zamora</surname>
<given-names>M.A.</given-names>
</name>
<name>
<surname>Skarmeta</surname>
<given-names>A.F.</given-names>
</name>
</person-group>
<article-title>Mobile digcovery: Discovering and interacting with the world through the Internet of Things</article-title>
<source>Pers. Ubiquitous Comput.</source>
<year>2014</year>
<volume>18</volume>
<fpage>323</fpage>
<lpage>338</lpage>
<pub-id pub-id-type="doi">10.1007/s00779-013-0648-0</pub-id>
</element-citation>
</ref>
<ref id="B37-sensors-16-00600">
<label>37.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ding</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>Q.</given-names>
</name>
</person-group>
<article-title>IoT-SVKSearch: A real-time multimodal search engine mechanism for the internet of things</article-title>
<source>Int. J. Commun. Syst.</source>
<year>2014</year>
<volume>27</volume>
<fpage>871</fpage>
<lpage>897</lpage>
<pub-id pub-id-type="doi">10.1002/dac.2647</pub-id>
</element-citation>
</ref>
<ref id="B38-sensors-16-00600">
<label>38.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Jirka</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Bröring</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Stasch</surname>
<given-names>C.</given-names>
</name>
</person-group>
<article-title>Discovery mechanisms for the sensor web</article-title>
<source>Sensors</source>
<year>2009</year>
<volume>9</volume>
<fpage>2661</fpage>
<lpage>2681</lpage>
<pub-id pub-id-type="doi">10.3390/s90402661</pub-id>
<pub-id pub-id-type="pmid">22574038</pub-id>
</element-citation>
</ref>
<ref id="B39-sensors-16-00600">
<label>39.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Nath</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Zhao</surname>
<given-names>F.</given-names>
</name>
</person-group>
<article-title>Sensormap for wide-area sensor webs</article-title>
<source>Computer</source>
<year>2007</year>
<volume>40</volume>
<fpage>90</fpage>
<lpage>93</lpage>
<pub-id pub-id-type="doi">10.1109/MC.2007.250</pub-id>
</element-citation>
</ref>
<ref id="B40-sensors-16-00600">
<label>40.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Liang</surname>
<given-names>S.H.</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>C.-Y.</given-names>
</name>
</person-group>
<article-title>GeoCENS: A Geospatial Cyberinfrastructure for the World-Wide Sensor Web</article-title>
<source>Sensors</source>
<year>2013</year>
<volume>13</volume>
<fpage>13402</fpage>
<lpage>13424</lpage>
<pub-id pub-id-type="doi">10.3390/s131013402</pub-id>
<pub-id pub-id-type="pmid">24152921</pub-id>
</element-citation>
</ref>
<ref id="B41-sensors-16-00600">
<label>41.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Bauer</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Longo</surname>
<given-names>S.</given-names>
</name>
</person-group>
<article-title>Geographic Service Discovery for the Internet of Things</article-title>
<source>Ubiquitous Computing and Ambient Intelligence. Personalisation and User Adapted Services</source>
<person-group person-group-type="editor">
<name>
<surname>Hervás</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Nugent</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Bravo</surname>
<given-names>J.</given-names>
</name>
</person-group>
<publisher-name>Springer International Publishing</publisher-name>
<publisher-loc>Cham, Switzerland</publisher-loc>
<year>2014</year>
<fpage>424</fpage>
<lpage>431</lpage>
</element-citation>
</ref>
<ref id="B42-sensors-16-00600">
<label>42.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Zhou</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>De</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Moessner</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Enabling Query of Frequently Updated Data from Mobile Sensing Sources</article-title>
<source>Proceedings of 13th IEEE International Conference on Ubiquitous Computing and Communications (IUCC 2014)</source>
<conf-loc>Chengdu, China</conf-loc>
<conf-date>19–21 December 2014</conf-date>
</element-citation>
</ref>
<ref id="B43-sensors-16-00600">
<label>43.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>De</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Elsaleh</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Barnaghi</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Meissner</surname>
<given-names>S.</given-names>
</name>
</person-group>
<article-title>An Internet of Things Platform for Real-World and Digital Objects</article-title>
<source>J. Scalable Comput. Pract. Exp.</source>
<year>2012</year>
<volume>13</volume>
<fpage>45</fpage>
<lpage>57</lpage>
</element-citation>
</ref>
<ref id="B44-sensors-16-00600">
<label>44.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Barnaghi</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Dong</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>C.</given-names>
</name>
</person-group>
<article-title>A Linked-Data Model for Semantic Sensor Streams</article-title>
<source>Proceedings of Green Computing and Communications (GreenCom), 2013 IEEE and Internet of Things (iThings/CPSCom), IEEE International Conference on and IEEE Cyber, Physical and Social Computing</source>
<conf-loc>Beijing, China</conf-loc>
<conf-date>20–23 August 2013</conf-date>
</element-citation>
</ref>
<ref id="B45-sensors-16-00600">
<label>45.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Fredj</surname>
<given-names>S.B.</given-names>
</name>
<name>
<surname>Boussard</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Kofman</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Noirie</surname>
<given-names>L.</given-names>
</name>
</person-group>
<article-title>A Scalable IoT Service Search Based on Clustering and Aggregation</article-title>
<source>Proceedings of Green Computing and Communications (GreenCom), 2013 IEEE and Internet of Things (iThings/CPSCom), IEEE International Conference on and IEEE Cyber, Physical and Social Computing</source>
<conf-loc>Beijing, China</conf-loc>
<conf-date>20–23 August 2013</conf-date>
</element-citation>
</ref>
<ref id="B46-sensors-16-00600">
<label>46.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Mayer</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Guinard</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Trifa</surname>
<given-names>V.</given-names>
</name>
</person-group>
<article-title>Searching in a web-based infrastructure for smart things</article-title>
<source>Proceedings of the 3rd International Conference on the Internet of Things (IoT 2012)</source>
<conf-loc>Wuxi, China</conf-loc>
<conf-date>24–26 October 2012</conf-date>
</element-citation>
</ref>
<ref id="B47-sensors-16-00600">
<label>47.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Timpner</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Schurmann</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Wolf</surname>
<given-names>L.</given-names>
</name>
</person-group>
<article-title>Trustworthy Parking Communities: Helping Your Neighbor to Find a Space</article-title>
<source>IEEE Trans. Dependable Secur. Comput.</source>
<year>2016</year>
<volume>13</volume>
<fpage>120</fpage>
<lpage>132</lpage>
<pub-id pub-id-type="doi">10.1109/TDSC.2015.2427838</pub-id>
</element-citation>
</ref>
<ref id="B48-sensors-16-00600">
<label>48.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Timpner</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Wolf</surname>
<given-names>L.</given-names>
</name>
</person-group>
<article-title>Query-response geocast for vehicular crowd sensing</article-title>
<source>Ad Hoc Netw.</source>
<year>2016</year>
<volume>36</volume>
<fpage>435</fpage>
<lpage>449</lpage>
<pub-id pub-id-type="doi">10.1016/j.adhoc.2015.06.003</pub-id>
</element-citation>
</ref>
<ref id="B49-sensors-16-00600">
<label>49.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Ahulló</surname>
<given-names>J.P.</given-names>
</name>
<name>
<surname>López</surname>
<given-names>P.G.</given-names>
</name>
<name>
<surname>Artigas</surname>
<given-names>M.S.</given-names>
</name>
<name>
<surname>Skarmeta</surname>
<given-names>A.F.G.</given-names>
</name>
</person-group>
<article-title>Supporting geographical queries onto DHTs</article-title>
<source>Proceedings of Local Computer Networks, 2008. LCN 2008. 33rd IEEE Conference on</source>
<conf-loc>Montreal, Que, Canada</conf-loc>
<conf-date>14–17 October 2008</conf-date>
</element-citation>
</ref>
<ref id="B50-sensors-16-00600">
<label>50.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Christophe</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Verdot</surname>
<given-names>V.</given-names>
</name>
<name>
<surname>Toubiana</surname>
<given-names>V.</given-names>
</name>
</person-group>
<article-title>Searching the ‘Web of Things’</article-title>
<source>Proceedings of the 2011 Fifth IEEE International Conference on Semantic Computing (ICSC)</source>
<conf-loc>Palo Alto, CA, USA</conf-loc>
<conf-date>18–21 September 2011</conf-date>
</element-citation>
</ref>
<ref id="B51-sensors-16-00600">
<label>51.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Du</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Zhou</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Shu</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Jia</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>Q.</given-names>
</name>
</person-group>
<article-title>An Effective IoT Services Indexing and Query Technique</article-title>
<source>Proceedings of the 2013 IEEE and Internet of Things (iThings/CPSCom), IEEE International Conference on and IEEE Cyber, Physical and Social Computing</source>
<conf-loc>Beijing, China</conf-loc>
<conf-date>20–23 August 2013</conf-date>
</element-citation>
</ref>
<ref id="B52-sensors-16-00600">
<label>52.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ebrahimi</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>ShafieiBavani</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Wong</surname>
<given-names>R.K.</given-names>
</name>
<name>
<surname>Fong</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Fiaidhi</surname>
<given-names>J.</given-names>
</name>
</person-group>
<article-title>An adaptive meta-heuristic search for the internet of things</article-title>
<source>Future Gener. Comput. Syst.</source>
<year>2015</year>
<pub-id pub-id-type="doi">10.1016/j.future.2015.12.006</pub-id>
</element-citation>
</ref>
<ref id="B53-sensors-16-00600">
<label>53.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Patni</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Henson</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Sheth</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Linked sensor data</article-title>
<source>Proceedings of the 2010 International Symposium on Collaborative Technologies and Systems (CTS)</source>
<conf-loc>Chicago, IL, USA</conf-loc>
<conf-date>17–21 May 2010</conf-date>
</element-citation>
</ref>
<ref id="B54-sensors-16-00600">
<label>54.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Chun</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Seo</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Oh</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>K.-H.</given-names>
</name>
</person-group>
<article-title>Semantic description, discovery and integration for the Internet of Things</article-title>
<source>Proceedings of the 2015 IEEE International Conference on Semantic Computing (ICSC)</source>
<conf-loc>Anaheim, CA, USA</conf-loc>
<conf-date>7–9 February 2015</conf-date>
</element-citation>
</ref>
<ref id="B55-sensors-16-00600">
<label>55.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Henson</surname>
<given-names>C.A.</given-names>
</name>
<name>
<surname>Pschorr</surname>
<given-names>J.K.</given-names>
</name>
<name>
<surname>Sheth</surname>
<given-names>A.P.</given-names>
</name>
<name>
<surname>Thirunarayan</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>SemSOS: Semantic sensor observation service</article-title>
<source>Proceedings of the International Symposium on Collaborative Technologies and Systems, 2009. CTS’09</source>
<conf-loc>Baltimore, MD, USA</conf-loc>
<conf-date>18–22 May 2009</conf-date>
</element-citation>
</ref>
<ref id="B56-sensors-16-00600">
<label>56.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Pschorr</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Henson</surname>
<given-names>C.A.</given-names>
</name>
<name>
<surname>Patni</surname>
<given-names>H.K.</given-names>
</name>
<name>
<surname>Sheth</surname>
<given-names>A.P.</given-names>
</name>
</person-group>
<source>Sensor discovery on linked data</source>
<publisher-name>The Ohio Center of Excellence in Knowledge-Enabled Computing (Kno.e.sis), Wright State University</publisher-name>
<publisher-loc>Dayton, OH, USA</publisher-loc>
<year>2010</year>
</element-citation>
</ref>
<ref id="B57-sensors-16-00600">
<label>57.</label>
<element-citation publication-type="webpage">
<article-title>LinkedGeoData</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://linkedgeodata.org/About">http://linkedgeodata.org/About</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B58-sensors-16-00600">
<label>58.</label>
<element-citation publication-type="webpage">
<article-title>Virtuoso SPARQL Query Editor—LinkedGeoData</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://linkedgeodata.org/sparql">http://linkedgeodata.org/sparql</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B59-sensors-16-00600">
<label>59.</label>
<element-citation publication-type="webpage">
<article-title>OWLIM-SE Geo-spatial Extensions</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="https://confluence.ontotext.com/display/OWLIMv54/OWLIM-SE+Geo-spatial+Extensions">https://confluence.ontotext.com/display/OWLIMv54/OWLIM-SE+Geo-spatial+Extensions</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B60-sensors-16-00600">
<label>60.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Battle</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Kolas</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>Enabling the geospatial Semantic Web with Parliament and GeoSPARQL</article-title>
<source>Semantic Web</source>
<year>2012</year>
<volume>3</volume>
<fpage>355</fpage>
<lpage>370</lpage>
</element-citation>
</ref>
<ref id="B61-sensors-16-00600">
<label>61.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Quilitz</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Leser</surname>
<given-names>U.</given-names>
</name>
</person-group>
<article-title>Querying Distributed RDF Data Sources with SPARQL</article-title>
<source>The Semantic Web: Research and Applications</source>
<person-group person-group-type="editor">
<name>
<surname>Bechhofer</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Hauswirth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Hoffmann</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Koubarakis</surname>
<given-names>M.</given-names>
</name>
</person-group>
<publisher-name>Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Heidelberg, Germany</publisher-loc>
<year>2008</year>
<fpage>524</fpage>
<lpage>538</lpage>
</element-citation>
</ref>
<ref id="B62-sensors-16-00600">
<label>62.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Acosta</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Vidal</surname>
<given-names>M.-E.</given-names>
</name>
<name>
<surname>Lampo</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Castillo</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Ruckhaus</surname>
<given-names>E.</given-names>
</name>
</person-group>
<article-title>ANAPSID: An Adaptive Query Processing Engine for SPARQL Endpoints</article-title>
<source>The Semantic Web – ISWC 2011</source>
<person-group person-group-type="editor">
<name>
<surname>Aroyo</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Welty</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Alani</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Taylor</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Bernstein</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Kagal</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Noy</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Blomqvist</surname>
<given-names>E.</given-names>
</name>
</person-group>
<publisher-name>Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Heidelberg, Germany</publisher-loc>
<year>2011</year>
<fpage>18</fpage>
<lpage>34</lpage>
</element-citation>
</ref>
<ref id="B63-sensors-16-00600">
<label>63.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Görlitz</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Staab</surname>
<given-names>S.</given-names>
</name>
</person-group>
<article-title>SPLENDID: SPARQL Endpoint Federation Exploiting VOID Descriptions</article-title>
<source>The Second International Conference on Consuming Linked Data</source>
<publisher-name>CEUR-WS.org</publisher-name>
<publisher-loc>Bonn, Germany</publisher-loc>
<year>2011</year>
<volume>Vol. 782</volume>
<fpage>13</fpage>
<lpage>24</lpage>
</element-citation>
</ref>
<ref id="B64-sensors-16-00600">
<label>64.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Schwarte</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Haase</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Hose</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Schenkel</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Schmidt</surname>
<given-names>M.</given-names>
</name>
</person-group>
<article-title>FedX: Optimization Techniques for Federated Query Processing on Linked Data</article-title>
<source>The Semantic Web – ISWC 2011</source>
<publisher-name>Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Heidelberg, Germany</publisher-loc>
<year>2011</year>
<fpage>601</fpage>
<lpage>616</lpage>
</element-citation>
</ref>
<ref id="B65-sensors-16-00600">
<label>65.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Zhou</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>De</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Moessner</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Implementation of federated query processing on Linked Data</article-title>
<source>Proceedings of the IEEE 24th International Symposium on Personal Indoor and Mobile Radio Communications (PIMRC), 2013</source>
<conf-loc>London, UK</conf-loc>
<conf-date>8–11 September 2013</conf-date>
</element-citation>
</ref>
<ref id="B66-sensors-16-00600">
<label>66.</label>
<element-citation publication-type="webpage">
<article-title>SPARQL 1.1 Federated Query</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.w3.org/TR/sparql11-federated-query/">http://www.w3.org/TR/sparql11-federated-query/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B67-sensors-16-00600">
<label>67.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Buil-Aranda</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Arenas</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Corcho</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Polleres</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Federating queries in SPARQL 1.1: Syntax, semantics and evaluation</article-title>
<source>Web Semantics Sci. Ser. Agents World Wide Web</source>
<year>2013</year>
<volume>18</volume>
<fpage>1</fpage>
<lpage>17</lpage>
<pub-id pub-id-type="doi">10.1016/j.websem.2012.10.001</pub-id>
</element-citation>
</ref>
<ref id="B68-sensors-16-00600">
<label>68.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Calbimonte</surname>
<given-names>J.-P.</given-names>
</name>
<name>
<surname>Jeung</surname>
<given-names>H.Y.</given-names>
</name>
<name>
<surname>Corcho</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Aberer</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Enabling Query Technologies for the Semantic Sensor Web</article-title>
<source>Int. J. Semant. Web Inf. Syst.</source>
<year>2012</year>
<volume>8</volume>
<fpage>43</fpage>
<lpage>63</lpage>
<pub-id pub-id-type="doi">10.4018/jswis.2012010103</pub-id>
</element-citation>
</ref>
<ref id="B69-sensors-16-00600">
<label>69.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Barbieri</surname>
<given-names>D.F.</given-names>
</name>
<name>
<surname>Braga</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Ceri</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Valle</surname>
<given-names>E.D.</given-names>
</name>
<name>
<surname>Grossniklaus</surname>
<given-names>M.</given-names>
</name>
</person-group>
<article-title>C-SPARQL: A Continuous Query Language for RDF Data Streams</article-title>
<source>Int. J. Semant. Comput.</source>
<year>2010</year>
<volume>4</volume>
<fpage>3</fpage>
<lpage>25</lpage>
<pub-id pub-id-type="doi">10.1142/S1793351X10000936</pub-id>
</element-citation>
</ref>
<ref id="B70-sensors-16-00600">
<label>70.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Anicic</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Fodor</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Rudolph</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Stojanovic</surname>
<given-names>N.</given-names>
</name>
</person-group>
<article-title>EP-SPARQL: a unified language for event processing and stream reasoning</article-title>
<source>Proceedings of the 20th international conference on World wide web</source>
<conf-loc>Hyderabad, India</conf-loc>
<conf-date>28 March–1 April 2011</conf-date>
</element-citation>
</ref>
<ref id="B71-sensors-16-00600">
<label>71.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Le-Phuoc</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Dao-Tran</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Parreira</surname>
<given-names>J.X.</given-names>
</name>
<name>
<surname>Hauswirth</surname>
<given-names>M.</given-names>
</name>
</person-group>
<article-title>A Native and Adaptive Approach for Unified Processing of Linked Streams and Linked Data</article-title>
<source>The Semantic Web – ISWC 2011</source>
<publisher-name>Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Heidelberg, Germany</publisher-loc>
<year>2011</year>
<fpage>370</fpage>
<lpage>388</lpage>
</element-citation>
</ref>
<ref id="B72-sensors-16-00600">
<label>72.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Shin</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Eom</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>K.-H.</given-names>
</name>
</person-group>
<article-title>Q-ASSF: Query-adaptive semantic stream filtering</article-title>
<source>Proceedings of the IEEE International Conference on Semantic Computing (ICSC), 2015</source>
<conf-loc>Anaheim, CA, USA</conf-loc>
<conf-date>7–9 February 2015</conf-date>
</element-citation>
</ref>
<ref id="B73-sensors-16-00600">
<label>73.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Perera</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Zaslavsky</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>C.H.</given-names>
</name>
<name>
<surname>Compton</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Christen</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Georgakopoulos</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>Sensor Search Techniques for Sensing as a Service Architecture for the Internet of Things</article-title>
<source>IEEE Sens. J.</source>
<year>2014</year>
<volume>14</volume>
<fpage>406</fpage>
<lpage>420</lpage>
<pub-id pub-id-type="doi">10.1109/JSEN.2013.2282292</pub-id>
</element-citation>
</ref>
<ref id="B74-sensors-16-00600">
<label>74.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Shah</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Sardana</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Searching in internet of things using VCS</article-title>
<source>Proceedings of the First International Conference on Security of Internet of Things</source>
<conf-loc>Kollam, India</conf-loc>
<conf-date>17–19 August 2012</conf-date>
</element-citation>
</ref>
<ref id="B75-sensors-16-00600">
<label>75.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pfisterer</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Romer</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Bimschas</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Kleine</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Mietz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Truong</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Hasemann</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Kroller</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Pagel</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Hauswirth</surname>
<given-names>M.</given-names>
</name>
</person-group>
<article-title>SPITFIRE: toward a semantic web of things</article-title>
<source>IEEE Commun. Mag.</source>
<year>2011</year>
<volume>49</volume>
<fpage>40</fpage>
<lpage>48</lpage>
<pub-id pub-id-type="doi">10.1109/MCOM.2011.6069708</pub-id>
</element-citation>
</ref>
<ref id="B76-sensors-16-00600">
<label>76.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Truong</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Romer</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Fuzzy-based sensor search in the web of things</article-title>
<source>Proceedings of the 3rd International Conference on the Internet of Things (IOT), 2012</source>
<conf-loc>Wuxi, China</conf-loc>
<conf-date>24–26 October 2012</conf-date>
</element-citation>
</ref>
<ref id="B77-sensors-16-00600">
<label>77.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Elahi</surname>
<given-names>B.M.</given-names>
</name>
<name>
<surname>Romer</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Ostermaier</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Fahrmair</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Kellerer</surname>
<given-names>W.</given-names>
</name>
</person-group>
<article-title>Sensor ranking: A primitive for efficient content-based sensor search</article-title>
<source>Proceedings of the 2009 international conference on information processing in sensor networks</source>
<conf-loc>San Francisco, CA, USA</conf-loc>
<conf-date>13–16 April 2009</conf-date>
</element-citation>
</ref>
<ref id="B78-sensors-16-00600">
<label>78.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Michel</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Julien</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Payton</surname>
<given-names>J.</given-names>
</name>
</person-group>
<article-title>Gander: Mobile, Pervasive Search
<italic>of</italic>
the Here and Now
<italic>in</italic>
the Here and Now</article-title>
<source>IEEE Internet Things J.</source>
<year>2014</year>
<volume>1</volume>
<fpage>483</fpage>
<lpage>496</lpage>
<pub-id pub-id-type="doi">10.1109/JIOT.2014.2347132</pub-id>
</element-citation>
</ref>
<ref id="B79-sensors-16-00600">
<label>79.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Qian</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Che</surname>
<given-names>X.</given-names>
</name>
</person-group>
<article-title>Security-enhanced Search Engine Design in Internet of Things</article-title>
<source>J. UCS</source>
<year>2012</year>
<volume>18</volume>
<fpage>1218</fpage>
<lpage>1235</lpage>
</element-citation>
</ref>
<ref id="B80-sensors-16-00600">
<label>80.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Mietz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Romer</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Exploiting correlations for efficient content-based sensor search</article-title>
<source>Proceedings of the 2011 IEEE Sensors</source>
<conf-loc>Limerick, Ireland</conf-loc>
<conf-date>28–31 October 2011</conf-date>
</element-citation>
</ref>
<ref id="B81-sensors-16-00600">
<label>81.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Mayer</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Guinard</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>An extensible discovery service for smart things</article-title>
<source>Proceedings of the Second International Workshop on Web of Things</source>
<conf-loc>San Francisco, CA, USA</conf-loc>
<conf-date>12–15 June 2011</conf-date>
</element-citation>
</ref>
<ref id="B82-sensors-16-00600">
<label>82.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Comer</surname>
<given-names>D.</given-names>
</name>
</person-group>
<article-title>Ubiquitous B-tree</article-title>
<source>ACM Comput. Surv. (CSUR)</source>
<year>1979</year>
<volume>11</volume>
<fpage>121</fpage>
<lpage>137</lpage>
<pub-id pub-id-type="doi">10.1145/356770.356776</pub-id>
</element-citation>
</ref>
<ref id="B83-sensors-16-00600">
<label>83.</label>
<element-citation publication-type="webpage">
<article-title>HyperCat Specification v2.01</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.hypercat.io/standard.html">http://www.hypercat.io/standard.html</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B84-sensors-16-00600">
<label>84.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Guttman</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>R-trees: A dynamic index structure for spatial searching</article-title>
<source>SIGMOD Rec.</source>
<year>1984</year>
<volume>14</volume>
<fpage>47</fpage>
<lpage>57</lpage>
<pub-id pub-id-type="doi">10.1145/971697.602266</pub-id>
</element-citation>
</ref>
<ref id="B85-sensors-16-00600">
<label>85.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Navas</surname>
<given-names>J.C.</given-names>
</name>
<name>
<surname>Imielinski</surname>
<given-names>T.</given-names>
</name>
</person-group>
<article-title>GeoCast—Geographic addressing and routing</article-title>
<source>Proceedings of the 3rd Annual ACM/IEEE International Conference on Mobile Computing and Networking</source>
<conf-loc>Budapest, Hungary</conf-loc>
<conf-date>26–30 September 1997</conf-date>
</element-citation>
</ref>
<ref id="B86-sensors-16-00600">
<label>86.</label>
<element-citation publication-type="webpage">
<article-title>Resource Description Framework (RDF)</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.w3.org/RDF/">http://www.w3.org/RDF/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B87-sensors-16-00600">
<label>87.</label>
<element-citation publication-type="webpage">
<article-title>SPARQL Query Language for RDF</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.w3.org/TR/rdf-sparql-query/">http://www.w3.org/TR/rdf-sparql-query/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B88-sensors-16-00600">
<label>88.</label>
<element-citation publication-type="webpage">
<article-title>Linked Data—Design Issues</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.w3.org/DesignIssues/LinkedData.html">http://www.w3.org/DesignIssues/LinkedData.html</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B89-sensors-16-00600">
<label>89.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Taylor</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Parsons</surname>
<given-names>E.</given-names>
</name>
</person-group>
<article-title>Where Is Everywhere: Bringing Location to the Web</article-title>
<source>IEEE Internet Comput.</source>
<year>2015</year>
<volume>19</volume>
<fpage>83</fpage>
<lpage>87</lpage>
<pub-id pub-id-type="doi">10.1109/MIC.2015.50</pub-id>
</element-citation>
</ref>
<ref id="B90-sensors-16-00600">
<label>90.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<collab>NIMA</collab>
</person-group>
<article-title>Department of Defense World Geodetic System 1984, Its Definition and Relationships With Local Geodetic Systems</article-title>
<source>NIMA TR8350.2</source>
<publisher-name>National Imagery and Mapping Agency</publisher-name>
<publisher-loc>Springfield, VA, USA</publisher-loc>
<year>2000</year>
</element-citation>
</ref>
<ref id="B91-sensors-16-00600">
<label>91.</label>
<element-citation publication-type="webpage">
<article-title>OpenLink’s Virtuoso</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://virtuoso.openlinksw.com/">http://virtuoso.openlinksw.com/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B92-sensors-16-00600">
<label>92.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Jaiswal</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Dey</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Dasgupta</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Mukherjee</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Spatial query handling in semantic web application: An experience report</article-title>
<source>Proceedings of the Applications and Innovations in Mobile Computing (AIMoC), 2015</source>
<conf-loc>Kolkata, India</conf-loc>
<conf-date>12–14 February 2015</conf-date>
</element-citation>
</ref>
<ref id="B93-sensors-16-00600">
<label>93.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Oguz</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Ergenc</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Yin</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Dikenelli</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Hameurlain</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>Federated query processing on linked data: A qualitative survey and open challenges</article-title>
<source>Knowl. Eng. Rev.</source>
<year>2015</year>
<volume>30</volume>
<fpage>545</fpage>
<lpage>563</lpage>
<pub-id pub-id-type="doi">10.1017/S0269888915000107</pub-id>
</element-citation>
</ref>
<ref id="B94-sensors-16-00600">
<label>94.</label>
<element-citation publication-type="webpage">
<article-title>ESPER</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.espertech.com/products/esper.php">http://www.espertech.com/products/esper.php</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B95-sensors-16-00600">
<label>95.</label>
<element-citation publication-type="webpage">
<article-title>Xively - Public Cloud for the Internet of Things</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="https://xively.com/">https://xively.com/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B96-sensors-16-00600">
<label>96.</label>
<element-citation publication-type="webpage">
<article-title>GeoNames Ontology</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.geonames.org/ontology">http://www.geonames.org/ontology</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B97-sensors-16-00600">
<label>97.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Compton</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Barnaghi</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Bermudez</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>GarcíA-Castro</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Corcho</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Cox</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Graybeal</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Hauswirth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Henson</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Herzog</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>The SSN ontology of the W3C semantic sensor network incubator group</article-title>
<source>Web Semantics Sci. Ser. Agents World Wide Web</source>
<year>2012</year>
<volume>17</volume>
<fpage>25</fpage>
<lpage>32</lpage>
<pub-id pub-id-type="doi">10.1016/j.websem.2012.05.003</pub-id>
</element-citation>
</ref>
<ref id="B98-sensors-16-00600">
<label>98.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Malhotra</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Gardner</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Patz</surname>
<given-names>R.</given-names>
</name>
</person-group>
<article-title>Implementation of Elliptic-Curve Cryptography on Mobile Healthcare Devices</article-title>
<source>Proceedings of the 2007 IEEE International Conference on Networking, Sensing and Control</source>
<conf-loc>London, UK</conf-loc>
<conf-date>15–17 April 2007</conf-date>
</element-citation>
</ref>
<ref id="B99-sensors-16-00600">
<label>99.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pelekis</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Frentzos</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Giatrakos</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Theodoridis</surname>
<given-names>Y.</given-names>
</name>
</person-group>
<article-title>HERMES: A trajectory DB engine for mobility-centric applications</article-title>
<source>Int. J. Knowl. Based Organ.</source>
<year>2015</year>
<volume>5</volume>
<fpage>19</fpage>
<lpage>41</lpage>
<pub-id pub-id-type="doi">10.4018/ijkbo.2015040102</pub-id>
</element-citation>
</ref>
<ref id="B100-sensors-16-00600">
<label>100.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Frentzos</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Gratsias</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Theodoridis</surname>
<given-names>Y.</given-names>
</name>
</person-group>
<article-title>Index-based most similar trajectory search</article-title>
<source>Proceedings of Data Engineering, 2007. ICDE 2007. IEEE 23rd International Conference on</source>
<conf-loc>Istanbul, Turkey</conf-loc>
<conf-date>15–20 April 2007</conf-date>
</element-citation>
</ref>
<ref id="B101-sensors-16-00600">
<label>101.</label>
<element-citation publication-type="webpage">
<article-title>Elasticsearch</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="https://www.elastic.co/products/elasticsearch">https://www.elastic.co/products/elasticsearch</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B102-sensors-16-00600">
<label>102.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Schmidt</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Görlitz</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Haase</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Ladwig</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Schwarte</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Tran</surname>
<given-names>T.</given-names>
</name>
</person-group>
<article-title>Fedbench: A benchmark suite for federated semantic data query processing</article-title>
<source>The Semantic Web–ISWC 2011</source>
<publisher-name>Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Heidelberg, Germany</publisher-loc>
<year>2011</year>
<fpage>585</fpage>
<lpage>600</lpage>
</element-citation>
</ref>
<ref id="B103-sensors-16-00600">
<label>103.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Bassi</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Bauer</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Fiedler</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Kramp</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Kranenburg</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Lange</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Meissner</surname>
<given-names>S.</given-names>
</name>
</person-group>
<source>Enabling Things to Talk: Designing Iot Solutions with the IoT Architectural Reference Model</source>
<publisher-name>Springer</publisher-name>
<publisher-loc>Heidelberg, Germany</publisher-loc>
<year>2013</year>
</element-citation>
</ref>
<ref id="B104-sensors-16-00600">
<label>104.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Meyer</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Ruppen</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Magerkurth</surname>
<given-names>C.</given-names>
</name>
</person-group>
<article-title>Internet of Things-Aware Process Modeling: Integrating IoT Devices as Business Process Resources</article-title>
<source>Advanced Information Systems Engineering: 25th International Conference, CAiSE 2013, Valencia, Spain, June 17-21, 2013. Proceedings</source>
<person-group person-group-type="editor">
<name>
<surname>Salinesi</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Norrie</surname>
<given-names>M.C.</given-names>
</name>
<name>
<surname>Pastor</surname>
<given-names>Ó.</given-names>
</name>
</person-group>
<publisher-name>Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Heidelberg, Germany</publisher-loc>
<year>2013</year>
<fpage>84</fpage>
<lpage>98</lpage>
</element-citation>
</ref>
<ref id="B105-sensors-16-00600">
<label>105.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Christophe</surname>
<given-names>B.</given-names>
</name>
</person-group>
<article-title>Managing Massive Data of the Internet of Things through Cooperative Semantic Nodes</article-title>
<source>Proceedings of Semantic Computing (ICSC), 2012 IEEE Sixth International Conference on</source>
<conf-loc>Palermo, Italy</conf-loc>
<conf-date>19–21 September 2012</conf-date>
</element-citation>
</ref>
<ref id="B106-sensors-16-00600">
<label>106.</label>
<element-citation publication-type="webpage">
<person-group person-group-type="author">
<name>
<surname>De</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Cassar</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Christophe</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Fredj</surname>
<given-names>S.B.</given-names>
</name>
<name>
<surname>Bauer</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Santos</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Jacobs</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Zeybek</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>de las Heras</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Martín</surname>
<given-names>G.</given-names>
</name>
</person-group>
<article-title>Concepts and solutions for entity-based discovery of IoT resources and managing their dynamic associations</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="http://www.iot-a.eu/public/public-documents/documents-1">http://www.iot-a.eu/public/public-documents/documents-1</ext-link>
</comment>
<date-in-citation>(accessed on 26 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B107-sensors-16-00600">
<label>107.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Jin</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Chun</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Jung</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>K.-H.</given-names>
</name>
</person-group>
<article-title>IoT service selection based on physical service model and absolute dominance relationship</article-title>
<source>Proceedings of the 2014 IEEE 7th International Conference on Service-Oriented Computing and Applications (SOCA)</source>
<conf-loc>Matsue, Japan</conf-loc>
<conf-date>17–19 November 2014</conf-date>
</element-citation>
</ref>
<ref id="B108-sensors-16-00600">
<label>108.</label>
<element-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Tönjes</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Reetz</surname>
<given-names>E.S.</given-names>
</name>
<name>
<surname>Moessner</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Barnaghi</surname>
<given-names>P.M.</given-names>
</name>
</person-group>
<article-title>A test-driven approach for life cycle management of internet of things enabled services</article-title>
<source>Proceedings of the Future Network & Mobile Summit (FutureNetw), 2012</source>
<conf-loc>Berlin, Germany</conf-loc>
<conf-date>4–6 July 2012</conf-date>
</element-citation>
</ref>
<ref id="B109-sensors-16-00600">
<label>109.</label>
<element-citation publication-type="webpage">
<article-title>Apache Hadoop</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="https://hadoop.apache.org/">https://hadoop.apache.org/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
<ref id="B110-sensors-16-00600">
<label>110.</label>
<element-citation publication-type="webpage">
<article-title>Apache Spark</article-title>
<comment>Available online:
<ext-link ext-link-type="uri" xlink:href="https://spark.apache.org/">https://spark.apache.org/</ext-link>
</comment>
<date-in-citation>(accessed on 25 April 2016)</date-in-citation>
</element-citation>
</ref>
</ref-list>
</back>
<floats-group>
<fig id="sensors-16-00600-f001" position="float">
<label>Figure 1</label>
<caption>
<p>Classifications of the Search Techniques in WoT.</p>
</caption>
<graphic xlink:href="sensors-16-00600-g001"></graphic>
</fig>
<fig id="sensors-16-00600-f002" position="float">
<label>Figure 2</label>
<caption>
<p>WoT System Model.</p>
</caption>
<graphic xlink:href="sensors-16-00600-g002"></graphic>
</fig>
<table-wrap id="sensors-16-00600-t001" position="float">
<object-id pub-id-type="pii">sensors-16-00600-t001_Table 1</object-id>
<label>Table 1</label>
<caption>
<p>WoT Applications and Enabling Search Techniques.</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Domain</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Applications</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Requirements</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Techniques</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Smart Cities</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Community-based Flood Monitoring;
<break></break>
Mobile Applications;
<break></break>
ollution Monitoring;
<break></break>
Public Rental Bicycle System;
<break></break>
Soil Monitoring;
<break></break>
Water Level Monitoring;
<break></break>
Weather Monitoring</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Require search with multiple functionalities (e.g., search by descriptions, by locations, or others);
<break></break>
Require managing fast changing and updating of sensing data;
<break></break>
May require both real-time and historical data access;
<break></break>
Require data analysis/prediction;
<break></break>
Require handling of mobile objects and their states</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Real-time Data Retrieval;
<break></break>
Entity Search;
<break></break>
Location-based Search;
<break></break>
Context-based Sensor Search</td>
</tr>
<tr>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Home Automation</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Adaptive Building Smart Control of Washing Machine</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dynamical selection of the surrounding/affecting resources Discovery of devices</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Entity Search Sensor Search</td>
</tr>
<tr>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Manufacturing</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Lifecycle Management for Industrial Automation Systems</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">The discovery needs to be enabled in a dynamic environment where physical resources appear and disappear during lifecycle phases.</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Search</td>
</tr>
<tr>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Smart Grids</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual Power Plants</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Require dynamically finding operateable distributed energy resources</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Entity Search</td>
</tr>
<tr>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Network Management</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Device, Network, and Application Management</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Require finding all devices that have a certain set of properties.</td>
<td align="left" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Search</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="sensors-16-00600-t002" position="float">
<object-id pub-id-type="pii">sensors-16-00600-t002_Table 2</object-id>
<label>Table 2</label>
<caption>
<p>Comparison of Search Techniques According to Basic Principles Classification (Abbreviations are listed in the footer).</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Classification</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Technique</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Data Format</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Access Approach</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Type</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Scale of Experiments</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">D
<sup>1</sup>
</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Ar
<sup>2</sup>
</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Implementation</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Remarks</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">GSN [
<xref rid="B25-sensors-16-00600" ref-type="bibr">25</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual sensors in XML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based search, SQL query with time window</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/MySQL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Extended as XGSN [
<xref rid="B26-sensors-16-00600" ref-type="bibr">26</xref>
] for distributed data acquisition and semantic annotation.
<break></break>
Integrated with Link Sensor Middleware (LSM) [
<xref rid="B27-sensors-16-00600" ref-type="bibr">27</xref>
] in OpenIoT [
<xref rid="B28-sensors-16-00600" ref-type="bibr">28</xref>
] project</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SenseWeb [
<xref rid="B29-sensors-16-00600" ref-type="bibr">29</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor ontology (an extension of the namespace defined by OGC SWE)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Map display with text description </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword/spatial search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Many applications described but none accessible</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dyser [
<xref rid="B30-sensors-16-00600" ref-type="bibr">30</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual sensors (microformat)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">URL/HTTP/HTML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based/value-based</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">385 sensors over 5 months</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/PHP</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Query of state of real world objects;
<break></break>
Computation required for state awareness, the scale is limited to a small number of sensors</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Microsearch [
<xref rid="B31-sensors-16-00600" ref-type="bibr">31</xref>
]
<break></break>
Snoogle [
<xref rid="B32-sensors-16-00600" ref-type="bibr">32</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Direct communication with sensor motes with built-in metadata </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual sensors in built-in format</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based top-k search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">TelosB motes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Early search implementations with limited functionalities and limited scalability</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">LiveWeb [
<xref rid="B33-sensors-16-00600" ref-type="bibr">33</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor data in XML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTML/AJAX</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Real-time content search based on keywords, category, and value range </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">PHP/Java/Apache/MySQL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Practical implementation without evaluation Should fit in global scale</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">lmDNS-SD [
<xref rid="B34-sensors-16-00600" ref-type="bibr">34</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Extended DNS record for sensors and objects</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">List of sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Resource directory based on DNS-SD</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">P2P</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Existing Internet standards utilised, thus fit in Web scale</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">DNS Search [
<xref rid="B35-sensors-16-00600" ref-type="bibr">35</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Extended DNS record for sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTTP REST/WADL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">URL and DNS-based (type/location)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">250,000 zones</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">BIND/MySQL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Utilise DNS structure; fit in Global scale</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing
<break></break>
Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Mobile Digcovery [
<xref rid="B36-sensors-16-00600" ref-type="bibr">36</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Integration of Multi-types</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">JSON-based response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Multi-functional JSON-based query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">ElasticSearch</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Combination of search engine and Web Infrastructure</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing
<break></break>
Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">IoT-SVKSearch [
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sampling values with metadata in Raw Data Store</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Data in built-in format</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based (B
<sup>+</sup>
-tree), spatial-temporal (R-tree), value-based (B
<sup>+</sup>
-tree) search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">140,800~352,000 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dec</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">PostgreSQL/file system</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Multiple search functionalities supported</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Text Indexing
<break></break>
Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OSIRIS [
<xref rid="B38-sensors-16-00600" ref-type="bibr">38</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OGC SWE Sensor model and data model</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SWE services</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial, temporal and keyword-based search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">JSI/Apache Lucene</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Applications in Smart City domain
<break></break>
Website of the project no longer accessible</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SensorMap [
<xref rid="B39-sensors-16-00600" ref-type="bibr">39</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Direct communication with web accessible sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Web services APIs</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial search (based on COLR-tree/crawling)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">MSRSense toolkit</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SenseWeb-based application, not accessible currently</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">GeoCENS [
<xref rid="B40-sensors-16-00600" ref-type="bibr">40</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OGC SOS, SensorML, OGC O&M</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SWE services</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial search (Peano space filling curves)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">~40,000 sensors/procedures</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">P2P</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Designed for sensor data from smaller organizations or individuals</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Geographic Service Discovery [
<xref rid="B41-sensors-16-00600" ref-type="bibr">41</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Services with geo-information</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial search (R-tree index/category server)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">3200 services</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">R-tree is combined with distributed architecture</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">FUTS Data Query [
<xref rid="B42-sensors-16-00600" ref-type="bibr">42</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual Object ontology in OWL-DL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SenML/JSON</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial search with time window/sensor type</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cloud database for huge data storage</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial Indexing</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Geospatial Indexing [
<xref rid="B23-sensors-16-00600" ref-type="bibr">23</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OWL-S</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic query (R-tree index)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">10,000 services</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">R-tree and Semantic query combined</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">IoT Platform [
<xref rid="B43-sensors-16-00600" ref-type="bibr">43</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN ontology/OWL-DL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/Apache Tomcat</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Demo in smart building, could be applied to a larger scale as well</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Linked Sensor Streams [
<xref rid="B44-sensors-16-00600" ref-type="bibr">44</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF stream data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Type/location based query (based on clustering)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 stream data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Evaluation provided for clustering, not for search</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">IoT Service Search [
<xref rid="B45-sensors-16-00600" ref-type="bibr">45</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OWL-S</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Service access standard</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic-based query (based on clustering)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">7500 services</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java Web Application/ Apache Tomcat</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Mobile services may crash this architecture</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Web-based Infrastructure [
<xref rid="B46-sensors-16-00600" ref-type="bibr">46</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Microdata
<break></break>
Microformats</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword matching with scope</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">600 simulated sensors
<break></break>
100,000 resources</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">ApacheBench</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Demo in smart building, mobile services may crash this architecture</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Geocasting [
<xref rid="B47-sensors-16-00600" ref-type="bibr">47</xref>
,
<xref rid="B48-sensors-16-00600" ref-type="bibr">48</xref>
,
<xref rid="B49-sensors-16-00600" ref-type="bibr">49</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Geolocation-based query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">P2P</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Flexible approach, no reliance on any model or architecture</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Non-location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">WoT Search [
<xref rid="B50-sensors-16-00600" ref-type="bibr">50</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual Object ontology in OWL-DL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Search with user preference and geo-location (search by application or human)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Technique not implemented</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Non-location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">IoT Serv
<break></break>
ices Indexing [
<xref rid="B51-sensors-16-00600" ref-type="bibr">51</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Web services (DPWS)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">REST/SOAP</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Functionality clusters, spatial query (SWC-tree), temporal query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">1600 IoT-WS
<break></break>
50 clusters</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">C#/Matlab</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Clustering process does not scale when IoT-WSs increase</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Non-location-based Clustering</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">AntClust [
<xref rid="B52-sensors-16-00600" ref-type="bibr">52</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN Ontology</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Ant clustering based on context</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">100,000 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Good performance on query time but may need a lot of time to deal with incoming data, thus may not be suitable for real-time search</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn>
<p>
<sup>1</sup>
D is short for Dynamicity.
<sup>2</sup>
Ar is short for Architecture. Other abbreviations include AJAX: Asynchronous JavaScript and XML, Cen: Centralised, Dec: Decentralised, Dis: Distributed, DNS-SD: DNS Service Directory, DPWS: Devices Profile for Web Services, FUTS: Frequently Updated Timestamped and Structured, HTML: HyperText Markup Language, JSI: Java Spatial Index, JSON: JavaScript Object Notation, O&M-S: Semantically annotated O&M, OGC: Open Geospatial Consortium, OWL: Web Ontology Language, OWL-DL: OWL- Description Logics, OWL-S: Semantic Markup for Web Services, RDB: Relational Database, RDFS: RDF Schema, SenML: Sensor Markup Language, SML-S: Semantically annotated SensorML, SOAP: Simple Object Access Protocol, SOS: Sensor Observation Service, SWE: Sensor Web Enablement, WADL: Web Application Description Language, XML: eXtensible Markup Language.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<table-wrap id="sensors-16-00600-t003" position="float">
<object-id pub-id-type="pii">sensors-16-00600-t003_Table 3</object-id>
<label>Table 3</label>
<caption>
<p>Comparison of Search Techniques According to Data/Knowledge Representation (Abbreviations are listed in the footer of
<xref ref-type="table" rid="sensors-16-00600-t002">Table 2</xref>
).</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Classification</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Technique</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Data Format</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Access Approach</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Type</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Scale of Experiments</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">D
<sup>1</sup>
</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Ar
<sup>2</sup>
</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Implementation</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Remarks</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Centralised</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Linked Sensor Data [
<xref rid="B53-sensors-16-00600" ref-type="bibr">53</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTML/XML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 weather stations</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtuoso RDF</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Combination of Linked Data, sensors and sensor data</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Centralised</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">IoT-DS [
<xref rid="B54-sensors-16-00600" ref-type="bibr">54</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">100,000 instances</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Proposed IoT directory is similar to IoT Gateway</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Centralised</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SemSOS [
<xref rid="B55-sensors-16-00600" ref-type="bibr">55</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SML-S/O&M-S</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SOS query mapping to SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Apache Jena </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Mobile sensors are ignored</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Centralised</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SemSOS [
<xref rid="B56-sensors-16-00600" ref-type="bibr">56</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SWE based model in Linked Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OGC SWE SOS</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Named location based query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 weather stations </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF2Go/Sesame</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Different implementation of SemSOS</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Centralised</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">LinkedGeoData [
<xref rid="B57-sensors-16-00600" ref-type="bibr">57</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint
<break></break>
HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL-like query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Enables geolocation query as part of a SPARQL query
<break></break>
Online version available at [
<xref rid="B58-sensors-16-00600" ref-type="bibr">58</xref>
] </td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Centralised</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OWLIM-SE [
<xref rid="B59-sensors-16-00600" ref-type="bibr">59</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF/RDFS/OWL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL-like query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Enable geolocation query as part of a SPARQL query</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Centralised</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">GeoSPARQL [
<xref rid="B60-sensors-16-00600" ref-type="bibr">60</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL-like query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Apache Jena</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Enable geolocation query as part of a SPARQL query</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Federated</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">DARQ [
<xref rid="B61-sensors-16-00600" ref-type="bibr">61</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF datasets</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dec</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Requires service descriptions of datasets
<break></break>
Supports limited queries</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Federated</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">ANAPSID [
<xref rid="B62-sensors-16-00600" ref-type="bibr">62</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF datasets</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dec</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Python</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Requires predicates of datasets</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Federated</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPLENDID [
<xref rid="B63-sensors-16-00600" ref-type="bibr">63</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF datasets</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dec</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Requires VoID of datasets</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Federated</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">FedX [
<xref rid="B64-sensors-16-00600" ref-type="bibr">64</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF datasets</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dec</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Easy to be extended as only the endpoint is required</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Federated</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Federated Query Implementation [
<xref rid="B65-sensors-16-00600" ref-type="bibr">65</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF datasets</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dec</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Easy to be extended as only the endpoint is required</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Federated</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL 1.1 Federated Query [
<xref rid="B66-sensors-16-00600" ref-type="bibr">66</xref>
,
<xref rid="B67-sensors-16-00600" ref-type="bibr">67</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF datasets</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">W3C Recommendation for Federated Query</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDB Mapping</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">GSN [
<xref rid="B25-sensors-16-00600" ref-type="bibr">25</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual sensors in XML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based search,
<break></break>
SQL query with time window</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/MySQL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Extended as XGSN [
<xref rid="B26-sensors-16-00600" ref-type="bibr">26</xref>
] for distributed data acquisition and semantic annotation. Integrated with Link Sensor Middleware (LSM) [
<xref rid="B27-sensors-16-00600" ref-type="bibr">27</xref>
] in OpenIoT [
<xref rid="B28-sensors-16-00600" ref-type="bibr">28</xref>
] project</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDB Mapping</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SenseWeb [
<xref rid="B29-sensors-16-00600" ref-type="bibr">29</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor ontology (an extension of the namespace defined by OGC SWE)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Map display with text description </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword/spatial search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Many applications described but none is accessible</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDB Mapping
<break></break>
Semantic Modelling</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQLstream [
<xref rid="B68-sensors-16-00600" ref-type="bibr">68</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN ontology</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Continuous SPARQL query with time window</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">8000 data values/second</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Data mapped to DSMS</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic Modelling</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">C-SPARQL [
<xref rid="B69-sensors-16-00600" ref-type="bibr">69</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF streams</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Continuous SPARQL query (time window/ periodical execution)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Data mapped to DSMS
<break></break>
No evaluation provided</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic Modelling</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">EP-SPARQL [
<xref rid="B70-sensors-16-00600" ref-type="bibr">70</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF and RDF event streams</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Continuous SPARQL query </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 triples/20 locations</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Prolog language</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Designed for Event Processing</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic Modelling</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">CQELS [
<xref rid="B71-sensors-16-00600" ref-type="bibr">71</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF streams</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Continuous SPARQL query </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">10 million triples</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Processing directly on Linked Stream Data</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic Modelling</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">LSM [
<xref rid="B27-sensors-16-00600" ref-type="bibr">27</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN ontology</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint/HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">CQELS</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">70,000 sensor data sources</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/Virtuoso/Hadoop</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Integrated with XGSN [
<xref rid="B26-sensors-16-00600" ref-type="bibr">26</xref>
] in OpenIoT [
<xref rid="B28-sensors-16-00600" ref-type="bibr">28</xref>
]</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic Modelling</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Q-ASSF [
<xref rid="B72-sensors-16-00600" ref-type="bibr">72</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN ontology</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">CQELS</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">200 queries/3000 sensors/16,000 triples</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RabbitMQ/Apache Jena</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Filtering algorithm to reduce sensor communications and triple transmission</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic Modelling</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Linked Sensor Streams [
<xref rid="B44-sensors-16-00600" ref-type="bibr">44</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF streams</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Type/Location based query (based on clustering)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 stream data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Combination of Linked Data and sensor streams</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="sensors-16-00600-t004" position="float">
<object-id pub-id-type="pii">sensors-16-00600-t004_Table 4</object-id>
<label>Table 4</label>
<caption>
<p>Comparison of Search Techniques According to Content being Searched (Abbreviations are listed in the footer of
<xref ref-type="table" rid="sensors-16-00600-t002">Table 2</xref>
).</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Classification</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Technique</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Data Format</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Access Approach</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Search Type</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Scale of Experiments</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">D
<sup>1</sup>
</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Ar
<sup>2</sup>
</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Implementation</th>
<th align="center" valign="middle" style="border-top:solid thin;border-bottom:solid thin" rowspan="1" colspan="1">Remarks</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Instantaneous Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">LiveWeb [
<xref rid="B33-sensors-16-00600" ref-type="bibr">33</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor data in XML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTML/AJAX</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Real-time content search based on keywords, category, and value range </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">PHP/Java/Apache/MySQL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Practical implementation without evaluation Should fit in global scale</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Instantaneous Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SensorMap [
<xref rid="B39-sensors-16-00600" ref-type="bibr">39</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Direct communication with web accessible sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Web services APIs</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial search (based on COLR-tree/crawling)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">MSRSense toolkit</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SenseWeb-based application, currently not accessible </td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Instantaneous Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">GeoCENS [
<xref rid="B40-sensors-16-00600" ref-type="bibr">40</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OGC SOS, SensorML, OGC O&M</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SWE services</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial search (Peano space filling curves)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">~40,000 sensors/procedures</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">P2P</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Designed for sensor data from smaller organizations or individuals</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Instantaneous Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">CQELS [
<xref rid="B71-sensors-16-00600" ref-type="bibr">71</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF streams</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Continuous SPARQL query </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">10 million triples</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Processing performed directly on Linked Stream Data</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Instantaneous Data
<break></break>
Historical Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">IoT-SVKSearch [
<xref rid="B37-sensors-16-00600" ref-type="bibr">37</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sampling values with metadata in Raw Data Store</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Data in built-in format</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based (B
<sup>+</sup>
-tree), spatial-temporal (R-tree), value-based (B
<sup>+</sup>
-tree) search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">140,800~352,000 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dec</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">PostgreSQL/file system</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Multiple search functionalities supported</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Instantaneous Data Historical Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">FUTS Data Query [
<xref rid="B42-sensors-16-00600" ref-type="bibr">42</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual Object ontology in OWL-DL</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SenML/JSON</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial search with time window/sensor type</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cloud database for huge data storage</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Historical Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">LSM [
<xref rid="B27-sensors-16-00600" ref-type="bibr">27</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN ontology</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint/HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">CQELS</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">70,000 sensor data sources</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/OpenLink Virtuoso/Apache Hadoop</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Integrated with XGSN [
<xref rid="B26-sensors-16-00600" ref-type="bibr">26</xref>
] in OpenIoT [
<xref rid="B28-sensors-16-00600" ref-type="bibr">28</xref>
]</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OSIRIS [
<xref rid="B38-sensors-16-00600" ref-type="bibr">38</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OGC SWE Sensor model and data model</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SWE services</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Spatial, temporal and keyword-based search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">JSI/Apache Lucene</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Applications in Smart City domain,
<break></break>
Website of the project no longer accessible</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Microsearch [
<xref rid="B31-sensors-16-00600" ref-type="bibr">31</xref>
]
<break></break>
Snoogle [
<xref rid="B32-sensors-16-00600" ref-type="bibr">32</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Direct communication with sensor motes with built-in metadata </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual sensors in built-in format</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based top-k search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">TelosB motes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Early search implementations with limited functionalities and limited scalability</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Linked Sensor Data [
<xref rid="B53-sensors-16-00600" ref-type="bibr">53</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTML/XML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 weather stations</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OpenLink Virtuoso</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Combination of Linked Data, sensors and sensor data</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SemSOS [
<xref rid="B56-sensors-16-00600" ref-type="bibr">56</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SWE based model in Linked Data</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OGC SWE SOS</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Named location based query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 weather stations </td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RDF2Go/Sesame</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Mobile sensors are ignored</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">CASSARAM [
<xref rid="B73-sensors-16-00600" ref-type="bibr">73</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN ontology</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">1,000,000 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Apache Jena API</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Multiple sensor feature support
<break></break>
Fast top-k sensor selection</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">VCS [
<xref rid="B74-sensors-16-00600" ref-type="bibr">74</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Server nodes (objects)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">List of nodes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based query with multiple features</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">P2P</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No evaluation provided</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">OpenIoT [
<xref rid="B28-sensors-16-00600" ref-type="bibr">28</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SSN ontology</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL endpoint/HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Continuous SPARQL query/Publish and Subscribe model</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">XGSN/LSM</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Multiple practical applications provided</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Sensor
<break></break>
Context-based Entity</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPITFIRE [
<xref rid="B75-sensors-16-00600" ref-type="bibr">75</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor (RDF triple)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">SPARQL query response</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">CQELS</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">40 physical sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Jena Semantic Web Framework</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Semantic sensor descriptions</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Content-based Sensor</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Fuzzy-based Sensor Search [
<xref rid="B76-sensors-16-00600" ref-type="bibr">76</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor data streams</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor data stream based search for sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">1500 data points/day</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Ranking based on sensor data prediction</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Content-based Sensor
<break></break>
Content-based Entity</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dyser [
<xref rid="B30-sensors-16-00600" ref-type="bibr">30</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Virtual sensors (microformat)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">URL/HTTP/HTML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Keyword-based/value-based</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">385 sensors over 5 months</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/PHP</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Query of state of real world objects
<break></break>
Computation required for state awareness, the scale is limited to small number of sensors</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Content-based Sensor
<break></break>
Content-based Entity</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor Ranking [
<xref rid="B77-sensors-16-00600" ref-type="bibr">77</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor with outputs in built-in format</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Ranked list of sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Prediction based ranking for content-based sensor search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">C++</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Local scale deployment</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Entity</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Gander [
<xref rid="B78-sensors-16-00600" ref-type="bibr">78</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Nodes (objects) (tuple space/tuple graph)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">HTTP REST</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Multi-hop query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">20,000 mobile visitors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">P2P</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Mobile applications for smart university</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Entity</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">ISE [
<xref rid="B79-sensors-16-00600" ref-type="bibr">79</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Encrypted RFID records</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">XML/HTML/JSON</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Database-based query</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">1,000,000 RFID records</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Dis</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Nginx/Tokyo Cabinet/C++</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cryptography for security</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Content-based Entity</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Correlation-based Sensor Search [
<xref rid="B80-sensors-16-00600" ref-type="bibr">80</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor with sensor data in built-in format</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">List of sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Sensor search with a given state/output</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">384 sensors</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Java/SMILE reasoning engine</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Based on sensor data correlation</td>
</tr>
<tr>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Context-based Entity</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">DiscoWoT [
<xref rid="B81-sensors-16-00600" ref-type="bibr">81</xref>
]</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Built-in description for resources (objects)</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">JSON/XML</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">RESTful interface search</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">-</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Yes</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">Cen</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">AutoWoT toolkit</td>
<td align="center" valign="middle" style="border-bottom:solid thin" rowspan="1" colspan="1">No evaluation provided</td>
</tr>
</tbody>
</table>
</table-wrap>
</floats-group>
</pmc>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/CyberinfraV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000131 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 000131 | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Ticri/CIDE
   |area=    CyberinfraV1
   |flux=    Pmc
   |étape=   Corpus
   |type=    RBID
   |clé=     PMC:4883291
   |texte=   Search Techniques for the Web of Things: A Taxonomy and Survey
}}

Pour générer des pages wiki

HfdIndexSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/RBID.i   -Sk "pubmed:27128918" \
       | HfdSelect -Kh $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd   \
       | NlmPubMed2Wicri -a CyberinfraV1 

Wicri

This area was generated with Dilib version V0.6.25.
Data generation: Thu Oct 27 09:30:58 2016. Site generation: Sun Mar 10 23:08:40 2024