...
In UMA trust model terminology, this scenario is considered to be in the category person-to-person. Alice is the resource owner (technical term) and Authorizing Party (contractual term), acting on her own behalf, and Bob is the Requesting Party, also acting on his own behalf. (In his turn, Bob would serve as the Authorizing Party for his own personal cloud, and Alice might very well be a Requesting Party seeking subscriptions to it.) The CloudOS-enabled authorization service of the CloudOS would be an "authorization managerserver" or AM in UMA technical terms, run by an Authorization Manager Operator. Every cloud-hosted source of Alice's information would, in UMA technical terms, be a "resource server", run by a Resource Server Operator. The software application Bob would use to access Alice's cloud info would be a "client".
In UMA's rendering of Phil Windley's personal cloud conception, her UMA-protected cloud would include anything for which:
...
The UMA group's Google TechTalk video from February 2012 demonstrates how the SMARTAM authorization service could be used to provide subscription request workflows. (Note that it uses old UMA terminology: authorization manager, host, and requester rather than authorization server, resource server, and client.)