Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

UMA telecon 2013-10-24

Date and Time

Agenda

  • Note: Next week, the US meeting time is canonical, so UK participants and anyone else whose clock has changed should take careful note of the temporarily changed meeting time
  • Demo video status (original rough cut, new beta version)
  • IDESG, MIT conference, and IIW reports
  • Resource descriptions for user attribute retrieval (email thread)
  • SAML IdP+UMA attribute release discussion (email thread)
  • AS=C use case discussion (most recent previous notes) – any conclusions yet?
  • Field interop feature test issues if time
  • AOB

Minutes

Reports from other events

Scott David gave an awesome talk on Entropy at the MIT conference, and the audience even hounded him to keep going past the time slot. (smile) The presentations are available online. Hal Abelson's talk on Information Accountability was also especially interesting and relevant to UMA.

Going in to the IDESG meeting, the challenge was to ratify its new operational model. We believe the plenary approved the proposed governance rules. This means the IDESG can operate as a standalone self-funded entity, apart from the federal government. A lot of questions are still outstanding, regarding (e.g.) current work groups and work streams.

Demo video status

Please see the updated links above to get to the real beta version of the video. It's coming along nicely!

Resource description design

We reviewed Roland's proposal, and realized that it's more about resource sets that have resource subsets (all referring to the same scopes), rather than being about scopes with sub-scopes. Maciej observes that there's a lot of repetition in the example given, which could be factored out and made into a pointer somehow.

Eve was thinking that there are opportunities for "virtual" or "complex" layers for both resource sets (as Roland has demonstrated) and scopes, e.g., "read" and "write" could combine into "all". If we need resource sub/supersets, here's one design question we need to answer: Is there a need to have multiple overlapping sets of resources (attributes/claims in Roland's case)? Or is a hierarchy completely sufficient?

Thomas ask about the ability to do queries on resources before fetching them. Our resource set "type" property (see the RSR spec) does give the ability to query about the types of available resources, without mandating that the AS support this use case.

A resource like "photo album" probably has available scopes that are different from a resource like "photo". So what would it mean to gather together a bunch of protected photo resources under a single protected photo album resource, and what scopes should/would apply to both?

Attendees

  • Eve
  • Domenico
  • Thomas
  • Maciej

Next Meetings

  • All-hands meeting on Thursday, October 31, at 9am PT (time chart) - note that US goes off summer time on Nov 3
  • No labels