Good to know.
Since the draft you mention has turned into a working group draft quite
some time already, I would be interested in input what would need to be
changed to obtain compatibility.
Gr??e, Carsten
Lankswert, Patrick wrote:
> Carsten,
>
> Although the standards folks have taken guidance
Hi,
A new getting started guide would be very nice.
When doing so could someone also describe some demo scenarios like you have to
start this application and then this and now they can send messages to each
other using this part of the specification. I am lost in all these binaries
that are get
IoTivity is now part of the standard OpenWrt package feed [0]. You can install
it like every other package in OpenWrt trunk. The OpenWrt package contains some
patches to the build system which are needed to make it build on different
platforms and to provide the build options to the compiler. It
R&D Center, IoT Solution Lab. | Web & Convergence Team
Principal Engineer
T: +82-31-301-6107, M: +82-10-9530-6107
E-mail :juney at samsung.com
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachmen
Carsten,
Although the standards folks have taken guidance from
draft-bormann-core-links-json, the link format in JSON for OIC does not adhere
to the draft and not compatible. They have also made it the default format of
OIC.
Pat
> -Original Message-
> From: iotivity-dev-bounces at lis
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150702/bc288b51/attachment.html>
- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150702/0a5752d9/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 141666 bytes
Maybe I should mention at I'm at this very moment integrating the
technical content of draft-li-core-cbor-equivalents-00.txt into
draft-ietf-core-links-json -- that should enable the use of CBOR for
link-format as well.
One other aspect (since I don't have access to the spec):
Since you want to ge
On Thursday 02 July 2015 15:19:03 ??? wrote:
> Thiago,
>
>
>
> I?d just like to confirm one thing.
>
> My understanding from your explanation is if there is someone to wants to
> use JSON,
>
> then it is very easy to add JSON parser and use it based on current
> IoTivity API implementation. Is
On Thursday 02 July 2015 17:06:14 Hauke.Mehrtens at lantiq.com wrote:
> Why not replace the complete documentation with a link to some wiki pages or
> integrate the wiki pages into the website? I do not think that we will get
> lots of problems with some people adding bad content, only spam would b
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150702/07af7690/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201507021504235_Z5JE7EUA.gif
Type: image/gif
Size: 13168 bytes
Des
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150702/8db30b28/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201507021501993_BEI0XT4N.gif
Type: image/gif
Size: 13168 bytes
Des
12 matches
Mail list logo
