Hi Zoltan,
Thanks for sharing this information. Information shared by you is really useful for further analysis of proposed activity. Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Strategy Team | Open Source Group Open Connectivity Foundation (OCF) | Iotivity | Javascript Foundation (JSF) From: Kis, Zoltan [mailto:[email protected]] Sent: Tuesday, April 25, 2017 4:09 PM To: Dwarkaprasad Dayama <dwarka.dayama at samsung.com> Cc: iotivity-dev <iotivity-dev at lists.iotivity.org> Subject: Re: [dev] New IoTivity activity "IoT Software Platform" proposal On Fri, Apr 21, 2017 at 11:30 AM, Dwarkaprasad Dayama <dwarka.dayama at samsung.com <mailto:dwarka.dayama at samsung.com> > wrote: Hi IoTivity dev community members, Having an easy to use and quick to market IoT solutions are future of IoT business. Another important attribute is light in weight because in general IoT devices will be holding less memory as compared to high end smart devices. Considering above key quality attributes, I would like to propose ?IoT Software Platform? a packaged solution that has Kernel, Engine/Compiler/Interpreter & IoT framework. Zephyr is a lightweight, simple and well written OS that is easy to grasp, with a lot of samples available. However, in the stack above, probably this is the part that can be encapsulated most and there are a number of options, as mentioned by others. There seems to be consensus that JerryScript JS engine is a good choice. Other languages/interpreters are gaining interest too in IoT, but we could say JerryScript is a good starting focus. The framework built on JerryScript is again an area where many choices are possible. One of them, and quite mature at that is "zephyr.js" [1], which provides for not only OCF APIs, but also BLE, W3C Generic Sensors, and low level HW APIs (GPIO, PWM, AIO, SPI, I2C, UART, etc). Also, another stack of interest is based on Node.js. For this, iotivity-node [2] provides implements a "low-level" JS API that copies the iotivity C API, and a "high-level" JS API [3] that zephyr.js is also implementing. Also, it defines a test suite for the OCF JS APIs. There is work going on to extend JerryScript with Node.js type module support etc. (see e.g. https://github.com/jerryscript-project/jerryscript/issues/1717 and related PRs). I am not saying JavaScript should be the main focus, but certainly has one of the easiest learning curves. That is further eased by using Zephyr JS IDE [4]. [1] https://github.com/01org/zephyr.js [2] https://github.com/iotivity/iotivity-node [3] https://github.com/01org/iot-js-api [4] https://github.com/01org/zephyrjs-ide Best regards, Zoltan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170425/45f845c4/attachment.html>
