JSON Data Definition Format (JDDF)
draft-ucarion-jddf-05
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2020-01-26 (latest revision 2020-01-23) | ||
| Replaced by | draft-ucarion-json-type-definition | ||
| Stream | ISE | ||
| Intended RFC status | Experimental | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | ISE state | Replaced | |
| Consensus Boilerplate | Unknown | ||
| Document shepherd | Adrian Farrel | ||
| IESG | IESG state | Replaced by draft-ucarion-json-type-definition | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | Adrian Farrel <rfc-ise@rfc-editor.org> | ||
https://www.ietf.org/archive/id/draft-ucarion-jddf-05.txt
Abstract
This document proposes a format, called JSON Data Definition Format (JDDF), for describing the shape of JavaScript Object Notation (JSON) messages. Its main goals are to enable code generation from schemas as well as portable validation with standardized error indicators. To this end, JDDF is strategically limited to be no more expressive than the type systems of mainstream programming languages. This strategic limitation, as well as the decision to make JDDF schemas be JSON documents, also makes tooling atop of JDDF easier to build. This document does not have IETF consensus and is presented here to facilitate experimentation with the concept of JDDF.
Authors
Ulysse Carion (ulysse@segment.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)