1、 Copyright 2011 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue., White Plains, NY 10601 (914) 761-1100 Approved July 13, 2011 Table of Contents Page Foreword 2 Intellectual Property . 2 1 Scope 32 Conformance Notation 33 Normative References 34 Definitions and Terms . 45 A
2、rchitecture . 65.1 Overview (Informative) 6 5.2 SMPTE Media Package Components 7 6 Media Package Constraints on OPC 97 Media Package Schemas . 117.1 Table of Contents Part 11 7.2 Presentation Part 19 7.3 Media Application Part 37 7.4 Track Container Part 37 7.5 DRM License Part 38 7.6 Descriptive Me
3、tadata Part 38 7.7 Resource Part . 38 Annex A Bibliography (Informative) 39Page 1 of 39 pages SMPTE ST 2053:2011 SMPTE STANDARD Media Package for Storage, Distribution and Playback of Multimedia File Sets and Internet Resources SMPTE ST 2053:2011 Page 2 of 39 pages Foreword SMPTE (the Society of Mot
4、ion Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on six continents. SMPTEs Engineering Documents, including Standards, Recommended Practices
5、, and Engineering Guidelines, are prepared by SMPTEs Technology Committees. Participation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are dr
6、afted in accordance with the rules given in Part XIII of its Administrative Practices. SMPTE ST 2053 was prepared by Technology Committee 24TB. Intellectual Property At the time of publication no notice had been received by SMPTE claiming patent rights essential to the implementation of this Standar
7、d. However, attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. SMPTE shall not be held responsible for identifying any or all such patent rights. SMPTE ST 2053:2011 Page 3 of 39 pages 1 Scope This document describes the physical pack
8、aging format of the SMPTE Media Package. This specification is derived from the ISO 29500-2 specification for Open Packaging Conventions. The SMPTE Media Package Format may combine multiple media files, metadata files, playback applications, and other files, along with an XML Table of Contents, in a
9、 single ZIP file that can be stored and distributed as a single object using simple file transfer protocols such as HTTP:. Systems that have ZIP file readers may read or extract or add individual files in a Media Package. The Table of Contents and related XML files enable a media player to select ap
10、propriate media files, tracks, DRM licenses, presentation applications, and other media-specific constructs for playback, download, streaming, or updating. A reader that fully supports Open Packaging Conventions can utilize additional functionality, such as advanced file properties and digital signa
11、tures. 2 Conformance Notation Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: “shall“, “should“, or “may“. Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, c
12、hanged, or added editorially without affecting interoperability. Informative text does not contain any conformance keywords. All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as “Informative“ or individual paragraphs that start with “Note:”
13、 The keywords “shall“ and “shall not“ indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted. The keywords, “should“ and “should not“ indicate that, among several possibilities, one is recommended as particularly suitable, without m
14、entioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords “may“ and “need not“ indicate courses of action permissible within the
15、limits of the document. The keyword “reserved” indicates a provision that is not defined at this time, shall not be used, and may be defined in the future. The keyword “forbidden” indicates “reserved” and in addition indicates that the provision will never be defined in the future. A conformant impl
16、ementation according to this document is one that includes all mandatory provisions (“shall“) and, if implemented, all recommended provisions (“should“) as described. A conformant implementation need not implement optional provisions (“may“) and need not implement them as described. Unless otherwise
17、 specified, the order of precedence of the types of normative information in this document shall be as follows: Normative prose shall be the authoritative definition; Tables shall be next; followed by formal languages; then figures; and then any other language forms, including normatively referenced
18、 XML schema files (*.XSD files). 3 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agree
19、ments based on this recommended practice are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. SMPTE ST 2053:2011 Page 4 of 39 pages ISO/IEC 29500-2 Open Packaging Conventions (OPC, 2008 November 15), http:/standards.iso.org/ittf/Publicly
20、AvailableStandards/c051459_ISOIEC%2029500-2_2008%28E%29.zip World Wide Web Consortium (W3C) (2004, February 4). Extensible Markup Language (XML) 1.0 (Third Edition) World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 1: Structures (Second Edition) World Wide Web Consortium (W3C) (200
21、4, October 28). XML Schema Part 2: Datatypes (Second Edition) RFC 3986 Uniform Resource Identifier (URI); Generic Syntax, The Internet Society, Berners-Lee, T., R. Fielding, and L. Masinter, 2005, http:/www.ietf.org/rfc/rfc3986.txt RFC 3987 Internationalized Resource Identifiers (IRIs), The Internet
22、 Society, Duerst, M. and M. Suignard, 2005, http:/www.ietf.org/rfc/rfc3987.txt BCP-47 Best Current Practice, Tags for Identifying Languages, IETF RFC, http:/www.rfc-editor.org/rfc/bcp/bcp47.txt (September 2009 edition; includes RFC 5656, and RFC 4647) This is a multi-element standard and includes as
23、 an integral portion of this document: 2053a, 2053b, 2053c, and 2053d. 4 Definitions and Terms Words intended to convey the meaning defined in this document are capitalized. When a word matching a defined term is not capitalized, it is understood to convey its generic English meaning. Content Type C
24、omponent: XML markup (stored in a ZIP item) that identifies the MIME Media Type of each Part in the Package. DRM: “Digital Rights Management”; usually relying on encryption of files or streams, and control of decryption keys in DRM licenses that manage playback to prevent unintended use of the encry
25、pted content. File: An ordered sequence of bytes or byte streams stored in a file system that assigns a name to those bytes, including a hierarchical organization (“path”) of volumes and directories, and some method by which the named bytes can be read. The bytes of a file have different physical al
26、locations on different storage devices in a file system, on different file systems, when stored as a web resource, or when stored as a Part in a Media Package. However, the logical byte stream and file name are typically maintained independent of the physical storage system, so the term also is used
27、 to refer to the logical byte stream and file name. IRI: International Resource Identifier. License: A DRM license that manages decryption keys and playback rules for a particular DRM system. OPC: ISO/IEC 29500-2 Open Packaging Conventions standard. Package: A structured container file that has inde
28、pendent physical and logical organization and conforms to the ISO 29500-2 OPC standard. Package Component: Any data component defined in a Package, including Parts, Relationships, and the Content Types Stream. Package Root: The top organizational level (root) of a Package, represented by the “/” str
29、ing. SMPTE ST 2053:2011 Page 5 of 39 pages Part: A logical entity of data that has been stored as a physical ZIP item in a Package. Every Part consists of three elements: An ordered sequence of bytes (i.e., “a data stream”). A Part Name that corresponds to the physical name of the ZIP Item in the pa
30、ckage. Part Names are constrained by IRI naming conventions as described in the ISO 29500-2 Open Packaging Conventions specification, Section 9.1.1 “Part Names”. A Content Type specifying the MIME Media Type of the Part, as identified in the Content Type Component. Part Name: The IRI of a Part in th
31、e Package. Physical Package Format: A specific file format that can implement all the capabilities of a Package (e.g., a Zip Archive and associated logical Package format specification). Presentation Application: An “application” or computer program ranging from simple playlists and parameters, to m
32、ore complex declarative markup languages, to procedural code such as interpreted script language, intermediate languages partially compiled for virtual machines, or fully compiled binary code for native execution on specific processor hardware. A Presentation Applications primary purpose is the pres
33、entation and control of media essence and related information, including user input and Internet input. Relationship: A directional association between a Source and a Target. Relationships are expressed as XML in a Packages Relationship Parts, associated with the Package Root via naming convention o
34、r with an individual Part, and function like a flexible internal file “directory” system that is independent of physical storage organization. Relationship Part: A Package Part (XML markup) where Relationships are stored. A Relationships Part can be associated with each Part in the Package, or can b
35、e associated with the Package Root. This association is represented by naming convention relative to the associated Part or Package Root. Resource: A URI-addressable object on the Internet that is used to provide additional data or capabilities to the referring component. Source: A Package or a Part
36、 of a Package that is the origin of the directional association described by a Relationship. The URI of the Source is that of the Part with which the Relationship Part that stores the Relationship markup is associated. Target: A Part or Resource that is the destination of a directional association d
37、escribed by a Relationship. The URI of the Target Part or Resource is an attribute of the XML element that defines the Relationship. Track: A logical abstraction usually referring to a single essence stream such as audio, video, or subtitle; but more generally to any data that is delivered or render
38、ed sequentially in combination with audio and video. Physical storage of multiple Tracks may be in a single Track Container or multiple Track Containers. Track Container: A single A/V file, XML, or Resource that may contain one or more Tracks. XSD: W3C XML Schema Definition file format ZIP Archive:
39、A ZIP file as defined in the OPC specification. A ZIP archive contains ZIP items. ZIP Item: A ZIP item is an atomic set of data in a ZIP Archive that becomes a file when the archive is extracted. A ZIP Item has a “/” delimited name that corresponds to a folder hierarchy such that when a ZIP-based Pa
40、ckage is unzipped, an organized set of files and folders results. SMPTE ST 2053:2011 Page 6 of 39 pages 5 Architecture 5.1 Overview (Informative) A SMPTE Media Package is a ZIP-based file container that includes XML documents and naming compliant with the ISO 29500-2 Open Packaging Conventions stand
41、ard, plus XML documents defined herein for the management and playback of media essence files and their contained streams, and other types of files that may be useful for the description or presentation of the essence files. Media Packages are useful for storage and electronic distribution of multip
42、le files in a single container where multiple files are required to provide, for example, multiple resolutions, bitrates, codecs, content protection systems, languages, versions, episodes, collections, albums, metadata, and interactive presentation applications. Media Packages enable dynamic storage
43、 in the sense that files can be easily added or removed from a Media Package, similar to a computer file folder. A device can inspect a Media Package and discover files of interest in its Table of Contents and download them from a server for local storage in the Media Package, and subsequent playbac
44、k and copying of that Media Package. When new content or Presentations become available, they can be identified in an updated Table of Contents, and new Presentations and their related files can be downloaded to the Media Package. The Table of Contents lists “Presentations”, which can be as simple a
45、s linear playback of an audio, or audio/video file, but can also reference Presentation Applications intended for execution that may include menus, interactivity, online components, streaming, etc. A Presentation may combine multiple essence files in sync, in sequence, overlaid, switched, mixed, in
46、“3D”, etc. Presentations listed in the Table of Contents include format identification to enable devices to locate presentations they are capable of playing, and playback options so that they can select preferred Tracks according to language, ratings, accessibility, audio channels, video quality, an
47、d other factors. Figure 1 SMPTE Media Package Architecture, showing components unique to a Media Package (Informative) SMPTE ST 2053:2011 Page 7 of 39 pages 5.2 SMPTE Media Package Components The blue (or dark when black and white) components in the block diagram (Figure 1) are XML documents defined
48、 in this specification, and are in addition to structures normally included in a ZIP container that is OPC compliant. The “MediaApplication” boxes indicate contained files or “Parts” that are referenced either by the Table of Contents XML document, or a Presentation XML document. Each component is e
49、xplained in more detail below. 5.2.1 Media Package The “MediaPackage” box indicates the container, which appear as a single ZIP file to a file system or file transfer protocol, but to a ZIP file reader as a folder of files (ZIP Items or OPC Parts) with hierarchical path names. Since this is an OPC compliant Package, it also includes OPC Parts that are not shown separately in this diagram. A SMPTE Media Package reader may apply Media Package specific schemas to interpret the XML
