DCNC - Appendix #3 - Content Type and Version Number

The Content Type and Version field is the area of the Naming Convention that identifies what type of content the DCP contains — whether it’s a feature, a trailer, a short subject, etc. — and what the version number is.  The field can contain up to 7 characters.  All content should be categorized as one of the following:

In the Composition Playlist

 

The Content Type is listed at //ContentKind:

<CompositionPlaylist xmlns=”http://www.smpte-ra.org/schemas/429-7/2006/CPL”>

     …

     <ContentKind>feature</ContentKind>

     …

</CompositionPlaylist>

 

Additional Notes:

If the scope attribute is absent, the permissible SMPTE 429-7 ContentKind values are as follows: “feature”, “trailer”, “teaser”, “test”, “rating”, “advertisement”, “short”, “transitional”, “psa”, and “policy”.  If the scope attribute is present and set to “http://www.smptera.org/schemas/429-16/2014/CPL-Metadata#scope/content-kind”, the permissible SMPTE ST 429-16 ContentKind values are as follows: “clip”, “promo” and “stereocard.”  See the specification for details.

 It’s important to add a version number after the Content Type code.  For example, feature version 2 would be “FTR-2”, etc.  This is important not only for selecting the correct version, but also for matching an “OV” with a “VF” version file.  (See Appendix #8.)  The Content Type field can also be expanded to add 2D or 3D identifiers.  (See Appendix #3a.) 

In the Composition Playlist

 

The Version Number is listed at //Reel[1]//VersionNumber:

<CompositionMetadataAsset xmlns=”http://www.smpte-ra.org/schemas/429-16/2014/CPL-Metadata”>

     …

     <VersionNumber status=”final”>2</VersionNumber>

     …

</CompositionMetadataAsset>

 

Additional Notes:

  1. The status attribute of the version number should have one of the following values: “final”, “temp”, or “pre”.
  2. The VersionNumber element of the Composition Metatdata Asset is preferred over the ContenVersion element of the Composition Playlist.  The latter element is more suitable for registry-based identifiers such as EIDR.

 After the Content Type and Version number in the Content Type Field, you may add further descriptions or “Content Type Modifiers” in sub-fields separated by hyphens.
For example:  POL-1-Temp-RedBand-TheatreChain-3D-6fl-48

These are used “a la carte” only if needed, and must be used in this order with these words:

In the Composition Playlist


The Chain is listed at //Reel[1]//Chain:

<CompositionMetadataAsset xmlns=”http://www.smpte-ra.org/schemas/429-16/2014/CPL-Metadata”>

     …

     <Chain>Grand Cinemas</Chain>

     …

</CompositionMetadataAsset>


The Luminance is listed at //Reel[1]/Luminance:

<CompositionMetadataAsset xmlns=”http://www.smpte-ra.org/schemas/429-16/2014/CPL-Metadata”>

     …

     <Luminance units=”foot-lambert”>3.5</Luminance>

     …

</CompositionMetadataAsset>


2D content is identified by the presence of the MainPicture element, which is listed at //Reel//MainPicture[1]:

<Reel>

     …

     <MainPicture>…</MainPicture>

     …

</Reel>


3D content is identified by the presence of the MainStereoscopicPicture element, which is listed at //Reel//MainStereoscopicPicture[1]:

<Reel xmlns:msp-cpl=”http://www.smpte-ra.org/schemas/429-10/2008/Main-Stereo-Picture-CPL”>

     …

     <msp-cpl:MainStereoscopicPicture>…</msp-cpl:MainStereoscopicPicture>

     …

</Reel>


The Frame Rate is listed at //Reel//MainPicture[1]/FrameRate or //Reel//MainStereoscopicPicture[1]/FrameRate:

<Reel>

     …

     <MainPicture>

          <FrameRate>48 1</FrameRate>

     </MainPicture>

     …

</Reel>


Additional Notes:

  1. The MainPicture and MainStereoScopicPicture elements are mutually exclusive: both may not appear within the same reel.
  2. The MainStereoScopicPicture element is described in the SMPTE 429-10 standard.