...
- Authorizing user Alice, who chooses to set and share her current location through various applications
- Authorization Manager that orchestrates An application that serves as an Authorization Manager (AM) on Alice's behalf, orchestrating which location applications can write to and read from other applications
- Applications that are Hosts of location information (some of which are also Requesters)
- Applications A web-based location application called HotLocale (H) that is a Host of a location resource on Alice's behalf
- Web-based location applications called RovingAround (R1) and RoadWarrior (R2) that are Requesters of location information (some of which are also Hosts)on Alice's behalf
Short Description
Today's location services such as FireEagle, BrightKite, and Dopplr let Alice set her location within any one of several applications, and then use OAuth-enabled connections to propagate that information through other such services. Since Alice can end up "chaining" services this way quite easily, with a thicket of pairwise connections, it's valuable for her to know and control where this information is flowing to. In this scenario, a user of FireEagle, Dopplr, and BrightKite wants HotLocale and RovingRound wants to arrange to connect them all up to be able to read and write her location to all of up so that her location can be propagated among them, and she wants to get a global view through her authorization manager CopMonkey AM about who's allowed to do what, so she can change and stop permissions in a coordinated way.
...
Below is a screenshot showing that FireEagle and Dopplr have the capability today to have two-way location information flow. Our user wants to be able to see this "combinatorily", for all location services and indeed for all such services on the web that she chooses to use for hosting any data or content.
Overview of Use Case Flow
This scenario assumes that Alice has an account at each of AM, H, R1, and R2. These accounts might be driven off of federated login, for example, Alice might log in to HotLocale through Google and RoadWarrior through Facebook; this is immaterial to the scenario.
Use Case: Alice Sets Up Access Authorization Between Two Location Services
...