Skip to content

Update Content Type description and scope note #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
palemieux wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Content Type description and scope note #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/content/contenttypes-cpl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
The Content Type is listed at **//ContentKind**:[^1]
The Content Type is listed at **//ContentKind**:

<CompositionPlaylist xmlns=”http://www.smpte-ra.org/schemas/429-7/2006/CPL”>
…
<ContentKind>feature</ContentKind>
…
<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.*
+_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.
Copy link
Copy Markdown
Collaborator

@SteveLLamb SteveLLamb Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator

@SteveLLamb SteveLLamb Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

@palemieux palemieux Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator

@SteveLLamb SteveLLamb Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are still usable as CTT fields.

Copy link
Copy Markdown
Contributor Author

@palemieux palemieux Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If they are usable in CTT, then the bug is with the TMS and servers and no note is necessary.