>Is a devcie-to-device spec what you need? >I note UPnP is working on a device to >cloud spec.
There are 10+ communication protocols in active development targeting iot applications. They are all very similar in technical aspects: plaintext protocols for structured data with extra features. Such protocols are only a common communication fabric, they do not define any schema for transmitted data or objects.
Say, there are 10 different smart thermometers from different brands that can see each other on the network, send data to each other, but the temperature data they send will be in 10 different incompatible formats.
Indeed, all you have to do is define the object name and object type then wrap it in some kind of format. You can do it in ASN.1(SNMP), TLV(RPC), XML(UPnP/SOAP), JSON(AJAX) or D-BUS(AllJoyn)... there are hundreds way to do the same thing. You can even invent new object schema easily and engieers love to invent stuff, even though there are lots of well-defined, implemented, tested then outdated, forgotton standards.
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. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.