glossary

The purpose of this page is to create a glossary for the basic OPENi conepts . The glossary has been created based on the content in the DoW and it is expected to evolve and reach a stable v1.0 through the discussions during the startign period of the project.

Cloud based Service (or Service) and Cloud Based Service Provider (or Service Provider)

Any service that exists today on the web and can be accessible through its public APIs by an application that runs on a device. Examples of such service providers today are popular platforms for photo sharing, video & music streaming, recommendations, data storage, data syncing, social networking, bookmarking, news, online payments, analytics, and advertising.

reference: DoW section 1.1.2 Motivation for OPENi [p. 5]

Consumer (or Application Consumer or User)

Any person that uses an application on one of his devices

Developer (or Application Developer)

Any person of busines that is reponsible for creating, deploying or operating an application.

OPENi API Framework

A set of generic web APIs that will abstract the functionality of existing (publicly available) cloud based service APIs. Each OPENi API will provide a set of generic methods, to be used by application developers, which on the backend will bind to several service APIs. For Example, the OPENi Photo API will provide a SearchPhoto method which on the backend will use the APIs of Flickr, Photobucket or some other service provider according to the users preferences to search for photos.

reference: DoW section 1.1.3 Key OPENi Concepts and Features [p. 7]

OPENi Cloudlet

A Cloudlet is the user's personal space in the cloud which he (i.e. the user) can customize in order to store his data and content in the cloud and make them available to applications.

reference: DoW section 1.1.3 Key OPENi Concepts and Features [p. 7]

OPENi Cloudlet Platform

This is the cloud platform that provides users with the necessary capabilities to create, deploy, host and manage their Cloudlets. The OPENi Cloudlet Platform will provide:

• A User Interface (UI) so that users can customize the operation of their Cloudlets - i.e. set/increase/decrease the Cloudlet size, set settings about what data to store, set application permissions about read/write stored data, etc
• A set of APIs so that applications can access the hosted Cloudlets in the platform - i.e. discover the cloudlet, retrieve the user's settings, read/write data, etc

reference: DoW section 1.1.3 Key OPENi Concepts and Features [p. 7]

OPENi Service Enablers

A set of "purpose-built" services that will be delivered by OPENi with the objective to enable application developers to provide their application users with the ability to access multiple cloud based services and/or to combine contextual information from one application, service or device with another. Service enables SHOULD NOT disrupt the business model of nether service providers or application developers. Service Enablers for context brokering, security and authorisation, service failover and multi-device UI rendering will be considered by OPENi.

reference: DoW section 1.1.3 Key OPENi Concepts and Features [p. 7]