Better mechanism to examine "stealthy" DCP screwups (Ymagis example)

[wolfgangw]

See Ymagis' SINTELSTILL_TST_C_XX-XX_2K_20121006_YMA_OV_506fc8cf-b238-4809-a88f-7290ac120207 for a great example of a package which will play on many systems and yet is still broken, in a funny way:

Their commercial tool QuickDCP -- with the best of intentions to generate an Interop package -- generates "ASSETMAP" with a (wrong) SMPTE-AM-ish default namespace -- instead of "ASSETMAP" with a correct Interop AM default namespace. They also generate a PackingList with a wrong default namespace. And their Interop CPL is missing RatingList.

This package, examined in context, tells you a lot about the state of affairs re systems in the field, authoring systems and compliance.

Both recent Clipster versions and dcp_inspect catch the errors mentioned above, if a bit tight-lipped in the case of the former.

A better inspection mechanism is required to give more useful feedback about this almost-but-not-quite (or stealthy, if you will) class of package errors.