JSON Schema: core definitions and terminology
draft-zyp-json-schema-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-08-04 (latest revision 2013-01-31) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-zyp-json-schema-04.txt
Abstract
JSON Schema defines the media type "application/schema+json", a JSON based format for defining the structure of JSON data. JSON Schema provides a contract for what JSON data is required for a given application and how to interact with it. JSON Schema is intended to define validation, documentation, hyperlink navigation, and interaction control of JSON data.
Authors
Francis Galiegue
(fgaliegue@gmail.com)
Kris Zyp
(kris@sitepen.com)
Gary Court
(gary.court@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)