Access Needs for Public Resources
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reading issue #240, the Access Request section of the Data Interoperability specification, and the existing “Social Agent Shares Access” flow. Done means resolving how an application requests public access for a permissive tree, whether separate websites need separate access requests, and whether a public agent concept should be defined.
Written by the indexing model from the issue text.
Description
Suggested Use Case
Suppose I build an application allowing a user to manage a website and serve it from their Solid Pod. Supposing we have some way of storing such a static website in a permissive tree (see #240), and are able to describe an access need for this data.
Open questions
- How would an application then define an access need for making this instance of the permissive tree public?
- Also, it might be the case that I want to serve multiple websites, from different instances of such a permissive tree. Would I send an Access Request for this purpose?
Suggested course of action
- Define the concept of a public agent, like
foaf:Agentis to be used in WAC for this purpose. - Perhaps the latter question should actually be clarified under the "Social Agent Shares Access"-flow that is already mentioned in the specification.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- 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/data-interoperability-panel
-
Align with LWS Access Requests and GrantsMay be free again @elf-pavlik claimed this 76 days ago, and no pull request is open. Open
solid/data-interoperability-panel#338 · 11 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
solid/data-interoperability-panel#337 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
solid/data-interoperability-panel#336 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/data-interoperability-panel#335 · 3 comments ·
-
Remove `interop:AccessAuthorization`, `interop:AccessGrant` and `interop:AccessNeedGroup`May be free again @elf-pavlik claimed this 511 days ago, and no pull request is open. Open
solid/data-interoperability-panel#334 · 5 comments · 1 assignee ·
All issues in solid/data-interoperability-panel
Similar issues
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 72/100
vercel-labs/skills#2370 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 3 days
-
bug developer portal
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
discord/discord-api-docs#8645 ·
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 1/5 1-3 hours Newbie friendliness 88/100