Conoce como reutilizar aplicaciones estándar web ya existentes para una fácil integración con aplicaciones de terceros. Paolo Carrasco Especialista en Experiencia de Usuario 10 años de experiencia en el mundo de la tecnología, desarrollando, liderando equipos y ahora en el mundo de la experiencia de diseño. Fausto Castañeda Desarrollador Software Ing. en Electrónica y Redes de la Información, con 6 años de experiencia como desarrollador de software, hardware y telemática.

1. Web of Things (WoT)
Fausto Castañeda | Paolo Carrasco
Thoughtworks Ecuador
Intro and Demo

2. Where we are now?
We have an "internet of screens"*.
We need "smart stuff".
* Philip Moynagh - https://youtu.be/C8NMRpZb6Ss

3. What is expected from companies today?
To response immediately:
- to the needs of the users
- to the trends of the market
- to the government regulations

4. What can IoT bring to us?

5. What is expected from developers today?

6. How could IoT be helpful?
● Monitor
● Search
● Control

7. Key concepts of IoT
Physical stuff
Unique ID
Events
Listener / Controller
channel

8. WoT - Web of Things
Interconnection of things over the web.
● Features
○ Uses HTTP.
○ Synchronous functionality through Resource Oriented Architecture. i.e.
REST.
○ Asynchronous functionality through web syndication standards like ATOM
or server-push web mechanisms as COMET or HTML5-compliant
technology like WebSockets.

9. ¿Why REST?
It is lightweight (in comparison with others, like SOAP)
It is great to represent objects in general:
● Insert a new one
● Check their status
● Update them
● Remove a new one

10. Example
Request
PUT https://check-my-house.now/fausto/radio/my-radio
{"status": "on"}
Response
200 OK
{status: on}

11. WoT vs IoT
IoT WoT
Communication over network layer (IP). Communication over application layer
(HTTP).
RFID, Zigbee, Bluetooth, 6LowPAN,
CoAP
HTTP, REST, HTML5, URI, JS, Web
Feeds
High coupling Loose coupling

12. Web of Things
● Pros
o Reusability of standard web applications that already exist (URI, HTTP,
REST, JS, etc).
o Easy integration with third party applications.
o Loose coupling of services provided by smart objects.
o Uniform interface to access and build on the functionality of smart
objects.
● Cons
○ In RESTful WoT applications, HTTP may be too heavy for battery
powered devices.

13. CoAP
● Constrained Application Protocol
● Web transfer protocol optimized for constrained power and
processing capabilities of WoT smart objects.
● Alternative to HTTP.
● Applications:
○ Smart objects are large in volume.
○ Smart objects are deployed in the field.
○ Smart objects are frequently communicating with the Web.
○ Smart objects are transferring high volume of data.
○ Smart objects are sleeping between the communication sessions.
● Features:
○ Simpler hardware requirements than HTTP.
○ Compact binary header.

14. IMPLEMENTATION
Review of Frameworks for WoT

15. Platforms

16. WoT - GitHub
Name Description
EPCIS Web
Adapter
Fosstrak module for making RFID tagged objects
accessible through REST
AutoWoT Java program that integrate smart devices into the WoT
ThngDroid A REST client and extensible API wrapper for all Android
devices.
EVRYTHNG Free Online Service. A set of APIs to make products
smarter and more connected.
aREST* REST Api for Arduino
Ethernet Arduino Ethernet Shield is a network module that connect
Arduino to internet and provides the library for develop
applications with HTTP, DHCP, TELNET, DNS.

17. CoAP - Implementations
Project Programming
Language
Link
Californium Java https://www.eclipse.org/cali
fornium
CoAPthon Python https://github.com/Tanga
nelli/CoAPthon
CoAPSharp C#, .NET http://www.coapsharp.co
m
nCoAP Java https://github.com/oklein
e/nCoAP
Ruby CoAP Ruby https://github.com/nning/
coap
Cooper Javascript https://github.com/mkova
tsc/Copper

18. DEMO
Simple example of WoT

19. Controlling bulbs over web
REST Server
A
B
C
DWeb client

20. Controlling bulbs over web (2)
REST Server
PUT /bulb/A/1
A
B
C
DWeb client

21. Controlling bulbs over web (3)
REST Server
PUT /bulb/A/0
A
B
C
DWeb client

22. Controlling bulbs over web (4)
REST Server
GET /bulb/B
A
B
C
DWeb client
RESP: 1

23. Controlling bulbs over web (5)
REST Server
GET /bulb/C
A
B
C
DWeb client
RESP: 0

24. Controlling bulbs over web (5)
● Bulb REST Server
○ Ethernet API
○ aREST API
○ Arduino API
● Bulb Client
○ Yeoman
○ AngularJS
○ Bootstrap
● Hardware
○ Arduino Uno
○ Arduino Ethernet Shield R3
○ LED, Resistors and Transistors.

25. Controlling bulbs over web (6)
● Projects
○ Bulb Server
https://github.com/Fausto888/WOT-bulb-service.git
○ Bulb Client
https://github.com/Fausto888/WOT-bulb-ui.git

26. More resources
A Web of Things application architecture - Guinard Dominique
(available in PDF)
REST in practice - Jim Webber, Savas Parastatidis, Ian Robinson
(to understand more about REST)
Internet of Things - EconocomTV: http://youtu.be/p_R5ZVWMhzM

27. QUESTIONS?

28. THANK YOU
For questions or suggestions:
Fausto Castaneda
fcastane@thoughtworks.com
Paolo Carrasco
paolo.carrasco@thoughtworks.com