Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document proposal for acl:agentClass acl:PayingAgent #100

Merged
merged 3 commits into from
Sep 4, 2021

Conversation

michielbdejong
Copy link
Contributor

Copy link
Member

@csarven csarven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think it would help to go through an issue/discussion or this is ready as proposal?

Below is not intended to knock off what's proposed (it could even be combined), just want to raise awareness as a comment:

I think we should look into how ODRL policies can be loosely coupled with the authorization system. Payment-for-authorization is one aspect, but there are many others. For example, see section on Duty property with a Permission https://www.w3.org/TR/odrl-model/#duty-perm .

Brought this up awhile back in solid/authorization-panel#55, solid/data-interoperability-panel#31 , solid/specification#116 (ctrl-f "odrl").

See also: w3c/odrl#12

proposals/paying-agent.md Outdated Show resolved Hide resolved
ah yes, that was a copy-paste typo. thanks!

Co-authored-by: Sarven Capadisli <info@csarven.ca>
@michielbdejong
Copy link
Contributor Author

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.

@csarven csarven merged commit c1e5fd2 into solid:main Sep 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants