RFC 7464: JavaScript Object Notation (JSON) Text Sequences
In plain English — editorial summary, not part of the RFC
This document describes the JavaScript Object Notation (JSON) text sequence format and associated media type "application/json-seq". A JSON text sequence consists of any number of JSON texts, all encoded in UTF-8, each prefixed by an ASCII Record Separator (0x1E), and each ending with an ASCII Line Feed character (0x0A).
Document record
- Document ID
- RFC7464
- Published
- February 2015
- Authors
- N. Williams
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7484Finding the Authoritative Registration Data (RDAP) ServiceObsoleted
March 2015
- RFC 7493The I-JSON Message FormatCurrent
March 2015
- RFC 7095jCard: The JSON Format for vCardCurrent
January 2014
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 7515JSON Web Signature (JWS)Current
May 2015
- RFC 7516JSON Web Encryption (JWE)Current
May 2015
- RFC 7517JSON Web Key (JWK)Current
May 2015
- RFC 7519JSON Web Token (JWT)Updated
May 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?