solid / solid/data-interoperability-panel
Establish patterns for supporting to successive versions of shapes and shape trees
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
A key element to the success of the application interoperability specification will be applications' ability to adapt to and support successive versions of shapes and shapes trees.
To make that actually work, some best practices will need to be established around how shapes and shape trees should evolve from version to version, and how applications should handle those changes.
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 reviewing the application interoperability specification and its existing treatment of shapes and shape trees. Define documented best practices for evolving successive versions and for applications handling those changes; done means the guidance is established clearly enough to support interoperability.
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