...
UMA telecon 2010-02-18
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Date and Time
- Day: Thursday, 18 Feb 2010
- Time: 9:00-10:30am PST | 12:00-1:30pm EST | 17:00-18:30 UTC (time chart)
- Dial-In:
- Skype: +9900827042954214
- US: +1-201-793-9022 | Room Code: 295-4214 (other local country numbers available on request)
Agenda
- Roll call
- Approve minutes of UMA telecon 2010-02-04 and UMA telecon 2010-02-11
- Action item review
- Review F2F plans
- Spec review: editor's choice
- Lexicon discussion
- Scenario review
- Custodian (splitting "authorizing user" and "host service user")
- Employer/employee (other mandatory access control in addition to UMA discretionary access control)
- And the "multiple protections on a resource" thread
- Health data (trusted dynamic resource discovery)
- AOB
...
Regrets:
- Bill Smith
Minutes
Roll call
Quorum was reached.
Approve minutes of UMA telecon 2010-02-04 and UMA telecon 2010-02-11
Minutes of both meetings APPROVED.
Action item review
- 2009-10-15-2 Eve Closed Write a "Hey, Sailor" scenario to illuminate the needs around Requesters that ask for resource access without the User expecting them. Completed! We'll try to decide the disposition today.
- 2009-12-03-04 Eve Open Add terms-negotiation scenarios to Scenarios document. Delayed while we sort through requester concepts. Still pending.
- 2010-01-28-2 Joe Open Edit protected inbox scenario in response to telecon and email discussion. He will make progress this week.
- 2010-02-04-1 Iain Closed Share Mydex screen shots that illustrate how a relationship manager UX can be handled. Eve will send to all who attended last week and this week.
- 2010-02-11-1 Paul Open Develop new core spec draft. Still pending; RSN. We're actively interested in having additional spec editors join the ranks. Tom H. and Maciej are interested.
- 2010-02-11-2 Dom Closed Develop wireframes that explore data-sharing analytics possibilities. See section below for discussion.
- 2010-02-11-3 Eve Closed Edit terminology section in core spec.
- 2010-02-11-4 Maciej Closed Recommend terminology around custodianship on the mailing list. Maciej liked Eve's proposals well enough for now, so this is closed.
New AI summary
Eve | Open | Revise the UMA March F2F schedule. |
| |
Eve | Open | Edit the lexicon and graphics to account for the 2010-02-18 discussion. |
| |
Paul and others | Open | Send email to the list explicating views on custodianship, mapping them to the written scenario. | Paul has already sent his note; others should follow. |
...
Let's meet just the Wednesday 9am-noon, instead of also meeting Tuesday afternoon. We're likelier to get quorum this way. We'll still cancel the Thursday call that week.
Lexicon discussion
Joe notes that "user agent" isn't in our lexicon; Eve will add a reference to the source (HTTP spec?) of that term. He also notes that the terms PDP and PEP, being from a particular domain, don't have a place in any "official" diagram explaining the high-level protocol view.
...
Joe's preference for "host service user" is to say "host user" instead, but we had some worry that this implies that the user is a host. We played with several other options in addition: "user of the host", "hosting user" (wrong), "primary resource user", and "primary resource controller". We didn't settle on an answer, but we started to deep-dive into discussing the custodian scenario.
Custodian (splitting "authorizing user" and "host service user")
...