...
- Reviewing use cases doc
Attending: Eve, Andrew, Tim, Adrian, Paul
NOTE: No Legal call next week – and possibly the week after!
AI: Eve: Look for substitute Legal call as necessary.
Tim reports that he's well on his way with deliverable #2.
Let's take a "breadth-first" approach to the use cases in deliverable #1 today. Tim asks: What's the general nature of the authorization services being developed today? Are there any? Are they primarily C2G or C2B? Yes, and they are split, with also some B2B. Eve ranks the top three-to-four use cases as healthcare (and healthcare-plus-IoT, with IoT generally being quite broad and horizontal), government/citizen interactions, and financial. Adrian notes that regulation is a powerful motivator for using UMA, and thus the consumer component seems to be critical to adoption.
Use case C: And here the FCC decision from October just got reversed again! Reasons to think this use case for UMA is valid: UMA would give a standardized interface for ISPs to offer third-party partners for efficient integration (more money on both sides), and wherever regs allow either "legitimate business interests" or "consent" as valid bases to collect and share data it's better to ask for consent because of user trust risks and creeping regulation scope (IT cost and user trust risks of having to ask for consent later). This could be Alice-to-Alice sharing (she shares with some app that she will use) or Alice-to-other sharing (e.g. for marketing purposes, maybe even "targeted" for some goodie offered to her, but maybe not).
Worked on use case D.
Worked on use case E. We decided to make it just the parent/guardian use case.
AI: Eve: Try to add a payment use case as a variation on D.
2017-03-17
- Reviewing use cases doc
...