| Re: [m2m-iwg] M2M Top-Level Project |
|
Benjamin, I agree that writing the scope of such a top-level project will be difficult. As we’ve discussed in the past, part of the problem is that there are a number of terms out there that overlap in meaning: machine-to-machine, internet of things, internet of everything, etc. Coming up with a scope that is inclusive but still finite is going to be a challenge. The M2M working group has the same challenge. I like your suggested theme of “Connecting”. Are you suggesting that as a potential scope statement, or as the name of the top-level project? From: m2m-iwg-bounces@xxxxxxxxxxx [mailto:m2m-iwg-bounces@xxxxxxxxxxx] On Behalf Of Benjamin Cabé Hi Mike, all, +1, definitely. I think a top-level project would really help to federate M2M projects under a common umbrella. It would be good to discuss what domains we would like the top-level project to cover. At the moment the M2M IWG charter states that it coordinates the work around tools, frameworks and protocols for M2M ; which is probably a good basis for a top-level project charter. However, I think we should be more clear regarding the fact that some projects are targeting constrained embedded devices (Mihini, Paho clients), and some other target full-fledged servers (e.g. Ponte). Also, the M2M IWG as of today is very much focused on enabling M2M by providing the basic building blocks (device management, communication protocols etc.), while I think there should also be room for technologies that are further down the development chain, especially the ones allowing the development of end-user applications making use of M2M data. From a very high-level perspective, I'd like to have a top-level project with a tagline that could be "Connecting". Connecting machines to machines (embedded agents, protocols, brokers, protocol "adapters"…), connecting developers to machines (tools, debuggers, simulators, code generators …), connecting end-users to machines (SCADA, visual dashboards, …). What are your thoughts? Benjamin-- De : Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
|