# 2020-06-17 Authorization Panel ## Agenda * [Clarify purpose of this panel #70](https://github.com/solid/authorization-and-access-control-panel/issues/70) * [Align panel name and properties with panel purpose #71](https://github.com/solid/authorization-and-access-control-panel/issues/71) * [Prioritize initiatives for the panel #72](https://github.com/solid/authorization-and-access-control-panel/issues/72) * [Handle User-Focused Client Constraining Access Control via the ACL #68](https://github.com/solid/authorization-and-access-control-panel/issues/68) * [Next week agenda](https://hackmd.io/j1W-01rXSRm5CVZw7E8BMg) ## Present - Henry S - Justin B - Jackson M - elf Pavlik - Josh C ## Minutes ### [Clarify purpose of this panel #70](https://github.com/solid/authorization-and-access-control-panel/issues/70) - Jackson: I recall that we considered WAC as set in stone. - Justin: Aaron submited a lot of issues pointing out amibiguities. We also have proposals to exted it like taggin from Michel. - ...: I see original purpose to narrow. New one needs to cover WAC and access requests. - Pavlik: I think taking look at initiatives can help us clarify how broad purpose do we need. ### [Prioritize initiatives for the panel #72](https://github.com/solid/authorization-and-access-control-panel/issues/72) - Justin: It's based on minutes from previous week. It also incorporates some perspectives from editorial meetings. TimBL agrees that we need normative WAC draft. - Pavlik: Should include an initiatize for requesting access (see ruben's proposal and the ecosystem proposal by interop panel). *Noted in the github issue*. - Jackson: mentioning [Create a Generalizable baseline for interop #74](https://github.com/solid/authorization-and-access-control-panel/issues/74) ## Votes Initiatives: Use cases and Requirements: JB+1, EP+1, JC+1, JM+1, HS+1 WAC normative Draft: JB+1, JM+1, EP+1, JC+1, HS+1 Resolving client constraints: JC+1, JM+1, JB+1, HS+0, EP+1 Vote on purpose in #70 - EP+1, JM+1, HS+1, JB+1 Vote on panel name - Proposed: Authorization Panel - JM+1, HS+1, EP+1, JB+1 ## Actions - EP: Use cases and requirements for ACL rule privacy (keep confidential case) - JB: Document initiatives that received votes - JB: Action based on results of 70, 71, 72