Tests don't always set `daptm:represents`

[nigelmegitt]

Some of the test stimuli don't have the expected result because they don't specify daptm:represents.

Valid tests that are in fact invalid because of this:

• dapt-valid-originTimecode
• dapt-valid-descType-extension-value
• dapt-valid-descType-no-descType
• dapt-valid-descType-registry-value
• dapt-valid-onScreen
• dapt-valid-scriptEventMapping
• dapt-valid-serialization

Similarly many (most?) of the invalid tests are invalidated due to the same omission, which can mask whether or not they are failing validation for the intended reason.

Fix is to set daptm:represents so that the computed value meets the requirements of §4.7 Represents.

[css-meeting-bot]

The Timed Text Working Group just discussed Tests don't always set daptm:represents w3c/dapt-tests#41, and agreed to the following:

• SUMMARY: @nigelmegitt to propose a fix for the affected tests

The full IRC log of that discussion

<nigel> Subtopic: Tests don't always set daptm:represents #41
<nigel> github: https://github.com//issues/41
<nigel> Nigel: I found a load of valid tests that are not valid because of constraints around daptm:represents
<nigel> .. and it's also an issue with invalid files where you might get them showing as invalid for the wrong reason.
<nigel> .. So firstly I wanted to warn everyone, in case you're using these tests,
<nigel> .. and secondly, I'll propose a fix.
<nigel> SUMMARY: @nigelmegitt to propose a fix for the affected tests