Key takeaway
Evaluate the intended composition against the named receiver’s available track resources. The same supplemental can resolve for one receiver and still lack a required resource for another.
The received folder is not the whole composition
A media delivery engineer receives an IMF supplemental with a new composition playlist and an audio asset. The picture file is absent. Calling the package corrupt immediately may be wrong: the composition can intentionally reference track files delivered earlier. Calling it complete because every received file passes an integrity check may also be wrong.
IMF User Group BP 002 distinguishes a complete package from a supplemental that omits one or more track files referenced by its composition. Its handling guidance describes resolving resource identifiers against the recipient’s existing inventory. The relevant question therefore names both the intended composition and the particular receiver.
This article follows that dependency question. It does not validate a real IMF package, execute playback or determine whether any content can be licensed. A receiver possessing a file is not, by that fact alone, entitled to every proposed use.
Resolve the same resource graph for two receivers
The hypothetical composition CPL-C references picture P1, audio A2 and text T1. The new package contains CPL-C and A2. These are symbolic aliases for the illustration, not real IMF UUIDs or filenames. Assume the stated resource references and inventory matches have already been established.
Receiver inventory I7 contains P1 but not T1. Combining its inventory with the received resources gives {P1, A2}; subtracting that set from required {P1, A2, T1} leaves missing {T1}. Receiver I8 already has P1, A2 and T1, so no referenced track resource is missing under this deliberately limited check.
The result is a precise resource request for I7, rather than a request to resend every earlier asset. For I8, it is a resolved dependency set, not an assertion that the composition has passed all package validation, decoding, timing, presentation or rights checks.
| Composition requirement | In new package? | Receiver I7 prior inventory | Receiver I8 prior inventory |
|---|---|---|---|
| Picture P1 | No | Available | Available |
| Audio A2 | Yes | Not needed from prior inventory | Available |
| Text T1 | No | Absent: request this resource | Available |
| Missing referenced track set after combination | Package alone is not the test | {T1} | Empty set for this limited check |
Make inventory matches inspectable
A package filename is not enough evidence that an earlier asset satisfies a composition reference. Retain the actual resource identifier, the inventory object it resolved to and the package or prior delivery that supplied it. If an inventory entry has disappeared or cannot be opened, record the resolution gap instead of relying on an old delivery-success flag.
The completed example treats inventory I7 as one particular snapshot. A later delivery of T1 changes the available set and can resolve the missing resource without changing CPL-C. Conversely, deleting a required earlier asset can make a previously resolvable composition incomplete for that receiver. Preserve the inventory basis when explaining a historical delivery result.
This is separate from checking received bytes against an applicable expected checksum. All bytes in the new package could match their expected values while T1 remains absent. Packing-list and asset-map checks also have their own scope. The dependency artifact supplements those checks rather than claiming to replace them.
Translate provider terminology without making it universal
Sony Pictures’ historical IMF specification v2.1 describes a Base or original version and supplemental versions that use previously supplied essence alongside new composition or essence material. That provider example helps explain why a later delivery may intentionally omit picture already held by its recipient.
However, BP 002 explicitly warns that “OV” has multiple meanings. Preserve the vocabulary and version of the particular delivery agreement. Do not rewrite every provider’s base package as a universal IMF category or assume that a label alone establishes the recipient’s inventory.
The Sony page’s publication label is 09-06-2018. The historical year and specification version can be retained without guessing the day/month order. BP 002 was published on 5 August 2021 and is best-practice material that may be updated; this article does not claim its explanatory terms prove conformance to every current SMPTE requirement.
Name the composition and the receiving inventory in the result
The final fictional delivery note says: “CPL-C requires P1, A2 and T1. With package A2 and inventory I7, missing track resources are {T1}. With the stated inventory I8, the referenced track set resolves.” It preserves exactly which dependency test was performed.
That language avoids treating intentional reuse as corruption and avoids treating a complete-looking folder as a playable composition. The next media-system checks can work from the resolved resource set, with their own evidence and acceptance decisions.