 | This article has multiple issues. Please help improve it or discuss these issues on the talk page . (Learn how and when to remove these messages)
|
Web of Things (WoT) describes a set of standards by the World Wide Web Consortium (W3C) for the interoperability of different Internet of things platforms and application domains. [1]
The four WoT building blocks provide a way to implement systems that conform with the WoT architecture.
The key component of WoT building blocks is the WoT Thing Description. A Thing Description describes a virtual or a physical device (Thing). It defines an information model of a Thing based on semantic vocabulary and a serialization based on JSON. TD can be considered as the main entry point for a Thing, like an index.html page for a website. TDs foster interoperability by providing both human and machine-readable (and understandable) metadata about a Thing, such as a title, ID, descriptions, etc. A Thing Description also describes all available actions, events, and properties of a Thing, as well as all available security mechanisms to access them. TDs are highly flexible in order to guarantee interoperability. Besides the standard functionality, it defines a mechanism to extend the functionality (through the Context Extension Framework). [2]
IoT uses a large variety of protocols to interact with Things since there does not exist a suitable protocol. One of the main challenges for the Web of Things is to handle the variety of protocols and interaction mechanisms. This problem is tackled through the Binding Templates. WoT Binding Templates provide a collection of communication metadata blueprints to support various IoT solutions. A Binding Template is created only once and then can be reused in any Thing Description. [2]
The WoT Scripting API is an optional building block of the Web of Things. It eases IoT application development by providing an ECMAScript-based application API in a similar manner to how web browsers provide an API for web applications. By having a universal application runtime system, Scripting API solves the problem of heterogeneity of IoT systems. It also enables creating of reusable scripts to implement the device logic, which significantly improves the portability of the application modules. [2]
The current reference implementation of the WoT scripting API is an open-source project called node-wot, which is developed by the Eclipse Thingweb project. [3]
In WoT architecture, security is relevant to all aspects of the architecture. Specification of each WoT building block contains several considerations regarding the security and privacy of that particular block. Security is supported by certain explicit features, such as public metadata in Thing Descriptions and separation of concerns in the design of Scripting API. There is also a specification called WoT Security and Privacy Guidelines , guiding a variety of security and privacy related concerns. [2]
Connecting objects to the Web arguably started around the year 2000. In 2002, a peer-reviewed paper presented the Cooltown project. [4] This project explored the use of URLs to address and HTTP interact with physical objects such as public screens or printers.
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. [5] While most of the work in the IoT space focused on network protocols, there was a need to think about the convergence of data from IoT devices. 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.
The idea of the Web as an application layer for the IoT started to emerge in 2007. Several researchers started working in parallel to these concepts. Amongst them, Dominique Guinard and Vlad Trifa started the Web of Things online community and published the first WoT manifesto, advocating the use of Web standards (REST, Lightweight semantics, etc.) to build the application layer of the IoT. The manifesto was published together with an implementation on the Sun SPOT platform. At the same time, Dave Raggett from W3C started talking about a Web of Things at various W3C and IoT events. Erik Wilde published "Putting Things to REST", a self-published concept paper looking at utilizing REST to sense and control physical objects. [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 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.[ citation needed ]
However, a number of researchers in the WSN community started considering these ideas more seriously. 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. [9] [10]
Following this, Guinard and Trifa presented their end-to-end implementation of the concepts and presented it in a peer-reviewed publication accepted at the World Wide Web conference in 2009. [11] Building on this implementation and uniting efforts, a RESTful architecture for things was proposed in 2010 by Guinard, Trifa and Wilde. [12] Guinard, Trifa and Wilde ran the first International Workshop in 2010 on the Web of Things [13] and has been an annual occurrence since. These workshops morphed into a growing community of researchers and practitioners could discuss the latest findings and ideas on the Web of Things [ citation needed ].
In 2011, two of the first PhD thesis on the Web of Things were presented at ETH Zurich: Building Blocks for a Participatory Web of Things: Devices, Infrastructures, and Programming Frameworks from Vlad Trifa [14] and A Web of Things Application Architecture – Integrating the Real-World into the Web from Dominique Guinard. [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. [16]
In 2014, the W3C showed an increased interest on the Web of Things and organized the W3C Workshop on the Web of Things, [17] under the lead of Dave Raggett together with Siemens and the COMPOSE European project. This workshop leads to the creation of the Web of Things Interest Group at W3C [18] and the submission of the Web Thing Model. [19]
The same year, Siemens announced the creation of a research group dedicated to the Web of Things. [20] In October 2014, Google also announced its interest in these ideas by launching the Physical Web GitHub project. [21]
The Web of Things Interest Group identified the required set of standards needed for the Web of Things in February 2017. [22] The Working Group has started working on four deliverables called WoT Architecture, [23] WoT Thing Description, [24] WoT Scripting API, [25] and WoT Binding Templates. [26]
A web service (WS) is either:
Web annotation can refer to online annotations of web resources such as web pages or parts of them, or a set of W3C standards developed for this purpose. The term can also refer to the creations of annotations on the World Wide Web and it has been used in this sense for the annotation tool INCEpTION, formerly WebAnno. This is a general feature of several tools for annotation in natural language processing or in the philologies.
REST is a software architectural style that was created to guide the design and development of the architecture for the World Wide Web. REST defines a set of constraints for how the architecture of a distributed, Internet-scale hypermedia system, such as the Web, should behave. The REST architectural style emphasises uniform interfaces, independent deployment of components, the scalability of interactions between them, and creating a layered architecture to promote caching to reduce user-perceived latency, enforce security, and encapsulate legacy systems.
The canvas element is part of HTML5 and allows for dynamic, scriptable rendering of 2D shapes and bitmap images. It is a low level, procedural model that updates a bitmap. HTML5 Canvas also helps in making 2D games.
The Device Description Repository (DDR) is a concept proposed by the Mobile Web Initiative Device Description Working Group (DDWG) of the World Wide Web Consortium. The DDR is supported by a standard interface and an initial core vocabulary of device properties. Implementations of the proposed repository are expected to contain information about Web-enabled devices. Authors of Web content will be able to make use of repositories to adapt their content to best suit the requesting device. This will facilitate the interaction and viewing of Web pages across devices with widely varying capabilities.
HTML5 is a markup language used for structuring and presenting hypertext documents on the World Wide Web. It was the fifth and final major HTML version that is now a retired World Wide Web Consortium (W3C) recommendation. The current specification is known as the HTML Living Standard. It is maintained by the Web Hypertext Application Technology Working Group (WHATWG), a consortium of the major browser vendors.
Internet of things (IoT) describes devices with sensors, processing ability, software and other technologies that connect and exchange data with other devices and systems over the Internet or other communication networks. The Internet of things encompasses electronics, communication, and computer science engineering. "Internet of things" has been considered a misnomer because devices do not need to be connected to the public internet; they only need to be connected to a network and be individually addressable.
The W3C Geolocation API is an effort by the World Wide Web Consortium (W3C) to standardize an interface to retrieve the geographical location information for a client-side device. It defines a set of objects, ECMAScript standard compliant, that executing in the client application give the client's device location through the consulting of Location Information Servers, which are transparent for the application programming interface (API). The most common sources of location information are IP address, Wi-Fi and Bluetooth MAC address, radio-frequency identification (RFID), Wi-Fi connection location, or device Global Positioning System (GPS) and GSM/CDMA cell IDs. The location is returned with a given accuracy depending on the best location information source available.
WebRTC is a free and open-source project providing web browsers and mobile applications with real-time communication (RTC) via application programming interfaces (APIs). It allows audio and video communication and streaming to work inside web pages by allowing direct peer-to-peer communication, eliminating the need to install plugins or download native apps.
The Open Geospatial Consortium (OGC) is an international voluntary consensus standards organization that develops and maintains international standards for geospatial content and location-based services, sensor web, Internet of Things, GIS data processing and data sharing. The OGC was incorporated as a not for profit in 1994. At that time, the official name was the OpenGIS Consortium. Currently, commercial, government, nonprofit, universities, and research organizations participate in a consensus process encouraging development, maintenance, and implementation of open standards.
JSON-LD is a method of encoding linked data using JSON. One goal for JSON-LD was to require as little effort as possible from developers to transform their existing JSON to JSON-LD. JSON-LD allows data to be serialized in a way that is similar to traditional JSON. It was initially developed by the JSON for Linking Data Community Group before being transferred to the RDF Working Group for review, improvement, and standardization, and is currently maintained by the JSON-LD Working Group. JSON-LD is a World Wide Web Consortium Recommendation.
EVRYTHNG is an internet of things (IoT) software company based in London, with operations in Oregon, New York, Beijing, Minsk and Switzerland. The company delivers real-time data and actionable information about “smart products” featuring a digital identity in its EVRYTHNG Product Cloud, which connects consumer packaged goods to the web for business intelligence.
WebAssembly (Wasm) defines a portable binary-code format and a corresponding text format for executable programs as well as software interfaces for facilitating communication between such programs and their host environment.
Crosswalk Project was an open-source web app runtime built with the latest releases of Chromium and Blink from Google. The project was founded by Intel's Open Source Technology Center in September 2013.
WebXR Device API is a Web application programming interface (API) that describes support for accessing augmented reality and virtual reality devices, such as the HTC Vive, Oculus Rift, Meta Quest, Google Cardboard, HoloLens, Apple Vision Pro, Magic Leap or Open Source Virtual Reality (OSVR), in a web browser. The WebXR Device API and related APIs are standards defined by W3C groups, the Immersive Web Community Group and Immersive Web Working Group. While the Community Group works on the proposals in the incubation period, the Working Group defines the final web specifications to be implemented by the browsers.
Vlad Trifa is a computer scientist, researcher and Chief Product Officer at Ambrosus who played a key role in defining and implementing the application layer of the Internet of Things. He is particularly known for his early contributions to the Web of Things along with other researchers such as Dominique Guinard, Erik Wilde and Friedemann Mattern. Vlad is widely published author and a recognized expert in distributed embedded sensing and interactive devices, and their integration with enterprise applications using Web technologies.
SensorThings API is an Open Geospatial Consortium (OGC) standard providing an open and unified framework to interconnect IoT sensing devices, data, and applications over the Web. It is an open standard addressing the syntactic interoperability and semantic interoperability of the Internet of Things. It complements the existing IoT networking protocols such CoAP, MQTT, HTTP, 6LowPAN. While the above-mentioned IoT networking protocols are addressing the ability for different IoT systems to exchange information, OGC SensorThings API is addressing the ability for different IoT systems to use and understand the exchanged information. As an OGC standard, SensorThings API also allows easy integration into existing Spatial Data Infrastructures or Geographic Information Systems.
WebUSB is a JavaScript application programming interface (API) specification for securely providing access to USB devices from web applications.
Dominique "Dom" Guinard is the CTO of EVRYTHNG. He is a technologist, entrepreneur and developer with a career dedicated to building the Internet of Things both in the cloud and on embedded Things. He is particularly known for his early contributions to the Web of Things along with other researchers such as Vlad Trifa, Erik Wilde and Friedemann Mattern. Guinard is a published researcher, a book author and a recognized expert in Internet of Things technologies
The Thing Description (TD) (or W3C WoT Thing Description (TD)) is a royalty-free, open information model with a JSON based representation format for the Internet of Things (IoT). A TD provides a unified way to describe the capabilities of an IoT device or service with its offered data model and functions, protocol usage, and further metadata. Using Thing Descriptions help reduce the complexity of integrating IoT devices and their capabilities into IoT applications.
