Difference between revisions of "IoT/M2MIWG/TLP Charter Draft"

From Eclipsepedia

< IoT
Jump to: navigation, search
(Services and Runtimes)
(Out of scope)
Line 63: Line 63:
 
= Out of scope =
 
= Out of scope =
  
* x
+
* TBD
* x
+

Revision as of 10:37, 1 July 2013

Warning2.png
Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.


Note.png
Naming
In this document, "Eclipse M2M" is used as a temporary name for the top-level project

The following names have been proposed in recent discussions:


This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse M2M Top-Level Project. This document extends the Eclipse Standard Top-Level Charter v1.1, and includes the required content and overrides which follow. It is anticipated that as the standard charter is updated, this charter will incorporate the changes and make adjustments as seen fit by the PMC, and with approval from the EMO and board of directors.

Contents

Overview

The Eclipse M2M Top-Level Project is an open source collaborative software development project dedicated to providing extensible, standards-based protocols, runtimes and tools for enabling a connected world.

  • Descriptive name: xxx
  • Nickname: xxx

Mission

The mission of the project is to provide:

  1. Protocols implementations that can easily be consumed by end solution developers as well as framework developers
  2. Runtimes that abstract the complexity of direct hardware and communication stack manipulation
  3. Tools that facilitate the development of connected systems

This document describes the composition and organization of the project, roles and responsibilities of the participants, and development process for the project.

Scope

The scope of Eclipse M2M is as follows:

  • Implementation of communication protocols applicable to M2M communications due to their nature (bandwidth efficiency, security, ...)
  • Investigation and research related to future protocols
  • Implementation of low-level services (application management, device management, ...) needed for enabling and simplifying the connection of systems with each other, using the aforementioned protocols implementations
  • Implementation of high-level services that enable vertical applications whose primary goal is to connect things
  • Tooling for supporting the use of the aforementioned protocols and services in order to enable the development and the operation of connected systems

Protocols

The project will initially be structured into the following sub-projects:

  • Paho: Paho delivers reference implementations for the MQTT protocol

Services and Runtimes

The project will initially be structured into the following sub-projects, xxx

  • Mihini: Mihini delivers a Linux based runtime enabling application development in programming languages such as Lua and C, and providing services such as Application Management and Device Management.
  • Ponte (?): Ponte provides a server runtime for bridging M2M protocols to REST.

Tooling

  • Koneki Target Management

Incubator Projects

The Incubator will focus on new developments that are relevant to the other Eclipse M2M sub-projects, which because of their nature would not be appropriate for direct inclusion in the effected sub-project. This could be because the work is still experimental, will have a longer timeline than can be contained within a single release, has dependencies on external IP that has not yet cleared the Eclipse Foundation IP process, or is simply potentially too destabilizing in nature.

Out of scope

  • TBD