Update Content Type description and scope note#90
Open
palemieux wants to merge 1 commit into
Open
Conversation
Clarified the Content Type description and added a note about the scope attribute for ContentKind.
SteveLLamb
requested changes
Nov 17, 2025
| <CompositionPlaylist> | ||
|
|
||
| [^1]: *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.smpte–ra.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.* No newline at end of file | ||
| +_NOTE_: As specified at SMPTE ST 429-7, 6.8, the `scope` attribute of the `ContentKind` element is present and set to the value specified in the _ContentKind Scope_ column of the register, _unless_ the _ContentKind Scope_ is equal to `http://www.smpte-ra.org/schemas/429-7/2006/CPL`, in which case the `scope` attribute can be omitted. |
Collaborator
There was a problem hiding this comment.
Suggested change
| +_NOTE_: As specified at SMPTE ST 429-7, 6.8, the `scope` attribute of the `ContentKind` element is present and set to the value specified in the _ContentKind Scope_ column of the register, _unless_ the _ContentKind Scope_ is equal to `http://www.smpte-ra.org/schemas/429-7/2006/CPL`, in which case the `scope` attribute can be omitted. | |
| _NOTE_: As specified at SMPTE ST 429-7, 6.8, the `scope` attribute of the `ContentKind` element is present and set to the value specified in the _ContentKind Scope_ column of the register, _unless_ the _ContentKind Scope_ is equal to `http://www.smpte-ra.org/schemas/429-7/2006/CPL`, in which case the `scope` attribute can be omitted. | |
| _NOTE 2_: The scope `http://www.smpte-ra.org/schemas/2067-3/2013#content-kind` and its defined ContentKinds should be used with caution, as support for these Content Types are limited in DC equipment, and may cause issues and/or confusion in theatrical environments. | |
Collaborator
There was a problem hiding this comment.
This address Adam's other point, and something that hadn't been addressed. We have to advise not to use the IMF based ContentKinds, as sorting in both TMS and servers don't have wide support for these values, and often get dropped to "unknown" or not listed at all.
Contributor
Author
There was a problem hiding this comment.
We have to advise not to use the IMF based ContentKinds, as sorting in both TMS and servers don't have wide support for these values, and often get dropped to "unknown" or not listed at all.
Let's remove them from the register then.
Collaborator
There was a problem hiding this comment.
They are still usable as CTT fields.
Contributor
Author
There was a problem hiding this comment.
If they are usable in CTT, then the bug is with the TMS and servers and no note is necessary.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #89