SMPTE ST 430-11-2010 D-Cinema Operations Auxiliary Resource Presentation List《数字电影运营 辅助资源显示列表》.pdf

《SMPTE ST 430-11-2010 D-Cinema Operations Auxiliary Resource Presentation List《数字电影运营 辅助资源显示列表》.pdf》由会员分享，可在线阅读，更多相关《SMPTE ST 430-11-2010 D-Cinema Operations Auxiliary Resource Presentation List《数字电影运营 辅助资源显示列表》.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、 Copyright 2010 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved November 2, 2010 Table of Contents Page Foreword . 2 Intellectual Property 2 1 Scope . 3 2 Conformance Notation . 3 3 Normative References . 3 4 Glossary . 4 5 Ov

2、erview (Informative) . 4 5.1 Usage . 4 5.2 Composition Playlist Mapping 4 5.3 Show Playlist Mapping . 4 6 Document Description 5 6.1 Namespace 5 6.2 Graphical Representation 6 6.3 Schema Elements 6 7 Schema Definition 8 8 Example (Informative) 9 9 XML Diagram Legend (Informative) . 10 9.1 Element Sy

3、mbols . 10 9.2 Model Symbols (“compositors“) . 11 9.3 Types . 11 9.4 Model Groups and References 11 Annex A Bibliography (Informative) . 13 Page 1 of 13 pages SMPTE ST 430-11:2010 SMPTE STANDARD D-Cinema Operations Auxiliary Resource Presentation List SMPTE ST 430-11:2010 Page 2 of 13 pages Foreword

