It also enables the creation of reusable scripts to implement device logic, significantly enhancing the portability of application modules.
Security is supported by specific features, such as public metadata in Thing Descriptions and the separation of concerns in the design of the Scripting API.
Following this early work, the growing interest in and implementation of the Internet of things started to raise some questions about the application layer of the IoT.
Researchers and practitioners started envisioning the IoT as a system where data from various devices could be consumed by Web applications to create new use cases.
[6] Early mentions of the Web of Things as a term also appeared in a paper by Vlad Stirbu et al.[7] From 2007 onwards, Trifa, Guinard, Wilde, and other researchers tried publishing their ideas and concepts at peer-reviewed conferences, but their work was rejected by the Wireless Sensor Networks research community on the basis that Internet and Web protocols were too verbose and limited in the context of real-world devices,[8] preferring to focus on optimization of memory and computation usage, wireless bandwidth, or very short duty cycles.
In early 2009, several respected WSN researchers, such as David Culler, Jonathan Hui, Adam Dunkels, and Yazar Dogan, evaluated the use of Internet and Web protocols for low-power sensor nodes and showed the feasibility of the approach.
[11] Building on this implementation and uniting efforts, a RESTful architecture for things was proposed in 2010 by Guinard, Trifa, and Wilde.
These workshops morphed into a growing community of researchers and practitioners who could discuss the latest findings and ideas on the Web of Things [citation needed].
[15] Building on this work, Simon Mayer emphasized the importance of REST's uniform interface, and in particular the HATEOAS principle, in his PhD thesis.
[19] In October 2014, Google also announced interest in these ideas by launching the Physical Web GitHub project.