|
Top-level
 @jg10 I see now, thank you! A flash drive on steroids. But how are permissions handled? Does every application reserve some prefix or what? The library is too immature, to be honest. If I ever get to serious Soliding, I'll make my own. The OIDC spec is long, but looks quite implementable, I think. 5 comments
@VincentTunru @jg10 Sad. WAC has received a new version this year, while ACP only in 2022. I suppose the specwriters are more focused on WAC? ACP has been mostly pushed by Inrupt, the company Tim Berners-Lee founded around Solid, and which is mostly focusing on enterprise customers. (Disclosure: I used to work there a couple of years ago.) It's the method their Solid instance https://pod.inrupt.com uses. WAC was the initial access control spec for Solid, and is still used by the main community-used server, https://solidcommunity.net. So they're both the main focus for an important cohort of people, unfortunately... In general it's important to note that the Solid specifications are still in flux - but I don't think permissions is a major issue at this time - WAC and ACP are sufficiently similar that two possible solutions include having client libraries interoperate across both or updating WAC to include missing features |
Gregory's Server
@bouncepaw @jg10 Permissions are a bit of a mess, unfortunately, as there are (so far) two competing standards for that, so different servers might implement different standards. Solid doesn't mandate a particular one, so it's even possible that additional ones arise in the future.
The two specs are:
- Web Access Control: https://solidproject.org/TR/wac
- Access Control Policies: https://solidproject.org/TR/acp