WEB OF THINGS (WoT)
Established in 2007, by Dom Guinard and VladTrifa webofthings.org is a community of developers, researchers, and designers exploring the future of the physical Web. The Web of Things aims to build the Internet of Things in a truly open, flexible, and scalable way, using the Web as its application layer. This is your one place pit-stop for all things WoT: blog posts, events, learning resources, conference and standard activities
Definition of Web of Things (WoT)
Web of Things (WoT) refers to a set of standards formed by the world wide web consortium (W3C) to facilitate the interoperability, fragmentation, and usability of the Internet of Things (IoT). In other words, it is a subset of the internet of things (IoT) and is built around software standards such as REST, HTTP, and URIs to allow devices to interact with one another.
W3C Web of Things
The Web of Things (WoT) seeks to counter the fragmentation of the IoT by using and extending existing, standardized Web technologies. By providing standardized metadata and other re-usable technological building blocks, W3C WoT enables easy integration across IoT platforms and application domains.
Web of Things (WoT) describes a set of standards by the World Wide Web Consortium (W3C) for the interoperability of different Internet of things (IoT) platforms and application domains.
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 IoT 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.”
-Mobidev
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.
Why Do We Need the Web of Things (WoT)?
The Web of Things (WoT) Architecture:
An Example of Web of Things (WoT) Application:
Why Do We Need the Web of Things (WoT)?
There’s no doubt that the internet of things (IoT) has made things easier for us, but it also brings in complexities as the number of devices around us increases. One of the significant hurdles in the widespread adoption of IoT has been the difficulty communicating and managing all these devices.
To communicate with your ten IoT devices, you need ten mobile applications. This won’t be convenient as you will have to switch between one app to another. Unfortunately, that is happening with most IoT devices.
The problem is that there’s not a single “lingua franca” spoken by every object – there are 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 been able to actualize its full potential.
Connecting devices to the internet and giving them IP addresses is only the first step towards the internet of things as it facilitates data exchange. However, it doesn’t guarantee that devices understand what it means.
That’s why we need something like HTTP, a universal way to transfer data in text, images, sound, and other media elements so that devices communicate with each other.
The Web of Things – or WoT – is what fills this vacuum by using and adapting Web protocols to connect anything in the physical world and give it a presence on the World Wide Web!
WoT vs. IoT
When we look from a distance, the purpose served by both IoT and WoT is very similar. Their motive is to connect smart devices to the internet. There are some minor differences on paper, but they play a significant role when you know the critical meaning behind them. When trying to elaborate their differences, the purpose each serves is the same, but the implementation is where the difference becomes apparent.
IoT is the resolved networking layer between all the devices. That means every individual device needs a medium to communicate with one another. IoT development services serve the purpose of providing every device with a medium to transport information from point A to point B.
However, it has nothing to do with how the data transfers, what the information is, or the purpose of reaching the desired destination. This is a huge limitation that becomes quite noticeable.
Without such standards, it doesn’t make sense to call it the “internet” of things. WoT bridges this gap as it works as an application layer. WoT fixes the rules of the road. The pure existence of WoT is to set systematic paths for the information to transfer between points and ensure compatibility with source and destination.
WoT is not a competition or a substitute for IoT but rather a subset of it. The purpose of WoT is to enhance the features of IoT. It fulfills the purpose by curating the standard definitions and models on how the devices will be represented on the internet.
IoT vs WoT
While the Internet of Things and Web of Things 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 IoT and WoT is the layer at which each establishes interconnectivity between devices. In this case, IoT solves just the network layer between devices. That is, each device has a transport medium over which to communicate.
In contrast to IoT’s network layer solutions, WoT can be thought of as the application layer. It sits on top of IoT conceptually and functionally. WoT is not an alternative or competitor to IoT; instead, it tries to enhance IoT. It does this by defining standard definitions and models for representing devices on the Internet.
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.
The Web of Things (WoT) Architecture:
The WoT is composed of many different progressing architectural standards. Many organizations proposed the standards prompted by W3C. This complete standardization by the world wide web consortium is the foundation of various building blocks. These are:
- Layer 1 - Accessibility / Access
- Layer 2 - Findability / Find
- Layer 3 - Sharing / Share
- Layer 4 - Composition / Compose
Layer 1- Accessibility:
This layer converts anything into a web thing. This will enable us to interact with the converted web thing with HTTP requests. A web thing is a REST API that permits us to communicate with anything in the actual world.
- HTML
- REST API
- URL / URI
- Gateway
- HTTP
Layer 2 - Findability:
It is one thing to make the data more accessible, but it is wholly different than the applications can understand what the data is or the purpose. For this purpose, the second layer comes into action.
It ensures that other HTTP users can use your device, and it is easily discoverable and workable by different WoT applications. It is done by resing the semantic web standards to explain the things and their purpose of existing.
- REST Crawler
- Linked Data
- Link Header
- Search Engines
- JSON
Layer 3 - Sharing:
This layer’s job is to find a safe way to transfer the data across services securely. Different protocols are used at this level, such as TLS, OAuth, etc.
- Social Networks
- OAuth
- RDFa
- Encryption
- Authentication
Layer 4 - Composition:
The fourth step is to find a way and tools to build an application for the web of things. At the Composition layer, web tools span from web toolkits (JavaScript SDKs) that provide a higher-level abstraction to dashboards with programmable widgets, and lastly, physical mashup tools like Node-RED.
- Systems Integration
- Node-RED
- Automated UI generation
- Web Application
- IFTTT
An Example of Web of Things (WoT) Application:
In case of a burglary, you want your CCTV camera to give a signal to your security alarm system and warn you over the web anywhere in the world. This can be made possible by WoT as it establishes communication protocols and standards to create a ‘web’ of things.
Kamal Rupareliya, Intuz, Embeddedcomputing web-of-things
- Interoperability is one of the essential attributes of any internet-facing appliance.
- Web of Things is a web standard of the Internet of Things to enable communication between smart things and web-based applications.
- Mozilla WebThing gateway is a smart IoT gateway that can be used to integrate smart devices in a vendor-neutral way and to provide a web interface to monitor and control devices over the web.
- The Mozilla IoT project provides lots of add-ons to integrate with different smart appliances, third-party APIs, cloud etc. Being an open source project, anybody can add new plugins into this project.
- The Mozilla IoT project provides REST API adhering to the Web of Things standard to communicate with smart devices.
Eclipse and Mozilla did some good work on this aspect. The Mozilla WebThings project, which has two parts:
- WebThings Gateway - A smart IoT gateway focused on interoperability and security, which is also an integral part of the gateway.
- WebThings Framework - A collection of reusable software components to help developers to build their own web things, which directly expose the Web Thing API.
Conclusion
WoT evolves IoT from a pure concept to a fully-developed architectural approach for smart device interaction. It serves to define standards for IoT-enabled devices to communicate better.
Web of things (WoT) is the future improvised version of this existing thing. Web of things is trying to lay down a standardized communication protocol so that every device can communicate with one another.
|
|
Home/ Info/ Products/ BIG TECH Metaverse Metaverse Vs. Virtual Reality PC Buyers Guide/ IEEE 802 Standards Social Media Platforms Technology Videos/ Computer & IT Certifications Processor Generations Memory SSD Vs. HDD HTML 5G Android Tips and Tricks STEM Business Intelligence Tools Web Intelligence Quantum Computing Artificial Intelligence (AI) Robotics Internet of Things (IOT) Renewable Energy Nano Technology Windows Run Commands Mac Keyboard Shortcuts Linux CLi Commands Venus Project/ Computer Security and Law Techno Lingo Encyclopedias Search Engines Glossary Online Jobs Contact
Active Components Passive Components Test Electrical Components Electronics Classification
AWS Certification Google Certification Oracle Certifications cisco certifications Huawei Certification Microsoft Certifications Linux Certification Business Certifications
Google-Cloud-Platform-Guide Amazon-Web-Services-Guide Global-Cloud-Infrastructure-Of-AWS Amazon-Web-Services-Cli-Guide AWS-Cloudformation Devops Microsoft-Azure Oracle-Cloud Digitalocean-Cloud Openstack-Cloud
Certified Enterprise Blockchain Professional (CEBP) Web 3.0 Satoshi Nakamoto Cryptocurrency Dark Web Ethereum NFT Merkle Tree El-Salvador eNaira
Web C++ JAVA Python Python Glossary Angular.js Scala
Copyright BICT Solutions Privacy Policy. | Terms and Conditions apply | All rights reserved.