I-JSON
I-JSON is a restricted JSON profile for interoperable exchange of structured data.
Input: UTF-8 is required; unpaired surrogates and Unicode noncharacters are prohibited. Object names must be unique after escape decoding. [1]
Numbers: Numbers SHOULD NOT exceed binary64 range or precision; this is not a blanket MUST rejection rule. Values needing greater magnitude or precision are recommended as strings with agreed application semantics. [1]
Structure: Any JSON value is permitted; objects or arrays are recommended for compatibility with older receivers. [1]
Comparison: Ordinary JSON only recommends unique names. Decoded-name comparison is not Unicode normalization. [2] JCS preserves strings and adds deterministic serialization rules; I-JSON alone does not select canonical bytes. [3]
Use: A successful parse is insufficient evidence of profile conformance. Check application requirements and signature validity separately before acting on signed data. [3]
Relations
Citations
- RFC 7493: The I-JSON Message Format, sections 2.1-2.3 and 4.1 (Standards Track)
- RFC 8259: Object-name interoperability and decoded string comparison, sections 4 and 8.3
- RFC 8785: Input adaptation, serialization and verification order, sections 3.1-3.2 and 5
Further reading
Sources & caveats
- Primary-source synthesis of the I-JSON profile and its distinction from JSON syntax, application validity and JCS canonicalization.
- No new parser experiment or complete I-JSON validator is presented.