solid / solid/data-interoperability-panel
Access Needs for Public Resources
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
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.
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 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.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100