URI persistence, ownership, and representation management
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Should the Solid Protocol provide a set of mechanisms enabling URI owners to manage URI persistence?
Related:
- https://github.com/solid/specification/issues/61
- https://github.com/solid/specification/issues/72
- https://github.com/solid/specification/issues/136
- https://github.com/solid/specification/issues/151
- https://github.com/solid/specification/issues/206
- https://github.com/solid/specification/issues/279
- https://github.com/solid/specification/issues/280
- https://github.com/solid/specification/issues/285
- https://github.com/solid/specification/issues/317
- https://github.com/solid/specification/issues/474
- ...
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 issue text and the related Solid specification issues 61, 72, 136, 151, 206, 279, 280, 285, 317, 474, and any subsequent discussion. Identify whether URI persistence, ownership, and representation management have a defined scope or acceptance criteria; done would require an agreed protocol mechanism, not a localized code change.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100