Page Comparison

...

• Day: Thursday, 10 Dec 2009
• 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)

Attendees

Quorum: 10 of 19.

Voting participants:

...

1. Adams, Trent

• Akram, Hasan

1. Bryan, Paul
2. Carroll, Tom
3. Catalano, Domenico
4. Chadwick, David
5. Davis, Peter
6. Fletcher, George
7. Hanson, Michael
8. Lizar, Mark
9. Machulak, Maciej
10. Maler, Eve
11. Scholz, Christian
12. Smith, Bill

Regrets:

• Tom Holodnik
• Iain Henderson

Agenda

• Administrative
  • Roll call
  • Approve minutes of UMA F2F 2009-12-03
  • Action item review
    • Eve: "Hey, Sailor" scenario
    • Gerry: hData scenario
    • Hasan: "Protected status query" issue into Scenarios doc
    • Eve: (with Maciej, Hasan, Dom) Slide deck
    • Mark W.: Shindig contacts
    • Eve: Reach out to OAuth consumer devs
    • Paul: Strawman claims-handling spec
    • Eve: Terms-negotiation scenarios
• Review and approve/defer/reject scenarios and use cases
  • E-commerce
  • Personal loan
• Claims spec review
• AOB

Minutes

TBS

...

Administrative

Roll call

Quorum was achieved.

Approve minutes of UMA F2F 2009-12-03

Minutes of 2009-12-

...

03 APPROVED.

Action item review

• Eve: "Hey, Sailor" scenario: still pending, though partly covered by the terms negotiation scenario writeups.
• Gerry: hData scenario: Eve will take an AI to ping Gerry to get this done.
• Hasan: "Protected status query" issue into Scenarios doc: to be done next week; we're pleased with the diagrams so far; Paul notes that some of the arrows do vs. don't represent protocol interactions, so maybe we need to have conceptual vs. "protocol-accurate" versions. Swimlane diagrams are best for strict protocol accuracy.
• Eve: (with Maciej, Hasan, Dom) Slide deck: still in process: consider doing a webinar early in the new year.
• Eve: Reach out to OAuth consumer devs/Mark W.: Shindig contacts: Mark uncovered two appropriate Google and Shindig contacts, including one person intimately familiar with the Dropbox OAuth implementation. Eve will follow up with Mark's contacts, and talk with the JanRain RPX guys.
• Paul: Strawman claims-handling spec: still pending.
• Eve: Terms-negotiation scenarios: still pending; David suggests that the "requester identification" and general "statement" scenarios might bleed together. There is little-to-no difference in implementation between a uniquely identified vs. a non-uniquely identified requester. This is precisely the issue that is hanging Paul up.

New AIs collected during the meeting:

• Eve to reach out to Gerry
• Slide deck team to work out a plan to host a status update webinar
• Eve: contact Mark's names
• Eve: soften "prove in court" language in e-commerce scenario
• Eve: remove "payment privacy" use case from e-commerce scenario
• Paul and Mike: comment on Dom's latest diagrams on the list
• Eve: capture potential requirement about independently verifiable access-agreement claims

Review and approve/defer/reject scenarios and use cases

The criteria are:

• Does this scenario belong in the problem space for UMA V1? (if not, defer or reject)
• If so, does it clearly articulate its distinctive aspects? (if not, revise)
• If so, does it appropriately steer clear of technical detail? (if not, revise)
• If so, then approve

E-commerce

Mike: "If Staplers behaves badly (gives out her data against her rules or allows a data breach to occur), she wants to be able to prove so