The OM2M project is an open source implementation of the ETSI M2M standard. It provides a framework for developing services independently of the underlying network and aims to facilitate deployment of vertical applications and heterogeneous devices.

This is a great initiative. I am currently actively studying ETSI M2M standard and existing open source materials (porting Actility open source gateway to RaspberryPi). I think such platform can leverage commons issues an M2M application and/or service provider may face.

You can count me as an interested individual for this project. I may also contribute.

Great! I experimented also the Actility solution which is partially open source. I hope to provide within OM2M a full open source and extensible ETSI M2M platform. Next, OM2M will follow the OneM2M specifications (ftp://ftp.onem2m.org) for a global M2M platform.
It is pleasure to work with you.

Hi Giuseppe,
I don't know, your domain of interest: sensors, network, service, architecture, use case, M2M in general, etc. I think we can imagine plenty interesting plugins, extensions, use, etc.
We can start to exchange and when the source will be published you will be ready .

Thierry,
I'm interested in M2M in general. At present, we are working on the implementation of GIP for managing non-ETSI devices and on the corresponding ETSI-based GAs and NAs. An open source M2M platform is really important for an horizontal approach common for different use cases and for different application environments and I think this can really provide a strong impulse for a widespread availability of this technology.

This is an excellent initiative. I am currently exploring capability layers(N/G/DSCLs) and resources. There is quite a lot of doubts and queries with respect to the specification. "Count me an interested party" I am also interested in actively contribute to this initiative.

You are welcome. It is true, the ETSI M2M specification is quite complex and evolve rapidly. Fortunately, the M2M service platform follows a RESTful architecture style which simplify considerably the proposed API. We are also working on the OSGi layer to enhance modularity and extensibility.

On 11/29/2013 03:40 PM, Mahdi Ben Alaya wrote:
> You are welcome. It is true, the ETSI M2M specification is quite complex
> and evolve rapidly. Fortunately, the M2M service platform follows a
> RESTful architecture style which simplify considerably the proposed API.
> We are also working on the OSGi layer to enhance modularity and
> extensibility.

What kind of data store is proposed for this initiative. I have just started implementing the NSCL layer with MongoDB as the data store. Although, I am quite for Java, J2EE, Spring for the NSCL layer... just for research purpose... exploring NodeJS @ GSCL layer... I appreciate your thoughts/opinion on this part.

You are welcome. It is true, the ETSI M2M specification is quite complex and
evolve rapidly. Fortunately, the M2M service platform follows a RESTful
architecture style which simplify considerably the proposed API. We are also
working on the OSGi layer to enhance modularity and extensibility.

Hi ,
we are waiting for the result of the trademark review and hope the next step will start quickly because we are ready to upload the source in eclipse foundation. You will have access to a very flexible implementation of ETSI
standard based on OSGI. So you will be able to specialise or extend very easily the code for a gateway or a device. We also start to develop tutorial and experiment them with students from my University.

I have just come across this thread while evaluating Eclipse Paho. My company has been working in the M2M field for a few years (we develop M2M middleware). We are then very interested in this proposal, at least for testing and probably for developing as well. I understood that the proposal has been accepted and should be started in the weeks to come. I am looking forward for the beginning of this project then.

The wiki will give you all information to download OM2M (clone the git) and to download 3
other packages. The complete IP process is not finalised with eclipse so manual download
is still necessary for those 3 packages (DB4O, obix and ETSI XSD files ).