…he following rules are included from [ RFC3986 ]: URI and URI-Reference; from [ RFC4288 ]: type-name and subtype-name; from W3C.REC-html401-19991224 ]: MediaDesc; from [ RFC5646 ]: Language-Tag; and from [ RFC5987 ], ext-value and parmname. Nottingham Standards Track [Page 3] RFC…

…pe-name ; Where "type-name" and "subtype-name" are ; defined in Section 4.2 of [RFC4288] Description: This parameter can be specified on properties that are used to reference an object. The parameter specifies the media type [ RFC4288 ] of the referenced object. For example, on t…

…he following rules are included from [ RFC3986 ]: URI and URI-Reference; from [ RFC4288 ]: type-name and subtype-name; from W3C.REC-html401-19991224 ]: MediaDesc; from [ RFC5646 ]: Language-Tag; and from [ RFC5987 ], ext-value and parmname. Nottingham Standards Track [Page 3] RFC…

…source Identifiers (IRIs) , http://www.ietf.org/rfc/rfc3987.txt , IETF, 2005. [ RFC4288 ] N. Freed, J. Klensin, Media Type Specifications and Registration Procedures , http://www.ietf.org/rfc/rfc4288.txt , IETF, 2005. [ RFC4514 ] K. Zeilenga, Lightweight Directory Access Protocol…

…035 ]. [ MIME ] refers to [ RFC2045 ], [ RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], and [ RFC4289 ]. [ SMIMEv2 ] refers to [ RFC2311 ], [ RFC2312 ], [ RFC2313 ], [ RFC2314 ], and [ RFC2315 ]. [ SMIMEv3 ] refers to [ RFC2630 ], [ RFC2631 ], [ RFC2632 ], [ RFC2633 ], [ RFC26…

… XML specification. 8.2 . Media Type This section defines the MIME media type [ RFC4288 ] for use with vCard-in-XML data. To: ietf-types@iana.org Subject: Registration of media type application/vcard+xml Type name: application Subtype name: vcard+xml Required parameters: none Opt…

… XML specification. 8.2 . Media Type This section defines the MIME media type [ RFC4288 ] for use with vCard-in-XML data. To: ietf-types@iana.org Subject: Registration of media type application/vcard+xml Type name: application Subtype name: vcard+xml Required parameters: none Opt…

…e" and "value" are from [ RFC2045 ] ; "type-name" and "subtype-name" are from [ RFC4288 ] 5.8 . CALSCALE The CALSCALE parameter is identical to the CALSCALE property in iCalendar (see [RFC5545], Section 3.7.1 ). It is used to define the calendar system in which a date or date-tim…

…ute" and "value" are from [ RFC2045 ; "type-name" and "subtype-name" are from [ RFC4288 5.8 . CALSCALE The CALSCALE parameter is identical to the CALSCALE property in iCalendar (see [RFC5545], Section 3.7.1 ). It is used to define the calendar system in which a date or date-time …

…l as specified in Section 3.1 . The registration uses the template present in [ RFC4288 ]. 3.1 . Media Type for Downloadable Sounds Type name: application Subtype name: oebps-package+xml Required parameters: none Optional parameters: none Encoding considerations: OPF files are UT…

…his was done to encourage people toward application/*, matching the guidance in RFC4288 , the predecessor to RFC6838 . Since then, however, the industry widely adopted text/* anyway. The definitions in this document reflect the current state of implementation across the JavaScrip…

…ute" and "value" are from [ RFC2045 ; "type-name" and "subtype-name" are from [ RFC4288 5.8 . CALSCALE The CALSCALE parameter is identical to the CALSCALE property in iCalendar (see [RFC5545], Section 3.7.1 ). It is used to define the calendar system in which a date or date-time …

…l as specified in Section 3.1 . The registration uses the template present in [ RFC4288 ]. 3.1 . Media Type for Downloadable Sounds Type name: application Subtype name: oebps-package+xml Required parameters: none Optional parameters: none Encoding considerations: OPF files are UT…

… uses two new media types that conform to the registry mechanism described in [ RFC4288 ], a new message header that conforms to the registry mechanism described in [ RFC3864 ], and two new link relations that conform to the registry mechanism described in [ RFC4287 ]. 16.1 . Con…

… uses two new media types that conform to the registry mechanism described in [ RFC4288 ], a new message header that conforms to the registry mechanism described in [ RFC3864 ], and two new link relations that conform to the registry mechanism described in [ RFC4287 ]. 16.1 . Con…