1  Introduction

This document is subject to the OpenNI Service Terms and Acceptable Use Policy[1] and is intended for developers who want to share their Natural Interaction Middleware Library via the OpenNI website.

The objective of the OpenNI Arena website:


This document assumes:

 [2]

All developers that wish to publish a middleware library via the OpenNI Arena will have to declare the OpenNI compliance of their Middleware.

2  The Middleware Library Format

A Middleware Library is a software layer inside an application[3] that serves as an intermediary between the application code and lower level SDK code or system software. Middleware makes it easier for software developers to perform lower level processing on data (in this case, raw OpenNI output), so they can focus on the specific purpose of their application.

Your Middleware should be submitted in a ZIP/RAR file containing a folder with the binaries and resources elements (images, package info, config files, README.TXT, etc.).

Recommended Middleware Library name format: [MWNAME_VERSION.zip].

We recommend the ZIP file to include:

OpenNI requires a folder named OpenNI2 with all its files under the working directory.

The software submitted can be a “free to try”/trial/limited/time limited version of the middleware libraries, as long as the demo uploaded on the OpenNI website is free.

If you need to add licensing conditions, EULA, etc. please place them as separated TXT files in the root directory. (Optional)

The source code files may also be published as a single ZIP file formatted [MWNAME_VERSION_Sources.zip]. You should compress the source files required to compile and run the Middleware, as well as provide instructions for compiling the Middleware Library. (Optional)

If including releases of sample source code that does not contain the core Middleware Library mechanics, they should be published under the following file name: [MWNAME_VERSION_Partial-Sources.zip]

The Middleware should be reusable by applications. It should contain an application programming interface (API) that enables a developer to build an application that uses the Middleware Library.

Note: OpenNI2 must be integrated into your Middleware package before you submit it
OpenNI2 and the submitted Middleware need to be combined into a single functioning system that can be used by a developer who wants to build an application. They must be submitted as a single package that can provide both the functionality of OpenNI2, and of the Middleware library.

3  Checklist before Middleware Library Submission


4  Publish a Middleware Library

Elements required to upload your Middleware Library on the OpenNI site:


5  Middleware Library Review Process

The Middleware Library Review process evaluates the Middleware for release to the OpenNI Arena website. This evaluation checks to ensure that the Middleware adheres to guidelines listed in this document.

After submission, we will respond to the developer within a reasonable amount of time. At the sole discretion of the reviewer, we may request clarification on specific items or reject the middleware. In all cases, a notification will be sent to the developer’s registered email address.

Endnotes:
  1. OpenNI Service Terms and Acceptable Use Policy: http://www.openni.org/terms
  2. [Image]: http://www.openni.org/about/openni2_architecture-3/
  3. application: http://www.techterms.com/definition/application
  4. http://openni.org: http://openni.org
  5. OpenNI Service Terms and Acceptable Use Policy.: http://www.openni.org/policy