NoelDeMartin
commented
1 year ago For anyone getting here who is using ESS, I can confirm that I've been able to edit the permissions of my recipes using podbrowser.inrupt.com.
If you want to take a look at the documents structure, you can see my Ramen recipe here: https://umai.noeldemartin.com/viewer?url=https://storage.inrupt.com/f812dfc7-74ae-40fb-8c31-54be91065a52/cookbook/juns-ramen%23it
At the moment, Umai only supports managing permissions using WAC.
The main reason for that is that I've written the communication with the POD myself, and I still haven't gotten around to read the ACP spec (and it looks a lot more complicated than WAC).
As far as I know, ACP is only used by ESS, and the spec is still a draft. So, for the time being, I don't think I'm going to implement it. But I'll leave this issue open in order to track its progress (if any).
This is not necessarily a problem, though. The point of Solid is that you can combine applications to get different capabilities. And I would think that most POD providers have an interface capable of editing permissions for the protocol they are using. If not, I think you should ask your provider for this feature, because in my opinion that's a core necessity for Solid users (regardless of which apps they are using).
If you're going to update permissions outside of Umai, everything you need to know is that publicly-readable recipes will be considered "Unlisted"; and they will be considered "Public" if they point to a
schema:ItemListwith apurl:isReferencedByproperty.