Page History

...

1) Accessibility needs and prefs doc for several users (will be provided) conforming to ISO/IEC 24751 and AccessForAll standards to be published at UMA-protected RESTful-style URLs on an UMA-compliant Resource Server (RS).
 - Unicon to build and configure the RS leveraging SMART's Python for UMA (PUMA) library per instructions on SMART blog
 - http://smartjisc.wordpress.com/2012/04/13/releasing-puma/^{Image Removed}
 - In GPII architecture terms (http://wiki.gpii.net/index.php/A_Detailed_Tour_of_the_Cloud4all_Architecture^{Image Removed}), this RS "host" is meant to be a cloud instance of the Preferences Server.

...

3) Simple UMA client/relying party (RP) app that allows access to user's own needs & pref doc (person-to-self sharing model).
 - Unicon to write RP client web app leveraging the PUMA library per instructions on SMART blog. Client to interact with RS and AS as specified above.
 - In GPII architecture (http://wiki.gpii.net/index.php/A_Detailed_Tour_of_the_Cloud4all_Architecture^{Image Removed}), this RP client is meant to be a cloud instance of the Flow Manager
 - Coding will need to include implementation of an abstract PUMA interface for a simple set of storage/persistence operations
 - RP Client to be delivered with an integrated set of test modules and logging capabilities.

...