Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "OM2M/Roadmap"

Line 5: Line 5:
 
== Release 0.8.0 ==
 
== Release 0.8.0 ==
  
The first release of OM2M is planned for [strike]April 8, 2015[/strike]. It will include the following features:
+
The first release of OM2M is planned for April 8, 2015. It will include the following features:
  
 
* Implement the SmartM2M standard. For more information see [http://www.etsi.org/technologies-clusters/technologies/m2m SmartM2M standard]
 
* Implement the SmartM2M standard. For more information see [http://www.etsi.org/technologies-clusters/technologies/m2m SmartM2M standard]
Line 26: Line 26:
 
== Release 1.0.0 ==
 
== Release 1.0.0 ==
  
The second release of OM2M is planned for September 2015. It will include the following features:
+
The second release of OM2M is planned for September, 2015. It will include the following features:
  
 
* Implement the oneM2M standard. For more information see [http://www.onem2m.org/ oneM2M standard].
 
* Implement the oneM2M standard. For more information see [http://www.onem2m.org/ oneM2M standard].

Revision as of 08:49, 31 March 2015

This page describes the current plan for the upcoming features of the OM2M project.

Please note that this roadmap is a moving target. Depending on priorities and community contribution, the roadmap can change any time, so do not take it for granted, but see it as a guidance of direction.

Release 0.8.0

The first release of OM2M is planned for April 8, 2015. It will include the following features:

  • Implement the SmartM2M standard. For more information see SmartM2M standard
  • Provide a modular architecture running on top of an OSGi layer based on Eclipse Equinox.
  • Integrate Maven and Tycho to automate build process and RCP development.
  • Provide a protocol-independent CORE plugin to handle generic REST request.
  • Enable machine registration, application deployment, container management, resource discovery, access right authorization, subscription / notification, group management, and resource announcement.
  • Provide a HTTP communication binding plugin based on Jetty and Apache HTTP client libraries.
  • Provide a CoAP communication binding plugin based on the Californium library.
  • Provide a simple retargeting mechanism to connect HTTP and CoAP enabled devices.
  • Provide an interworking sample plugin with simulated devices to show how to connect legacy devices.
  • Provide a web interface plugin for browsing and debugging each machine resource structure.
  • Provide a DAO persistence layer based on EclipseLink JPA library to support different SQL and NOSQL database solutions.
  • Replace the DB4O database with the H2 database which provide better performance.
  • Introduce required persistence parameters to the "config.ini" file to simplify the JPA configuration.
  • Replace the XSD resource validation with a native validation mechanism that offers more flexibility.
  • Replace the OASIS OBIX library with a native encoder/decoder based on the JAXB library.
  • Improve the OM2M performance by optimizing the resource structure and database access.

Release 1.0.0

The second release of OM2M is planned for September, 2015. It will include the following features:

Back to the top