I wanted to point out explicitly that these revs implement solutions for not only issues we discussed in last Thursday's call, but also Monday's ad hoc, which had a small (if mighty :-) ) subset of folks on the call discussing matters.So please take a moment to review these revisions:
- The new Core Sec 3.10, Authorization Server Refreshes RPT (issue #284)
- The way Core Sec 1.3.1, HTTP Usage, now reads and the fact that the extensibility profiles no longer exist (issue #267)
- The mention in the example in Core Sec 3.6.2 of "...#IDToken" instead of "...#HybridIDToken", and the claim_profiles_supported config property has gone away in favor of just uma_profiles_supported (issue #263)
- The fact that RReg Sec 2.1 and Sec 2.1.1 now each have a name and description, each section enables optional RFC 7591-based language and script handling, and Sec 4 discusses sanitizing inputs meant to be displayed (issues #271 and #272)
- RReg Sec 2.2.5 now says "resource owner" instead of "user" (issue #273, ish)
- I added a bunch more sections to the UIG, partly to preserve interesting but no longer spec-related text there and partly to fulfill the purpose of having reviewers be able to go there to see a bit of our "design trail".
- I also finally (15 months later?!?) incorporated Andi's 1.0.1 revisions to the UIG Optional and Extension Properties section. Ouch. Apologies.
On Tue, Mar 7, 2017 at 10:58 PM, Eve Maler <eve@xmlgrrl.com> wrote:https://docs.kantarainitiative.org/uma/ed/uma-core-2.0-18. html I've been doing some big copyediting reviews and hope to have another wave of revisions up before Thursday's call, but most of the substantive issues have been cleared, and I wanted to get these out for review now.Agenda for Thursday out in a second.