[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2m-iwg] M2M Top-Level Project Charter Draft
|
Kai/all,
Thanks a lot for your input. A good point, and +1 for IoT as mentioned before.
While I don't want to reply to more than a subject, the SCADA thread here is equally important, certainly not just to Kai or myself. And probably a bit harder (given its sheer size and sub-projects
) SCADA shall also find its places under such M2M or IoT (or whatever the name ends up being) umbrella.
For now, boht SCADA and Ponte probably best belong in the "Incubator" chapter, unless this is just a "playground" by itself for other smaller projects and initiatives?
You raised a good question about the layers for Sensor Web and IoT/M2M.
Some of these suggest more:
Best Regards,
Werner
On Tue, Jul 2, 2013 at 1:41 PM,
<m2m-iwg-request@xxxxxxxxxxx> wrote:
Send m2m-iwg mailing list submissions to
m2m-iwg@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://dev.eclipse.org/mailman/listinfo/m2m-iwg
or, via email, send a message with subject or body 'help' to
m2m-iwg-request@xxxxxxxxxxx
You can reach the person managing the list at
m2m-iwg-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of m2m-iwg digest..."
Today's Topics:
1. Re: M2M Top-Level Project Charter Draft (Kai Kreuzer)
2. Eclipse SCADA introduction (J?rgen Rose)
3. Re: M2M Top-Level Project Charter Draft (UOMo)
----------------------------------------------------------------------
Message: 1
Date: Mon, 1 Jul 2013 23:16:24 +0200
From: Kai Kreuzer <kai@xxxxxxxxxxx>
To: m2m Industry Working Group <m2m-iwg@xxxxxxxxxxx>
Subject: Re: [m2m-iwg] M2M Top-Level Project Charter Draft
Message-ID: <F5944C78-C773-4EF3-97B3-C6C9C0D6CF9F@xxxxxxxxxxx>
Content-Type: text/plain; charset="windows-1252"
Hi Benjamin,
I quite like the charter! And I have a VERY boring suggestion for the naming: Eclipse IoT :-)
I know, a big buzzword and its hype might be over one day, but at the moment I would actually see it as the most descriptive and appropriate, so I wanted to throw it into the discussion.
In the scope section you write:
"Implementation of communication protocols applicable to M2M communications due to their nature (bandwidth efficiency, security, ?)"
Looking from the Home Automation perspective, I think this is a too narrow scope. For HA, the M2M communication part is not so important, but rather the protocol that is used to communicate with different gateways. Just to give you an example: For the EnOcean protocol (see http://www.enocean.com/en/energy-harvesting-wireless/), it is not so interesting to understand what goes over the radio (what is very constrained), but how to communicate with the usb radio stick over the serial interface. So I think the protocol scope would actually boil down to "Implementation of communication protocols". Open question would be: Which OSI layers would be in scope here? Is 4-7 enough or would you also see layers 1-3 in the scope?
Best regards,
Kai
