JSON Constrained Notation (JSCN)
draft-miller-json-constrained-notation-00

Document Type Expired Internet-Draft (individual)
Last updated 2017-11-19 (latest revision 2017-05-18)
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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-miller-json-constrained-notation-00.txt

Abstract

This specification addresses the challenges of using JavaScript Object Notation (JSON) with constrained devices by providing a standard set of mapping rules to Concise Binary Object Representation (CBOR) that preserve all semantic information, such that the original JSON string can be identically re-created. JSON Constrained Notation can also be used by devices as a native data format, which can then be represented as JSON when necessary for diagnostics, compatibility, and ease of integration with higher-level systems.

Authors

Jeremie Miller (jeremie@jabber.org)
Peter Saint-Andre (peter@filament.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)