1. Project Overview & Quickstart (json-schema-org/json-schema-spec)
File: README.md
Welcome to JSON Schema
JSON Schema is a vocabulary that allows you to validate, annotate, and
manipulate JSON documents.
This repository contains the sources for the work in progress of the next
set of JSON Schema IETF Internet Draft (I-D) documents. For the latest released
I-Ds, please see the
Specification page on the website.
Call for contributions and feedback
Reviews, comments and suggestions are most welcome!
Please read our guidelines for contributing.
Status
For the current status of issues and pull requests, please see the following
labels
Labels are assigned based on
Sensible GitHub Labels.
Authoring and Building
Specification
To build all the spec files to HTML from the Markdown sources, run npm run build -- specs. You can also build each individually with npm run build -- specs/filename.md (Example: npm run build -- specs/jsonschema-core.md). You
can also use wildcards to build multiple specs at the same time: npm run build -- specs/jsonschema-*.md. The HTML files will be available in the web folder.
The spec is built using Remark, a markdown engine with
good support for plugins and lots of existing plugins we can use. Remark also
has a language server and
a VSCode extension we can use to
get linting and link checking while developing the spec.
Plugins
The following is a not-necessarily-complete list of configured plugins and the
features they make available to you.
- remark-lint -- Enforce markdown
style guide. - remark-validate-links --
Check for broken links. - remark-gfm -- Adds support for
GitHub Flavored Markdown specific markdown features such as autolink literals,
footnotes, strikethrough, tables, and tasklists. - remark-heading-id -- Adds
support for{#my-anchor}syntax to add anidto an element so it can be
referenced using URI fragment syntax. - remark-headings
-- A collection of enhancements for headings.- Adds hierarchical section numbers to headings.
- Use the
%appendix%prefix on headings that should be numbered as an
appendix.
- Use the
- Adds id anchors to headers that don't have one
- Example:
#section-2-13 - Example:
#appendix-a
- Example:
- Makes the heading a link utilizing its anchor
- Adds hierarchical section numbers to headings.
- remark-reference-links
-- Adds new syntax for referencing a section of the spec using the section
number as the link text.- Example:markdown
## Foo {#foo} ## Bar This is covered in {{foo}} // --> Renders to "This is covered in [Section 2.3](#foo)" - Link text will use "Section" or "Appendix" as needed
- Example:
- remark-table-of-contents
-- Adds a table of contents in a section with a header called "Table of
Contents". - remark-code-titles
-- Add titles to code blocks- Example:markdown
\`\`\`jsonschema "My Fun Title" { "type": "string" } \`\`\` - The languages
jsonschemaandjsonhave special styling - The title will be parsed as a JSON string, but you have to double escape
escaped characters. So, to getMy "quoted" title, you would need to write"My \\\\"quoted\\\\" title".
- Example:
- rehype-highlight --
Syntax highlighting. - rehype-highlight-code-lines
-- Adds line numbers to code blocks. Supports ranges. - remark-flexible-containers
-- Add a callout box using the following syntax. Supported container types arewarning,note, andexperimental.markdown::: {type} {title} {content} :::
Internet-Drafts
To build components that are being maintained as IETF Internet-Drafts, runnpm run build-ietf.
Descriptions of the xml2rfc, I-D documents, and RFC processes:
- https://xml2rfc.tools.ietf.org/authoring/draft-mrose-writing-rfcs.html
- https://www.ietf.org/tao.html
- https://www.ietf.org/ietf-ftp/1id-guidelines.html
- https://www.rfc-editor.org/rfc/rfc7322.txt
Test suites
Conformance tests for JSON Schema and its vocabularies may be found
in their own repository.
Tests for the meta-schema are included here. Run npm test to run the
meta-schema tests. To get a test coverage report, you can use npm run test:coverage. In addition to the CLI report, a detailed HTML report will be
generated in the coverage directory and can be viewed using something likenpx http-server coverage.
The website
The JSON Schema web site is at http://json-schema.org/
The source for the website is maintained in a separate repository.
Contributors
Code Contributors
This project exists thanks to all the people who contribute. [Contribute].
Financial Contributors
Become a financial contributor and help us sustain our community. [Contribute]
Sponsors
Here are our top sponsors. You could be next! [Become a sponsor]
Individuals
License
The contents of this repository are licensed under either the BSD
3-clause license or the Academic Free License v3.0.
File: adr/README.md
Architectural Decision Log
This log lists the architectural decisions for the JSON Schema specification.
- ADR-2022-04-08
- Acknowledge ambiguity in additionalProperties behaviour and fix after patch
release
You can find the ADR for using ADRs in our community repo ADR log.
For new ADRs, please use template.md as basis. More information
on MADR is available at https://adr.github.io/madr/. General information about
architectural decision records is available at https://adr.github.io/.
2. Official Technical Reference & Guides (json-schema-org/website)
<a href="https://github.com/json-schema-org/website/graphs/contributors" alt="JSON Schema GitHub website contributors">
</a>
<a href="https://github.com/json-schema-org/website/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22" alt="Good First JSON Schema issue">
</a>
<a href="https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md" alt="Contributor Covenant">
</a>
<a href="https://www.repostatus.org/#active" alt="Repo status">
</a>
<a href="https://json-schema.org/slack" alt="JSON Schema Slack">
</a>๐ Welcome to the JSON Schema website
This repository contains the source code of the JSON Schema website:
- Powered by Next.js,
- Uses the Tailwind CSS framework,
- Built and deployed with Netlify.
Setting up the Project
Please refer to INSTALLATION.md for instructions on how to set up the project for local development.
Project structure
This repository has the following structure:
โโโ .github # Definitions of GitHub workflows, pull request, and issue templates
โโโ components # Various generic components such as "Button", "Figure", etc.
โโโ data # JSON Schema implementations
โโโ styles # Various CSS files
โโโ lib # Various JS code for preparing static data to render on pages
โโโ pages # Website's pages source, including raw markdown files and React page templates
โ โโโ overview # JSON Schema initiative docs
โ โโโ blog # Blog posts
โ โโโ learn # JSON Schema docs
โ โโโ implementations # Various pages to describe tools
โโโ public # Data for site metadata and static assets such as images
โโโ next.config.js # Next.js configuration fileContribute
Here are some areas where you can contribute to the website:
- Blog posts
- Case studies
- Design
- Documentation improvements
- Website enhancements
- Add a new JSON Schema implementation
- JSON Schema Landscape
To identify good first issues to work on, join our Slack workspace and visit the #contribute channel. This channel is specifically designed for onboarding and supporting new contributors.
You should also check out our Contributing guidelines.
Contributors
Thanks to these wonderful people who contributed to this website:
Made with contributors-img.
Sponsors
Backers
Thank you to all our backers!
Connect with the JSON Schema Community
Inspired by
This document was inspired by AsyncAPI website README.md.
License
The contents of this repository are licensed under either the BSD 3-clause license or the Academic Free License v3.0. See LICENSE.