Consider removing the `acl:origin` feature
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- authorization, security
Research direction
Start by reading the linked discussion in issue 81 and pull request 129 to understand the rationale for removing acl:origin. The work is not ready to start until the upgrade path and intended scope are defined; done would require an agreed specification change and migration plan.
Written by the indexing model from the issue text.
Description
I think acl:origin was useful when WAC was combined with WebID+TLS, but now that the Solid project combines WAC with Solid+OIDC, I think it has lost its meaning and it would be better to remove it. Not sure what the upgrade path would be, and I'm not proposing we work on this now, I just wanted to document that this would be a thing to consider, and leave this issue open for when people in the future develop WAC further.
- Dominant language
- HTML
- Stars
- 131
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solid/web-access-control-spec
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
solid/web-access-control-spec#140 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
solid/web-access-control-spec#139 · 6 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
solid/web-access-control-spec#137 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/web-access-control-spec#136 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/web-access-control-spec#135 ·
All issues in solid/web-access-control-spec
Similar issues
-
Discovered ports from service discovery are never propagated to modules in Module.load()Possibly taken @vishalmore90 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OWASP/Nettacker#1828 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
sjkim1127/Reversecore_MCP#363 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
OpenZeppelin/openzeppelin-relayer#967 ·
Maintainers usually reply within 1 day
-
bot-found bug priority: P3
Difficulty 1/5 Under an hour Newbie friendliness 74/100
madenvel/KalinkaPlayer#497 ·
-
follow-redirects - CVE-2026-116689Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 70/100
axios/axios#11409 · 1 reaction ·
Maintainers usually reply within 1 day