RFC 8259

E208072

IETF RFC Internet standard technical specification

RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (5)

Label	Occurrences
RFC 8259 canonical	6
RFC 7159	2
RFC 8259 JSON specification	1
RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format	1
The JSON Data Interchange Syntax (RFC 8259 influence)	1

How this entity was disambiguated

This entity first appeared as the object of triple T1869659 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: RFC 8259
Context triple: [JSON, standardizedAs, RFC 8259]

A. RFC 8999
RFC 8999 is an Internet Engineering Task Force (IETF) standards document produced by the QUIC Working Group that specifies aspects of the QUIC transport protocol.
B. RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
C. RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
D. RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
E. RFC 8551
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: RFC 8259
Target entity description: RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.

A. RFC 8999
RFC 8999 is an Internet Engineering Task Force (IETF) standards document produced by the QUIC Working Group that specifies aspects of the QUIC transport protocol.
B. RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
C. RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
D. RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
E. RFC 8551
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
F. None of above. chosen

Statements (56)

Predicate	Object
instanceOf	IETF RFC ⓘ Internet standard ⓘ technical specification ⓘ
acronymExpansion	Request for Comments 8259 ⓘ
allowsCharacterEncoding	UTF-16 ⓘ UTF-32 ⓘ
area	Applications ⓘ
author	Tim Bray ⓘ
category	Standards Track ⓘ
defines	JSON ⓘ JSON semantics ⓘ JSON syntax ⓘ
definesDataFormat	JavaScript Object Notation ⓘ linked to: JSON
documentURI	https://www.rfc-editor.org/rfc/rfc8259 ⓘ
editor	Tim Bray ⓘ
hasSection	Arrays ⓘ Conformance ⓘ Data Model ⓘ Grammar ⓘ Introduction ⓘ Numbers ⓘ Objects ⓘ Security Considerations ⓘ Strings ⓘ Whitespace ⓘ
keyword	Internet protocol ⓘ JSON ⓘ data interchange ⓘ
obsoletes	RFC 7159 ⓘ linked to: RFC 4627
publicationDate	2017-12 ⓘ
publishedBy	IETF ⓘ linked to: Internet Engineering Task Force Internet Engineering Task Force ⓘ
relatedTo	ECMA-404 ⓘ JavaScript language ⓘ linked to: JavaScript
shortTitle	JSON Data Interchange Format ⓘ linked to: JSON
specifies	JSON array ⓘ JSON boolean ⓘ JSON null ⓘ JSON number ⓘ JSON object ⓘ JSON string ⓘ JSON text ⓘ arrays are ordered sequences of values ⓘ escaping rules for JSON strings ⓘ limitations on numeric values in JSON ⓘ name/value pairs in JSON objects ⓘ ordering of members in JSON objects is insignificant ⓘ strings are sequences of Unicode code points ⓘ
specifiesCharacterEncoding	UTF-8 ⓘ
status	Internet Standard ⓘ
stream	IETF ⓘ linked to: Internet Engineering Task Force
title	The JavaScript Object Notation (JSON) Data Interchange Format ⓘ linked to: JSON
updates	JSON specification ⓘ
usesNotation	ABNF ⓘ
workingGroup	JSON Working Group ⓘ
year	2017 ⓘ

How these facts were elicited

Referenced by (11)

Full triples — surface form annotated when it differs from this entity's canonical label.

JSON → standardizedAs → RFC 8259 ⓘ

ECMA-404 → relatedTo → RFC 8259 ⓘ

ECMA-404 → compatibleWith → RFC 8259 JSON specification ⓘ

linked to: RFC 8259

RFC 4627 → obsoletedBy → RFC 7159 ⓘ

linked to: RFC 8259

RFC 4627 → obsoletedBy → RFC 8259 ⓘ

Douglas Crockford → notableWork → The JSON Data Interchange Syntax (RFC 8259 influence) ⓘ

linked to: RFC 8259

JSON Working Group → producedStandard → RFC 8259 ⓘ

JSON Working Group → producedStandard → RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format ⓘ

linked to: RFC 8259

Request for Comments 8259 → shortName → RFC 8259 ⓘ

RFC 7158 → obsoletedBy → RFC 7159 ⓘ

linked to: RFC 8259

RFC 7158 → obsoletedBy → RFC 8259 ⓘ

All labels observed (5)

How this entity was disambiguated Show

Statements (56)

How these facts were elicited Show

Referenced by (11)

How this entity was disambiguated

How these facts were elicited