Specify mechanism for data portability
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Specify how one migrates their data, including the "meta" information around it (i.e. access control, audit history, shape constraints) from one Solid pod to another, or from one Solid pod to a different medium altogether. See this effort underway in data interoperability / portability panel.
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 with the linked data-portability effort in the Solid data interoperability/portability panel and review how it relates to this specification issue. The work is done when the specification defines a migration mechanism covering pod data and its metadata, including access control, audit history, and shape constraints, for transfers between pods and to other media.
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