JSON Schema: core definitions and terminology
draft-zyp-json-schema-04
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Francis Galiegue, Kris Zyp , Gary Court | ||
| Last updated | 2013-08-04 (Latest revision 2013-01-31) | ||
| Replaced by | draft-wright-json-schema | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-wright-json-schema | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Kris Zyp
Gary Court
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)