{
  "slug": "i-json",
  "term": "I-JSON",
  "aliases": [
    "Internet JSON",
    "RFC 7493"
  ],
  "definition": "I-JSON is a restricted JSON profile for interoperable exchange of structured data.",
  "note": "Input: UTF-8 is required; unpaired surrogates and Unicode noncharacters are prohibited. Object names must be unique after escape decoding. [ijson-profile]\n\nNumbers: 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. [ijson-profile]\n\nStructure: Any JSON value is permitted; objects or arrays are recommended for compatibility with older receivers. [ijson-profile]\n\nComparison: Ordinary JSON only recommends unique names. Decoded-name comparison is not Unicode normalization. [ijson-json] JCS preserves strings and adds deterministic serialization rules; I-JSON alone does not select canonical bytes. [ijson-jcs]\n\nUse: A successful parse is insufficient evidence of profile conformance. Check application requirements and signature validity separately before acting on signed data. [ijson-jcs]",
  "related": [
    "data-serialization",
    "json-canonicalization-scheme"
  ],
  "citations": [
    {
      "id": "ijson-profile",
      "title": "RFC 7493: The I-JSON Message Format, sections 2.1-2.3 and 4.1 (Standards Track)",
      "url": "https://www.rfc-editor.org/rfc/rfc7493.html",
      "accessed": "2026-11-21"
    },
    {
      "id": "ijson-json",
      "title": "RFC 8259: Object-name interoperability and decoded string comparison, sections 4 and 8.3",
      "url": "https://www.rfc-editor.org/rfc/rfc8259.html",
      "accessed": "2026-11-21"
    },
    {
      "id": "ijson-jcs",
      "title": "RFC 8785: Input adaptation, serialization and verification order, sections 3.1-3.2 and 5",
      "url": "https://www.rfc-editor.org/rfc/rfc8785.html",
      "accessed": "2026-11-21"
    },
    {
      "id": "ijson-reading",
      "title": "Hesela: Choose the rules before hashing JSON",
      "url": "https://hesela.com/analyses/checksums-identity-and-lost-writes/#json-canonicalization",
      "accessed": "2026-11-21"
    }
  ],
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-21",
  "provenance": [
    "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."
  ]
}
