On 31/08/2016 19:14, Ian Skerrett
wrote:
Laurent,
Thank you for
the Edje information. However, for the white paper we don’t
plan on putting detail project descriptions. We will
certainly put links to the projects.
Hmm, OK.
I was just trying to reproduce what was in the section "
OS Stack for IoT Gateways", with short descriptions about Kura and
SmartHome, or in the section "
OS Stack for IoT Platforms", with a short description about OM2M.
What I do want
to make sure is that we describe the general features for
each stack. For example, what are the key software features
required on an IoT device. We have try to define these
features in the white paper. Do you agree with them?
I do.
-
Laurent
Ian
Hi
Ian, Benjamin,
Here's a proposal for some content for a Edje-related
paragraph in the "OS Stack for Devices" section.
I couldn't edit on the doc itself, so here it is inlined, so
it doesn't get lost.
Eclipse Edje defines a standard high-level Java API for
accessing hardware features delivered by 32-bit
microcontrollers (MCU) for using serial links, general purpose
inputs/outputs, or digital/analog converters. MCUs are small,
low-cost, low-power processors designed to run software in
resource-constrained environments: low memory (typically KB),
flash (typically MB) and frequency (typically MHz). MCUs are
provided by silicon vendors along with evaluation kits and are
typically the ideal vectors for large scale deployments of
low-power and cost-effective IoT, embedded or wearable
devices. Edje aims at unifying and easing the programming of
apps for MCUs using the largely adopted Java language.
I'll try to get ASAP a working setup to be able collaborate on
the doc.
Regards,
-
Laurent
|
![MicroEJ]()
|
Laurent
Lagosanto
•
Senior
Architect
Tel:
+33 (0)6 86 70 64 38
11,
rue du Chemin Rouge, IS2T - Bât. D
44300
Nantes, France
MicroEJ
• Developer
• Community
![Twitter]() ![LinkedIn]() ![Youtube]()
|
|
|
This
email (and all attachments) may contain
information that is proprietary privileged, and/or
confidential. If you received this e-mail in error
or if it was improperly forwarded to you, the
information contained in the e-mail should, at all
times, remain confidential. Please notify the
sender immediately by e-mail, and delete or
destroy the original and any copies. Any
unauthorized use, disclosure, reproduction,
retention or distribution by any person other than
the intended recipient is strictly prohibited.
|
On 30/08/2016
19:57, Ian Skerrett wrote:
Benjamin and I
have been working on a new way to talk about the Eclipse IoT
community. Our community has come a long way over the last
number of years. We typically talk about Eclipse IoT as
implementing IoT standards and IoT frameworks. This is
certainly still true but I think it does not encompass a lot
of our new projects.
The new approach
we are suggesting is to show how the Eclipse IoT community
is implementing 3 different stacks of open source software
for IoT solutions. The 3 stacks target: 1) devices, 2)
gateways and 3) IoT platforms. We have written the first
draft of a white paper to describe each of these stacks. We
will also be following up with a presentation and eventually
an update web site.
During the IoT
WG meeting on Wednesday we would like to discuss the white
paper and get your feedback. https://docs.google.com/document/d/1bDtkBw560wihAUv-UG9Srwqb6xsr-ZD1mgeYgDDRt_E/edit?usp=sharing
Thanks
Ian
_______________________________________________
iot-wg mailing list
iot-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-wg
_______________________________________________
iot-wg mailing list
iot-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-wg
--
 |
Laurent Lagosanto •
Senior
Architect
Tel:
+33 (0)6 86 70 64 38
11, rue du
Chemin Rouge, IS2T - Bât. D 44300 Nantes,
France
MicroEJ • Developer • Community
   |
|
|
This
email (and all attachments) may contain information that
is proprietary privileged, and/or confidential. If you
received this e-mail in error or if it was improperly
forwarded to you, the information contained in the
e-mail should, at all times, remain confidential. Please
notify the sender immediately by e-mail, and delete or
destroy the original and any copies. Any unauthorized
use, disclosure, reproduction, retention or distribution
by any person other than the intended recipient is
strictly prohibited.
|
|
