OPENi Service Enablers as per architecture changes and decisions made in London meeting
Authors: CGI
Date: 01/08/2013
Archive: [OPENi_Service_Enablers]
In this article it is presented the most actual set of Service Enablers, based both on D2.5 document and the decisions made in London meeting.
After changes in the architecture, some of the old SE's are not considered as such anymore, as they are conceived now as platform components. Please refer to [OPENi Service Enablers] list for justification. In OPENi we define service enablers to be any addition to the core platform that enables a group of services be developed that otherwise cannot.
Service Enablers
| Service Enabler Name | Description | Partner responsible for | API reference | Comments |
|---|---|---|---|---|
| [Health SE] | APP developers would benefit from having a common Health Service Enabler that allows them to plug into their application. This SE allows to access and manage health and wellness data (physical measures...). If this SE provided HL7 standard compatibility, developers would be able to access to different HealthCare Information Systems. | CGI | - | Potential SE for use case, as per D2.5.. Legal restrictions |
| [Biometric Comparison SE] | The Biometric Comparison SE for user identity management is intended to provide a comfortable and safe way to perform identification onto de system. The main advantage consist of avoiding passwords' handling. However, the major constraint stems from the dependency on the HW and the possibility to embed it on the devices. | CGI | - | Potential SE for identification management. HW restrictions |
| [Compliance SE] | One of the key issues with APP development is ensuring that the data retrieval doesn't break any policy laws as they may change during the lifetime of the app. It has been hightlighted at FIA the cost involved in maintaining this. | ??? | - | |
| [Recommendation SE] | APP developers would benefit from having a common Recommendation Service Enabler that allows them to plug in into their application. This SE will capture data on the performance or utility of their APP by the user. It makes this data available for further recommendation techniques. | NTUA | - | |
| [Timeline SE] | The Timeline SE aggregates the cloudlet data and the Cloud-Based Services data to summarise the user's identity (e.g. activities, data and metadata) over all connected channels into a temporal view. It is exposed to the app developer and enables him the data and events without the need to access the actual data in real time. A timeline can provide different granularity levels (e.g. only metadata) to further the user's privacy. | Ambiesense, WIT | - | |
| [Loyalty Rewards SE] | APPS will look to take personal user's data for use in a campaign or for data mining purposes. This SE allows apps to sign up to a common rewards scheme such as StarAlliance or the One4All card, that are used in Ireland. | Ambiesense | - | |
| [Analytics SE] | APP developers would benefit from having a common Analytics Service Enabler that allows them to plug into their application. This SE will capture data on the performance or utility of their APP by the user. It makes this data available for further analytic techniques. | Betapond | - | |
| [Advertising SE] | VELTI | - | ||
| [Market SE] | A market is a generic component used to sell and buy goods, advertisement space or virtual items. | ??? | - | Potential SE for use case, as per D2.5. |
Comments
Related
Wiki: OPENi Service Enablers
Wiki: Home