4、 SMPTE (the Society of Motion 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 Standa

5、rds, Recommended Practices, 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 En

6、gineering Documents are drafted in accordance with the rules given in Part XIII of its Administrative Practices. SMPTE ST 430-11 was prepared by Technology Committee 21DC. Intellectual Property At the time of publication no notice had been received by SMPTE claiming patent rights essential to the im

7、plementation of this Standard. 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 430-11:2010 Page 3 of 13 pages 1 Scope This standa

8、rd defines a document for specifying the location of resources on a digital cinema server and the corresponding position at which they should be presented during the play out of a single composition or a show comprised of multiple compositions. 2 Conformance Notation Normative text is text that desc

9、ribes 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, changed, or added editorially without affecting interoperabilit

10、y. 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:” The keywords “shall“ and “shall not“ indicate requirements st

11、rictly 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 mentioning or excluding others; or that a certain course of act

12、ion 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 limits of the document. The keyword “reserved” indicates a pro

13、vision 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 implementation according to this document is one that includes all

14、 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 specified, the order of precedence of the types of normative

15、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. 3 Normative References Note: All references in this document to other SMPTE documents use the

16、current numbering style (e.g. SMPTE ST 429-7:2006) although, during a transitional phase, the document as published (printed or PDF) may bear an older designation (such as SMPTE 429-7-2006). Documents with the same root number (e.g. 429-7) and publication year (e.g. 2006) are functionally identical.

17、 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 agreements based on this standard are encouraged to investig

18、ate the possibility of applying the most recent edition of the standards indicated below. World Wide Web Consortium (W3C) (2004, February 4). Extensible Markup Language (XML) 1.0 (Third Edition). SMPTE ST 430-11:2010 Page 4 of 13 pages World Wide Web Consortium (W3C) (2004, October 28). XML Schema P

19、art 1: Structures (Second Edition). World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 2: Datatypes (Second Edition). Internet Engineering Task Force (IETF) (November 1996) RFC1738 - Uniform Resource Locators (URL). Internet Engineering Task Force (IETF) (1996, November). RFC 2396 U

20、niform Resource Identifiers (URI): Generic Syntax. Internet Engineering Task Force (IETF) (2005, July). RFC 4122 A Universally Unique Identifier (UUID) URN Namespace.7. SMPTE ST 429-7:2006, D-Cinema Packaging Composition Playlist. 4 Glossary The following paragraphs define the acronyms used in this

21、document. ACS: Auxiliary Content Server CPL: Composition Playlist DCS: Digital Cinema Server HTTP: Hypertext Transfer Protocol RPL: Auxiliary Resource Presentation List 5 Overview (Informative) This standard defines a schema for the interchange of the list of auxiliary resources available to the pla

22、yout of one or more compositions. The Auxiliary Resource Presentation List File identifies the auxiliary content resources needed for the current show or composition and their relative position on the timeline. 5.1 Usage The RPL provides a list of auxiliary resources available in the next compositio

23、n or sequence of compositions to be played. It is presented by a Digital Cinema Server (DCS) to an Auxiliary Content Server (ACS) at some time before playout begins. An ACS will obtain timeline updates from the DCS and determine which resources should be presented. 5.2 Composition Playlist Mapping E

24、ach ReelResources element within the RPL correlates to a single reel within a CPL. Each ReelResource element corresponds to a single Reel Asset within a CPL. While any reel asset could be mapped into the RPL, the intention is to map lower bit rate resources not “rendered” by the DCS, e.g. subtitles,

25、 captions, and special effects. Resources are intended to be pre-fetched before start of playout to allow for synchronous playout with the first frame of content. 5.3 Show Playlist Mapping Multiple compositions can be played in sequence to create a “show” timeline. To ensure continuity across CPL bo

26、undaries, an RPL can be created to represent the entire show timeline. Multiple ReelResources elements, representing the reels for multiple CPLs, can be present in a single RPL. In this case, the TimelineOffset attribute of the ReelResources element identifies the show-relative offset of the referen

27、ced resources. SMPTE ST 430-11:2010 Page 5 of 13 pages 6 Document Description 6.1 Namespace The structures defined in this document are represented using the Extensible Markup Language (XML) XML 1.0, and specified using XML Schema XML Schema Part 1: Structures and XML Schema Part 2: Datatypes. This

28、specification shall be associated with a unique XML namespace name Namespaces in XML. The namespace name shall be the string value http:/www.smpte-ra.org/schemas/430-11/2010/RPL”. This namespace name conveys both structural and semantic version information, and serves the purpose of a traditional ve

29、rsion number field. XML namespace names used in this standard are identified in Table 1. Namespace names are represented as Uniform Resource Identifier (URI) values RFC 23961. Table 1 XML Namespaces Qualifier URI rpl http:/www.smpte-ra.org/schemas/430-11/2010/RPL The URI listed in Table 1 is normati

30、ve, whereas the namespace qualifier value (used in Table 1 and elsewhere in this standard) is not normative. Thus, namespace qualifier values may be replaced in instance documents by any arbitrary XML compliant namespace qualifier, meaning that conformant implementations shall expect any XML complia

31、nt namespace qualifier value that is associated with a URI from Table 1. Datatypes from other schemas that are used in this document will be prefixed with the appropriate namespace qualifier (e.g. xs:dateTime). See XML Schema Part 2: Datatypes for further information about these types. 1Readers unfa

32、miliar with URI values as XML namespace names should be aware that although a URI value begins with a “method” element (“http” in this case), the value is designed primarily to be a unique string and does not necessarily correspond to an actual on-line resource. Applications implementing this standa

33、rd should not attempt to resolve URI values on-line. SMPTE ST 430-11:2010 Page 6 of 13 pages 6.2 Graphical Representation Below is a graphical representation of the ResourcePresentationList schema. Figure 1 ResourcePresentationList schema representation 6.3 Schema Elements 6.3.1 PlayoutID optional T

34、he optional PlayoutID attribute is used to correlate the RPL to the current playout. The use of the PlayoutID is intended to prevent stale (incorrect) auxiliary resources from playing out with the current presentation. 6.3.2 ReelResources Each ReelResources element defines the list of auxiliary reso

35、urces that may be presented at the same point in the timeline. It contains attributes that apply to all child resources. 6.3.2.1 TimelineOffset The TimelineOffset attribute defines the position (in edit units) in the timeline at which the child resources shall begin presentation. 6.3.2.2 ReelID The

36、ReelID identifies the Reel ID in the CPL associated with the ReelResources. SMPTE ST 430-11:2010 Page 7 of 13 pages 6.3.2.3 EditRate The EditRate attribute defines the number of edit units per second for the associated CPL Reel. 6.3.3 ReelResource The ReelResource element identifies all the attribut

37、es for a given auxiliary resource. 6.3.3.1 Id The Id attribute identifies the Resource UUID. 6.3.3.2 ResourceType The ResourceType attribute corresponds to the element name of a child element of the AssetList element in the CPL. Example ResourceTypes are MainSubtitle, MainCaption, ClosedCaption, and

38、 OpenCaption. 6.3.3.3 Language optional The optional Language attribute corresponds to the Language attribute for assets from the same referenced CPL track. 6.3.3.4 EntryPoint optional The optional EntryPoint attribute identifies the entry point in edit units from which this resource shall be offset

39、. Each EntryPoint attribute corresponds to the EntryPoint attribute for the associated asset from the referenced CPL. Playout of this resource starts EntryPoint edit units from the start of this resource. If this attribute is not present, a value of 0 shall be assumed. 6.3.3.5 Duration optional The

40、optional Duration attribute identifies the duration of the playable region of the associated asset from the referenced CPL. The resource stops playing at EntryPoint plus Duration edit units. If this attribute is not present, asset playback shall stop after (IntrinsicDuration EntryPoint)/EditRate sec

41、onds. 6.3.3.6 IntrinsicDuration The IntrinsicDuration attribute defines the Native Duration of the associated asset from the referenced CPL. The IntrinsicDuration is the duration, in edit units, of the entire resource, including portions that are not to be played, such as that portion before EntryPo

42、int. 6.3.4 ResourceFile The ResourceFile element identifies a URL for a resource file. The URL may be absolute, including the protocol (e.g. HTTP), host IP address, path, and filename, or may be relative to the location of this file (specifying a relative or absolute path and the filename). 6.3.4.1

43、ResourceID optional The optional ResourceID attribute identifies the UUID of this resource. This UUID is used to correlate resources referenced by UUID to their filename. SMPTE ST 430-11:2010 Page 8 of 13 pages 7 Schema Definition The XML Schema document presented in this section normatively defines

44、 the structure of an RPL using a machine-readable language. While this schema is intended to faithfully represent the structure presented in the normative prose portions (Sections 3 through 6) of this document, conflicts in definition may occur. In the event of such a conflict, the normative prose s

45、hall be the authoritative expression of the standard. The mapping between auxiliary content resource files and their presentation on the timeline SMPTE ST 430-11:2010 Page 9 of 13 pages 8 Example (Informative) The RPL example below represents a show with 4 trailer compositions, each 120 seconds in d

46、uration, and 1 feature composition, 40 minutes in duration with 2 reels of 20 minutes each. Each composition has an edit rate of 24/1. Captions are only present in the feature composition, so the timeline offset for the first resource in the feature is set to 4 * 120 seconds * 24 edit units/second =

47、 11520 edit units. In this example, each ReelResources element corresponds to a single reel in the feature composition. http:/192.168.1.1/reel1/caption_en-us_r1.xml http:/192.168.1.1/reel1/caption_fr_r1.xml http:/192.168.1.1/reel1/closedSubtitle_r1_file1.xml http:/192.168.1.1/reel2/caption_en-us_r2.

48、xml http:/192.168.1.1/reel2/caption_fr_r2.xml http:/192.168.1.1/reel2/closedSubtitle_r2_file1.xml SMPTE ST 430-11:2010 Page 10 of 13 pages 9 XML Diagram Legend (Informative) The following provides a legend for notation used in diagrams depicting XML structures. 9.1 Element symbols In the schema desi

49、gn diagrams presented above of this document, only the elements are drawn. Attributes are not visible. The cardinality of the element (01, 1 exactly, 0n, 1n) is indicated by the border of the elements. Optional elements are drawn with a dashed line, required elements with a solid line. A maximum occurrence greater one is indicated by a double border. Optional element Min. occurrence = 0, Max. occurrence = 1 Required single element Min. occur