Status of JSON Schema for references spec
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 366
- Forks
- 96
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
@tomnicholas and I noted @martindurant's mention in https://github.com/fsspec/kerchunk/pull/17#issuecomment-789205972 of the possibility of eventually representing the references spec as JSON Schema. We do not see further mention of JSON Schema in the docs or in any issues/prs and are curious what the current status of this is.
Edit: For context, we imagine a machine-readable spec may be useful in many contexts including validation and possibly further development of JS-based frontend clients for kerchunk.
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 references spec and the linked comment in pull request #17, then search the repository's documentation, issues, and pull requests for JSON Schema discussions. Done means documenting the current status and clarifying whether a machine-readable schema is planned for validation or frontend clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100