JSON Canonical Form
draft-staykov-hu-json-canonical-form-00

Document Type Expired Internet-Draft (individual)
Last updated 2013-05-11 (latest revision 2012-11-07)
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-staykov-hu-json-canonical-form-00.txt

Abstract

A single JSON document can have multiple logically equivalent physical representations. While convenient for human interaction, this flexibility is inconvenient for cases where a machine is used to assess the logical equivalence of documents. In cases where logical equivalence is useful, an encoder should produce a canonical form of a JSON document. For example, since digital signatures demand the same physical representation for logically equivalent documents, a canonical physical representation would allow the signature to apply to the logical document. This internet draft has the goal to define a canonical form of JSON documents. Two logically equivalent documents should have same canonical form.

Authors

Georgi Staykov (gstaykov@vmware.com)
Jeff Hu (jhu@vmware.com)

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