Draft 03 https://docs.kantarainitiative.org/uma/ed/uma-core-2.0-03.html. We're starting to make enough invasive changes that reading it through more comprehensively is a good idea, but here are the difference sets https://github.com/KantaraInitiative/wg-uma/commits/mpd-edits to pay close attention to: - First wave of edits https://github.com/KantaraInitiative/wg-uma/commit/c7982502dc87557509dc5b217... after last Thursday - Ignore the trivial stuff and hunt for lines 288, 392, 418, 1196 (edited more just below), 1307 (a bit) - In future, I'll try and isolate that extra-space stuff into a separate commit - Second wave of edits https://github.com/KantaraInitiative/wg-uma/commit/9316db4f5202d163e11aa1f07... after last Thursday - Implemented https://github.com/KantaraInitiative/wg-uma/commit/2521674d9f186f6b5676d29c8... issue #251 - Quick cleanup of permission ticket language Domenico has done some nice flowchart-y graphics around the notion of "authorization process", "authorization interface", and the new token landscape we can look at together tomorrow. Let's see if we can get quorum, cement decisions around this direction, and settle on set math decisions (what flexibility does the RS have? what are the parameters within which the client works? how does this all work when it's possible to register multiple resource sets when getting a permission ticket?) tomorrow. *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl