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.
Difference between revisions of "OM2M/Roadmap"
< OM2M
(→Fixed bugs) |
|||
| Line 2: | Line 2: | ||
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. | 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 1.0.0 (June 22, 2016) == | ||
| + | === Features === | ||
| + | Implementation of the oneM2M standard. For more information see [http://www.onem2m.org/ oneM2M standard]. | ||
| + | Main supported features: | ||
| + | |||
| + | * Nodes: IN-CSE, MN-CSE, ASN-CSE, and ADN. | ||
| + | * Reference Points: MCA, and MCC. | ||
| + | * Resource types: CSEBase, RemoteCSE, ACP, AE, Container, ContentInstance, Subscription, Group, Node, Request, PoA, etc. | ||
| + | * Request primitives: Retrieve, Create, Update, Delete, and Notify. | ||
| + | * Addressing formats: Structured and Unstructured. | ||
| + | * Addressing modes: Absolute, SP-relative, and CSE-Relative. | ||
| + | * Protocol Bindings: HTTP and CoAP. | ||
| + | * Content Formats: XML and JSON. | ||
| + | * Communication Modes: Blocking, Non Blocking Syhcnronous, and Non Blocking Asynchrnonous. | ||
| + | * Multihop: retargeting via PoA. | ||
| + | * Storage mode: SQL and NoSQL (SQL H2 by default) | ||
| + | * Security: SSL/TLS | ||
| + | |||
| + | === Fixed bugs === | ||
== Release 0.8.0 (April 8, 2015) == | == Release 0.8.0 (April 8, 2015) == | ||
| Line 29: | Line 49: | ||
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=453467 Bug 453467] - Can't access a malformed created application | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=453467 Bug 453467] - Can't access a malformed created application | ||
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=463941 Bug 463941] - OM2M starting blocked on ObixMapper | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=463941 Bug 463941] - OM2M starting blocked on ObixMapper | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 06:03, 1 June 2016
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.
Contents
Release 1.0.0 (June 22, 2016)
Features
Implementation of the oneM2M standard. For more information see oneM2M standard. Main supported features:
- Nodes: IN-CSE, MN-CSE, ASN-CSE, and ADN.
- Reference Points: MCA, and MCC.
- Resource types: CSEBase, RemoteCSE, ACP, AE, Container, ContentInstance, Subscription, Group, Node, Request, PoA, etc.
- Request primitives: Retrieve, Create, Update, Delete, and Notify.
- Addressing formats: Structured and Unstructured.
- Addressing modes: Absolute, SP-relative, and CSE-Relative.
- Protocol Bindings: HTTP and CoAP.
- Content Formats: XML and JSON.
- Communication Modes: Blocking, Non Blocking Syhcnronous, and Non Blocking Asynchrnonous.
- Multihop: retargeting via PoA.
- Storage mode: SQL and NoSQL (SQL H2 by default)
- Security: SSL/TLS
Fixed bugs
Release 0.8.0 (April 8, 2015)
Features
The first release of OM2M 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.
Fixed bugs
- Bug 463673 - Problem in starting the GUI of the IPU sample plugin in the GSCL
- Bug 463778 - Replace the native launcher with an independent single script
- Bug 453467 - Can't access a malformed created application
- Bug 463941 - OM2M starting blocked on ObixMapper