...
| Anchor | ||||
|---|---|---|---|---|
|
The requirements with numbers starting at zero all come from the UMA Work Group charter, and were thus approved when the group was launched.
R# | Title | Requirement | Explanation/commentary |
|---|---|---|---|
R0a | Access relationship service | Support the notion of a distinct online service for managing data-sharing and service-access relationships ("access relationships" for short) between an individual and his or her online services that request such access. |
|
R0b | User-driven policies and terms | Allow an individual to select policies and enforceable contract terms that govern access, as well as data storage, further usage, and further sharing on the part of requesting services. |
|
R0c | User management of access relationship | Allow an individual to conduct short-term and long-term management of access relationships, including modifying the conditions of access or terminating the relationship entirely. |
|
R0d | Auditing | Allow an individual to audit and monitor various aspects of access relationships. |
|
R0e | Requester-Host direct access | Allow requesting services to interact directly with responding services in a fashion guided by policy while an individual is offline, reserving real-time user approval for extraordinary circumstances. |
|
R0f | Multiple Hosts | Allow requesting services to interact with multiple responding services associated with the same individual. |
|
R1 | Host/AM separation | It must be possible to provide Host and AM functions in separate Web domains. | Approved on 2009-10-01. |
R2 | Resource orientation | User data access and service access must be enabled through accessing Web resources that have URLs. | Approved on 2009-10-01. |
...