Network Working Group P. Hoschka
Request for Comments: 4536 W3C
Category: Informational May 2006
Network Working Group P. Hoschka
Request for Comments: 4536 W3C
Category: Informational May 2006
The application/smil and application/smil+xml Media Types
The application/smil and application/smil+xml Media Types
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This document specifies the media type for versions 1.0, 2.0, and 2.1 of the Synchronized Multimedia Integration Language (SMIL 1.0, SMIL 2.0, SMIL 2.1). SMIL allows integration of a set of independent multimedia objects into a synchronized multimedia presentation.
本文档指定了同步多媒体集成语言（SMIL 1.0、SMIL 2.0、SMIL 2.1）1.0、2.0和2.1版的媒体类型。SMIL允许将一组独立的多媒体对象集成到同步的多媒体表示中。
The World Wide Web Consortium (W3C) has issued specifications that define versions 1.0 [1], 2.0 [2] and 2.1 [3] of the Synchronized Multimedia Integration Language (SMIL). This memo provides information about the application/smil and application/smil+xml media types.
万维网联盟（W3C）发布了定义同步多媒体集成语言（SMIL）1.0[1]、2.0[2]和2.1[3]版本的规范。此备忘录提供了有关application/smil和application/smil+xml媒体类型的信息。
The definition is based on RFC 3023, which defines the use of the "application/xml" media type [4]. Before using the "application/smil" or "application/smil+xml" media type, implementors must thus be familiar with [4].
该定义基于RFC 3023，它定义了“应用程序/xml”媒体类型的使用[4]。因此，在使用“application/smil”或“application/smil+xml”媒体类型之前，实现者必须熟悉[4]。
SMIL allows integrating a set of independent multimedia objects into a synchronized multimedia presentation. Using SMIL, an author can
SMIL允许将一组独立的多媒体对象集成到同步的多媒体表示中。使用SMIL，作者可以
1. describe the temporal behavior of the presentation, 2. describe the layout of the presentation on a screen, 3. associate hyperlinks with media objects, and 4. define conditional content inclusion/exclusion based on system/network properties.
1. 描述演示文稿的时间行为，2。在屏幕上描述演示文稿的布局，3。将超链接与媒体对象关联，以及4。根据系统/网络属性定义条件内容包含/排除。
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: smil
MIME子类型名称：smil
Required parameters: none
所需参数：无
Optional parameters:
可选参数：
charset
字符集
Same as charset parameter considerations of application/xml in RFC 3023.
与RFC 3023中application/xml的字符集参数注意事项相同。
profile
轮廓
See Section 5 of this document.
见本文件第5节。
Encoding considerations:
编码注意事项：
Same as encoding considerations of application/xml in RFC 3023
与RFC 3023中应用程序/xml的编码注意事项相同
Security considerations: See Section 6, "Security Considerations", of this document.
安全注意事项：见本文件第6节“安全注意事项”。
Interoperability considerations:
互操作性注意事项：
SMIL documents contain links to other media objects. The SMIL player must be able to decode the media types of these media in order to display the whole document. To increase interoperability, SMIL has provisions for including alternate versions of a media object in a document.
SMIL文档包含指向其他媒体对象的链接。SMIL播放器必须能够解码这些媒体的媒体类型，才能显示整个文档。为了提高互操作性，SMIL规定在文档中包含媒体对象的替代版本。
Published specification: See [1], [2], and [3]
已发布规范：参见[1]、[2]和[3]
Applications which use this media type:
使用此媒体类型的应用程序：
SMIL players and editors
SMIL播放器和编辑器
Additional information:
其他信息：
Semantics of fragment identifiers in URIs: The SMIL media type allows a fragment identifier to be appended to a URI pointing to a SMIL resource (e.g., http://www.example.com/test.smil#foo). The semantics of fragment identifiers for SMIL resources are defined in the SMIL specification.
URI中片段标识符的语义：SMIL媒体类型允许将片段标识符附加到指向SMIL资源的URI（例如。，http://www.example.com/test.smil#foo). SMIL资源的片段标识符的语义在SMIL规范中定义。
Magic number(s):
幻数：
There is no single initial byte sequence that is always present for SMIL files. However, Section 4 of this document gives some guidelines for recognizing SMIL files.
SMIL文件没有始终存在的单个初始字节序列。然而，本文档的第4节给出了一些识别SMIL文件的指南。
File extension(s): .smil, .smi, .sml
文件扩展名：.smil、.smi、.sml
NOTE: On the Windows operating system and the Macintosh platform, the ".smi" extension is used by other formats. To avoid conflicts, it is thus recommended to use the extension ".smil" for storing SMIL files on these platforms.
注意：在Windows操作系统和Macintosh平台上，其他格式使用“.smi”扩展名。为了避免冲突，建议使用扩展名“.smil”在这些平台上存储smil文件。
Macintosh File Type Code(s): "TEXT", ".SMI", "SMIL"
Macintosh文件类型代码：“TEXT”、“.SMI”、“SMIL”
Object Identifier(s) or OID(s): none
Object Identifier(s) or OID(s): none
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
The author of this memo.
这份备忘录的作者。
Intended usage: OBSOLETE
预期用途：过时
Author/Change controller:
作者/变更控制员：
The SMIL specification is a work product of the World Wide Web Consortium's SYMM Working Group.
SMIL规范是万维网联盟的SYMM工作组的工作成果。
The W3C has change control over the specification.
W3C对规范具有变更控制权。
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: smil+xml
MIME子类型名称：smil+xml
Required parameters: See registration of application/smil.
所需参数：请参阅应用程序注册/smil。
Optional parameters: See registration of application/smil.
可选参数：请参阅应用程序注册/smil。
Encoding considerations: See registration of application/smil.
编码注意事项：请参阅注册应用程序/smil。
Security considerations: See Section 6, "Security Considerations", of this document
安全注意事项：见本文件第6节“安全注意事项”
Interoperability considerations: See registration of application/smil.
互操作性注意事项：请参阅应用程序注册/smil。
Published specification: See registration of application/smil.
已发布规范：请参阅应用程序注册/smil。
Applications which use this media type: See registration of application/smil.
使用此媒体类型的应用程序：请参阅应用程序注册/smil。
Additional information: See registration of application/smil.
其他信息：请参阅应用程序注册/smil。
Magic number(s): See registration of application/smil.
幻数：参见申请注册/smil。
File extension(s): See registration of application/smil.
文件扩展名：请参阅应用程序注册/smil。
Macintosh File Type Code(s): See registration of application/smil.
Macintosh文件类型代码：请参阅应用程序注册/smil。
Object Identifier(s) or OID(s): See registration of application/smil.
对象标识符或OID：请参阅应用程序注册/smil。
Person & email address to contact for further information: See registration of application/smil.
联系人和电子邮件地址以了解更多信息：请参阅申请注册/smil。
Intended usage: COMMON
预期用途：普通
Author/Change controller: See registration of application/smil.
作者/更改控制器：请参阅应用程序注册/smil。
All SMIL files will have the string "<smil" near the beginning of the file. Some will also begin with an XML declaration that begins with "<?xml", though that alone does not indicate a SMIL document.
所有SMIL文件的开头附近都会有字符串“<SMIL”。有些还将以一个以“<？XML”开头的XML声明开始，尽管这本身并不表示SMIL文档。
All SMIL 2.0 files must include a declaration of the SMIL 2.0 namespace. This should appear shortly after the string "<smil", and should read 'xmlns="http://www.w3.org/2001/SMIL20/Language"'.
所有SMIL 2.0文件都必须包含SMIL 2.0命名空间的声明。这应该出现在字符串“<smil”之后不久，应该是“xmlns=”http://www.w3.org/2001/SMIL20/Language"'.
All SMIL 2.1 files must include a declaration of a SMIL 2.1 namespace, appearing shortly after the string "<smil". The namespace string depends on the language profile. Please refer to the SMIL 2.1 specification for the definition of the relevant namespace names.
所有SMIL 2.1文件都必须包含SMIL 2.1名称空间的声明，该名称空间出现在字符串“<SMIL”之后。名称空间字符串取决于语言配置文件。有关相关命名空间名称的定义，请参阅SMIL 2.1规范。
This parameter is meant to be used in MIME media-type-based content negotiation (such as that done with the HTTP "Accept" header) to negotiate for a variety of SMIL-based languages. It is modelled after the "profile" parameter in the application/xhtml+xml MIME type registration [5] and is motivated by very similar considerations.
此参数用于基于MIME媒体类型的内容协商（例如使用HTTP“Accept”头完成的协商），以协商各种基于SMIL的语言。它是根据application/xhtml+xmlmime类型注册[5]中的“profile”参数建模的，其动机非常类似。
The parameter is intended to be used only during content negotiation. It is not expected that it be used to deliver content, or that origin web servers have any knowledge of it (though they are welcome to). It is primarily targeted for use on the network by proxies in the HTTP chain that manipulate data formats (such as transcoders).
该参数仅用于内容协商期间。不希望它被用于交付内容，也不希望原始web服务器了解它（尽管欢迎他们使用）。它主要用于HTTP链中操纵数据格式（如转码器）的代理在网络上使用。
The value of the profile attribute is a URI that can be used as a name to identify a language. Though the URI need not be resolved in order to be useful as a name, it could be a namespace, schema, or language specification.
profile属性的值是一个URI，可以用作标识语言的名称。虽然URI不需要解析才能用作名称，但它可以是名称空间、模式或语言规范。
For example, user agents supporting only SMIL Basic (see http://www.w3.org/TR/smil20/smil-basic.html) currently have no standard means to convey their inability to fully support SMIL 2.0. While SMIL 2.0 Basic user agents are required to parse the full SMIL 2.0 language, there is potentially a substantial burden in receiving and parsing document content that will not be presented to the user, since its functionality is not included in SMIL Basic.
例如，仅支持SMIL Basic的用户代理（请参阅http://www.w3.org/TR/smil20/smil-basic.html)目前还没有标准的方法来表达他们无法完全支持SMIL 2.0。虽然需要SMIL 2.0 Basic用户代理来解析完整的SMIL 2.0语言，但在接收和解析不会呈现给用户的文档内容时可能会有很大的负担，因为SMIL Basic中不包含其功能。
In the future, the functionality afforded by this parameter will also be achievable by the emerging work on a protocol to transfer Composite Capability/Preferences Profiles (CC/PP) descriptions [6]. It is suggested that the "profile" parameter be used until the CC/PP protocol work has been finalized.
在未来，该参数提供的功能也将通过传输复合能力/偏好配置文件（CC/PP）描述的协议的新兴工作来实现[6]。建议在CC/PP协议工作完成之前使用“profile”参数。
An example use of this parameter as part of a HTTP GET transaction would be:
将此参数用作HTTP GET事务的一部分的示例如下：
Accept: application/smil+xml;
profile="http://www.w3.org/2001/SMIL20/HostLanguage"
Accept: application/smil+xml;
profile="http://www.w3.org/2001/SMIL20/HostLanguage"
SMIL documents contain a construct that allows "infinite loops". This is indispensable for a multimedia format. However, SMIL clients should foresee provisions such as a "stop" button that lets users interrupt such an "infinite loop".
SMIL文档包含一个允许“无限循环”的构造。这对于多媒体格式来说是必不可少的。然而，SMIL客户机应该预见诸如“停止”按钮之类的条款，允许用户中断这种“无限循环”。
As with HTML, SMIL documents contain links to other media (images, sounds, videos, text, etc.), and those links are typically followed automatically by software, resulting in the transfer of files without the explicit request of the user for each one. The security considerations of each linked file are those of the individual registered types.
与HTML一样，SMIL文档包含指向其他媒体（图像、声音、视频、文本等）的链接，这些链接通常由软件自动跟踪，从而在不需要用户明确请求的情况下传输文件。每个链接文件的安全注意事项是单个注册类型的安全注意事项。
The SMIL language contains "switch" elements. SMIL provides no mechanism that ensures that the media objects contained in a "switch" element provide equivalent information. An author knowing that one SMIL player will display one alternative of a "switch" and another will display a different part can put different information in the two parts. While there are legitimate use cases for this, it also gives rise to a security consideration: The author can fool viewers into thinking that the same information was displayed when in fact it was not.
SMIL语言包含“开关”元素。SMIL没有提供任何机制来确保“switch”元素中包含的媒体对象提供等效信息。如果作者知道一个SMIL播放器将显示“开关”的一个备选方案，而另一个将显示不同的部分，则可以在这两个部分中输入不同的信息。虽然有合法的使用案例，但它也引起了安全考虑：作者可以欺骗观众，让他们认为相同的信息显示了，而实际上没有显示。
In addition, all of the security considerations of RFC 3023 also apply to SMIL.
此外，RFC 3023的所有安全注意事项也适用于SMIL。
[1] "Synchronized Multimedia Integration Language (SMIL) 1.0 Specification", W3C Recommendation REC-smil-19980615, http://www.w3.org/TR/1998/REC-smil/, July 1998.
[1] “同步多媒体集成语言（SMIL）1.0规范”，W3C建议REC-SMIL-19980615，http://www.w3.org/TR/1998/REC-smil/，1998年7月。
[2] "Synchronized Multimedia Integration Language (SMIL 2.0) - [Second Edition]", W3C Recommendation, http://www.w3.org/TR/2005/REC-SMIL2-20050107/, January 2005.
[2] “同步多媒体集成语言（SMIL 2.0）-[第二版]”，W3C建议，http://www.w3.org/TR/2005/REC-SMIL2-20050107/，2005年1月。
[3] "Synchronized Multimedia Integration Language (SMIL 2.1)", W3C Recommendation, http://www.w3.org/TR/2005/REC-SMIL2-20051213/, December 2005.
[3] “同步多媒体集成语言（SMIL 2.1）”，W3C建议，http://www.w3.org/TR/2005/REC-SMIL2-20051213/，2005年12月。
[4] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.
[4] Murata，M.，St.Laurent，S.，和D.Kohn，“XML媒体类型”，RFC 3023，2001年1月。
[5] Baker, M. and P. Stark, "The 'application/xhtml+xml' Media Type", RFC 3236, January 2002.
[5] Baker，M.和P.Stark，“应用程序/xhtml+xml”媒体类型”，RFC 3236，2002年1月。
[6] H. Ohto, J. Hjelm, G. Klyne, M. Butler, L. Tran, F. Reynolds, C. Woodrow "Composite Capability/Preferences Profiles (CC/PP): Structure and Vocabularies 1.0", W3C Recommendation http://www.w3.org/TR/CCPP-struct-vocab/, January 2004.
[6] H.Ohto，J.Hjelm，G.Klyne，M.Butler，L.Tran，F.Reynolds，C.Woodrow“复合能力/偏好配置（CC/PP）：结构和词汇表1.0”，W3C建议http://www.w3.org/TR/CCPP-struct-vocab/，2004年1月。
Author's Address
作者地址
Philipp Hoschka W3C/ERCIM 2004, route des Lucioles - B.P. 93 06902 Sophia Antipolis Cedex FRANCE
Philipp Hoschka W3C/ERCIM 2004，Lucioles路线-B.P.93 06902 Sophia Antipolis Cedex法国
EMail: ph@w3.org
EMail: ph@w3.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。