…thod" values MUST be further encapsulated with a "multipart/mixed" MIME entity [RFC2046]. This will allow each of the iCalendar objects to be encapsulated within their own "text/calendar" MIME entity. Note 2: A MIME body part with a "Content-Type" value of "text/calendar" that la…

… some restrictions on MIME entities and they are described in [ RFC2045 ] and [ RFC2046 ]. In particular, the UTF-16 family, UCS-4, and UTF-32 are not allowed (except over HTTP[RFC2616], which uses a MIME-like mechanism). Thus, if an XML document or external parsed entity is enco…

…same metadata may be expressed in various forms. The representation media type [RFC2046] , in particular, plays such an important role in the Web architecture that its value can be described in many different locations. Given multiple sources of metadata and the possibility that …

…hod" values MUST be further encapsulated with a "multipart/mixed" MIME entity [ RFC2046 ]. This will allow each of the iCalendar objects to be encapsulated within their own "text/calendar" MIME entity. Note 2: A MIME body part with a "Content-Type" value of "text/calendar" that l…

…cessing Representation Data 3.1.1.1. Media Type HTTP uses Internet media types [RFC2046] in the Content-Type Section 3.1.1.5 ) and Accept Section 5.3.2 ) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data format …

…TOM] application/json JSON [JSON] application/octet-stream Generic binary data [RFC2046] application/microdata+json Microdata as JSON application/rss+xml RSS application/wasm WebAssembly [WASM] application/x-www-form-urlencoded Form submission application/xhtml+xml HTML applicati…

…ssing Representation Data 3.1.1.1 . Media Type HTTP uses Internet media types [ RFC2046 ] in the Content-Type Section 3.1.1.5 ) and Accept ( Section 5.3.2 ) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data form…

… applies to the EPUB Publication as a whole. media-type [optional] A media type RFC2046 that specifies the type and format of the resource referenced by this link Content Model Empty The metadata element may contain zero or more link elements. The href attribute of the link eleme…

…owledgments See Section 10 of [RFC7230] 8. References 8.1. Normative References RFC2046 Freed, N. and N. Borenstein, “ Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types ”, RFC 2046, November 1996. RFC2119 Bradner, S., “ Key words for use in RFCs to Indicate Requi…

…cessing Representation Data 3.1.1.1. Media Type HTTP uses Internet media types [RFC2046] in the Content-Type (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data format …

…ssing Representation Data 3.1.1.1 . Media Type HTTP uses Internet media types [ RFC2046 ] in the Content-Type Section 3.1.1.5 ) and Accept ( Section 5.3.2 ) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data form…

…ssing Representation Data 3.1.1.1 . Media Type HTTP uses Internet media types [ RFC2046 ] in the Content-Type Section 3.1.1.5 ) and Accept ( Section 5.3.2 ) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data form…

…ssing Representation Data 3.1.1.1 . Media Type HTTP uses Internet media types [ RFC2046 ] in the Content-Type Section 3.1.1.5 ) and Accept ( Section 5.3.2 ) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data form…

… some restrictions on MIME entities and they are described in [ RFC2045 ] and [ RFC2046 ]. In particular, the UTF-16 family, UCS-4, and UTF-32 are not allowed (except over HTTP[RFC2616], which uses a MIME-like mechanism). Thus, if an XML document or external parsed entity is enco…

…ssing Representation Data 3.1.1.1 . Media Type HTTP uses Internet media types [ RFC2046 ] in the Content-Type Section 3.1.1.5 ) and Accept ( Section 5.3.2 ) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data form…