… href="*"> <img href="*"> <video src="*"> and other similar links. In a JSON ([ RFC7159 ]) document, the receiver should look for properties whose values are an exact match for the URL. If the document is plain text, the receiver should look for the URL by searching for the strin…

… registries for these identifiers. All these specifications utilize JSON-based [RFC7159] data structures. This specification also describes the semantics and operations that are specific to these algorithms and key types. Registering the algorithms and identifiers here, rather th…

…7049 ]. CBOR extended the data model of the JavaScript Object Notation (JSON) [ RFC7159 ] by allowing for binary data, among other changes. CBOR is being adopted by several of the IETF working groups dealing with the IoT world as their encoding of data structures. CBOR was design…

…registries for these identifiers. All these specifications utilize JSON-based [ RFC7159 ] data structures. This specification also describes the semantics and operations that are specific to these algorithms and key types. Registering the algorithms and identifiers here, rather t…

…entifiers. All these specifications utilize JavaScript Object Notation (JSON) [ RFC7159 ] based data structures. This specification also describes the semantics and operations that are specific to these algorithms and key types. Registering the algorithms and identifiers here, ra…

…tionally, parts of the request. This section describes how to generate a JSON [ RFC7159 ] object from the HTTP request. Each value below is included as a member of the JSON object at the top level. at REQUIRED. The access token value. This string is assumed to have no particular …

… registries for these identifiers. All these specifications utilize JSON-based [RFC7159] data structures. This specification also describes the semantics and operations that are specific to these algorithms and key types. Registering the algorithms and identifiers here, rather th…

…herefore subject to the same encoding considerations specified in Section 8 of [RFC7159] Hoffman & Snell Standards Track [Page 5] RFC 7386 JSON Merge Patch October 2014 Security considerations: As defined in this specification Published specification: This specification. Applicat…

…7049 ]. CBOR extended the data model of the JavaScript Object Notation (JSON) [ RFC7159 ] by allowing for binary data, among other changes. CBOR is being adopted by several of the IETF working groups dealing with the IoT world as their encoding of data structures. CBOR was design…

…after performing any JSON string escape processing, per Section 8.3 of RFC 7159 RFC7159 ], and then UTF-8-encoding the resulting Unicode code points. This means, for instance, that these payloads represented as JSON strings are equivalent ("$.02", "\u0024.02"). Unassigned Unicode…

…tional parameters: N/A Encoding considerations: Same as for application/json ([ RFC7159 ] section 8.1) Privacy and security considerations: See 7. Privacy and security considerations Applications that use this MIME type: Web browsers Additional information: Magic number(s): N/A F…

…FC7049]. CBOR extended the data model of the JavaScript Object Notation (JSON) [RFC7159] by allowing for binary data, among other changes. CBOR is being adopted by several of the IETF working groups dealing with the IoT world as their encoding of data structures. CBOR was designe…

…, and "string" in this document are to be interpreted as described in RFC 7159 [RFC7159]. 1.2. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpr…

… Validation failures to the indicated URI. The UA does this by POSTing a JSON [ RFC7159 ] message to the URI; the JSON message takes this form: "date-time": date-time, "hostname": hostname, "port": port, "effective-expiration-date": expiration-date, "include-subdomains": include-…

… Validation failures to the indicated URI. The UA does this by POSTing a JSON [ RFC7159 ] message to the URI; the JSON message takes this form: "date-time": date-time, "hostname": hostname, "port": port, "effective-expiration-date": expiration-date, "include-subdomains": include-…