Handling of resources which did not go through the HTTP interface
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Should the Solid spec say anything about handling external resources mapped to pod's storage and URI space? Similarly, resources may come or cease to exist in a storage without going through the HTTP interface. Examples: index.html is created manually, bar/ is mapped (or symlinked) under /foo/.
To what extent is this in scope and should have defined behaviours? If at all:
- Should containers list resources sharing the same path segment?
- Do these resources adhere to the same lifecycle as resources which went through the HTTP interface?
- What are the interaction models on these resources? Is there any? A default? Determine/Derived.. how?
- ..
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.
Research direction
Start by reviewing the Solid specification's treatment of containers, storage, URI space, resource lifecycle, and interaction models. Use the examples of manually created index.html and mapped or symlinked bar/ to frame the scope, then resolve whether externally created resources need defined behavior and how each listed question should be answered.
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
- 20/100