NOTE: I've found one editing bug, a fix for which we'll have to incorporate into our motion (sorry about that):
- My edit of issue #354 should have introduced new resource registration endpoint error code invalid_request, but I over-copied from my source for the description text, and it says unsupported_method_type instead.
On Mon, Sep 4, 2017 at 8:14 PM, Eve Maler <eve@xmlgrrl.com> wrote:For your consideration and reviewing assistance as well, here's the final Disposition of Comments document:We'll need to turn this in to the Leadership Council when we ask them to certify the specs to progress to All-Member Ballot. Note that I've added a column describing/paraphrasing/boiling down the issues. On Mon, Sep 4, 2017 at 8:03 PM, Eve Maler <eve@xmlgrrl.com> wrote:I'm still having trouble uploading (I've asked Oliver to help with that already), so the drafts are attached to this email.As already requested, all of you, PLEASE take an hour ASAP to read through these specs to ensure they look okay. Key updates:
- Resolutions to newish issue #354, sub-issue 1 and 2, including a new but pretty minor OPTIONAL FedAuthz error code in FebAuthz Sec 3.2 -- thanks to James and Cigdem for their important contributions here!
- Grant Sec 3.3.4 on authorization assessment -- I caught a super-confusing point in the wording here, and Cigdem unravelled more of the same in the worked example and all over -- please read through, you won't be sorry. :) The example turned out to be critical to put in, and I think our #337f commenter will be very glad of our efforts.
Voting participants will need to weigh in starting Wednesday with your e-ballot vote (voting participants: Domenico, Sal, Andi, Maciej, Eve, Mike, Cigdem).By the way, right now we DO have a meeting scheduled on Thursday, but I report for jury duty tomorrow morning, so we'll see what happens...