1
Important Questions and Answers
CP25C10-Web of Things
Syllabus
1. Introduction to Web of Things: Evolution: From IoT to WoT, Architecture of WoT: Thing
Description, Binding, Servient, Protocol Bindings, Web protocols overview (HTTP, Web
Sockets, MQTT, CoAP), WoT Scripting and Interaction Models (Properties, Actions,
Events).
Activities:
• Mind map comparison of IoT vs WoT
• Analysis of WoT reference architecture.
2. WoT Standards and Thing Description (TD): W3C WoT Architecture and Building
Blocks, Thing Description (TD): Syntax, Vocabulary, JSON-LD format, TD Schema
validation and interpretation, Semantic Annotation in TD.
Activities:
• Write TD for a smart device in JSON-LD
• Validate TD using WoT tools.
3. Implementation of WoT Servients: WoT Servient structure: Exposed vs Consumed
Things, Node-WoT framework, WoT Scripting API, Protocol bindings: HTTP, MQTT,
CoAP.
Activities:
• Build a WoT Servient with Node-WoT
• Demo using WoT Scripting API.
V.
4. Interoperability, Security, and Privacy: Interoperability challenges, Security mechanisms:
U
m
HTTPS, OAuth2.0, Access Control, Privacy and anonymization, Trust and identity in WoT
ap
ecosystems.
at
Activities:
hy
• Present security issues in WoT
,Pr
• Design secure architecture for smart home.
of
./
EC
N
ot
es
, 2
5. Applications and Future Trends in WoT: Smart Cities, Smart Homes, e-Health, IIoT,
Cloud and Edge integration, Data analytics and AI in WoT, Future directions: Digital twins,
Metaverse.
Activities:
• Present case studies of real-world WoT
• Brainstorm WoT smart city features.
6. Integration to WoT: Integrating an Arduino to WoT – Integrating BeagleBone to WoT –
Integrating an Intel Edition to WoT – Integrating other Embedded systems to WoT.
Activities: Create a simple project to integrate an embedded device with WoT.
S.No. Description
Unit-I
Introduction to Web of Things
Basic Concepts
S.
Basic Concept Important Points
No.
Evolution from IoT connects physical devices through networks. WoT uses web standards
1
IoT to WoT and APIs to access and control IoT devices easily.
Web of Things WoT integrates IoT devices using web technologies such as HTTP, URLs,
2
(WoT) REST APIs and JSON.
The main components are Thing Description (TD), Servient, Protocol
3 WoT Architecture
Bindings, and Interaction Models.
A machine-readable document describing a device's properties, actions,
Thing Description
4 events, security and communication interfaces. It is commonly represented
(TD)
using JSON-LD.
Defines how abstract WoT interactions are mapped to specific
5 Binding
communication protocols and their messages.
A software entity that hosts or consumes Thing Descriptions and supports
6 Servient
interactions with physical or virtual things.
Connect WoT interactions to protocols such as HTTP, WebSocket, MQTT
7 Protocol Bindings
and CoAP.
Uses a request-response model. Common methods: GET, POST, PUT and
8 HTTP
V.
DELETE. Suitable for web APIs.
U
m
Provides persistent, two-way communication between client and server over a
9 WebSocket
ap
single connection. Suitable for real-time updates.
at
A lightweight publish-subscribe messaging protocol using a broker. Suitable
hy
10 MQTT
for low-bandwidth IoT networks.
,Pr
11 CoAP A lightweight REST-based protocol designed for constrained devices and
of
./
EC
N
ot
es
, 3
low-power networks. Commonly uses UDP.
WoT Scripting Provides programming interfaces to discover things and interact with their
12
API properties, actions and events.
Represent the current state of a thing. Example: temperature, humidity or
13 Properties
motor speed.
Represent operations performed by a thing. Example: switch on a motor or
14 Actions
unlock a door.
Represent notifications about changes or occurrences. Example: fire alarm or
15 Events
motion detected.
Important equations and representations
Plain-text representation
Concept
IoT model Physical Thing + Sensors/Actuators + Network
WoT model IoT Devices + Web Standards + APIs
HTTP request Client -> Request -> Server -> Response
MQTT communication Publisher -> Broker -> Subscriber
Property interaction Read(Property) -> Current Value
Action interaction Invoke(Action, Input) -> Output
Event interaction Thing -> Event Notification -> Consumer
WoT interaction model Thing = Properties + Actions + Events
Remember for exams: Properties describe what a thing knows, Actions describe what a thing can do,
and Events describe what happens. WoT improves interoperability by providing a common web-
based way to interact with different IoT devices.
Multiple Choice QA
1. What is the main purpose of the Web of Things (WoT)?
A) To replace the Internet with a new network
V.
B) To integrate IoT devices using Web standards
U
m
ap
C) To increase hardware size
at
hy
D) To eliminate communication protocols
, Pr
of
./
EC
N
ot
es
, 4
Answer: B) To integrate IoT devices using Web standards
Reason: WoT uses Web technologies and standardized interfaces to improve interoperability among
IoT devices from different manufacturers.
2. Which of the following describes a Thing Description (TD) in WoT?
A) A hardware manufacturing document
B) A database backup file
C) A machine-readable description of a Thing's metadata and interactions
D) An operating system
Answer: C) A machine-readable description of a Thing's metadata and interactions
Reason: A Thing Description defines a Thing's properties, actions, events, security information, and
communication details, commonly using JSON-LD.
3. What is the primary role of a Servient in WoT architecture?
A) To manufacture IoT sensors
B) To host or consume Things and support their interactions
C) To provide only electrical power
D) To store images exclusively
Answer: B) To host or consume Things and support their interactions
Reason: A Servient combines server and client capabilities. It can expose Things to other applications
and interact with remote Things.
V.
U
4. Which protocol is primarily designed for lightweight communication in constrained IoT devices
m
using a REST-like model?
ap
at
hy
A) FTP
,Pr
of
./
EC
N
ot
es
Important Questions and Answers
CP25C10-Web of Things
Syllabus
1. Introduction to Web of Things: Evolution: From IoT to WoT, Architecture of WoT: Thing
Description, Binding, Servient, Protocol Bindings, Web protocols overview (HTTP, Web
Sockets, MQTT, CoAP), WoT Scripting and Interaction Models (Properties, Actions,
Events).
Activities:
• Mind map comparison of IoT vs WoT
• Analysis of WoT reference architecture.
2. WoT Standards and Thing Description (TD): W3C WoT Architecture and Building
Blocks, Thing Description (TD): Syntax, Vocabulary, JSON-LD format, TD Schema
validation and interpretation, Semantic Annotation in TD.
Activities:
• Write TD for a smart device in JSON-LD
• Validate TD using WoT tools.
3. Implementation of WoT Servients: WoT Servient structure: Exposed vs Consumed
Things, Node-WoT framework, WoT Scripting API, Protocol bindings: HTTP, MQTT,
CoAP.
Activities:
• Build a WoT Servient with Node-WoT
• Demo using WoT Scripting API.
V.
4. Interoperability, Security, and Privacy: Interoperability challenges, Security mechanisms:
U
m
HTTPS, OAuth2.0, Access Control, Privacy and anonymization, Trust and identity in WoT
ap
ecosystems.
at
Activities:
hy
• Present security issues in WoT
,Pr
• Design secure architecture for smart home.
of
./
EC
N
ot
es
, 2
5. Applications and Future Trends in WoT: Smart Cities, Smart Homes, e-Health, IIoT,
Cloud and Edge integration, Data analytics and AI in WoT, Future directions: Digital twins,
Metaverse.
Activities:
• Present case studies of real-world WoT
• Brainstorm WoT smart city features.
6. Integration to WoT: Integrating an Arduino to WoT – Integrating BeagleBone to WoT –
Integrating an Intel Edition to WoT – Integrating other Embedded systems to WoT.
Activities: Create a simple project to integrate an embedded device with WoT.
S.No. Description
Unit-I
Introduction to Web of Things
Basic Concepts
S.
Basic Concept Important Points
No.
Evolution from IoT connects physical devices through networks. WoT uses web standards
1
IoT to WoT and APIs to access and control IoT devices easily.
Web of Things WoT integrates IoT devices using web technologies such as HTTP, URLs,
2
(WoT) REST APIs and JSON.
The main components are Thing Description (TD), Servient, Protocol
3 WoT Architecture
Bindings, and Interaction Models.
A machine-readable document describing a device's properties, actions,
Thing Description
4 events, security and communication interfaces. It is commonly represented
(TD)
using JSON-LD.
Defines how abstract WoT interactions are mapped to specific
5 Binding
communication protocols and their messages.
A software entity that hosts or consumes Thing Descriptions and supports
6 Servient
interactions with physical or virtual things.
Connect WoT interactions to protocols such as HTTP, WebSocket, MQTT
7 Protocol Bindings
and CoAP.
Uses a request-response model. Common methods: GET, POST, PUT and
8 HTTP
V.
DELETE. Suitable for web APIs.
U
m
Provides persistent, two-way communication between client and server over a
9 WebSocket
ap
single connection. Suitable for real-time updates.
at
A lightweight publish-subscribe messaging protocol using a broker. Suitable
hy
10 MQTT
for low-bandwidth IoT networks.
,Pr
11 CoAP A lightweight REST-based protocol designed for constrained devices and
of
./
EC
N
ot
es
, 3
low-power networks. Commonly uses UDP.
WoT Scripting Provides programming interfaces to discover things and interact with their
12
API properties, actions and events.
Represent the current state of a thing. Example: temperature, humidity or
13 Properties
motor speed.
Represent operations performed by a thing. Example: switch on a motor or
14 Actions
unlock a door.
Represent notifications about changes or occurrences. Example: fire alarm or
15 Events
motion detected.
Important equations and representations
Plain-text representation
Concept
IoT model Physical Thing + Sensors/Actuators + Network
WoT model IoT Devices + Web Standards + APIs
HTTP request Client -> Request -> Server -> Response
MQTT communication Publisher -> Broker -> Subscriber
Property interaction Read(Property) -> Current Value
Action interaction Invoke(Action, Input) -> Output
Event interaction Thing -> Event Notification -> Consumer
WoT interaction model Thing = Properties + Actions + Events
Remember for exams: Properties describe what a thing knows, Actions describe what a thing can do,
and Events describe what happens. WoT improves interoperability by providing a common web-
based way to interact with different IoT devices.
Multiple Choice QA
1. What is the main purpose of the Web of Things (WoT)?
A) To replace the Internet with a new network
V.
B) To integrate IoT devices using Web standards
U
m
ap
C) To increase hardware size
at
hy
D) To eliminate communication protocols
, Pr
of
./
EC
N
ot
es
, 4
Answer: B) To integrate IoT devices using Web standards
Reason: WoT uses Web technologies and standardized interfaces to improve interoperability among
IoT devices from different manufacturers.
2. Which of the following describes a Thing Description (TD) in WoT?
A) A hardware manufacturing document
B) A database backup file
C) A machine-readable description of a Thing's metadata and interactions
D) An operating system
Answer: C) A machine-readable description of a Thing's metadata and interactions
Reason: A Thing Description defines a Thing's properties, actions, events, security information, and
communication details, commonly using JSON-LD.
3. What is the primary role of a Servient in WoT architecture?
A) To manufacture IoT sensors
B) To host or consume Things and support their interactions
C) To provide only electrical power
D) To store images exclusively
Answer: B) To host or consume Things and support their interactions
Reason: A Servient combines server and client capabilities. It can expose Things to other applications
and interact with remote Things.
V.
U
4. Which protocol is primarily designed for lightweight communication in constrained IoT devices
m
using a REST-like model?
ap
at
hy
A) FTP
,Pr
of
./
EC
N
ot
es
