<?xml version="1.0" encoding="UTF-8"?>

XML Declaration (required)

The character encoding of your document must be defined.

iTunes only accepts UTF-8 encoding as it efficiently encodes non-Roman characters.

Important: The metadata.xml file must not contain a byte-order mark (BOM).

<package xmlns="http://apple.com/itunes/importer" version="film5.2">

Package Container (required)

The version attribute is required.

Packages created to this specification must indicate version="film5.2". The “film” portion of the attribute must be in lowercase letters.

<language>en-US</language>

Language (required)

The primary language of the metadata for this package. The language specified in this tag indicates which language the non-localized tags are expressed in, and the <locales> blocks provide alternative localizations.

Important: The value delivered with the <language> tag cannot be changed once the initial delivery has been imported.

As a best practice when specifying a language, use the region subtag (for example, the US of en-US) only when it conveys helpful information, such as spelling variations between countries. For example, there is generally not a need to distinguish between Japanese as used in one country versus another, so you should use only the language code subtag (ja) instead of the language code and region subtags (ja-JP). In cases where specifying a region is appropriate, use the hyphen character to combine a language subtag with a region subtag. This identifies both the language and the specific location where the language is used. For English with American spelling, use en-US; for English with British spelling, use en-GB.

The language codes are formatted according to the best practices recommended by the Internet Engineering Task Force (IETF) in a group of documents known collectively as BCP 47, and in particular, RFC 5646 (http://tools.ietf.org/html/rfc5646), which is part of BCP 47. An overview of these best practices is provided here: http://www.w3.org/International/articles/language-tags/. See “Language Codes” in the iTunes Package Film Specification for a list of common codes.

<provider>sonypicturesentertainment</provider>

Provider (required, Apple-supplied)

This value should be the iTunes-defined provider shortname given for partner identification. The value must match the provider shortname used in Transporter (the value that is after -s in the Transporter command). Note that it is the value you pass as an argument to Transporter, not the value in the XML, that determines the account you are delivering to. Contact your iTunes Technical Representative for this value.

<itunes_extra>

iTunes Extra (required)

The <itunes_extra> element block specifies the menu structure, templates, assets, and other content for the iTunes Extras.

<vendor_id>CLOUDY_MEATBALLS2_ITUNES_EXTRAS</vendor_id>

iTunes Extras Vendor Identifier (required, 1-100 bytes, see restrictions)

The permanent value that uniquely identifies this iTunes Extras separately from any other content given by the provider. This ID is used for updating. Vendor identifiers cannot be reused.

Note: This vendor identifier is not the same as the vendor identifier of the core film.

Restrictions: The vendor identifier can only contain alphanumeric characters and underscore marks; it cannot contain spaces, dashes, ampersands, other punctuation, or symbols. The vendor identifier is case-sensitive and must not start with an underscore.

<eidr>10.5240/9500-780F-E4D0-91D9-A8C8-O</eidr>

iTunes Extras EIDR (optional)

The EIDR (Entertainment Identifier Registry) is a universal, unique identifier system for movie and television assets. Any level of EIDR is accepted in this field, so long it is in valid format. For more information, see http://eidr.org/about-us/.

The format of the EIDR identifier is 10.5240/XXXX-XXXX-XXXX-XXXX-XXXX-C, where:

• 10.5240 represents the standard prefix of an EIDR value

• X represents a hexadecimal digit

• C represents the check character

<release_date>2014-07-10</release_date>

iTunes Extras Release Date (optional)

This tag is used to delay the release of the iTunes Extras. If you do not supply a <release_date> tag, the iTunes Extras will go live once the core film is available on the Store and the submitted package has been approved by the provider and Apple Quality Control. The date supplied must be the date of delivery or later; if the date is in the past, the iTunes Extras will not validate and you will not be able to submit the package. The date value must be in YYYY-MM-DD format.

If you submit an update to the iTunes Extras during the “delayed release” time period, that update replaces the existing package in the queue. You can have only one delayed release package waiting to go live at a time; you cannot submit multiple updates with staggered releases.

Important: The release date is intended for core promotions or to prevent the iTunes Extras from going live immediately after it has been approved by Apple Quality Control on catalog titles already live on the Store. For example, if a catalog title live on iTunes has new bonus content available for the anniversary of the film’s release, this tag can be used to target that release date of this iTunes Extras.

<content_item content_type="video">

  <vendor_id>CLOUDY_WITH_A_CHANCE_OF_MEATBALLS_2_2013</vendor_id>

</content_item>

Content Item (required)

The <content_item> block specifies the core content to which the iTunes Extras is connected. The content_type attribute indicates the type of content, in this case, video. The <vendor_id> tag is the vendor ID of the core film.

Note: There can only be one iTunes Extras per core film, and an iTunes Extras can be connected to only one core film. Once an iTunes Extras with a specific vendor ID is attached to a core film with a specific vendor ID, it cannot be detached, and the vendor IDs cannot be changed.

<title>Cloudy With a Chance of Meatballs 2</title>

Title (required; 1-256 bytes)

The title of the iTunes Extras.

Note: Do not include line breaks in the title. If blank lines or line breaks are included, the title will not display correctly for the customer.

<description>Flamangos, Cheesespiders, Hippotatomuses! Oh my! We sit down with filmmakers to discuss the inspiration behind these wacky food-animal hybrids that have taken over Swallow Falls.</description>

Description (required; 1-4000 bytes)

The default description of the iTunes Extras for the iTunes Store. Descriptions should explain whatʼs included in the iTunes Extras and can be up to 4000 bytes. This description is used if you do not provide a description at the <rootnode> level.

<locales>

Locales (optional)

Provides a mechanism to specify regional and language variations for the title and description of the iTunes Extras. For each language in which the title needs to appear, supply a <locale> tag and the title and description translated into the specified language.

Updates: When editing or adding a locale in a metadata update, include all locales (not just the one(s) being edited or added) and all the required tags; otherwise the locales not included will be removed. To intentionally remove a locale, submit a metadata update and include all the locales, omitting the locale(s) you want to remove. To remove all locales, submit a metadata update with an empty <locales> tag. If a metadata update omits the <locales> block altogether, no changes will be made to the locales.

  <locale name="es">

Locale Name (required within the <locales> tag)

Identifies the language in which the localized title appears. The locale can indicate both the language and the optional location where the language is spoken, for example, fr-CA indicates French as spoken in Canada.

<title>Nublado con posibilidad de albóndigas 2</title>

Localized Title (required within the <locales> tag; 1-256 bytes)

The title of the iTunes Extras in the language specified with the <locale> tag.

Note: Do not include line breaks in the title. If blank lines or line breaks are included, the title will not display correctly for the customer.

<description>Flamangos, Cheesespiders, Hippotatomuses! Oh my! Nos sentamos con los cineastas para discutir la inspiración detrás de estos híbridos animal-alimento extravagantes que se han apoderado de Swallow Falls.</description>

Localized Description (required within the <locales> tag; 1-4000 bytes)

The description of the iTunes Extras in the language specified with the <locale> tag. Descriptions should explain what’s included in the iTunes Extras and can be up to 4000 bytes.

 </locale>

</locales>

<rootnodes>

Root Nodes (required on initial delivery)

The <rootnodes> block defines territory-specific menu structures; each territory menu is defined with a <rootnode> block.

You can set up several menu structures that display different nodes with child nodes. This is useful when you need to exclude some content if that content has not been cleared for a specific territory. For example, if a gallery has not been cleared for use in France, you can set up another root node that excludes that gallery or provide an alternate gallery without the items that have not been cleared in France.

Note: If you’re keeping the menu structure as-is and not making any changes to any root nodes, leave out the entire <rootnodes> block.

<rootnode>

Root Node (required)

Begins a territory-specific top level menu. Each root node is territory- (or territories-) specific, which are specified using the <territories> block (see the annotation below).

You must supply at least one <rootnode> with at least one defined <territory>.

<vendor_id>CLOUDY_MEATBALLS2_ITUNES_EXTRA_US</vendor_id>

Root Node Vendor Identifier (required; 1-100 bytes; see restrictions)

The permanent value that uniquely identifies this node in this package and among any nodes ever submitted by this provider on any iTunes Extras.

Restrictions: The vendor identifier can only contain alphanumeric characters and underscore marks; it cannot contain spaces, dashes, ampersands, other punctuation, or symbols. The vendor identifier is case-sensitive and must not start with an underscore.

<title>Cloudy With a Chance of Meatballs 2</title>

Title (required; 1-256 bytes)

The title of the iTunes Extras to use for this root node.

Note: Do not include line breaks in the root node title. If blank lines or line breaks are included, the title will not display correctly for the customer.

<short_title>Extras</short_title>

Short Title (optional; 1 to 40 bytes)

If provided, the short title is used in lists (such as an item on a menu), instead of the full title in cases where the title is too long to fit.

<description>Check out the Mouth Watering Extras for Cloudy With a Chance of Meatballs 2! Includes 4 new mini-movies, Deleted Scenes, whacky featurettes and more! There is no lack of food fun!</description>

Description (optional; 1-4000 bytes)

The description of the iTunes Extras for the iTunes Store. This description will display for the countries listed in the <rootnode>. This description can differ from the default description provided in the <itunes_extra> block. Descriptions should explain whatʼs included in the iTunes Extras for the countries in the <rootnode> and can be up to 4000 bytes. If no description is provided for the countries in the <rootnode>, the default description in the <itunes_extra> will be used.

<territories>

   <territory>US</territory>

   <territory>ES</territory>

</territories>

Territory (at least one <territory> is required)

The territory in which to display this navigational structure. Must be specified as an ISO 3166-1 alpha 2 country code.

In this example, this root node will be used for the U.S. and Spain.

Notes:

• Within an iTunes Extras, a <territory> can be listed only once (the same territory cannot be listed in more than one <rootnode>).

• Once an iTunes Extras has been approved by Apple, you can move a territory to a different <rootnode>, but you cannot remove it from the iTunes Extras as a whole.

<background_gallery_link vendor_id="CLOUDY_MEATBALLS2_MAIN_BG_GALLERY"/>

Background Gallery Link (required on the <rootnode>; otherwise optional)

Specifies the vendor ID of the gallery (with <gallery_type> of menubg) that contains the video, images, and/or audio to use as the background for this node.

Note: The background video, images, and/or audio referenced by this <background_gallery_link> tag will be used for locales for which a localized <background_gallery_link> tag has not been provided.

<locales>

 <locale name="es">

   <title>Nublado con posibilidad de albóndigas 2</title>

   <short_title>Extras</short_title>

   <description>¡Te vas a chupar los dedos con los extras de Lluvia de albóndigas 2! Incluyen comentarios del director, 4 mini películas nuevas, escenas eliminadas, cortos para morirse de risa y más. ¡Diversión asegurada!</description>

   <background_gallery_link vendor_id="CLOUDY_MEATBALLS2_MAIN_BG_ES"/>

 </locale>

</locales>

Locales (<locale> is optional, but if supplied, <title> and <description> are required)

For each locale, supply a localized title, short title, description, and background video, images, and/or audio file. If you do not provide the <background_gallery_link> or <short_title> for a locale, the background and short title supplied on the <rootnode> will be used; in this example, the non-localized elements will be in English.

Note: If you do not provide localized <short_title> and <background_gallery_link> tags, the short title and background supplied in the default locale (as specified with the <language> tag) will be used. For example, if the default locale is English and if you do not provide French localizations, a user who has set French as the preferred language will see non-localized tags in English.

<transition>push</transition>

Transition (optional)

Specifies the transition to use between this node and its children. If you do not supply the <transition> tag, the default is dissolve.

Transitions include:

• dissolve

• none

• push

• wipe

<colors background="000000"/>

Colors (optional)

The <colors> tag with the background attribute specifies the color to use for the background in this root node on the Desktop. The background color fills the screen that is not covered by the iTunes window, which can be re-sized by the user. The color value must be a valid hexadecimal code. If you do not supply a color, the default color (which is black) will be used.

<navnodes>

Navigation Nodes (required on initial delivery)

The <navnodes> block creates the navigation of the territory-specific menu structure by defining the navigation nodes; each node is defined with a <navnode> block. Navigation nodes are specified by type (play, menu, gallery, scenes, cast, or related) and some types require that you specify a template. See the annotations below for further details.

Updates: To remove a navigation node, deliver the entire <navnodes> block, omitting the <navnode> you want to remove. If you’re not making any changes to any children nodes of this root node (keeping the menu structure as-is), leave out the entire <navnodes> block. To delete all navigation nodes, send an empty tag: <navnodes/>.

<navnode type="play">

Navigation Node (required)

Defines the navigation node type. A <navnode> must have a type and some types ("menu", "gallery", and "scenes") can be customized with a template to define its behavior.

The type attributes include:

• "play" (required): Plays the full-length feature

• "menu": Use to create your own nodes, such as Special Features

• "gallery": Use for image and video galleries

• "cast": Use to display cast and crew information and images

• "scenes": Use for scenes and scene groups

• "related" (required): Points to related iTunes content (automatically generated)

In this example, the type is "play", which cannot be customized so a template attribute has not been supplied. See the annotation below for the scenes navigation node for details on the template attribute.

Note: You must include a <navnode> for the Play and Related nodes. The Play navigation node must be listed first within the <navnodes> block and the Related navigation node must appear last.

<vendor_id>CLOUDY_MEATBALLS2_PLAY</vendor_id>

Navigation Node Vendor Identifier (required, 1-100 bytes, see restrictions)

The permanent value that uniquely identifies this node in this package and among any nodes ever submitted by this provider on any iTunes Extras. This ID is used for identifying the node during subsequent updates. Vendor identifiers cannot be reused.

Restrictions: The vendor identifier can only contain alphanumeric characters and underscore marks; it cannot contain spaces, dashes, ampersands, other punctuation, or symbols. The vendor identifier is case-sensitive and must not start with an underscore.

<title>PLAY</title>

Navigation Node Title (required; 1-256 bytes)

The name of the navigation node. For the Play navigation node, the title must be one word (“PLAY”, not “PLAY MOVIE”).

As a best practice, Apple recommends using all uppercase for the top level navigation node titles. The font and selection state are pre-set and cannot be changed.

You can also use the following optional tags for the Play navigation node: <locales>.

Note: Do not include line breaks in the navigation node title. If blank lines or line breaks are included, the title will not display correctly for the customer.

<preview_label>TRAILER</preview_label>

Navigation Node Preview Label (required; 1-256 bytes)

The label to use for the Play node when in preview mode. The label must be “TRAILER”. A customer can select it on the Store to preview the iTunes Extras before purchasing. The label can be localized.

This tag is only allowed on the Play navigation node.

<movie_label>MOVIE</movie_label>

Navigation Node Movie Label (required; 1-256 bytes)

The label to use for the Play node on an iOS device. The label must be “MOVIE”. The label can be localized.

This tag is only allowed on the Play navigation node.

<navnode type="scenes" template="carousel">

Navigation Node with Scenes (optional)

Defines the navigation node type and a template. A "scenes" navigation node can be customized with a template to define its behavior.

The template attributes available for use with the "scenes" navigation node include:

• "carousel": Content thumbnails with left/right scroll option

• "list_on_right": Text list of items and navigation on the right with preview on the left

• "list_on_left": Text list of items on the left with preview on the right

• "list_on_left_with_grid": Text list on the left with a grid of selected contents on the right

• "grid": A grid of selected contents on the right

See Templates Overview for example images, descriptions, and options for each template.

You can also use the following optional tags (described elsewhere in these annotations) for the scenes navigation node: <short_title>, <background_gallery_link>, <show_play_all>, <locales>, and <transition>. Specifying a <transition> on a scenes node sets the type of transition to use between the scenes when being viewed.

<vendor_id>CLOUDY_MEATBALLS2_SCENES</vendor_id>

Navigation Node Vendor Identifier (required, 1-100 bytes, see restrictions)

The permanent value that uniquely identifies this node in this package and among any nodes ever submitted by this provider on any iTunes Extras. Vendor identifiers cannot be reused.

Restrictions: The vendor identifier can only contain alphanumeric characters and underscore marks; it cannot contain spaces, dashes, ampersands, other punctuation, or symbols. The vendor identifier is case-sensitive and must not start with an underscore.

<title>SCENES</title>

Navigation Node Title (required; 1-256 bytes)

The name of the navigation node.

As a best practice, Apple recommends using all uppercase for the top level navigation node titles. The font and selection state are pre-set and cannot be changed.

Note: Do not include line breaks in the navigation node title. If blank lines or line breaks are included, the title will not display correctly for the customer.

<background_gallery_link vendor_id="CLOUDY_MEATBALLS2_SCENES_BG"/>

Background Gallery Link (optional for scene navigation nodes)

Specifies the vendor ID of the gallery (with <gallery_type> of menubg) that contains the video, images, and/or audio to use as the background for this node.

Note: If you do not supply a background item, the navigation node will use the background item of the parent node, in this example, that would be the root node. To prevent that, see the annotation for the <inherit_background_image> and <inherit_background_audio> tags below.

<show_play_all>true</show_play_all>

Show Play All (optional)

Indicates whether to show the "Play All" button. When the viewer selects the button, each video is played in the order they appear in the <scene_links> block. Allowed values are true or false. The tag is optional; if not supplied, the value defaults to false.

<navnode type="gallery" template="one_up">

 <vendor_id>CLOUDY_MEATBALLS2_COMMENTARY</vendor_id>

 <title>COMMENTARY</title>

 <description>Listen to the director's insights on the making of the film.</description>

 <locales>

  <locale name="es">

   <title>COMENTARIO</title>

   <description>Escuchar ideas del director en la realización de la película.</description>

  </locale>

 </locales>

 <gallery_link vendor_id="CLOUDY_MEATBALLS2_COMMENTARY_GALLERY"/>

Navigation Node with a Video Gallery (optional)

Defines the navigation node that displays a video gallery. In this example, the navigation node is for the video that includes the director’s commentary. The core film will be cloned and the audio of the commentary will be included in the delivery of the iTunes Extra package. See the annotation for the Director's Commentary Video Gallery for more details. The navigation node for the commentary uses the "one_up" template so that the video with the accompanying commentary audio displays in full screen.

The <vendor_id>, <title>, and <gallery_link> tags are required for "gallery" navigation nodes.

The <gallery_link vendor_id="CLOUDY_MEATBALLS2_COMMENTARY_GALLERY"/> tag specifies the vendor ID of the gallery that contains the reference to the core film to be cloned, the audio file to use for the commentary, as well as a commentary-specific preview image. The <gallery_link> tag is required if the <navnode> type is gallery. The gallery that contains the video must have the <gallery_type> of video.

<navnode type="menu" template="list_on_right">

 <vendor_id>CLOUDY_MEATBALLS2_FEATURES</vendor_id>

 <title>FEATURES</title>

 <background_gallery_link vendor_id="CLOUDY_MEATBALLS2_FEATURES_BG"/>

 <selection_gallery_link vendor_id="CLOUDY_MEATBALLS2_SEL_FEATURES"/>

Navigation Node with Menu (optional)

Defines the navigation node that displays a menu of options; in this example, the menu options link to the bonus content in the iTunes Extras. The navigation node type "menu" can be customized with a template to define its behavior. (Note that if the <navnode> type allows a template, the template attribute is required and you must specify which one to use.)

The template attributes available for use with the "menu" navigation node include:

• "carousel": Content thumbnails with left/right scroll option

• "list_on_right": Text list of items and navigation on the right with preview on the left

• "list_on_left": Text list of items on the left with preview on the right

• "list_on_left_with_grid": Text list on the left with a grid of selected contents on the right

• "grid": A grid of selected contents on the right

• "rows": Scrolling rows or shelves of categorized content

See Templates Overview for example images, descriptions, and options for each template.

The <selection_gallery_link> tag (see the annotation below) is required only if this menu-type node is a child of another menu (non-root) node. You can also use the following optional tags (described elsewhere in these annotations): <short_title>, <background_gallery_link>, <show_play_all>, <locales>, and <transition>.

<navnode type="menu" template="list_on_right">

 <vendor_id>CLOUDY_MEATBALLS2_FEATURES</vendor_id>

 <title>FEATURES</title>

   <!-- begins a child menu within a navigation node -->

   <navnodes>

    <navnode type="gallery" template="list_on_left">

     <vendor_id>CLOUDY_MEATBALLS2_MINI_MOVIES</vendor_id>

     <title>Mini Movies</title>

     <description>Catch all your favorite characters in these all new Mini Movies.</description>

     <locales>

      <locale name="es">

        <title>Mini Películas</title>

        <description>Captura todos tus personajes favoritos en estos todos los nuevos Mini Película.</description>

      </locale>

     </locales>

     <selection_gallery_link vendor_id="CLOUDY_MEATBALLS2_SEL_MINI_MOVIES"/>

     <gallery_link vendor_id="CLOUDY_MEATBALLS2_MINI_MOVIES"/>

    </navnode>

Navigation Node Within Another Navigation Node (optional)

Use the <navnodes><navnode> tags within another <navnodes><navnode> block to create a menu within a main navigation node. In this example, the FEATURES menu has links to several bonus videos. This first navigation node displays a menu (list-on-left) that links to bonus content videos; the specified <gallery_link> identifies the gallery that stores the videos.

Note: The title for this navigation node (Mini Movies) does not need to appear in all uppercase because it is not a top level navigation node.

The <selection_gallery_link vendor_id="CLOUDY_MEATBALLS2_SEL_MINI_MOVIES"/> tag in this case is required; the parent navigation node (in this example, the FEATURES navigation node) is a menu-type navigation node, and the <selection_gallery_link> tag is required for both gallery-type and menu-type navigation nodes. The selection image appears on the parent node page when the user selects the menu item (in this example, the Mini Movies menu item). The gallery that contains the image must have the <gallery_type> of selection.

The <gallery_link vendor_id="CLOUDY_MEATBALLS2_MINI_MOVIES"/> tag links to the gallery that contains the videos. The <gallery_link> tag is required if the<navnode> type is gallery. The gallery that contains the videos must have the <gallery_type> of video.

<navnode type="gallery" template="carousel">

 <vendor_id>CLOUDY_MEATBALLS2_SKETCHES_GALLERY</vendor_id>

 <title>GALLERY</title>

 <description>Go behind the scenes and browse photo galleries about the world of Cloudy with a Chance of Meatballs 2.</description>

 <locales>

  <locale name="es">

   <title>GALERÍA</title>

   <description>Ir detrás de las escenas y navegar galerías de fotos sobre el mundo de Lluvia de albóndigas 2.</description>

  </locale>

 </locales>

 <gallery_link vendor_id="CLOUDY_MEATBALLS2_SKETCHES"/>

 <show_play_all>true</show_play_all>

Navigation Node with an Image Gallery (optional)

Defines the navigation node that displays an image gallery. The navigation node "gallery" can be customized with a template to define its behavior. (Note that if the <navnode> type allows a template, the template attribute is required and you must specify which one to use.)

The template attributes available for use with the "gallery" navigation node include:

• "carousel": Content thumbnails with left/right scroll option

• "list_on_right": Text list of items and navigation on the right with preview on the left

• "list_on_left": Text list of items on the left with preview on the right

• "expand_in_parent": Gallery items are presented as selectable choices directly on the parent menu

• "one_up": Content displays in full screen

• "grid": A grid of selected contents on the right

See Templates Overview for example images, descriptions, and options for each template.

The <vendor_id>, <title>, and <gallery_link> tags are required for "gallery" navigation nodes.

The <gallery_link vendor_id="CLOUDY_MEATBALLS2_SKETCHES"/> tag specifies the vendor ID of the gallery that contains the images. The <gallery_link> tag is required if the<navnode> type is gallery. The gallery that contains the images must have the <gallery_type> of generic.

The optional <show_play_all> tag indicates whether to show the "Slideshow" button. When the viewer selects the button, each image is played in the order they appear in the gallery that contains the images. Allowed values are true or false. The tag is optional; if not supplied, the value defaults to false.

You can also use the following optional tags (described elsewhere in these annotations) for the image gallery navigation node: <background_gallery_link>, <transition>, and <locales>.

 <inherit_background_image>false</inherit_background_image>

</navnode>

Inherit Background Image (optional)

Indicates if the navigation node should or should not use the same background as the parent node. Allowed values are true or false. In this example, a background image for this navigation node has not been supplied. By default, when you do not supply a background item (which can be one or more images or an audio file), the item from the parent node is used. If you do not want to use the same background item, use one of the following tags with the false value to prevent it:

• <inherit_background_image>

• <inherit_background_audio>

When the parent node has an audio background and you do not set the <inherit_background_audio> tag to false, the audio loop will continue to play even when the user navigates to another node until a false value is encountered.

<navnode type="cast">

 <vendor_id>CLOUDY_MEATBALLS2_CAST</vendor_id>

 <title>CAST AND CREW</title>

</navnode>

Cast and Crew Navigation Node (optional)

Use the <navnode="cast"> tag to create a menu on the root node page to link to cast and crew information as delivered with the core content. The <vendor_id> refers to the cast and crew delivered with the core content. See the iTunes Package Film Specification 5.2.1 (or higher) for details.

Note: If you have not updated the cast and crew to the new structure, the node will display related videos for cast members instead of cast member photo, character name, and description.

You can also use the following optional tags (described elsewhere in these annotations) for the cast navigation node: <short_title>, <background_gallery_link>, <transition>, <locales>, <inherit_background_image>, and <inherit_background_audio>.

<navnode type="related">

 <vendor_id>CLOUDY_MEATBALLS2_RELATED</vendor_id>

 <title>RELATED</title>

</navnode>

Related Content Navigation Node (required; 1-256 bytes for <title>)

Defines the Related navigation menu. A <navnode> must have a type and the type must be "related". iTunes automatically generates the content that is displayed when this node is selected.

You can also use the following optional tags (described elsewhere in these annotations) for the Related navigation node: <short_title>, <background_gallery_link>, <transition>, <locales>, <inherit_background_image>, and <inherit_background_audio>.

Note: You must include a <navnode> for the Play and Related nodes. The Play navigation node must be listed first within the <navnodes> block and the Related navigation node must appear last.

  </navnodes>

 </rootnode>

 <!-- other <rootnode>s for other territories would go here -->

</rootnodes>

<galleries>

Galleries (required)

The <galleries> block defines groups of related images, videos, or audio files. Each image, video, or audio is defined with a <gallery_item> tag.

Even if you are delivering only one gallery, it must be enclosed within a <galleries> block.

To remove a gallery, use <gallery remove="true"> and supply the <vendor_id>. For example:

<gallery remove="true">

 <vendor_id>CLOUDY_MEATBALLS2_MINIMOVIES_BG</vendor_id>

</gallery>

<gallery>

Gallery for Background Content (required on the default locale of each <rootnode>)

Begins a single gallery referenced by vendor ID (in this example, the gallery is used to store background items). Galleries build the audio, video, and image components used throughout the Extras. Galleries are referenced elsewhere in the XML by vendor ID using one of the following tags:

• <background_gallery_link>

• <gallery_link>

• <selection_gallery_link>

In this example, the specified gallery here stores items to use for background content.

<vendor_id>CLOUDY_MEATBALLS2_MAIN_BG_GALLERY</vendor_id>

Gallery Vendor Identifier (required, 1-100 bytes, see restrictions)

The permanent value that uniquely identifies this gallery in this package and among any galleries ever submitted by this provider on any iTunes Extras.

Restrictions: The vendor identifier can only contain alphanumeric characters and underscore marks; it cannot contain spaces, dashes, ampersands, other punctuation, or symbols. The vendor identifier is case-sensitive and must not start with an underscore.

<gallery_type>menubg</gallery_type>

<display_name>MAIN_BG_GALLERY</display_name>

Gallery Type and Display Name (required)

Indicates the type of gallery. Each <gallery> is assigned a predefined “type” that defines its content, behavior, and available templates.

The gallery types include:

• menubg: Gallery of background video, images, and/or audio

• video: Gallery of video clips, different than <scenes>

• generic: Gallery of still images

• selection: Gallery of images to display on the parent node when an item is selected

In this example, the gallery referenced by the <background_gallery_link vendor_id="CLOUDY_MEATBALLS2_MAIN_BG_GALLERY"/> tag earlier in the XML contains the video, images and/or audio asset file used for the background of the menu structure page. The gallery that contains the video, images and/or audio must have the <gallery_type> of menubg.

Note: You can have multiple menubg galleries to store background items for different nodes, or for different territories.

Display Name

Name of the gallery using up to 1024 bytes. Even though the display name does not show up on any device, you should provide a meaningful name, which will help during content review. Do not include line breaks in the display name.

<item_display_duration_seconds>7.5</item_display_duration_seconds>

Gallery Item Display Duration (optional)

Specifies how many seconds to display each image before transitioning to next. If you do not supply the tag, the default value is 6 seconds.

For a menubg gallery, the <item_display_duration_seconds> value specifies the time each background image is displayed (if you deliver multiple images).

<gallery_repeat_limit>5</gallery_repeat_limit>

Gallery Repeat Limit (optional)

For the audio-type background item, use the <gallery_repeat_limit> tag to specify how many times to run the audio loop. The default setting is no limit; if you do not set a limit or if you set the limit to zero, the audio loop will play continuously as the user navigates between nodes unless a node has the tag <inherit_background_audio> set to false.

Note that this tag does not apply to image-type backgrounds. If you supply the tag, but the menubg gallery does not include an audio item, the tag will be ignored.

<gallery_items>

Gallery Items (required)

Begins the gallery items block that includes the vendor ID and the asset file for each item in this menu background gallery. These items include the background images and/or audio file referenced elsewhere in the XML. Each gallery item must be assigned a unique vendor ID.

<gallery_item type="video">

 <vendor_id>CLOUDY_MEATBALLS2_MAIN_BG_VIDEO_LOOP</vendor_id>

 <eidr>10.5240/A7F9-B2E6-83C7-53CC-8159-D</eidr>

 <assets>

  <asset type="full">

    <data_file role="source">>

     <locale name="en-US"/>

     <file_name>mm_bg_video_loop.mov</file_name>

     <size>7699143756</size>

     <checksum type="md5">e7fa00d0356912be5610b01182a650fb</checksum>

     <attribute name="crop.top">142</attribute>

     <attribute name="crop.bottom">142</attribute>

     <attribute name="crop.left">4</attribute>

     <attribute name="crop.right">4</attribute>

    </data_file>

    <data_file role="audio.7_1">>

     <locale name="en-US"/>

     <file_name>main_bg_7_1.mov</file_name>

     <size>691266596</size>

     <checksum type="md5">1abedda87d7df4b12512cf50436b9714</checksum>

     <attribute name="audio.surround.force_5_1_downmix">true</attribute>

    </data_file>

  </asset>

 </assets>

</gallery_item>

Gallery Item Video Asset (required for a video-type item in the gallery)

The gallery item block specifies the asset file and the vendor ID. The gallery type is menubg and this type of gallery can contain video, images, and an audio file in a single gallery, so the <gallery_item> includes a type attribute to indicate whether the item is a video, image, or audio file.

The type attribute is required and for video files, the value must be "video".

The <asset> tag requires the <file_name>, <checksum>, <size>, and <locale> tags. The <attribute> tag for crop values is optional. You may also deliver additional or alternative audio tracks as data file elements associated with the video <asset>. Details for submitting audio with a video <asset> can be found later on in this document.

Video is optional for background galleries and is only supported in background galleries associated with the Main Menu. If a video is delivered to a background gallery associated with the Main Menu, the video will play with its embedded or associated audio data file element on Apple TV. All other platforms will display the supplied background images and audio loop instead of the video and its associated audio elements. If the Apple TV has a poor Internet connection, the supplied background images and audio loop will display in place of the video and its associated audio elements. When viewing iTunes Extras on Apple TV, video backgrounds will continuously loop on the Main Menu and child nodes will not inherit them. When navigating to a child node off the Main Menu, the supplied background images and audio loop will play in place of the video and its associated audio elements.

Video Asset Requirements:

• Apple ProRes

• 1080 pixels (1920 x 1080) or higher preferred

• Video length must be less than 10 minutes 30 seconds

• 4K HDR video loops are supported (see Metadata Example for HDR Dolby® Vision and Metadata Example for HDR10 in the iTunes Package Film Specification for details)

• Dolby Atmos audio is supported. (See iTunes Extras Metadata Example for a complete example of how to provide Dolby Atmos audio in the metadata. See Dolby Atmos Audio Source Asset Requirements for the audio file requirements.)

For complete video requirements, see the Film Content Profiles section of the iTunes Video and Audio Asset Guide.

Note: All HDR videos, including video loops, require a matching SDR source. The SDR source is referred to as the primary source (with the role="source"). An HDR video loop would be delivered as an additional data file with the role="source.hdr".

<gallery_item type="image">

 <vendor_id>CLOUDY_MEATBALLS2_MAIN_BG_GALLERY_IMG1</vendor_id>

 <assets>

  <asset display_target="AppleTV">

    <data_file>

     <file_name>main_bg.png</file_name>

     <size>3810026</size>

     <checksum type="md5">1c98189da56b23f7411862ec1abfda3f</checksum>

    </data_file>

  </asset>

<!-- additional display target assets here -->

 </assets>

</gallery_item>

Gallery Item Image Asset(s) (required for each image-type item in the gallery)

The gallery item block specifies the asset file(s) and the vendor ID. The gallery type is menubg and this type of gallery can contain video, images, and an audio file in a single gallery, so the <gallery_item> includes a type attribute to indicate whether the item is a video, image, or audio file.

If you deliver more than one image file in a background gallery, the images will be rotated in automatically as a slideshow. The default duration to display each image is 6 seconds. You can use the <item_display_duration_seconds> on the gallery to set a different duration (see the annotation above).

The type attribute is required and for image files, the value must be "image".

In this example, the gallery item is the image to use as the background of the root node, so the type is "image".

Indicating the target device for background images is required. You must provide an image for each target device. Use the display_target attribute to indicate the device for the image you are delivering:

• "AppleTV"

• "Desktop"

• "4K-16:9"

• "4K-4:3"

The <asset> tag requires the <file_name>, <checksum>, and <size> tags.

Image Asset Requirements:

• PNG

• RGB

• 72 dpi or higher

• 3840 x 2160 pixels for Apple TV

• 1920 x 1080 for desktop computers

• 2880 x 1620 for desktops with retina display

• 2880 x 1620 for 4K-16:9

• 2732 x 2048 for 4K-4:3

• All menu background sizes are minimum sizes with aspect ratios locked

<gallery_item type="audio">

 <vendor_id>CLOUDY_MEATBALLS2_MAIN_BG_LOOP</vendor_id>

 <assets>

  <asset>

    <data_file>

     <file_name>mm_bg.wav</file_name>

     <size>10004316</size>

     <checksum type="md5">d335dad616ab73fdfcec38592d0f5d82</checksum>

    </data_file>

  </asset>

 </assets>

</gallery_item>

Gallery Item Audio Asset(s) (required for an audio-type item in the gallery)

The gallery item block specifies the asset file and the vendor ID. In this example, the audio file being delivered is used as background audio for the root node and the gallery type is menubg. This type of gallery can contain video, images, and one audio file in a single gallery, so the <gallery_item> includes a type attribute to indicate whether the item is a video, image, or audio file.

The type attribute is required and for audio files, the value must be "audio".

The <asset> tag requires the <file_name>, <checksum>, and <size> tags.

The audio must be:

• WAV (.wav), M4A (.m4a), or FLAC (.flac)

• Uncompressed or lossless

• Stereo

• 44.1Khz minimum

• 16-bit or 24-bit resolution minimum

  </gallery_items>

</gallery>

<gallery>

 <vendor_id>CLOUDY_MEATBALLS2_DIRECTOR_COMMENTARY</vendor_id>

 <gallery_type>video</gallery_type>

 <display_name>Director's Commentary</display_name>

Director's Commentary Video Gallery (optional)

Begins a gallery referenced by vendor ID that stores the director’s commentary video used in the iTunes Extras. This is a video-type gallery (<gallery_type>video</gallery_type>) and all gallery items within the gallery must be video: <gallery_item type="video">. The annotations below explain tags specific to video galleries.

Display Name

Name of the gallery using up to 1024 bytes. Even though the display name does not show up on any device, you should provide a meaningful name, which will help during content review. Do not include line breaks in the display name.

<eidr>10.5240/BECF-0698-09AC-43D8-B39E-N</eidr>

Video Gallery Item EIDR (optional)

The EIDR (Entertainment Identifier Registry) is a universal, unique identifier system for movie and television assets. Any level of EIDR is accepted in this field, so long it is in valid format. For more information, see http://eidr.org/about-us/.

The format of the EIDR identifier is 10.5240/XXXX-XXXX-XXXX-XXXX-XXXX-C, where:

• 10.5240 represents the standard prefix of an EIDR value

• X represents a hexadecimal digit

• C represents the check character

<locales>

 <locale name="es">

   <display_name>Comentarios del director</display_name>

 </locale>

</locales>

Locales (optional)

For each locale, supply a localized gallery display name.

Note: If you do not provide localized <display_name> tags, the display name supplied in the default locale (as specified with the <language> tag) will be used. For example, if the default locale is English and if you do not provide French localizations, a user who has set French as the preferred language will see non-localized tags in English.

<gallery_items>

 <gallery_item type="video">

  <vendor_id>CLOUDY_MEATBALLS2_DIRECTOR_COMMENTARY</vendor_id>

  <display_name>Director Commentary</display_name>

Video Gallery Item Vendor ID, Display Name and Caption (see Note)

The gallery item tag specifies the type of item. (In this example, the gallery stores the director’s commentary assets, as well as a reference to the core film to be cloned. The gallery type is video, so the <gallery_item>type must be video). In addition to the asset file(s) and the vendor ID, you can deliver the display name and caption.

Vendor ID: Vendor ID of the bonus video is required

Display Name: Name of the bonus video as displayed on the screen, using up to 255 bytes. Do not include line breaks in the display name, or it will not display correctly for the customer.

Caption: An optional video description as displayed on the screen, using up to 1024 bytes.

Note: If the gallery template is either "list_on_right", "list_on_left", "list_on_left_with_grid", or "expand_in_parent", the <display_name> for each <gallery_item> is required.

<locales>

 <locale name="es">

   <display_name>Comentario director</display_name>

 </locale>

</locales>

Locales (optional)

For each locale, supply a localized gallery item display name and caption.

Note: If you do not provide localized <display_name> and <caption> tags, the display name and caption supplied in the default locale (as specified with the <language> tag) will be used. For example, if the default locale is English and if you do not provide French localizations, a user who has set French as the preferred language will see non-localized tags in English.

 <assets>

  <asset type="full">

    <data_file role="source">

     <locale name="en-US"/>

     <file_name>mainmoviesource.mov</file_name>

     <size>116834215910</size>

     <checksum type="md5">1278las239aaec0e25abb2da42dfe4b8</checksum>

     <attribute name="crop.top">0</attribute>

     <attribute name="crop.left">70</attribute>

     <attribute name="crop.bottom">0</attribute>

     <attribute name="crop.right">70</attribute>

    </data_file>

Video Gallery Item Asset(s) (required for each item in the gallery)

The gallery item block specifies the asset files for the director’s commentary, which include a reference to the source video, commentary audio asset, and a preview image that will be displayed next to the video selection. Specifying a <locale> is required.

To include a Director’s Commentary of the film as part of your Extras package, you can reuse the source video of the core film with new audio. To do this, copy the <data_file role="source"> metadata block from the core film metadata and add it to the video gallery you set up for the director’s commentary. Deliver the audio commentary track as a <data_file role="audio"> component associated with the <data_file role="source"> and include the audio file with the delivery of your package. Upon delivery, the video source will be cloned from the iTunes database and merged with the delivered audio track for the Extras package.

You can find the <data_file> metadata blocks delivered with the core film by doing a metadata lookup using the vendor ID of the film. (See iTunes Store Transporter User Guide for information on how to do a metadata lookup.) The data file metadata in the Extras delivery must exactly match the metadata from the core film delivery.

 <assets>

  <asset type="full">

    <data_file role="source.hdr">

     <attribute name="hdr.format">DolbyVision</attribute>

     <locale name="en-US"/>

     <file_name>commentaryaudioen-hdr-source.mov</file_name>

     <size>3244032000</size>

     <checksum type="md5">9df86c3e43e7b43ddeabb2ddfe4b8a42</checksum>

     <attribute name="crop.top">0</attribute>

     <attribute name="crop.left">70</attribute>

     <attribute name="crop.bottom">0</attribute>

     <attribute name="crop.right">70</attribute>

     <attribute name="image.textless_master">true</attribute>

    </data_file>

    <data_file role="mapping.hdr">

     <file_name>commentaryaudioen-hdr-source-mapping.xml</file_name>

     <size>16659</size>

     <checksum type="md5">df86c3eeabb2ddfe4b843e7b943dda42</checksum>

    </data_file>

4K HDR Video Gallery Item Asset(s (optional)

High Dynamic Range (HDR) content is supported in either Dolby Vision or HDR10 format. HDR video can display a wider range of color, brightness, and shades of darkness, which enhances details in the brightest and darkest areas in a video frame. These dynamic variations can change based on the target display and also for individual scenes within the video. To specify these variations, you must deliver additional metadata when delivering the HDR source video. See Metadata Annotations for HDR Dolby® Vision and Metadata Annotations for HDR10 in the iTunes Package Film Specification for annotations.

For delivery, the assets and files must meet certain requirements, including correlations between the SDR video and the HDR video (for example, the <locale> specified on the HDR video must match the <locale> of the SDR video). See Video Source Delivery Requirements in the iTunes Package Film Specification for the list of requirements. In addition, the HDR source assets must meet the requirements listed in Film HDR Source Profile in the iTunes Video and Audio Asset Guide.

    <data_file role="audio">

     <locale name="en-US"/>

     <file_name>commentaryaudioen.mov</file_name>

     <size>3123312</size>

     <checksum type="md5">a11915cb55de1407df5c91f4828945</checksum>

    </data_file>

  </asset>

Commentary Audio (optional)

To deliver commentary audio, use the role="audio" attribute with the <data_file> tag. Include the audio file with the delivery of your package.

  <asset type="artwork">

    <data_file role="source">

     <file_name>commentary.png</file_name>

     <size>165600</size>

     <checksum type="md5">77758f06f58512abb0244e25</checksum>

    </data_file>

  </asset>

 </assets>

Video Artwork (required)

An artwork file to use for the video with the director commentary. The image is required, as is the <file_name>, <size>, and <checksum> for the provided file.

The artwork must be:

• PNG (.png)

• RGB

• Alpha channel (optional)

• 72 dpi minimum

• 1920 width minimum or 1080 height minimum

• Aspect ratio less than 2.45 (Note that the aspect ratio of the artwork should match the aspect ratio of the video asset.)

 </gallery_item>

 </gallery_items>

</gallery>

<gallery>

 <vendor_id>CLOUDY_MEATBALLS2_MINI_MOVIES</vendor_id>

 <gallery_type>video</gallery_type>

 <display_name>Mini Movies</display_name>

Video Gallery (optional)

Begins a gallery referenced by vendor ID that stores bonus videos used in the iTunes Extras. This is a video-type gallery (<gallery_type>video</gallery_type>) and all gallery items within the gallery must be video: <gallery_item type="video">. The annotations below explain tags specific to video galleries. See the annotations above for other tags.

Display Name

Name of the gallery using up to 1024 bytes. Even though the display name does not show up on any device, you should provide a meaningful name, which will help during content review. Do not include line breaks in the display name.

<locales>

 <locale name="es">

   <display_name>Mini Películas</display_name>

 </locale>

</locales>

Locales (optional)

For each locale, supply a localized gallery display name.

Note: If you do not provide localized <display_name> tags, the display name supplied in the default locale (as specified with the <language> tag) will be used. For example, if the default locale is English and if you do not provide French localizations, a user who has set French as the preferred language will see non-localized tags in English.

<gallery_item type="video">

 <display_name>Mini Movie 1</display_name>

 <caption>Animators discuss creating and animating the oh-so-adorable foodimals.</caption>

Video Gallery Item Display Name and Caption (see Note)

The gallery item tag specifies the type of item. (In this example, the gallery stores the bonus videos and the gallery type is video, so the <gallery_item>type must be video). In addition to the asset file(s) and the vendor ID, you can deliver the display name and caption.

Display Name: Name of the bonus video as displayed on the screen, using up to 255 bytes. Do not include line breaks in the display name, or it will not display correctly for the customer.

Caption: A description of the bonus video as displayed on the screen, using up to 1024 bytes.

Note: If the gallery template is either "list_on_right", "list_on_left", "list_on_left_with_grid", or "expand_in_parent", the <display_name> for each <gallery_item> is required.

<locales>

 <locale name="es">

   <display_name>Mini película 1</display_name>

   <caption>Los animadores discuten la creación y animación de los adorables foodimals.</caption>

 </locale>

</locales>

Locales (optional)

For each locale, supply a localized gallery item display name and caption.

Note: If you do not provide localized <display_name> and <caption> tags, the display name and caption supplied in the default locale (as specified with the <language> tag) will be used. For example, if the default locale is English and if you do not provide French localizations, a user who has set French as the preferred language will see non-localized tags in English.

 <vendor_id>CLOUDY_MEATBALLS2_gummibear_extras20</vendor_id>

 <assets>

  <asset type="full">

    <data_file role="source">

     <locale name="en-US"/>

     <file_name>gummibear_extras.mov</file_name>

     <size>7389827534</size>

     <checksum type="md5">e7fa00d0356912be5610b01182a650fb</checksum>

     <attribute name="crop.top">142</attribute>

     <attribute name="crop.bottom">142</attribute>

     <attribute name="crop.left">4</attribute>

     <attribute name="crop.right">4</attribute>

    </data_file>

Video Gallery Item Asset(s) (required for each item in the gallery)

The gallery item block specifies the asset file(s) and the vendor ID. The assets include the source video, closed captions (if available), and a preview image that will be displayed next to the video selection. Specifying a <locale> is required.

In this example, the first video being delivered in this gallery is new to this release (meaning it is not a video previously delivered with a pre-5.2 version of an iTunes Extras). Since it is not a legacy video (see how to deliver legacy videos below), the video asset must be delivered with its crop dimensions.

iTunes Extras video gallery items can reuse the source video of the core film with new audio. To deliver the new audio, you can include the <data_file> metadata blocks from the core film metadata for any asset you want to include in the Extras package and omit the source files upon delivery. (See the annotation for the director’s commentary gallery above for an example.) Upon delivery, the video source will be cloned from the iTunes database and merged with the delivered audio track for the Extras package. Cloning also works for any component delivered with the film. In the previous example, you could also copy the <data_file role="captions"> metadata block to clone the existing closed captions into your Director’s Commentary.

You can find the <data_file> metadata blocks delivered with the core film by doing a metadata lookup using the vendor ID of the film. (See iTunes Store Transporter User Guide for information on how to do a metadata lookup.) The data file metadata in the Extras delivery must exactly match the metadata from the core film delivery.

The videos are displayed in the gallery in the order they appear in the XML.

    <data_file role="captions">

     <file_name>gummibear_extras.scc</file_name>

     <size>225432</size>

     <checksum type="md5">635095515f99c2d883540bafa90b3b64</checksum>

    </data_file>

Closed Captions Asset File (optional)

A data file element block must be included if the captions are delivered for the associated video. The "captions" role specifies that the delivered file is intended to be used as the closed captioning file for the iTunes Store encode. This role must be specified, or the package will be rejected.

In this block, the <file_name>, <size>, and <checksum> tags are required.

Note: iTunes Extras video assets are required to have closed captions if provided on other digital video formats.

    <data_file role="subtitles">

     <locale name="fr-FR"/>

     <file_name>subtitles_fr_gummibear_extras.itt</file_name>

     <size>88474</size>

     <checksum type="md5">99c2d86355f8354009551bafb3b64a90</checksum>

    </data_file>

Localized Subtitles (optional)

Subtitles are delivered as a role for the full asset. The files must be in the iTT file format with the extension .itt. See “iTunes Timed Text Profile” in the iTunes Package Film Specification for information on the iTT file format.

The <locale> identifies the language in which the subtitles appear. The locale indicates both the language and the optional location where the language is spoken.

See “Language Codes” in the iTunes Package Film Specification for more details.

In this block, the <locale>, <file_name>, <size>, and <checksum> tags are required.

    <data_file role="audio.7_1">

     <locale name="en-US"/>

     <file_name>71-audio_gummibear_extras.mov</file_name>

     <size>8730177839</size>

     <checksum type="md5">a765a9fc88ac893ead51366fbeb04d82</checksum>

     <attribute name="audio.surround.force_5_1_downmix">false</attribute>

    </data_file>

7.1 Surround Audio (optional)

To deliver Dolby Digital Plus audio, use the role="audio.7_1" attribute with the <data_file> tag. The 7.1 surround audio is optional and is delivered as a role for the full asset.

Note: The video source can only contain 2.0 stereo and an optional 5.1 surround audio; 7.1 surround audio cannot be combined with the source.

One 7.1 surround audio file can be provided for each desired language (and region). The <locale> tag is required for localized audio assets.

See the annotation directly above for information on specifying the language.

Use the "audio.surround.force_5_1_downmix" attribute indicate how to handle existing 5.1 surround audio:

• When you deliver 7.1 surround audio and a 5.1 surround audio file, you do not need to supply the "audio.surround.force_5_1_downmix" attribute; however, if you do supply it, it must be set to false.

• When you deliver 7.1 surround audio without a 5.1 surround audio file, you do not need to supply the "audio.surround.force_5_1_downmix" attribute; however, if you do supply it, it must be set to true. 5.1 surround audio will be automatically downmixed.

For details and delivery considerations, see 7.1 Surround Audio Delivery in the iTunes Package Film Specification.

    <data_file role="audio.object_based">

     <locale name="en-US"/>

     <file_name>audio_gummibear_extras_atmos.wav</file_name>

     <size>1142644642</size>

     <checksum type="md5">bc5b28a6200e5273202b7609f626fec0</checksum>

    </data_file>

Dolby Atmos Audio (optional)

To deliver Dolby Atmos audio, use the role="audio.object_based" attribute with the <data_file> tag. The Dolby Atmos audio is optional and is delivered as a role for the full asset.

Note: The video source can only contain 2.0 stereo and an optional 5.1 surround audio; Dolby Atmos audio cannot be combined with the source.

The <locale> tag is required and must match the locale of the full source video. If they do not match, delivery will fail.

For audio file requirements, see Dolby Atmos Audio Source Asset Requirements.

    <data_file role="audio">

     <locale name="fr-FR"/>

     <file_name>audio_fr_gummibear_extras.mov</file_name>

     <size>4916659</size>

     <checksum type="md5">9df86c3e43e7b43ddeabb2ddfe4b8a42</checksum>

    </data_file>

  </asset>

Localized Audio (optional)

Territory and language-specific audio can be supplied using the "locale" metadata structure. If used, the language must be included to specify the language; the region where the language is spoken is optional. One audio file can be provided for each desired language (and region). The <locale> tag is required for localized audio assets.

See “Language Codes” in the iTunes Package Film Specification for more details.

In this block, the <locale>, <file_name>, <size>, and <checksum> tags are required.

Note: If a video asset contains Chinese audio, the locale values must not contain script information. For example, the locale for Mandarin audio must be cmn, not cmn-Hant or cmn-Hans; the locale for Cantonese audio must be yue, not yue-Hant.

  <asset type="artwork">

    <data_file role="source">

     <locale name="en-US"/>

     <file_name>gummi_bear.png</file_name>

     <size>2027742</size>

     <checksum type="md5">5d4267c13a11b73d022971d8a22fb24e</checksum>

    </data_file>

  </asset>

 </assets>

Video Artwork (required)

An artwork file to use for the video preview artwork. This should be a still shot from the video itself. The image is required, as is the <file_name>, <size>, and <checksum> for the provided file.

The artwork must be:

• PNG (.png)

• RGB

• Alpha channel (optional)

• 72 dpi minimum

• 1920 width minimum or 1080 height minimum

• Aspect ratio less than 2.45 (Note that the aspect ratio of the artwork should match the aspect ratio of the video asset.)

</gallery_item>

<gallery_item type="video">

 <display_name>Mini Movie 2</display_name>

 <caption>This featurette gives you an inside look at a few of his hiding spots.</caption>

 <!-- Localizations go here -->

 <vendor_id>CLOUDY_MEATBALLS2_supermanny_extras20</vendor_id>

 <legacy_video vendor_id="CLOUDY_MEATBALLS2_ITUNES_EXTRAS_supermanny"/>

 <assets>

  <asset type="artwork">

    <data_file>

     <file_name>super_manny.png</file_name>

     <size>1262156</size>

     <checksum type="md5">b11cf3520fb349c5b90f16fc37baa4ba</checksum>

    </data_file>

  </asset>

 </assets>

</gallery_item>

Legacy Video Gallery Item (optional)

If a video has been previously delivered with an iTunes Extras using a pre-5.2 specification, you can refer to it by vendor ID instead of re-uploading an identical video. Use the <legacy_video> tag to supply the vendor ID. Note that the vendor ID supplied with this tag:

<vendor_id>CLOUDY_MEATBALLS2_supermanny_extras20</vendor_id>

is the vendor ID of this bonus video in this 5.2 version of the iTunes Extras, not the vendor ID of the legacy video.

Notes:

• When using a legacy video, the only asset that can be delivered within the <assets> block is artwork.

• This <legacy_video> tag works only once per <gallery_item>, for initial creation of that gallery item, and must be removed for subsequent update deliveries.

<gallery>

 <vendor_id>CLOUDY_MEATBALLS2_SKETCHES</vendor_id>

 <gallery_type>generic</gallery_type>

Image Gallery (optional )

Begins a single gallery referenced by vendor ID. This is a generic type gallery, which is used for photos and still images, and all gallery items within the gallery must be images: <gallery_item type="image">. The gallery is referenced elsewhere in the XML by vendor ID using the <gallery_link> tag. The annotations below explain tags specific to generic-type galleries. See the annotations above for other tags.

<display_name>Foodimal Sketches</display_name>

Image Gallery Display Name (required)

Name of the gallery using up to 1024 bytes. Even though the display name does not show up on any device, you should provide a meaningful name, which will help during content review. Do not include line breaks in the display name.

<locales>

 <locale name="es">

   <display_name>Bosquejos de Foodimals</display_name>

 </locale>

</locales>

Locales (optional)

For each locale, supply a localized gallery display name.

Note: If you do not provide localized <display_name> tags, the display name supplied in the default locale (as specified with the <language> tag) will be used. For example, if the default locale is English and if you do not provide French localizations, a user who has set French as the preferred language will see non-localized tags in English.

<item_display_duration_seconds>7.5</item_display_duration_seconds>

Gallery Item Display Duration (optional)

Specifies how many seconds to display each item before transitioning to next. If you do not supply the tag, the default value is 6 seconds.

For a generic gallery, the <item_display_duration_seconds> value specifies the time each image is displayed when Slideshow is selected. If Slideshow is not selected, the value supplied has no effect. Note that for the Slideshow button to be displayed, the <show_play_all> tag must be set to true on the gallery.

<gallery_repeat_limit>3</gallery_repeat_limit>

Gallery Repeat Limit (optional)

For image-type galleries, use the <gallery_repeat_limit> tag to specify how many times to loop through the slideshow, before stopping. The default setting is no limit; if you do not set a limit or if you set the value to zero, the images will display as a slideshow continuously until the user leaves the gallery.

<gallery_item type="image">

 <display_name>Foodimal Sketch 1</display_name>

 <alt_description>artist's concept line drawing in red of a pile of lumpy mashed potatoes</alt_description>

 <!-- Localizations go here -->

Image Gallery Item Display Name and Caption (see Note)

The gallery item block specifies the type of item. (In this example, the gallery stores the photos and still images and the gallery type is image, so the <gallery_item>type must be image). In addition to the asset file(s) and the vendor ID, you can deliver the display name, caption, and alt description.

Display Name: Name of the photo or image as displayed on the screen, using up to 255 bytes. Do not include line breaks in the display name, or it will not display correctly for the customer.

Caption: Description of the photo or image as displayed on the screen, using up to 1024 bytes.

Alt Description: Optional description of the gallery image so that visually-impaired customers can hear a VoiceOver that describes what is being displayed visually. This description should focus on the visual elements of the image and go into greater detail than the display name or caption provided with the image.

Note: If the gallery template is either "list_on_right", "list_on_left", "list_on_left_with_grid", or "expand_in_parent", the <display_name> for each <gallery_item> is required.

 <vendor_id>CLOUDY_MEATBALLS2_SKETCHES_1</vendor_id>

 <assets>

  <asset>

    <data_file>

     <file_name>ANI_MEALS_CONCEPTS_ckellman_01.png</file_name>

     <size>417041</size>

     <checksum type="md5">929feaa34b6025b5eb22ae2ef3ef00a7</checksum>

    </data_file>

  </asset>

 </assets>

</gallery_item>

<!-- Additional gallery items here -->

Image Gallery Item Asset(s) (required for each item in the gallery)

The gallery item block specifies the asset file(s) and the vendor ID. The assets include the image file.

The image must be:

• PNG (.png)

• RGB

• Alpha channel (optional)

• 72 dpi minimum

• 1920 width minimum or 1080 height minimum

The images are displayed in the gallery in the order they appear in the XML.

<gallery>

 <vendor_id>CLOUDY_MEATBALLS2_SEL_MINI_MOVIES</vendor_id>

 <gallery_type>selection</gallery_type>

Selection Image Gallery (optional)

Begins a single gallery referenced by vendor ID. This is a selection-type gallery, which is used to store an image to display when a node is selected. The selection image gallery is referenced elsewhere in the XML by vendor ID using the <selection_gallery_link> tag. The selection image appears on parent node page when the user selects the item. The gallery that contains the image must have the <gallery_type> of selection.

Note: Each selection image must be stored in its own gallery.

<display_name>mini_movies</display_name>

Selection Image Gallery Display Name (required)

Name of the gallery using up to 1024 bytes. Even though the display name does not show up on any device, you should provide a meaningful name, which will help during content review. Do not include line breaks in the display name.

<gallery_item type="image">

 <vendor_id>CLOUDY_MEATBALLS2_SEL_MINI_MOVIES_IMG</vendor_id>

 <assets>

  <asset>

    <data_file>

     <file_name>mini_movies.png</file_name>

     <size>2691234</size>

     <checksum type="md5">8de6b2de3c4f06daff99993356bf1df2</checksum>

    </data_file>

Selection Image Gallery Item (required)

The gallery item block specifies the vendor ID and the image asset file.

The selection image must be:

• PNG (.png)

• RGB

• Alpha channel (optional)

• 72 dpi minimum

• 1920 width minimum or 1080 height minimum

<scene_groups>

Scene Groups (optional)

Begins the block that defines groups of related scenes. In the iTunes Extras, you could supply all the scenes within one scene group, or you could group scenes together based on content, for example, all chase scenes.

To remove all scene groups, deliver an empty tag: <scene_groups/>.

Updates: When replacing or adding a scene group in a metadata update, include all scene groups (not just the one(s) being replaced or added); otherwise the scene groups not included will be removed. To intentionally remove a scene group, submit a metadata update and include all the scene groups, omitting the scene group(s) you want to remove. If there are no changes to the scene group(s), you can omit the <scene_groups> block.

<timecode_format>24/999 1000/nonDrop</timecode_format>

Timecode format (required)

Defines the timecode format in which the start and end times of the scenes are expressed. For each scene, use the <media_reference> tag to specify the start time and end time of a scene as taken from the core video.

The format can be qt_text or one of the SMPTE formats illustrated in the “Timecode Formats” appendix of the iTunes Package Film Specification.

Important: The frame modes (for example, nonDrop and dropNTSC) are case-sensitive.

<scene_group>

Scene Group (required within a <scene_groups>)

Begins a group of related scenes. A scene group is a collection of <scene_link>s around a similar theme. Each <scene_group> must contain at least one <scene_link>.

 <vendor_id>CLOUDY_MEATBALLS2_INVENTOR</vendor_id>

Scene Group Vendor ID (required, 1-100 bytes, see restrictions)

The permanent value that uniquely identifies this scene group in this package and among any scene groups ever submitted by this provider on any iTunes Extras.

Restrictions: The vendor identifier can only contain alphanumeric characters and underscore marks; it cannot contain spaces, dashes, ampersands, other punctuation, or symbols. The vendor identifier is case-sensitive and must not start with an underscore.

<title>The Inventor</title>

Scene Group Title (required)

The title of the scene group using up to 512 bytes.

Note: Do not include line breaks in the scene group title, or it will not display correctly for the customer.

<locales>

 <locale name="es">

   <title>El inventor</title>

 </locale>

</locales>

Locales (optional)

For each locale, supply a localized title of the scene group. The <title> is required if delivering locales.

 <scene_links>

Scene Group Scene Links (required)

Begins the scene links block that references a piece of content using its assigned <vendor_id>. The scene links point to the scenes (as specified in the <scenes> block) that belong to the scene group. The scenes show up within the scene group in the order the <scene_link> tags are delivered in the XML.

 <scene_link key_scene="true" vendor_id="CLOUDY_MEATBALLS2_A_GREAT_INVENTOR"/>

Scene Group Scene Link (required for each item in the Scene Group)

References a scene by Vendor ID. Note that a specific scene can be linked to by more than one scene group.

Use the key_scene attribute to indicate which scene to use for the key image for the scene group. Allowed values are true or false. The key image is displayed on the scene group selection screen. One key scene is required and only one scene per scene group can be the key scene.

    </scene_link>

    <!-- Additional <scene_link> tags here -->

   </scene_links>

  </scene_group>

</scene_groups>

 <scenes>

Scenes (required if using the “scenes” navigation node)

Begins the scenes block, which defines the content used for the scene groups.

Note: The <scenes> block is not equivalent to the chapters in the core video (where one scene begins where the other scene left off); they are hand-picked groups of scenes around a theme or topic.

Updates: When replacing or adding a <scenes> block in a metadata update, include all scenes (not just the one(s) being replaced or added); otherwise the scenes not included will be removed. To intentionally remove a scene, submit a metadata update and include all the scenes, omitting the scene you want to remove. If there are no changes to the <scenes> block, you can omit it.

 <scene>

Scene (required)

Begins the scene block, which identifies one of the scenes in the scene group. Each scene is referenced by vendor ID and identified by timecodes that refer to the core video.

 <media_reference start="00:00:29:09" end="00:01:53:05"/>

Scene Media Reference (required)

Identifies the timecode from the core video to indicate the start and end times of the scene. Both the start and end attributes are required. The format must match <timecode_format> as indicated in the <scene_groups> tag annotation. The end time must be later than the start time and cannot go beyond the end of the core video.

 <vendor_id>CLOUDY_MEATBALLS2_A_GREAT_INVENTOR</vendor_id>

Scene Vendor ID (required, 1-100 bytes, see restrictions)

The permanent value that uniquely identifies this scene in this package and among any scenes ever submitted by this provider on any iTunes Extras.

Restrictions: The vendor identifier can only contain alphanumeric characters and underscore marks; it cannot contain spaces, dashes, ampersands, other punctuation, or symbols. The vendor identifier is case-sensitive and must not start with an underscore.

 <title>A Great Inventor</title>

Scene Title (required)

The title of the scene using up to 512 bytes.

Note: Do not include line breaks in the scene title, or it will not display correctly for the customer.

 <description>Flint recalls wanting to be an inventor from an early age.</description>

Scene Description (optional)

The description of the scene using up to 4000 bytes.

 <alt_description>Flint watches a TV that features his hero who inspired him to invent things: a red-bearded scientist wearing square, green glasses and a white lab coat. The scientist speaks from his wood-paneled library about his first invention: a food bar. Next he appears in a science lab where they have produced an even better bar. The scientist stands on a green hill surrounded by children and he encourages all young future scientists to try to change the world.</alt_description>

Alternative Scene Description (optional)

Optional description of the scene so that visually-impaired customers can hear a VoiceOver that describes what is being displayed visually. This description should focus on the visual elements of the scene and go into greater detail than the title or description provided with the scene. The alternative scene description can be localized.

<locales>

 <locale name="es">

   <title>Un Gran Inventor</title>

   <description>Flint recuerda queriendo ser un inventor de una edad temprana.</description>

 </locale>

</locales>

Locales (optional)

For each locale, supply a localized title and description of the scene. If delivering locales, the <title> is required. Note that you can deliver a localized <alt_description>.

 <assets>

  <asset type="artwork">

    <data_file>

     <file_name>8451597_s01_00_01_22_03.png</file_name>

     <size>2576778</size>

     <checksum type="md5">e8a8e9006f512c946b3d7dda9c848513</checksum>

    </data_file>

  </asset>

 </assets>

Scene Artwork (required)

An artwork file to use for the preview image is required, as is the <file_name>, <size>, and <checksum> for the provided file. The type value must be "artwork". When updating, you can omit the <assets> block.

The artwork must be:

• PNG (.png)

• RGB

• Alpha channel (optional)

• 72 dpi minimum

• 1920 width minimum or 1080 height minimum

• Aspect ratio less than 2.45 (Note that the aspect ratio of the artwork should match the aspect ratio of the video asset.)

LOCALES <locales>

To change or add:

Include all locales (not just the one(s) being changed or added) and all the required tags.

To remove a locale:

Include all the locales, omitting the locale(s) you want to remove.

SCENE GROUPS <scene_groups>

If there are no changes to the scene group(s), you can omit the <scene_groups> block.

To change or add:

Include all scene groups (not just the one(s) being changed or added).

To remove a scene group:

Include all the scene groups, omitting the scene group(s) you want to remove.

To remove all scene groups:

Send an empty tag: <scene_groups/>

SCENES <scenes>

If there are no changes to the <scenes> block, you can omit it.

To change or add:

Include all scenes (not just the scene(s) being changed or added); otherwise the scenes not included will be removed.

To remove a scene:

Include all the scenes, omitting the scene you want to remove.

NAVIGATION NODES <navnodes>

If you’re not making any changes to any children nodes of a root node (keeping the menu structure as-is), leave out the entire <navnodes> block.

To change or add:

Include all navigation nodes (not just the one(s) being changed or added); otherwise the navigation nodes not included will be removed.

To remove a navigation node:

Deliver the entire <navnodes> block, omitting the <navnode>(s) you want to remove.

To remove all navigation nodes:

Send an empty tag: <navnodes/>

GALLERIES <galleries>

If you’re not making any changes to any galleries, you can leave out the entire <galleries> block.

To remove all galleries:

Submit an empty tag: <galleries/>.

Note: If you later add new galleries, the galleries and their content must use different vendor IDs than the ones you removed previously.

GALLERY <gallery>

To change gallery metadata or add a gallery:

Submit a <galleries> block and include only the <gallery>(s) being changed or added. If you omit a gallery from a <galleries> block that was previously delivered, that gallery is retained.

To remove a gallery:

To remove a gallery, use <gallery remove="true"> and supply the <vendor_id>. For example:

<gallery remove="true">

 <vendor_id>CLOUDY_MEATBALLS2_MINIMOVIES_BG</vendor_id>

</gallery>

GALLERY ITEMS <gallery_items>

If you’re not making any changes to any gallery items, leave out the entire <gallery_items> block.

When you submit a <gallery_items> block, deliver all the gallery items you want to keep; omitting a gallery item from a <gallery_items> block deletes that item.

See the next row for specifics on removing, adding, or moving gallery items.

GALLERY ITEM <gallery_item>

Gallery items, including videos and images, can be removed, added, or moved. (To replace a gallery item, see Gallery Item Asset-Only Update Examples.)

To remove an image or video:

To remove a gallery item, omit that item from the <gallery_items> block when doing a metadata update.

To move an image or video to another gallery:

First, remove the image or video from the <gallery_items> block. Then, do another metadata update to move the removed image or video to another <gallery_items> block. Important: Even though you are moving the same image or video file, it must have a new vendor ID when you place it into the new <gallery_items> block.

June 28, 2018 - Version 5.2.9

Added 4K HDR video. Changed minimum sizes for background images. Clarified titles.

August 9, 2017 - Version 5.2.7

The <description> tag can now be used at the <rootnode> level. Clarified crop dimensions.

September 13, 2016 - Version 5.2.6

Video can be delivered as a background item for the Main Menu for play on Apple TV. Added an optional tag (<eidr>) to support EIDR (Entertainment Identifier Registry). Clarified audio requirements. Changes to commentary audio.

June 22, 2016 - Version 5.2.5

Added delivery of director’s commentary to the XML example. Updated screenshots. Minor corrections.

January 26, 2016 - Version 5.2.4

Added information on reusing source files from the core feature film.

October 21, 2015 - Version 5.2.3

Added a role attribute on the <data_file> tag and a name attribute on the <attribute> tag for Dolby Digital Plus audio. Added a new tag: <alt_description>. Corrected artwork.

March 17, 2015 - Version 5.2.2

Added an optional <release_date> tag. The role attribute on the <data_file> tag for the full source video is required. Clarified updating <locales>. Added examples for subtitles and alternate audio.

August 12, 2014 - Version 5.2.1

Added delivery of menu background image assets and the Play label specific to iOS devices.

July 9, 2014 - Version 5.2

First release of this specification.