DCNC - Appendix #2 - Territory and Rating Introduction
The territory and rating field in the Naming Convention consists of two to six characters. The first two characters indicate the release territory. They are based on ISO 3166-1 country codes. The next 2-3 characters after a hyphen indicate the local rating, if one exists. For example, “US-13” would indicate: US territory with a feature rating of PG-13. For US trailers, “GB” indicates Green Band; “RB” indicates Red Band. “GB” indicates that the trailer has been approved for all audiences by the MPAA, but does not indicate the rating of the advertised feature. For Canadian trailers that are identical to the US version with the exception of the Rating Tag, use “CA” in the territory field and do not follow with “GB” or “RB”.
Some studios have been using the entry of “OV” for the territory to indicate “Original Version” meaning from the region of origin that first created the version. This differs from the use of “OV” in the package type that refers to a release that contains all parts of a feature opposed to a package type of “VF” which is a partial package that builds on the other packages.
The MPAA has requested that the Green Card at the head of US trailers be part of the main trailer DCP, instead of being enclosed as a separate package.
For generic international versions you may replace the Territory and Rating codes with:
INT-TD to denote International Texted
INT-TL to denote International Textless
Although “XX” is often used in the Language Field to denote “No Subtitles”, you should never use “XX” in the Ratings Field to denote “No Rating” since this may be confused with an “X” rating.
In the Composition Playlist
The Release Territory is listed at //Reel//CompositionMetadataAsset/ReleaseTerritory:
The Rating is listed at //RatingList//Rating[n]:
- Permissible values for the Release Territory are governed by the scope attribute. The value of the scope attribute informs the recipient which values can be present in ReleaseTerritory. For instance, if the default value (http://www.smpte-ra.org/schemas/429-16/2014/CPL-Metadata#scope/release-territory/UNM49) is used, then only values defined in the IETF RFC 5646 Language SubtagRegistry. Future versions of the specification (or individual parties) can define additional permissible sets of values by introducing new values for the scope attribute. If a recipient finds a scope value it does not understand, it will not know what values can be present, but should nevertheless present them to the user. In other words, whereas the choice of contents for, say FullContentTitleText, is left entirely to the author, the contents of a ReleaseTerritory instance is intended to be limited to the values permitted by the controlled vocabulary identified by the value of the scope attribute. By default, these are specified by IETF RFC 5646. RFC 5646 does not allow all the territory codes listed in appendices 2ab, nor does it allow “INT”.
- Release Territory codes should be in upper case.
- Permissible values for ratings are governed by the Agency element, which associates a unique URI with each rating system. There is no global registry for rating systems, but a reasonable alternative would be to use the MovieLabs Common Metadata Ratings, which has coverage of most rating systems.
- Note that “13”, “RB”, and “GB” are not permissible MPAA ratings. The “13” rating would map to “PG-13”. In the MovieLabs Common Metadata Ratings scheme, “RB” and “RB” can be accommodated by using the Agency URI “http://www.movielabs.com/md/ratings/US/MPAAT/1”