BY DOMINIQUE GUINARD | APRIL 8, 2017 Note: this article was first published in the [oT Technica Curiosa magazine. The Internet of Things — IoT for short — is here to stay and to change our world for the better. This grand vision depicts a world where people, buildings, and physical objects are connected to a single and common network. Bottles of soda, lighting systems, cars and everything in between can provide services and exchange data with each other. You might have noticed that the Internet of Things feels very much like an Intranet of Things: to interact with 10 different devices from your phone, you have to install 10 different apps. The problems is that there's not a single “lingua franca’ spoken by each and every object — there are literally hundreds! The worst part is that most of these IoT protocols and standards aren't compatible with each other, and for this reason the IoT hasn't (yet!) delivered on its promises. Connecting every Thing to the Internet and giving them an IP addresses in only the first step towards the Internet of Things. Things could then easily exchange data with each other, but not necessarily understand what that data means. This is what Web -anned with CamScannerto install 10 different apps. The problems is that there's not a single "lingua franca" spoken by each and every object — there are literally hundreds! The worst part is that most of these IoT protocols and standards aren't compatible with each other, and for this reason the IoT hasn't (yet!) delivered on its promises. Connecting every Thing to the Internet and giving them an IP addresses in only the first step towards the Internet of Things. Things could then easily exchange data with each other, but not necessarily understand what that data means. This is what Web protocols like HTTP brought to the Internet: a universal way to describe images, text, and other media elements so that machines could “understand” each. The Web of Things — or WoT ~ is simply the next stage in this evolution: using and adapting Web protocols to connect anything in the physical world and give it a presence on the World Wide Web! We define it as follow: 6S The Web of Things is a refinement of the Internet of Things by integrating smart things not only into the Internet (network), but into the Web Architecture (application). The Web of Things architecture Just like the OSI layered architecture organises the many protocols and standards of the Internet, the WoT architecture is an attempt to structure the Scanned with CamScannerIllustration: © loT For All © inv Ff & Internet of Things devices developed over time with unique and sometimes proprietary implementations. This causes difficulties when trying to network different devices. It also can lead to vendor lock-in, where users are tied to a certain company’s products due to incompatibility with other products on the market. The Web of Things was proposed to address the standardization of the Internet of Things and resolve some of these issues. What is the Web of Things? The concept of the Web of Things was first introduced by researchers around 2007. It has since been adopted and promoted by organizations like Mozilla, Siemens, and the World Wide Web Consortium (W3C). These organizations have established interest groups to define the standards that should Scanned with CamScannerThe concept of the Web of Things was first introduced by researchers around 2007. It has since been adopted and promoted by organizations like Mozilla, Siemens, and the World Wide Web Consortium (W3C). These organizations have established interest groups to define the standards that should govern the Web of Things. This includes the Web Thing Model, which represents a standardized way to provide information on a virtual or physical device, known as a Thing. While loT and Web of Things both essentially serve the same purpose of connecting smart devices over the Internet, there are some key differences to keep in mind. ¥ Click To Tweet Along with the Web Thing Model, the groups involved in developing the Web of ‘Scanned witl CamScannerAlong with the Web Thing Model, the groups involved in developing the Web of Things have also introduced several other standards. These include the WoT Architecture, WoT Thing Description, WoT Scripting API, and WoT Binding Templates. Each of these makes up the core components of the Web of Things design. loT vs WoT While the Internet of Things and Web of Things both essentially serve the same purpose of connecting smart devices over the Internet, there are some critical differences between them. These differences are defined by the purpose each one serves and the implementations they involve. The main difference between loT and WoT is the layer at which each establishes interconnectivity between devices. In this case, loT solves just the network layer between devices. That is, each device has a transport medium over which to Scanned mh tamscannerinvolve. The main difference between loT and WoT is the layer at which each establishes interconnectivity between devices. In this case, loT solves just the network layer between devices. That is, each device has a transport medium over which to communicate. To use the example of a highway, loT represents the road on which cars travel from place to place. It is purely the transportation medium for information to travel from point to point. It is not concerned with how data travels over it or what it intends to do when it reaches its destination. Because of this, the IoT itself cannot help guide information to its destination or coordinate between different data sources. This is where loT’s limitations begin to become apparent. In contrast to loT’s network layer solutions, WoT can be thought of as the application layer. It sits on top of the loT conceptually and functionally. WoT is not an alternative or competitor to loT; instead, it tries to enhance loT. It does this by defining Scanned with CamScanner— DEQHTtO DECOME appalen, In contrast to loT’s network layer solutions, WoT can be thought of as the application layer. It sits on top of the loT conceptually and functionally. WoT is not an alternative or competitor to loT; instead, it tries to enhance IoT. It does this by defining standard definitions and models for representing devices on the Internet. In the highway analogy, WoT represents the street signs, traffic lights, and engineered routes that establish the rules of the road. It exists to establish well-defined paths for data to travel between points and ensure that it is compatible with its source and destination. WoT enables devices to connect over the web using mainstream technologies and standards from a technical perspective—for example, HTML 5.0 and Javascript. The WoT paradigms promote RESTful API designs, a common Internet standard for application development. In summary, WoT evolves loT from a pure concept to a fully-developed architectural approach for smart device interaction. It Scanned with CamScannerIn summary, WoT evolves lol from a pure concept to a fully-developed architectural approach for smart device interaction. It serves to define standards for loT-enabled devices to communicate better. WoT Architecture The World Wide Web is composed of many different evolving architectural standards. The Web of Things architecture has been contributed to by many organizations, but it is spearheaded by the W3C, an established group to establish web standards. The W3C's standardization of WoT is based on several building blocks. These are the Thing Description, Binding Templates, Scripting API, and Security and Privacy Guidelines. The WoT Thing Description is the basis upon which loT devices (“Things”) can fit into WoT. The Thing Description defines the metadata and interfaces that a Thing should provide. This definition produces a format for metadata that is guaranteed to be machine-readable in compliance with the standard. Scanned with CamScannerProtocol Bindings refer to the protocols over which loT devices communicate. The W3C attempts to establish, therefore, the standard interfaces to interact with these protocols with Binding Templates. These Binding Templates allow unique Thing Descriptions to be modeled after and interact with different established protocols for communication. The WoT Scripting API provides a common programming language for implementing Thing connectivity over loT. This API is in the form of a JSON API. A device doesn’t need to use the Scripting API to be part of the WoT, but it is convenient to simplify application portability across platforms. Finally, the Security and Privacy Guidelines are perhaps the most important aspect of WoT. Much like the Internet itself does not define any specific safety guidelines for i 3 iFinally, the Security and Privacy Guidelines are perhaps the most important aspect of WoT. Much like the Internet itself does not define any specific safety guidelines for applications, neither does the Internet of Things. In a technical world where cyber- attacks and compromised personal electronic security are becoming a threat, ensuring that data is safe is more important than ever. This becomes especially true when physical devices are connected to the Internet. These devices can be directly connected to homes, offices, or even medical applications. This is why W3C has laid out the Security and Privacy Guidelines for developers to implement standard safety practices in Internet-connected devices. While the WoT architecture is very detailed, it is founded on these basic concepts. These four components comprise the basic layout of WoT. WoT Use Cases and Applications Scanned with CamScannerWoT Use Cases and Applications With the prevalent adoption of loT already in use, one may wonder if there are any practical reasons for this newer application layer in the real world. There are, in fact, many use cases for WoT standards in commercial, residential, and industrial capacities. Many people will interact with WoT through smart home technologies. A smart home is inherently dependent on many different devices communicating, either directly or through the cloud. Thermostats, doors, security cameras, and even smoke detectors need to be reachable by homeowners. WoT ensures that these devices all speak the “same language” when working together. In a commercial application, many of the exact needs still apply. WoT-enabled production facilities, smart factories can Scanned with CamScannerexact needs still apply. Wol-enabied production facilities, smart factories can take advantage of machinery connected to the Internet. This allows automated production capabilities and remote monitoring of that production. That monitoring can also ensure the safety of factory conditions, much like the security cameras and smoke detectors that help keep families safe at home. The possibilities of a standardized Internet of connected Things are endless. Agriculture, logistics, construction, transportation, and municipalities can all benefit from the advancements of smart device technology. These industries often overlap, so the interconnectivity of their devices with other businesses is essential to the smooth operation of the supply chain. WoT ensures that devices can communicate not just within one use case but also across use cases seamlessly. WoT Challenges Scanned with CamScannerWoT Challenges While WoT seeks to solve many loT problems, it does come with its challenges. No technology is perfect, and there are, of course, tradeoffs to certain gains. WoT is no exception to this. The main concern with WoT is security and privacy. As mentioned above, putting anything onto the Internet risks losing due to web application vulnerabilities. That risk is even more serious when there is a direct physical link to the real world. The W3C’s Security and Privacy Guidelines outline best practices for mitigating these risks. However, those guidelines are public, which poses the possibility that hackers could find loopholes in them. Also, when many devices follow the same standard, any weakness in that standard exposes every device to the same vulnerability. Besides security, WoT devices could suffer from energy inefficiency. A home or business that is fully connected to WoT will require many devices to be using slectricily canned with CamScannerBesides security, WoT devices could suffer from energy inefficiency. A home or business that is fully connected to WoT will require many devices to be using electricity 24/7. This round-the-clock operation is essential so that the device can activate at any time it is needed. Of course, this can be mitigated by identifying peak times when devices need to be active. But for certain use cases, such as security and safety systems. That need for constant availability is also a potential vector for failure. Denial-of-service (DoS) attacks can render devices inoperable, even if they are powered on all the time. In a DoS attack, hackers continuously send signals to a device to occupy its resources so that legitimate requests cannot be processed. The attack can lock valid users out of their own devices or even crash the devices for as long as the attackers have the resources to continue sending requests. The good news about WoT is that, as an open standard, it is always being innovated Scanned with CamScannerThe good news about WoT is that, as an open standard, it is always being innovated by the most active technical contributors who specialize in these areas. Because of that, security concerns and drawbacks can be solved over time as the standards improve. Even today, many of these risks are only minor, thanks to the hard work that has already been put in to set up the security guidelines of WoT. The Future of WoT The loT has been a revolutionary shift in the perception of the types of devices that connect to the Internet. It is no longer assumed that only computers can communicate over the web. Now, all types of devices, appliances, and tools can be programmed with the ability to improve their usability thanks to the Internet. This pervasive paradigm shift has evolved even further with the development of the Web of Things. As the growing capabilities of smart ar an CamscannerThe loT has been a revolutionary shift in the perception of the types of devices that connect to the Internet. It is no longer assumed that only computers can communicate over the web. Now, all types of devices, appliances, and tools can be programmed with the ability to improve their usability thanks to the Internet. This pervasive paradigm shift has evolved even further with the development of the Web of Things. As the growing capabilities of smart devices led to growing adoption, the need for standardized communication between devices grew as well. This growth shows no signs of slowing, as more and more devices are getting online every day. That’s where WoT has stepped in to help guide the changing landscape of smart devices to converge on common protocols for interconnectivity. This standardization will help WoT grow one of the more common trends in web technology. As the WoT architecture gains adoption among device developers, the capabilities “Scanned with CamScanner“tonverde On CONIMON Provocolstor interconnectivity. This standardization will help WoT grow one of the more common trends in web technology. As the WoT architecture gains adoption among device developers, the capabilities of these devices will increase. Devices will no longer be locked into their vendors, driving competition and innovation between producers. This alone will allow the trends of smart homes, businesses, factories, and cities to continue at an efficient and affordable rate. Internet of Things © inv f & Scanned with CamScannerThe Web of Things architecture Just like the OSI layered architecture organises the many protocols and standards of the Internet, the WoT architecture is an attempt to structure the galaxy of Web protocols and tools into a useful framework for connecting any device or object to the Web. The WoT architecture stack is not composed of layers in the strict sense, but rather of levels that add extra functionality, as shown in the figure below. Each layer helps to integrate Things to the Web even more intimately and hence making those devices more accessible for applications and humans! HTML JSON REST API Web Hooks rae HTTP URI/URL Gateway MOTT coap ets 6LOWPAN Thread Ethernet Wi-Fi Beacons Bluetooth ZigBee 3/4/56 Scanned with CamScannerTo illustrate what these layers bring to the IoT table, let us introduce the WoT Pi, a Raspberry Pi device running at EVRYTHNG in London. The WoT Pi is connected with a bunch of sensors (e.g., temperature, humidity) and actuators (e.g.,an LCD screen, LEDs) that you can interact with across the Internet. An Internet-connected camera allows you to see the setup live, check it out here: http//devices.webofthings io/camera/sensors/picture This layer is responsible for turning any Thing into a Web Thing that can be interacted with using HTTP requests just like any other resource on the Web. In other words, a Web Thing is a REST API that allows to interact with something in the real world, like opening a door or reading a temperature sensor located across the planet Scanned with CamScannerbondon Layer 1: Access This layer is responsible for turning any Thing into a Web Thing that can be interacted with using HTTP requests just like any other resource on the Web. In other words, a Web Thing is a REST API that allows to interact with something in the real world, like opening a door or reading a temperature sensor located across the planet. To illustrate this, the sensors of our Pi can be accessed via a simple HTTP request on the following URL: http//devices.webofthings.io/pi/sensors/ Go ahead and try this in your browser. You'll get a human friendly HTML representation with links to the sensors. Click on “temperature” and you'll get the temperature. What you are doing here is navigating the RESTful API of our Pi, just like you would be browsing a Web page. loT Things can be mapped to REST resources quite easily as show in the figure below. Root URL of your Pi passive infrared sensor focalhost:8484/pi Iie Sensors /sensors ‘Source: Building the Web of Things book webotthingsio Creative Commons Attribution 4.0 HTML is great for humans, but not atc for -anned with CamScanner(Creative Commons Attribution 4.0 HTML is great for humans, but not always for machines who prefer the JSON notation - Our Pi provides both. Run the following command in your terminal using cURL, a tool for communicating with HTTP APIs: curl =X GET -H "Accept: application/json" “http://devices .webof things. io/pi/sensors/humidity/* You will see the humidity level in our London office in JSON in your terminal. This is the ideal first step to build your first application that expands the Web into the real world! This is all good, but many IoT scenarios are real-time and/or event-driven. Instead of your application continuously asking for data from our Pi, you want it to get notified when something happens in the real world, for example humidity reaches a certain threshold or noise gets detected during the night. This is where another Web protocol can help: WebSocket. This Javascript code below is enough for a Web page to automatically get temperature updates from the WoT Pi. You can paste it in the console of your Web browser and you will see our Pi pushing the temperature every second to your browser. var socket = new WebSocket('ws://devices.webofthings.io/pi/sensors/temper socket.onmessage = function (event) { //Called when a message is received var result = JSON.parse(event.data); — _ Censeaniet— - SUEREL CHMESSRS S FUNCTION LEVELS Teel leU WIE Ss message is received var result = JSON. parse(event.data); console. log(result); yi Layer 2: Find Marking things accessible via an HTTP and WebSocket API is great but it doesn't mean applications can really “understand” what the Thing is, what data or services it offers, and so on This is where the second layer — Find — becomes interesting. This layer ensures that your Thing can not only be easily used by other HTTP clients but can also be findable and automatically usable by other WoT applications. The approach here is to reuse web semantic standards to describe things and their services. This enables searching for things through search engines and other web indexes as well as the automatic generation of user interfaces or tools to interact with Things. At this level technologies such as JSON-LD are in use: a language for semantically annotating JSON. This is also where standards such as the Web Things Model and the work of the W3C WoT group help: they define an abstract set of REST resources that Things should offer. Layer 3: Share The Internet of Things will only blossom if Things have a way to securely share data across services. This is the responsibility of the Share layer, which Scanned with CamScannerTesources that i hings shouid offer. Layer 3: Share The Internet of Things will only blossom if Things have a way to securely share data across services. This is the responsibility of the Share layer, which specifies how the data generated by Things can be shared in an efficient and secure manner over the web. At this level, another batch of Web protocols help. First, TLS, the protocol that makes transactions on the Web secure. Then, techniques such as delegated web authentication mechanisms like OAuth which can be integrated to our Things’ APIs. Finally, we can also use social networks to share Things and their resources to create a Social Web of Things! Layer 4: Compose Finally, once Things are on the Web (layer 1) where they can be found by humans and machines (layer 2) and their resources can be shared securely with others (layer 3), it's time to look at how to build large- scale, meaningful applications for the Web of Things. In other words, we need to understand the integration of data and services from heterogeneous Things into an immense ecosystem of web tools such as analytics software and mashup platforms. Web tools at the Compose layer range from web toolkits—for example, JavaScript SDKs offering higher-level abstractions—to dashboards with programmable widgets, and finally to physical mashup tools such as Node-RED as shown below. _ Scanned with CamScannerFinally, once Things are on the Web (layer 1) where they can be found by humans and machines (layer 2) and their resources can be shared securely with others (layer 3), it's time to look at how to build large- scale, meaningful applications for the Web of Things. In other words, we need to understand the integration of data and services from heterogeneous Things into an immense ecosystem of web tools such as analytics software and mashup platforms. Web tools at the Compose layer range from web toolkits—for example, JavaScript SDKs offering higher-level abstractions—to dashboards with programmable widgets, and finally to physical mashup tools such as Node-RED as shown below. Inspired by Web 2.0 participatory services and in particular web mashups, physical mashups offer a unified view of the classical web and Web of Things and empower people to build applications using data and services from Web Things without requiring programming skills. A Physical Mashup with Node-RED Conclusion Scanned with CamScannerA Physical Mashup with Node-RED Conclusion The Web of Things is a high-level application protocol designed to maximize interoperability in the IoT, and we hope this short introduction gave you a taste of its potential. Web technologies are widely popular and offer all the flexibility and features needed for the majority of future oT applications, including discovery, security, and real-time messaging. While we only flew over the ideas of the WoT, we hope this sparked your interest in making IoT Things more accessible thanks to the Web. The Web of Things architecture is fully described in our book: “Building the Web of Things". The book is also packed with code examples on the Raspberry Pi using the Node.js language. The code is open source and freely available from: https://github.com/webofthings/wot- book. Tags: HTTP iot raspberrypi REST tutorial Websockets wot Scanned with CamScanner