Styxis
Company
Knowledge

Docling video export: checking picture source lists before handing JSON to another team

A completed conversion is different from a reusable document. Video and document teams should share the reload contract.

Docling video export: checking picture source lists before handing JSON to another team

Having a single source attached to a document does not authorize replacing its container with a single object. When pictures and text follow different paths, text success cannot establish that pictures can be saved and reloaded. Check the list representation required by the external schema for each item kind. [1, 2, 3]

What the primary source establishes

A report describes VideoPipeline assigning one TrackSource object to a picture.source field declared as a list, producing export warnings and reload ValidationError. The text path uses append and is distinguished as unaffected by this assignment issue. [1]

The handover decision

Create a manifest separating picture and text source shapes. Reload saved JSON under its schema before handing it to further analysis. Retain item_kind, item_id, source_container_kind, and reload_status so a text-only success does not approve the picture path. [1, 3]

A reference defined before the output

In the illustrative picture, even a single source must be represented as a list containing that source. The normal container kind is list; object is the counterexample. Matching the number of logical sources does not make these external representations interchangeable. [1, 3]

The scoped Truthound check

Truthound Core 3.3.2 can check extracted source_container_kind values against the permitted shape for each item kind using InSetValidator. An adapter must extract those shapes, and Docling schema revalidation remains a separate step. This does not validate image content or transcription accuracy. [1, 2, 3]

Limits and alternative choices

Container validation does not establish video content, transcript accuracy, or the actual recording time. Add assignment validation and official document-reload tests at the conversion boundary. If a later document schema permits a single object, evaluate the shape against that version's contract. [1, 3]

Application conditions

Prepare item-level source-container shapes and reload states, retaining item kind and identity.

Alternatives

Add assignment validation and official document-reload tests at the conversion boundary.

Limitations

  • Container validation does not establish video content, transcript accuracy, or the actual recording time.

Evidence

Event checked
Subject checked
Modified