Read-write access to a Collection

[elf-pavlik]

https://solid.github.io/authorization-panel/wac-ucr/#collection-readwrite

Alice worked with Milo in the past, where they produced a deliverable (document1) that she has included in her portfolio collection.

Alice realized that she doesn’t have the most up-to-date version document1, and needs Milo to replace it. She gives Milo read access and write access to the portfolio collection itself, which allows him to see the listing of its contents, as well as add and remove items from the collection.

He cannot read the contents of any of the resources included in the collection, but this is fine, since he knows the name of the resource he’s replacing.

Milo updates the contents of document1 to the most recent version.

---

I struggle to understand why Alice wouldn't just give Milo read-write access to the document1 itself.

[bblfish]

yes. so the idea is to be able to read the contents of the collection, and have write only access to document1, but not read access. If we allow some metadata on the collection, then the use case can be a team voting. Perhaps here we have a bidding game. Different groups of people can bid by each publishing to their own resource. But team members who have access to one resource cannot see what a previous team member bid: they can only overwrite. I can imagine a game where this would make sense, the aim being to create a tension between team members.

[matthieubosquet]

It looks like the UCR has significantly changed: https://solid.github.io/authorization-panel/authorization-ucr/#collection-readwrite

Can we close?