JSON Schema: interactive and non interactive validation
draft-fge-json-schema-validation-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-08-04 (latest revision 2013-01-31) | ||
| Replaced by | draft-wright-json-schema-validation | ||
| 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 | Replaced by draft-wright-json-schema-validation | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-fge-json-schema-validation-00.txt
Abstract
JSON Schema (application/schema+json) has several purposes, one of which is instance validation. The validation process may be interactive or non interactive. For instance, applications may use JSON Schema to build a user interface enabling interactive content generation in addition to user input checking, or validate data retrieved from various sources. This specification describes schema keywords dedicated to validation purposes.
Authors
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.)