@Luddy0. More to come in the next blog. Some of it is described in my book, specifically the importance of a self classifying "chirp" protocol. Open Source communities will maintain and manage the chirp taxonomy but in organic fashion as in Nature, see the presentation made at the IOT world event, and on my linked in page (cannot post URL) And it will be covered in next blog entry and looking forward to your comments then. Thanks for posting your comments. Francis
I'd love to be optimistic about this, but I just don't see how it works from the point of view of the consumers of this data. How can I operate on a stream of data whose format and meaning I learn dynamically, by discovery?
It reminds me a little of the premise of XML: by adopting a 'universal' format whose syntax is self-describing, we can share information from all kinds of sources easily. But has this promise really materialized? Are there systems that process XML sources whose meaning (rather than syntax) isn't independently standardized? I don't see it happening, and I don't understand how this case can be any different. The syntax side of XML works well enough, but the dynamic semantic side has gone nowhere.
If I create a device that does something new, takes some kind of reading from its environment and then announces the availability of this data, how can I write a consumer of that data without having prepared ahead of time to receive exactly that kind of data? I guess I can believe that I might be able to adapt to different formats for the data, but different categories of data altogether? I just don't see it. It sounds too abstract to me. That's especially so considering the volume of data which it is claimed will be available.
This is apart from the question of building an infrastructure that is prepared for several orders of magnitude more devices to begin publishing their presence.
I see IOT being successful in restricted environments where a changing population of devices with very tightly prescribed capabilities either operates in concert or under the control of a server(s). This more abstracted vision of vague capabilities announcing themselves: hard for me to believe.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.