Breaking News
Comments
Newest First | Oldest First | Threaded View
y_sasaki
User Rank
Author
Re: Is D2D what you need?
y_sasaki   7/9/2014 12:38:47 PM
NO RATINGS
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.

dougwithau
User Rank
Author
XKCD on the new standard
dougwithau   7/9/2014 12:17:28 PM
NO RATINGS
XKCD on Standards

http://xkcd.com/927/

baybal
User Rank
Author
Re: Is D2D what you need?
baybal   7/9/2014 5:07:47 AM
NO RATINGS
>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.

rick merritt
User Rank
Author
Is D2D what you need?
rick merritt   7/8/2014 10:16:43 AM
NO RATINGS
Is a devcie-to-device spec what you need? I note UPnP is working on a device to cloud spec.



Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
Radio
NEXT UPCOMING BROADCAST

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.
Like Us on Facebook
Special Video Section
LED lighting is an important feature in today’s and future ...
05:27
The LT8602 has two high voltage buck regulators with an ...
05:18
The quality and reliability of Mill-Max's two-piece ...
01:34
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...
See the Virtex® UltraScale+™ FPGA with 32.75G backplane ...
Vincent Ching, applications engineer at Avago Technologies, ...
The LT®6375 is a unity-gain difference amplifier which ...
The LTC®4015 is a complete synchronous buck controller/ ...
10:35
The LTC®2983 measures a wide variety of temperature sensors ...
The LTC®3886 is a dual PolyPhase DC/DC synchronous ...
The LTC®2348-18 is an 18-bit, low noise 8-channel ...
The LT®3042 is a high performance low dropout linear ...