Difference between revisions of "Wishlist for architecture"
From wiki.gpii
m (category added) |
(Updates June 2013) |
||
| Line 15: | Line 15: | ||
* Thin matchmaker (and transformer) / allowing web based applications and other apps more to use the common setting - 0.2 | * Thin matchmaker (and transformer) / allowing web based applications and other apps more to use the common setting - 0.2 | ||
* .INI settings handler 0.2 (needed for pilots) | * .INI settings handler 0.2 (needed for pilots) | ||
| + | |||
| + | ==Update June 2013== | ||
| + | |||
| + | ===Short Term=== | ||
| + | * Continue the model transformation work. | ||
| + | * Get the pilots branch merged into master. | ||
| + | ** Need to document clear JIRAs and wiki pages explaining each feature and the steps to test them. | ||
| + | * Automated integration testing (building on [[Cloud4all Integration Tests]] and [[Cloud4all Pilot Scenario Tests]]). | ||
| + | * Release GPII/Cloud4all v0.2 | ||
| + | |||
| + | ===New Features=== | ||
| + | * Android convergence. | ||
| + | * A re-envisioned Security Gateway (Oauth 2.0 & UMA). | ||
| + | * Web-based Flow Manager for web personalization. | ||
| + | * Error handling and logging improvements. | ||
| + | * Preference editors (see [[User Preferences UX]]). | ||
| + | * Settings snapshotter. | ||
| + | * Conditions in preferences set (see [[Proposal for Declarative Preference Conditions]]). | ||
| + | * Next generation Ontology Service. | ||
| + | * Separate ‘GPII framework’ from universal repository and offer it as a reusable framework for building apps (‘Kettle’). | ||
| + | * [[Unified Listing]]. | ||
| + | * [[Common Terms Registry]] (see [[Registry - database planning]] and [[Registry - choice of database]]). | ||
[[Category:GPII Architecture]] | [[Category:GPII Architecture]] | ||
Revision as of 09:49, 1 July 2013
Contents
What would you like to see the architecture working on
- Listening to device reporter - 0.2 / 0.3 (Android)
- Lifecycle manager and its relation to the service synthesizer tool.
- Connecting semantic framework with the solution registry.
- Mapping internal application users to GPII users. (Single sign on) - 0.3
- Document directory structure on the wiki - 0.2
- Document directory structure of the code
- Conditional preferences (example omnitor; change settings depending on which person you’re calling) - after actual device/environment reporter - 0.2/0.3
- Supporting binary data
- Proper device reporting - 0.2 / 0.3 (Android)
- Common terms registry / listing
- Snapshotting tool - 0.4 (start planning soon)
- Security - 0.3 (or at least have a plan!)
- Thin matchmaker (and transformer) / allowing web based applications and other apps more to use the common setting - 0.2
- .INI settings handler 0.2 (needed for pilots)
Update June 2013
Short Term
- Continue the model transformation work.
- Get the pilots branch merged into master.
- Need to document clear JIRAs and wiki pages explaining each feature and the steps to test them.
- Automated integration testing (building on Cloud4all Integration Tests and Cloud4all Pilot Scenario Tests).
- Release GPII/Cloud4all v0.2
New Features
- Android convergence.
- A re-envisioned Security Gateway (Oauth 2.0 & UMA).
- Web-based Flow Manager for web personalization.
- Error handling and logging improvements.
- Preference editors (see User Preferences UX).
- Settings snapshotter.
- Conditions in preferences set (see Proposal for Declarative Preference Conditions).
- Next generation Ontology Service.
- Separate ‘GPII framework’ from universal repository and offer it as a reusable framework for building apps (‘Kettle’).
- Unified Listing.
- Common Terms Registry (see Registry - database planning and Registry - choice of database).
