Wouter Termont

> Or is a Pod Browser application rather something that operates at the same privilege level as an Authorization Agent? This is not a desirable way to enable pod browser...

Thanks @elf-pavlik! > Every AA would need to provide minimal browsing functionality, at least showing human-readable labels for selecting data instances on the authorization screen. > It would be good...

Thanks @elf-pavlik! I think no one who was in the call disagrees on these entities/roles, and the most important question now is indeed how the AS gets the necessary info...

I took a quick look at #222, but would like to go into it more during the panel meeting. Specifically, I do not immediately see why the AA on one...

Thanks for the elaboration, @elf-pavlik. I do not immediately follow why the user would need to select _which_ LDP Container should be used, however. With the current state of the...

> We should always assume that the user has multiple storages, how would AA know in which storage container should be created? Indeed. You suggested an `interop:defaultRootContainer` triple for each...

_Discussed in [panel meeting of 2022-01-25](https://github.com/solid/data-interoperability-panel/blob/main/meetings/2022-01-25.md)_: - _Location of storage is maintained by registry link._ - _Nicer workflow could be achieved by having storage provider discover and notify via access...

Thank @elf-pavlik! Definitely something we should look into very soon! What I meant, though, was the interaction on AR-discovery: it is not specified explicitly that the request should contain a...

Context: awaiting confirmation of the idea to obsolete panels, a number of people (possible popping their heads up after summer slumber) were confused when no one turned up in some...

> Authorization guard enforcing access control policies will need to take both `webid` and `client_id` claims into account so what you said can not happen! Aren't we then unnecessarily duplicating...