Web of Things Core Concepts Paper

Together with Vlad and Erik Wilde, we’ve been trying since a while to write a scientific paper out of our common technical report that would sum up the founding concepts of the Web of Things. The paper finally got accepted for IoT 2010. This is a good sign because it emphasizes the fact that the Internet of Things community is now really looking into Web standards as a candidate common integration bus for the application layer of the physical world. A fact that did not really hold two years ago, when Erik’s attempt to publish a WoT paper at IoT 2008 did not succeed.

In a nutshell the paper is based on the fact that many efforts are currently centered around creating large-scale networks of “smart things” found in the physical world (e.g., wireless sensor and actuator networks, embedded devices, tagged objects). Rather than exposing real-world data and functionality through proprietary and tightly-coupled systems, in the paper we propose to make them an integral part of the Web. As a result, smart things become easier to build upon. Popular Web languages (e.g., HTML, Python, JavaScript, PHP) can be used to easily build applications involving smart things and users can leverage well-known Web mechanisms (e.g., browsing, searching, bookmarking, caching, linking) to interact and share these devices. In this paper, we begin by describing the Web of Things architecture and best-practices based on the
RESTful principles that have already contributed to the popular success, scalability, and modularity of the traditional Web. We then discuss several prototypes designed in accordance with these principles to connect environmental sensor nodes and an energy monitoring system to the World Wide Web. We finally show how Web-enabled smart things can be used in lightweight ad-hoc applications called “physical mashups”.

Enjoy the paper here, feedback is very welcomed!

Below is the current version of the slides I’ll present tomorrow at IoT 2010 in Tokyo:

You may also like...

  • We have been looking at using XMPP for some projects. Have you looked at it. It provides a number of useful features, that I would rather not implement over again.
    Presence is one thing that keeps coming up in my work (smart energy and HAN). Is the device connected, able to talk, some piece of the network down between the sensor and the server? These are really hard problems to solve.
    Nice slides, good luck with your talk.

  • Hey Doug, we did look at XMPP and did use it with one of our frameworks. It’s a great system and a nice way of doing pub/sub. However, it is not RESTful, i.e., not exposed to the Web as much as we’d like it to be: it does not run in a browser without additional software, is not really exposed to search-engines and is not browseable.

    Having said that in many cases, especially when exposing the API on the Web is not core to the project, it makes totally sense to use it. We might see the Web and pub/sub mechanisms soon being reconciliated with systems like pubsubhubbub or HTML 5 Web Sockets but these are still a quite early stage… Btw, we also worked on a system that provides pub/sub over a Web and RESTful API, you can find the corresponding publication here (http://www.inf.ethz.ch/personal/dguinard/publications/bibtex.html?file=/home/webvs/www/htdocs/publ/papers/trifam-webmes-2010) note that this project was lead by Vlad, my partner in WoT crimes 🙂

  • Pingback: This Week in #REST – Volume 30 (Nov 21 2010 – Dec 12 2010) « This week in REST()