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
Some errors in the manifest file are flagged up by the schematron code, but not surfaced to the UI. This is because only failed statements are displayed, not successful statements.
Attached see an MPD in ex62.zip which does trigger the report "@MimeType shall be common between all Representations in an Adaptation Set" but that report is not shown.
The solution is to either also surface successful reports, or to rewrite all reports into asserts. Even though the former would be the smaller change, I tend to the latter which seems cleaner, stylistically. It could also be confusing to the end user to read "successful report" when in fact something is broken in the manifest.
The text was updated successfully, but these errors were encountered:
wschidol
changed the title
manifest validator suppressed firing assertions
manifest validator suppresses firing assertions/successful reports
Jul 11, 2022
Some errors in the manifest file are flagged up by the schematron code, but not surfaced to the UI. This is because only failed statements are displayed, not successful statements.
Attached see an MPD in ex62.zip which does trigger the report "@MimeType shall be common between all Representations in an Adaptation Set" but that report is not shown.
The solution is to either also surface successful reports, or to rewrite all reports into asserts. Even though the former would be the smaller change, I tend to the latter which seems cleaner, stylistically. It could also be confusing to the end user to read "successful report" when in fact something is broken in the manifest.
The text was updated successfully, but these errors were encountered: