W3C home > Mailing lists > Public > public-wot-ig@w3.org > May 2016

Re: minutes and actions from call on WoT & iotivity/OCF

From: Carsten Bormann <cabo@tzi.org>
Date: Fri, 20 May 2016 15:09:02 +0200
Message-ID: <573F0C6E.5000403@tzi.org>
To: "Kis, Zoltan" <zoltan.kis@intel.com>
CC: Dave Raggett <dsr@w3.org>, Public Web of Things IG <public-wot-ig@w3.org>, Markus Jung <markus.jung@samsung.com>, Kevin Gavigan <kgavigan@jaguarlandrover.com>
Good point.  Using a JavaScript code base might provide good affinity to
the scripting API crowds.  How stable, how aligned with OCF
developments, how active would you describe this work?

Grüße, Carsten


Kis, Zoltan wrote:
> For the record, one could also use iotivity-node:
> https://github.com/otcshare/iotivity-node
> 
> Best regards,
> Zoltan
> 
> 
> On Fri, May 20, 2016 at 1:16 PM, Carsten Bormann <cabo@tzi.org
> <mailto:cabo@tzi.org>> wrote:
> 
>     Dave Raggett wrote:
>     > Iotivity is available as a plugin for the eclipse IDE on Linux with
>     > ports under development for Windows and iOS. This provides an emulator
>     > for devices conforming to the OCF specifications. Iotivity is also
>     > available for embedded systems running Linux, but is not suitable for
>     > microcontrollers with just kilobytes of RAM.
> 
>     Before people get too confused about this summary text:
> 
>     We were specifically talking about the simulator, which runs as an
>     Eclipse plugin (Java-based) and therefore needs a more powerful PC-style
>     environment.  IoTivity of course also provides components that run on
>     Things, down to RFC 7228 class-1 devices and below (there is even an
>     Arduino build).
> 
>     Grüße, Carsten
> 
> 
Received on Friday, 20 May 2016 13:09:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:03 UTC