…Media Types" registry [ IANA.MediaTypes ] in the manner described in RFC 6838 [ RFC6838 ], which can be used to indicate that the content is a JWT. o Type name: application o Subtype name: jwt o Required parameters: n/a o Optional parameters: n/a o Encoding considerations: 8bit; …

…s for Identifying Languages, http://www.ietf.org/rfc/rfc5646.txt , IETF, 2009. [RFC6838] N. Freed, J. Klensin, T. Hansen Media Type Specifications and Registration Procedures, http://www.ietf.org/rfc/rfc6838.txt , IETF, 2013. [RNG] ISO/IEC 19757-2 Document Schema Definition Langu…

…scheme is not coupled with a specific protocol nor with a specific media type [ RFC6838 ]. See Section 3 for a discussion of operations that can be performed on the object identified by a file URI. 1.1 . Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL"…

…his information is modeled after that specified for the "Media Types" registry [RFC6838]; if in doubt, the provisions of this registry should be applied analogously. Key Identifier: The key (conforming to suffix-key in Section 4.1) Registration Status: "Provisional" or "Permanent…

…scheme is not coupled with a specific protocol nor with a specific media type [ RFC6838 ]. See Section 3 for a discussion of operations that can be performed on the object identified by a file URI. 1.1 . Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL"…

…e "Media Types" registry [IANA.MediaTypes] in the manner described in RFC 6838 [RFC6838], which can be used to indicate that the content is a JWT. o Type name: application o Subtype name: jwt o Required parameters: n/a o Optional parameters: n/a o Encoding considerations: 8bit; J…

… Media Types registry [ IANA.MediaTypes ] in the manner described in RFC 6838 [ RFC6838 ], which can be used to indicate, respectively, that the content is a JWK or a JWK Set. o Type Name: application o Subtype Name: jwk+json o Required Parameters: n/a o Optional Parameters: n/a …

…scheme is not coupled with a specific protocol nor with a specific media type [ RFC6838 ]. See Section 3 for a discussion of operations that can be performed on the object identified by a file URI. 1.1 . Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL"…

…webp' Media Type This section contains the media type registration details per [RFC6838]. 6.1.1. Registration Details Type name: image Subtype name: webp Required parameters: N/A Optional parameters: N/A Encoding considerations: Binary. The Base64 encoding [RFC4648] should be use…

…p' Media Type This section contains the media type registration details as per [RFC6838]. 2.1. Registration Details Media type name: image Media subtype name: webp Required parameters: N/A Zern Expires 26 March 2022 [Page 2] Internet-Draft WebP Image Format Media Type Registratio…

…This information is modeled after that specified for the "Media Types" registry RFC6838 ; if in doubt, the provisions of this registry should be applied analogously. Key Identifier: The key (conforming to suffix-key in Section 4.1 Registration Status: "Provisional" or "Permanent"…

… "Media Types" registry [ IANA.MediaTypes ] in the manner described in RFC 6838 RFC6838 ], which can be used to indicate that the content is a JWT. o Type name: application o Subtype name: jwt o Required parameters: n/a o Optional parameters: n/a o Encoding considerations: 8bit; …

…istering party. 2.5 . URI Fragment Identifiers Media type definitions (as per [ RFC6838 ]) SHOULD specify the fragment identifier syntax(es) to be used with them; other specifications MUST NOT define structure within the fragment identifier, unless they are explicitly defining on…

… "Media Types" registry [ IANA.MediaTypes ] in the manner described in RFC 6838 RFC6838 ], which can be used to indicate that the content is a JWT. o Type name: application o Subtype name: jwt o Required parameters: n/a o Optional parameters: n/a o Encoding considerations: 8bit; …

…. IANA Considerations This specification defines two new Internet media types [ RFC6838 ]. 6.1 . application/problem+json Type name: application Subtype name: problem+json Required parameters: None Optional parameters: None; unrecognized parameters should be ignored Encoding cons…