Dylan conway

Dependency of T31 with other tasks

Component Text Deliverable Reference
Service Enablers Service enabler: A service enabler is a service building block or low-level service that, unlike applications runs close to the platform. As such is able to access data efficiently and store results as part of the platform. As service enablers extend the capabilities of OPENi, any internal stakeholder may be realized as service enabler. Internal stakeholders which are not supported by the generic API may expose their own API. For example, a timeline service enabler can generate a timeline for a requested user and expose it to any requesting application. D2.5 v.1 p.23
Core Service Enabler These components where identified as part of the core platform out of the use cases and user stories. D2.5 v.1 p.24
Synchronizer The synchronizer synchronizes content between cloud-based services and the OPENi platform. When a cloud-based service has new data the synchronizer updates the OPENi platform and vice versa. D2.5 v.1 p.24
Objects  Cloud-based service: As defined in previous documents.
 Item: Any digital object that can belong to an individual, such as videos, news or personal (social network) information and can be stored or referenced in the cloudlet.
 External Item: Any item that can be stored with a cloud-based service
 Temporary Item: Any item that is stored temporarily.
 Relations: Any relation between items.
D2.5 v.1 p.25
Anonymised data As a developer, I want to store anonymised personal user data with the OPENi platform provided directly from the end user (and/or 3rd Party Services e.g., mobile operators, social networks or tracking services), so that I can access them. D2.5 v.1 p.28
Personal Data Storage in OPENi As a user, I want to store personal data directly with the OPENi platform, so that it is secure and private. D2.5 v.1 p.31
Retailer Signup Data import, data sync, user centric D2.5 v.1 p.47

Related

Wiki: T31-_OPENi_APIs_Specification
Wiki: T3.1- OPENi APIs Specification