Friday, August 01, 2014

IoT: "CoAP" Constrained Application Protocol

Constrained Application Protocol - Wikipedia, the free encyclopedia:
"Constrained Application Protocol (CoAP) is a software protocol intended to be used in very simple electronics devices that allows them to communicate interactively over the Internet. It is particularly targeted for small low power sensors, switches, valves and similar components that need to be controlled or supervised remotely, through standard Internet networks. CoAP is an application layer protocol that is intended for use in resource-constrained internet devices, such as WSN nodes. CoAP is designed to easily translate to HTTP for simplified integration with the web, while also meeting specialized requirements such as multicast support, very low overhead, and simplicity."

www.vs.inf.ethz.ch/publ/papers/mkovatsc-2013-wot-copper.pdf
CoAP for the Web of Things:
From Tiny Resource-constrained Devices to the Web Browser

CoAP and a Web of Things Watching Things | ThoughtWor

IoT Primer: IoT Protocol Wars: MQTT vs CoAP vs XMPP

Internet of Things Protocols- Postscapes
ip-stack

IoT: What exactly is the Internet of Things? Infographic- Postscapes

What exactly is the Internet of Things? Infographic- Postscapes:



IoT: Talking with Things on Internet

But How Do We Actually Talk to the Internet of Things? | Innovation Insights | Wired.com:
"Natural language programs and voice interface systems are increasingly common additional features to devices and seem an obvious solution."


When the Internet was new (for mass-population), there was a lot of guessing what could be done with it,
starting with email, and with web in particular. 20 years later, many of those ideas are actually realized.
On one side, it is much less "perfect" than anticipated, but on the other it is broader: internet is not just a convenience anymore, it is an integral part of life for very large number of people.

The IoT comes with much more hype, but surprisingly without a "killer apps", like email and www ware in the early 90's. Something like Netscape would enable a major breakthrough, on the scale of Google.
So the question now is: what is "cooking" in research labs that may resemble web browser if IoT?
Obvious related, and primary, question is: what is the "www" of "IoT?"
It there is not such ":thing", it should be created NOW.