Program Information in MPD

cta-wave / dpctf-tests

Repo for DPCTF Tests. We prefer to keep the Tests separated from Test Runner

Other

1 stars 5 forks source link

Program Information in MPD #53

Closed haudiobe closed 1 year ago

haudiobe commented 3 years ago

In order to identify the CTA WAVE test asset vector properly, it is proposed to add the ProgramInformation into the test MPD.

The Program Information is currently proposed to be set as follows

The ProgramInformation element shall be present with the following information
- The Title element may be present as an instructive summary of the Test Asset.
- The Source element shall be present be set to "CTA WAVE"
- The Copyright element shall be present and shall bet set to
- The @moreInformationURL may be present and provide a link to additional information on this Test Asset, for example who produced it, etc.

Please comment on the above and also provide a proper copyright statement that is then added.

cta-source commented 3 years ago

Regarding ProgramInformation, should it include something like,

- The Mezzanine Annotations version information, to identify the mezzanine specification version for programmers seeking to work with the annotations?

louaybassbouss commented 3 years ago

@haudiobe I see two parts of this issue:

Provide ProgramInformation in the test MPD. Maybe better to raise issue in Test-Content project.
Make ProgramInformation available for the OF. We already parse the MPD while generating the tests and provide all details in tests.json. We will add a new property ProgramInformation with content from the test MPD.

jpiesing commented 3 years ago

28th September meeting Copyright information is already in the manifest. @haudiobe and @rbouqueau to discuss offline & ensure the DPCTF spec is correct.

jpiesing commented 2 years ago

@haudiobe @rbouqueau Have you checked the MPDs generated by the scripts are correct? Can we close this issue?

rbouqueau commented 2 years ago

The MPD were checked manually against the DASH-IF validator. The test-content-generation README is being updated to reflect the limitations of the current approach w.r.t. validation.

gitwjr commented 1 year ago

@rbouqueau check to see if Romain updated the readme and if that closes this issue.

rbouqueau commented 1 year ago

Yes, both the feature and the README are now ok. I'm closing this issue.

rbouqueau commented 1 year ago

PS: it seems I don't have the rights to close the issue, please someone make it for me! Thx

gitwjr commented 1 year ago

Both the features and the README are now OK.