Re: [m2m-iwg] M2M Top-Level Project Charter Draft

[UOMo <uomo@xxxxxxxxxxx>]

Ben/all,

Thanks for the update. It's a good start, though there are still a few lose ends.

First of all, naming like the example you already mentioned, "Connect" seems equally bad, see another magazine by exactly that name:

http://www.connect.de/ or various companies, most of them related to mobile communication rather than M2M or IoT.

Mylyn could be seen as probably the best example so far, since it not only has a "strange" name based on an idea and earlier product name that then forced it to change the name slightly. If the aim of the top level project was to focus on Connecting Machines to Machines, then the name should also reflect that. Personally beside simply calling it "M2M" (or must a name be different from the IWG for some organizational reason?) IoT would be brief but precise. Everything else would dilute it into "any form of communication" including Mobile phones, etc. If you want that, fine, if not, try to avoid these words. About the fancy Maori words, let me place the caveat from both UOMo (which was inspired by "OOo" the group once behind OpenOffice, but it also means "Man" or "Humane" which is a nice side-effect) where depending on the language people land everywhere from "OMO" (a washing powder) to "Homo" (and don't even start Italian, e.g. at Google, Twitter, etc. without the Eclipse context) and many have problems pronouncing it. Or another project I'm heavily involved in, Agorava (a creation of "Agora" the Latin word for "Market" or "Social Meeting Place" and the ending of "Java") where people especially in English-speaking countries seem to have extreme difficulties pronouncing it, every time we have e.g. a conference call with Oracle about synergies with Security, OAuth or JSRs involving these technologies.

Social Media and all similar services is also what you'd end up getting mistaken for more easily if you name the TLP "Connect", "Talk" or similar.

Especially its OAuth and other aspects at Ponte make it interesting not just for me, but e.g. those involved in Agorava. Red Hat has a large stake there, and it's needles to point out, that with the takeover of Fuse MQ it also gathered even more exposure and use cases for protocols like MQTT than it had before. 

Check out https://github.com/jottinger/sensor by Joseph Ottinger, who seems mainly involved in AMQP now. I didn't run the HW side of this myself, but had this End-to-end Sensor Web example involving Java EE and Android on my radar for quite a while.

This is why I feel both Java (Embedded, probably both SE and ME, while the latter may take a little, but all those Raspberry Pi demo cases out there work now and should be taken into consideration) and Android are notoriously missing.

Ponte beside OAuth also aims at several aspects of e.g. MQTT that make proper modularization highly recommended, and some of it may end up under "Protocols" or shared with projects there such as Paho.

Protocols is also an area, where other OASIS standards like UnitsML, SensorML or UCUM should become more relevant, too. Another area, Ponte is looking into based on .JS.

Werner

On Mon, Jul 1, 2013 at 6:00 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. M2M Top-Level Project Charter Draft (Benjamin Cab?)


----------------------------------------------------------------------

Message: 1
Date: Mon, 1 Jul 2013 08:18:42 -0700
From: Benjamin Cab? <bcabe@xxxxxxxxxxxxxxxxxx>
To: m2m Industry Working Group <m2m-iwg@xxxxxxxxxxx>
Subject: [m2m-iwg] M2M Top-Level Project Charter Draft
Message-ID: <CDF769EB.455CA%BCabe@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

All,

I have initalized a wiki page with a charter draft.
http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/TLP_Charter_Draft

I am looking forward to your comments, since it is of course a very first pass. Also, we can certainly discuss this document further during our call tomorrow.

Cheers,
Benjamin--


De : Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx<mailto:mike.milinkovich@xxxxxxxxxxx>>
Soci?t? : Eclipse Foundation
R?pondre ? : "mike.milinkovich@xxxxxxxxxxx<mailto:mike.milinkovich@xxxxxxxxxxx>" <mike.milinkovich@xxxxxxxxxxx<mailto:mike.milinkovich@xxxxxxxxxxx>>, m2m Industry Working Group <m2m-iwg@xxxxxxxxxxx<mailto:m2m-iwg@xxxxxxxxxxx>>
Date : mardi 11 juin 2013 21:02
? : "m2m-iwg@xxxxxxxxxxx<mailto:m2m-iwg@xxxxxxxxxxx>" <m2m-iwg@xxxxxxxxxxx<mailto:m2m-iwg@xxxxxxxxxxx>>
Objet : [m2m-iwg] M2M Top-Level Project

All,

The M2M working group has been pretty successful in recruiting projects. Has the time come to consider creating a new top-level project to help create a cohesive project community for our M2M technologies?

For those who are unfamiliar with them, top-level projects are the mechanism which ties a collection of projects in a particular domain to the Eclipse development and IP processes. It requires the creation of a project management committee (PMC), the appointment of a PMC leader, and having a written charter approved by the Board of Directors.

Mike Milinkovich
Executive Director
Eclipse Foundation
mike.milinkovich@xxxxxxxxxxx<mailto:mike.milinkovich@xxxxxxxxxxx>
+1.613.220.3223 mobile
+1.613.224.9461 x228 office
@mmilinkov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/m2m-iwg/attachments/20130701/ea9584a7/attachment.html>

------------------------------

_______________________________________________
m2m-iwg mailing list
m2m-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2m-iwg


End of m2m-iwg Digest, Vol 21, Issue 2
**************************************