- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
Template-Anchored Diffusion Decoding fixes field names and structural tokens in advance, allocates a bounded token span to each string value, and denoises only the value positions. The predicted spans are extracted by position and serialized into JSON. Diffusion-Aligned Visual Projection adapts the visual projector while freezing the remaining model.
The primary structured-extraction comparison uses a 50-page PDFA cohort. RippleVLM-8B improves content token-set F1 from to relative to its TADD baseline and returns records passing the JSON-plus-keys check on all 50 pages. The reported Qwen3-VL-8B Outlines baseline achieves higher content F1, , but a lower completion rate under its configured output cap. Additional experiments examine other diffusion backbones, field counts, and general VLM benchmarks.
Critical strengths
- The output contract is explicitly limited. The paper distinguishes fixed-key string objects from arbitrary JSON Schema and separates structural validity from semantic correctness (pp. 3–4).
- Unfavorable outcomes are disclosed. The manuscript reports unresolved adaptation gains on most variants, inconsistent B32 runs, and regressions on general benchmarks rather than claiming universal improvement (pp. 7–9).
- The interface is concrete. Positional value extraction and projector-only adaptation provide a reproducible design in principle, and the paper describes source mappings and arithmetic checks for its saved evaluation records.
Critical weaknesses
- Adaptation generalization is not established. Evaluation pages are sampled from the same local PDFA cache used for projector training, without an explicit page-level holdout. The authors acknowledge that evaluation pages may have been seen during training. The reported 8B gain therefore cannot be interpreted as clean held-out improvement (pp. 5 and 8).
- The structural comparison is not symmetric. TADD's returned object is constructed under predetermined keys and passed through a serializer, whereas the autoregressive baseline is evaluated on generated text. An autoregressive model that generates field values separately and uses the same serializer would also obtain the relevant structural guarantee. This essential control is missing (p. 4).
- The content metric does not evaluate structured extraction. Token-set F1 compares extracted values against full-page OCR text, ignoring word order, repetition, and field binding. Incorrectly placing body text under a title key can still receive credit. Multi-field experiments lack field-level reference values, and heading/body training targets come from heuristic text splitting (pp. 5 and 14–15).
- The efficiency comparison has several uncontrolled factors. Autoregressive decoding uses a 256-token cap, TADD allocates 96 tokens per field, and Bard-VL free generation uses a different cap. Image preprocessing and implementations also differ. Raw Outlines outputs and termination reasons are unavailable, so its low completion rate cannot be attributed reliably to a decoding limitation rather than truncation (pp. 5–6 and 14).
- The adaptation evidence is small and unstable. Only the 8B gain has a paired interval excluding zero among the reported adaptation comparisons, and that result shares the holdout problem. Two B32 baseline runs differ markedly in structural validity, with no resolved cause. A matched alternative adaptation objective is also absent (pp. 7–8).
- A numerical inconsistency remains. The abstract reports Outlines validity, while Table 1 and the results text report (pp. 1 and 6).
Questions for authors
- Can you rerun the adaptation evaluation on a strictly document-disjoint holdout and report exact overlap checks between training and evaluation data?
- What results are obtained by autoregressive per-field generation with the same field budgets, image preprocessing, and final serializer? Can you compare at matched field-level quality as well as matched latency?
- Can you evaluate against annotated field values using per-field accuracy and complete-record correctness, rather than page-level token-set overlap?
- Does DAVP outperform a matched alternative projector-training objective using the same data, trainable parameters, and compute? Which benefit is specifically attributable to the diffusion/template training arrangement?
- What caused the inconsistent B32 baseline runs, and which Outlines validity value is correct? Can you provide raw outputs, stopping reasons, and repeated-run measurements?