acl:originClass referenced throughout the code, but it's not formally defined in the WebACL spec
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 46
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
I'm working on the acl module and realized that acl:originClass (which is used throughout the module) is not defined in the Web Access Control spec, and not in the vocabulary. For the work I'm doing now (adding tests), I'll assume it's a predicate that is used, but I wanted to raise this issue to question whether we should support it at all, given it's lack of formal support.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start in the acl module and review the existing uses of acl:originClass alongside the tests being added. Compare those uses with the Web Access Control spec and its vocabulary, then determine whether support should be retained and formally defined or removed; done means the decision is reflected in the relevant tests and project behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100