search

solid / web-access-control-spec

Web Access Control (WAC)
https://solid.github.io/web-access-control-spec/
MIT License
121 stars 25 forks source link

Document proposal for acl:agentClass acl:PayingAgent #100

Closed michielbdejong closed 3 years ago

michielbdejong commented 3 years ago

As per https://github.com/solid/acl-check/pull/38#pullrequestreview-745034811

michielbdejong commented 3 years ago

Yes, this proposal is ready in its status as a proposal, that's why I added it to that separate folder and not created a PR on the main spec text. I implemented it in NSS as an experiment and proof-of-concept, but I do not expect the other servers to implement it unless we see some traction for it in the wild.

Note that if support for W3C-VC is added to WAC then this proposal becomes obsolete, because the ACL could just state that a verifiable "receipt of payment" credential is required, and the client could then just present their payment receipt as a "ticket" that gives them access.

Rather than a "ticket" system, the acl:PayingAgent proposal works more like a guest list.

Re ODRL, yes, I think @joepio is working with ODRL in the context of Solid Webmonetization.

I tried to document the current situation in https://github.com/solid/webmonetization#requiring-payment-for-resources

The concept 'paying agent' is left intentionally vague; it is implied that the user could pay to get access, but how much they should pay, how long the access would last, and what bundle options would exist to pay once for access to multiple (related) resources, is left out of scope in this proposal, I don't think that level of detail would belong in WAC.