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
Have a <daptm:daptOriginTimecode> element present at the path /tt/head/metadata/daptm:daptOriginTimecode whose content conforms to a clock-time with a frames component, as defined in <time-expression> AND
have a ttp:frameRate attribute on the root <tt> element with a valid value as per TTML2 (as per 5.7.3 ttp:frameRate)
Expect >=1 valid test resource.
Invalid test resources:
Have two or more <daptm:daptOriginTimecode> elements present at the path /tt/head/metadata/daptm:daptOriginTimecode OR
Have a <daptm:daptOriginTimecode> element present at the path /tt/head/metadata/daptm:daptOriginTimecode with content that does not conform to a clock-time with a frames component, as defined in <time-expression> OR
Have a <daptm:daptOriginTimecode> element present at the path /tt/head/metadata/daptm:daptOriginTimecode whose content conforms to a clock-time with a frames component, as defined in <time-expression> BUT has no ttp:frameRate attribute on the root <tt> element OR
Have a <daptm:daptOriginTimecode> element present at the path /tt/head/metadata/daptm:daptOriginTimecode whose content conforms to a clock-time with a frames component, as defined in <time-expression> and has a ttp:frameRate attribute on the root <tt> element BUT the frame component value >= the number of frames per second.
Expect >= 4 invalid test resources.
Presentation semantics
There are no presentation semantics associated with this feature.
Activity
nigelmegitt commentedon Apr 24, 2025
Valid test resources:
<daptm:daptOriginTimecode>
element present at the path/tt/head/metadata/daptm:daptOriginTimecode
whose content conforms to aclock-time
with aframes
component, as defined in<time-expression>
ANDttp:frameRate
attribute on the root<tt>
element with a valid value as per TTML2 (as per 5.7.3ttp:frameRate
)Expect >=1 valid test resource.
Invalid test resources:
<daptm:daptOriginTimecode>
elements present at the path/tt/head/metadata/daptm:daptOriginTimecode
OR<daptm:daptOriginTimecode>
element present at the path/tt/head/metadata/daptm:daptOriginTimecode
with content that does not conform to aclock-time
with aframes
component, as defined in<time-expression>
OR<daptm:daptOriginTimecode>
element present at the path/tt/head/metadata/daptm:daptOriginTimecode
whose content conforms to aclock-time
with aframes
component, as defined in<time-expression>
BUT has nottp:frameRate
attribute on the root<tt>
element OR<daptm:daptOriginTimecode>
element present at the path/tt/head/metadata/daptm:daptOriginTimecode
whose content conforms to aclock-time
with aframes
component, as defined in<time-expression>
and has attp:frameRate
attribute on the root<tt>
element BUT the frame component value >= the number of frames per second.Expect >= 4 invalid test resources.
Presentation semantics
There are no presentation semantics associated with this feature.
cconcolato commentedon Jun 9, 2025
Not sure we need to test that as this is basic XML rule.
cconcolato commentedon Jun 9, 2025
Should we have an invalid test when the attribute is present on a metadata element somewhere else, like body?
nigelmegitt commentedon Jun 10, 2025
I don't think it is, remember this is an element not an attribute.
nigelmegitt commentedon Jun 10, 2025
(it's an element not an attribute)
It's not prohibited elsewhere, so it wouldn't be an invalid test, just a meaningless one.
Add tests for `#daptOriginTimecode`
#daptOriginTimecode
#22