[New Work Item]: Access Requests and Grants
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- authorization, documentation
Research direction
Start by reading the Linked Web Storage Working Group editors draft in pull request 106 and compare it with the SAI access-request section. Done means producing the Solid specification for access requests and grants and coordinating its reference from the Solid26 implementors guide.
Written by the indexing model from the issue text.
Description
This is a new work item proposal to create a specification for access requests and grants.
The Linked Web Storage Working Group should soon have an editors draft for access requests and grants. This new work item is to 'backport' that ED to Solid in time for Solid26; ideally with this document reference from the Solid26 implementors guide.
Explain what you are trying to do, using no jargon or acronyms.
Provide a way for clients to request access to resources.
How is it done today, and what are the limits of the current practice?
SAI has a notion of access requests. However, there is no widespread implementation, and the approach does not match the approach being taken by the Linked Web Storage Working Group.
What is new in your approach, and why do you think it will be successful?
This approach will make it easier for Solid to conform with / depend upon Linked Web Storage.
How are you involving participants from multiple skill sets and global locations in this work item? (Skill sets: technical, design, product, marketing, anthropological, and UX. Global locations: Africa, the Americas, APAC, Europe, Middle East, Antarctica.)
At present we are not -- this is a clear gap.
What actions are you taking to make this work item accessible to a non-technical audience?
Surrounding this work item and the Solid26 implementors guide within the CG, the proposers of this work item are also developing:
- best practices and documentation for technical audiences,
- UX demos, briefing materials and publicity for non-technical audiences.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 110
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Contributor guide
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/specification
-
new-work-item
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#806 · 11 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#804 · 9 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
solid/specification#799 · 1 reaction ·
-
topic: resource access
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#797 · 4 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#788 · 4 comments · 1 reaction ·
All issues in solid/specification
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docToolchain/docToolchain#1705 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3566 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·