https://docs.kantarainitiative.org/uma/ed/uma-core-2.0-15.html

For tomorrow's meeting, we will use join.me/findthomas for screenshare and voice. I just remembered to doublecheck with Thomas that this would be okay, so if I send a panicked message at the last minute, you'll know why. :-)

Lots and lots of work, fairly invasive I'm afraid, almost all in service of what I hope are the final set math changes. No doubt we'll find some tweaks still to make, but let's the big decisions have been made. This takes into account the last ad hoc, the last telecon, and the GDoc we were working in.

Please pay special attention to the following sections, related to set math:

The TOC (for overall cleaner flow)
1.3.2 Resource and Scope Interpretation
3.4 Resource Server Requests Permissions on Client's Behalf With Authorization Server
3.6.5 Authorization Assessment and Results Determination (note revised title)
3.6.6 Authorization Server Response to Client on Authorization Success (note the following "PCT" section was folded in)

Also enhanced/tidied up:

1.4 Protocol Flow Summary / 2.2 Configuration Document and Discovery Endpoint (former now discusses and points to latter, and latter has expanded title; we actually have one more endpoint than we usually talk about)
3.2 Resource Server Registers Resources for Protection (added a note about RReg timing since this comes up a lot)

For tomorrow, it will really really help if people review the new text ahead of time, and if possible can even send comments in email. I want to work from the GitHub issues and pick off as many of them as we can (I don't know of any outstanding issues that aren't in GitHub, so please submit any you know of). Specifically, I plan to close some easy issues; anyone keeping an eye on issues they care about will be responsible for reopening/yelling...

Eve Maler
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl