{
  "slug": "json-text-sequence",
  "term": "JSON text sequence",
  "aliases": [
    "JSON-seq",
    "JSON text sequences",
    "RFC 7464"
  ],
  "definition": "A JSON text sequence frames UTF-8 JSON values with a record-separator byte before each value and a line-feed byte after it.",
  "note": "Framing: RFC 7464 registers application/json-seq. RS (0x1E) permits multiline values; consecutive separators are not empty records. [json-sequence-rfc]\n\nRecovery: Parsers can resume at another RS after malformed input. Top-level numbers, booleans and null require trailing JSON whitespace or must be dropped as potentially truncated. Encoder and recovery grammars differ. [json-sequence-rfc]\n\nIntegrity: No end marker or cryptographic integrity protection is provided. Recovering later values does not prove completeness. [json-sequence-rfc]\n\nStreaming: An incremental parser can emit partial results before a later error invalidates the element; emitted values alone are not validation evidence. [json-sequence-rfc]",
  "related": [
    "data-serialization",
    "newline-delimited-json"
  ],
  "citations": [
    {
      "id": "json-sequence-rfc",
      "title": "RFC 7464: JSON Text Sequences, sections 2-4",
      "url": "https://www.rfc-editor.org/rfc/rfc7464.html",
      "accessed": "2026-11-21"
    }
  ],
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-21",
  "provenance": [
    "Specification synthesis, not a parser conformance study or a crash-recovery experiment."
  ]
}
