…303 ]. 2012-11-15 2014-04-17 JavaScript Object Notation (JSON) +json RFC8259 ][ RFC6839 JSON is encoded using UTF-8, and is binary data. See RFC8259, Section 8.1 ] for additional encoding considerations. n/a The syntax and semantics of fragment identifiers specified for +json SHO…

…303 ]. 2012-11-15 2014-04-17 JavaScript Object Notation (JSON) +json RFC8259 ][ RFC6839 JSON is encoded using UTF-8, and is binary data. See RFC8259, Section 8.1 ] for additional encoding considerations. n/a The syntax and semantics of fragment identifiers specified for +json SHO…

…d Media Types In Section 9.6 , this specification updates the registration in [ RFC6839 ] for XML-based MIME types (the '+xml' types). When a new media type is introduced for an XML-based format, the name of the media type SHOULD end with '+xml' unless generic XML processing is i…

…ration to the appropriate registry. The initial registry content specification [RFC6839] provides examples of structured syntax suffix registrations. 6.1. Change Procedures Registrations may be updated in each registry by the same mechanism as required for an initial registration…

…ata Model Support processing of documents with a +json media type as defined in RFC6839 Added a brief description of the data model to the introduction. Fixed a number of document readability and flow issues related to all of the updates made over the last several moths. This doc…

…eters: None Optional parameters: None Encoding considerations: Binary, as per [ RFC6839 ], section 3.1; the charset parameter is not used and byte-order marks are not permitted, as per [ RFC7159 ], sections 11 and 8.1 Security considerations: See [ RFC7159 ] section 12 and the Se…

…e behaviors. 5. Fragment Identifiers In accordance with section 3.1 of RFC 6839 RFC6839 the syntax and semantics of fragment identifiers specified for any +json media type SHOULD be as specified for "application/json". (At publication of this document, there is no fragment identi…

…eters: None Optional parameters: None Encoding considerations: Binary, as per [ RFC6839 ], section 3.1; the charset parameter is not used and byte-order marks are not permitted, as per [ RFC7159 ], sections 11 and 8.1 Security considerations: See [ RFC7159 ] section 12 and the Se…

…lication/expect-ct-report+json media type (which uses the suffix established in RFC6839 ) for Expect-CT violation reports in the "Media Types" registry as follows. Type name: application Subtype name: expect-ct-report+json Required parameters: n/a Optional parameters: n/a Encodin…

…lication/expect-ct-report+json media type (which uses the suffix established in RFC6839 ) for Expect-CT violation reports in the "Media Types" registry as follows. Type name: application Subtype name: expect-ct-report+json Required parameters: n/a Optional parameters: n/a Encodin…

…e application/json media type or a media type with a +json suffix as defined in RFC6839 ]. In order to use an external context with an ordinary JSON document, an author MUST specify an IRI to a valid JSON-LD document in an HTTP Link Header [ RFC5988 ] using the link relation. The…

…e application/json media type or a media type with a +json suffix as defined in RFC6839 ]. In order to use an external context with an ordinary JSON document, when retrieving an ordinary JSON document via HTTP, processors MUST attempt to retrieve any JSON-LD document referenced b…

…ters: None Optional parameters: None Encoding considerations: Binary, as per [[!RFC6839]], section 3.1; the charset parameter is not used and byte-order marks are not permitted, as per [[!RFC7159]], sections 11 and 8.1 Security considerations: See [[RFC7159]] section 12 and the S…

…e application/json media type or a media type with a +json suffix as defined in RFC6839 ]. In order to use an external context with an ordinary JSON document, when retrieving an ordinary JSON document via HTTP, processors MUST attempt to retrieve any JSON-LD document referenced b…

…e application/json media type or a media type with a +json suffix as defined in RFC6839 ]. In order to use an external context with an ordinary JSON document, when retrieving an ordinary JSON document via HTTP, processors MUST attempt to retrieve any JSON-LD document referenced b…