solid / solid/data-interoperability-panel
Provide context that authorization agent should provision data registrations
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
In a conversation with @jeff-zucker I realized that the specification should be more explicit in pointing out when data registrations are provisioned (i.e. by the authorization agent during later stages of authorization flows).
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
No file or test is named. Start by locating the specification text covering authorization flows and data registrations; clarify that the authorization agent provisions registrations during later authorization stages. Done means the specification explicitly provides this context.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100