You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The start/end attributes of ContentKeyPeriod are defined for VOD as "media time for the start/end time for the period".
However, the value is a date (xs:dateTime) and there is no instructions on how to map date values to media times.
As a result, there is no portable way to use those attributes for VOD.
I can think of three possibilities to solve this issue.
Add new dedicated attributes for VOD (e.g. startOffset/endOffset), with their own type.
Change the type and definition of start/end to be either xs:dateTime for live or xs:duration (or xs:time) for VOD.
Define an epoch to be used to map dates to VOD offsets (e.g. start of VOD asset is mapped to UNIX epoch).
IMHO, first option is the cleanest.
The text was updated successfully, but these errors were encountered:
When considering adding new elements for VOD, I think it would be good to add the content type (vod/linear) at the cpix level, as an attribute next to the contentId. There may be additional aspects that are different for vod and linear, in addition to the ContentKeyPeriod items. For example - the way to generate the keyIds and keys.
The
start
/end
attributes ofContentKeyPeriod
are defined for VOD as "media time for the start/end time for the period".However, the value is a date (
xs:dateTime
) and there is no instructions on how to map date values to media times.As a result, there is no portable way to use those attributes for VOD.
I can think of three possibilities to solve this issue.
startOffset
/endOffset
), with their own type.start
/end
to be eitherxs:dateTime
for live orxs:duration
(orxs:time
) for VOD.IMHO, first option is the cleanest.
The text was updated successfully, but these errors were encountered: