idnits 2.17.1 draft-hoschka-smil-media-type-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 10. -- Found old boilerplate from RFC 3978, Section 5.5 on line 283. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 5 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 4 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 22 has weird spacing: '... [3] of the S...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 2006) is 6643 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' ** Obsolete normative reference: RFC 3023 (ref. '4') (Obsoleted by RFC 7303) Summary: 9 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group P. Hoschka 2 INTERNET DRAFT W3C 3 draft-hoschka-smil-media-type-13.txt February 2006 5 The application/smil and application/smil+xml Media Types 7 By submitting this Internet-Draft, each author represents that any 8 applicable patent or other IPR claims of which he or she is aware 9 have been or will be disclosed, and any of which he or she becomes 10 aware will be disclosed, in accordance with Section 6 of BCP 79. 12 Abstract 14 This document specifies the Media Type for versions 1.0, 2.0 and 2.1 15 of the Synchronized Multimedia Integration Language (SMIL 1.0, SMIL 16 2.0, SMIL 2.1). SMIL allows integration of a set of independent 17 multimedia objects into a synchronized multimedia presentation. 19 1. Introduction 21 The World Wide Web Consortium has issued specifications which define 22 versions 1 [1], 2 [2] and 2.1 [3] of the Synchronized Multimedia 23 Integration Language (SMIL). This memo provides information about the 24 application/smil and application/smil+xml Media Types. 26 The definition is based on RFC3023 defining the use of the 27 "application/xml" media type [4]. Before using the "application/smil" 28 or "application/smil+xml" media type, implementors must thus be 29 familiar with [4]. 31 2. Synchronized Multimedia Integration Language 33 SMIL allows integrating a set of independent multimedia objects into 34 a synchronized multimedia presentation. Using SMIL, an author can 36 1.describe the temporal behavior of the presentation 37 2.describe the layout of the presentation on a screen 38 3.associate hyperlinks with media objects 39 4.define conditional content inclusion/exclusion based on 40 system/network properties 42 3. Registration Information 44 To: ietf-types@iana.org 45 Subject: Registration of MIME media type application/smil 46 MIME media type name: application 48 MIME subtype name: smil 50 Required parameters: none 52 Optional parameters: 54 charset 56 Same as charset parameter considerations of application/xml in RFC 57 3023 59 profile 61 See Section 5 of this document. 63 Encoding considerations: 65 Same as encoding considerations of application/xml in RFC 3023 67 Security considerations: see Section "6. Security Considerations" below 69 Interoperability considerations: 71 SMIL documents contain links to other media objects. The SMIL player 72 must be able to decode the media types of these media in order to 73 display the whole document. To increase interoperability, SMIL has 74 provisions for including alternate versions of a media object in a 75 document. 77 Published specification: see [1], [2] and [3] 79 Applications which use this media type: 81 SMIL players and editors 83 Additional information: 85 Semantics of fragment identifiers in URIs: The SMIL media type allows 86 a fragment identifier to be appended to a URI pointing to a SMIL 87 resource (e.g. http://www.example.com/test.smil#foo). The semantics 88 of fragment identifiers for SMIL resources are defined in the SMIL 89 specification. 91 Magic number(s): 93 There is no single initial byte sequence that is always present for 94 SMIL files. However, Section 4 below gives some guidelines for 95 recognizing SMIL files. 97 File extension(s): .smil, .smi, .sml 99 NOTE: On the Windows operating system and the Macintosh 100 platform, the ".smi" extension is used by other formats. 101 To avoid conflicts, it is thus recommended to use the extension 102 ".smil" for storing SMIL files on these platforms. 104 Macintosh File Type Code(s): "TEXT", ".SMI", "SMIL" 105 Object Identifier(s) or OID(s): none 107 Person & email address to contact for further information: 109 The author of this memo. 111 Intended usage: OBSOLETE 113 Author/Change controller: 115 The SMIL specification is a work product of the World Wide Web 116 Consortium's SYMM Working Group. 118 The W3C has change control over the specification. 120 To: ietf-types@iana.org 121 Subject: Registration of MIME media type application/smil+xml 123 MIME media type name: application 125 MIME subtype name: smil+xml 127 Required parameters: see registration of application/smil 129 Optional parameters: see registration of application/smil 131 Encoding considerations: see registration of application/smil 133 Security considerations: see Section "6. Security Considerations" below 135 Interoperability considerations: see registration of application/smil 137 Published specification: see registration of application/smil 139 Applications which use this media type: see registration of 140 application/smil 141 Additional information: see registration of application/smil 143 Magic number(s): see registration of application/smil 145 File extension(s): see registration of application/smil 147 Macintosh File Type Code(s): see registration of application/smil 149 Object Identifier(s) or OID(s): see registration of application/smil 151 Person & email address to contact for further information: see 152 registration of application/smil 154 Intended usage: COMMON 156 Author/Change controller: see registration of application/smil 158 4. Recognizing SMIL files 160 All SMIL files will have the string "