- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This manuscript presents ITERAFIGURE, a system that treats a persistent object graph as the product of scientific-figure generation and as the authoritative state for later revision. Generation is organized as a Plan–Compose–Ground–Verify pipeline; editing is restricted to scope-guarded atomic operations over stable object IDs. The manuscript reports first-pass generation, single-turn editing, ten-step revision, human evaluation, and ablations.
Critical strengths
-
The problem is well motivated. Local edits to generated figures often disturb already-verified content, and the paper correctly identifies the gap between “editable” files and enforceable local editing.
-
The architecture is described in considerable implementation detail, including commit semantics, validation channels, and deterministic inspectors.
-
The blinded human study and the reporting of strict pass rates, preservation, and residual defects are appreciated.
Critical weaknesses
-
The core reason for rejection:The main contribution appears to lie in the generation workflow and interaction mechanism rather than in a new learning method or generalizable algorithmic insight, which raises questions about ICLR fit. Besides, the proposed “unified representation” appears very close to existing mxGraph XML. It is unclear whether the formulation in Eq. (1) is a novel abstraction or a reverse-engineering of mxGraph XML. If the latter, the representation itself should not be claimed as a core contribution.
-
Alternative representation is not justified. The paper adopts draw.io mxGraph XML but does not justify this choice against SVG, which is more widely used, highly expressive, and plausibly well suited to LLM generation. The authors should explain why mxGraph XML is preferable to SVG, considering dimensions such as expressiveness, editability, ecosystem support, and model-generation reliability. As written, mxGraph XML appears convenient rather than demonstrably superior. A technical argument and, ideally, a controlled comparison would be expected.
-
The manuscript’s coverage of related work on natural-language chart editing and generative editing interfaces appears incomplete; relevant efforts such as DynaVis [1], DataWink [2], ChartEdit [3], and ChartM3 [4] are not discussed. The authors should discuss the novelty of ITERAFIGURE relative to related figure-editing work.
Reference
[1] Vaithilingam P, Glassman E L, Inala J P, et al. Dynavis: Dynamically synthesized ui widgets for visualization editing[C]//Proceedings of the 2024 CHI Conference on Human Factors in Computing Systems. 2024: 1-17.
[2] Xie L, Lin Y, Liu C, et al. DataWink: Reusing and adapting SVG-based visualization examples with large multimodal models[J]. IEEE Transactions on Visualization and Computer Graphics, 2025.
[3] Zhao X, Liu X, Haoyue Y, et al. Chartedit: How far are mllms from automating chart analysis? evaluating mllms’ capability via chart editing[C]//Findings of the Association for Computational Linguistics: ACL 2025. 2025: 3616-3630.
[4] Yang D, Zhang L, Yue Z, et al. Chartm3: Benchmarking chart editing with multimodal instructions[C]//Proceedings of the 33rd ACM International Conference on Multimedia. 2025: 5001-5009.
Questions for authors
No Questions
4 comments
We thank the reviewer for the remaining weaknesses and answer them below.
W2: Why mxGraph rather than SVG?
"The authors should explain why mxGraph XML is preferable to SVG, considering dimensions such as expressiveness, editability, ecosystem support, and model-generation reliability."
"As written, mxGraph XML appears convenient rather than demonstrably superior. A technical argument and, ideally, a controlled comparison would be expected."
This paper targets method and architecture diagrams made of modules, connectors, and hierarchies. We do not claim that mxGraph is superior to SVG: as Section 3.3 states, adopting mxGraph is an editor-integration choice, not a new format or a controlled format comparison. mxGraph directly exposes hierarchy and connector endpoints for our deterministic checker, stable IDs map onto canvas selections, and draw.io supports mature manual continuation and export, which provides substantial convenience for human–AI collaborative editing. SVG has a broader rendering ecosystem and can likewise be configured with stable IDs and graph semantics; we did not run a controlled comparison and make no claim about model-generation reliability. The Guard requires only an addressable representation whose commit path validates a batch before applying it (Section 6, Conclusion), so the contribution does not lie in the format itself. A controlled study that holds the editor, prompts, and checker fixed while varying only the serialization is left to future work. We have added the corresponding discussion to the paper and give the full four-dimension argument in Appendix J.5.
W3: How does IteraFigure differ from DynaVis, DataWink, ChartEdit, and ChartM$^3$?
"The manuscript’s coverage of related work on natural-language chart editing and generative editing interfaces appears incomplete; relevant efforts such as DynaVis [1], DataWink [2], ChartEdit [3], and ChartM3 [4] are not discussed."
"The authors should discuss the novelty of ITERAFIGURE relative to related figure-editing work."
The four studies have been added to the related work. DynaVis combines natural language with persistent interactive widgets; DataWink reuses and adapts SVG-based visualization examples; ChartEdit and ChartM$^3$ provide chart-editing evaluations, and the latter also uses multimodal instructions to express the target. These works mainly address data visualization and data encoding, whereas IteraFigure targets method and architecture diagrams, with an emphasis on persistent object state, multi-round object-level modification, explicit selections, and pre-submission checks. The revised related-work discussion is organized around this difference in task and mechanism.
Response to the rebuttal
Thank you for your response. I appreciate the authors’ clarifications on my concerns, particularly regarding the contribution and novelty. Accordingly, I will raise my score.
Thank you for taking the time to carefully review our response and the additional clarifications, and for raising your score. We are glad that our discussion of the contribution and novelty addressed your concerns, and we sincerely appreciate your reconsideration and support.
Thank you for your review and constructive feedback. We respond to your weaknesses below.
W1: What is the technical contribution, and how does Eq. (1) relate to mxGraph?
Our contribution is to let a language model continuously generate, modify, and verify scientific figures around one persistent object state. Planning, figure composition, content validation, and visual revision act on the same object graph; natural language and an optional selection are turned into checkable object-level operations, and failure reasons are returned to the model for revision. Eq. (1) is not a new representation or abstraction: it states the fields that an mxGraph cell already carries—label ℓ, style attributes σ, geometry γ, hierarchical parent π, and connector endpoints ϵ—as a state tuple κ(c,G)=(ℓ(c),σ(c),γ(c),π(c),ϵ(c)), on which the operations and audits are defined. mxGraph is the existing editor format that carries this workflow. We therefore do not claim the representation itself as a core contribution; the contribution is the workflow that generates, modifies, and verifies one persistent object state.
On ICLR fit, this work studies how model-driven systems perform constrained, verifiable iterative modifications on persistent structured artifacts. In this problem area, one of our important baselines, AutoFigure, was published at ICLR 2026, in the same subject area we selected, namely applications to computer vision, audio, language, and other modalities. In addition, ScImage (ICLR 2025) and AutomaTikZ (ICLR 2024) are papers accepted at the conference in earlier years, showing that the problem studied here has been one of the topics ICLR has consistently covered over the years.
We agree that the contribution is methodological rather than a new learning method, and we do not present it as one; it belongs to verifier-gated generation, where a deterministic check admits a model proposal before it changes the state. The generalizable part is the mechanism condition, not the backbone: when an artifact is addressable and the commit path can validate a whole operation batch before applying it, the user's intended scope, the read-only context supplied to the model, and the writable scope can be kept separate, so non-target changes become detectable and rejectable before publication. This condition is not specific to mxGraph XML (Section 3.3 and Appendix J.5). The paper measures it rather than asserting it: matched-input single-turn editing, the strict ten-step audit, and the Selected-scope Guard ablation comparing the pathway with and without the pre-submission check under a fixed selected-scope interface (Sections 4.4–4.5, Appendices D.2 and E). The research value therefore lies in characterizing and measuring the controllability of model edits on structured artifacts—which non-target changes still occur, what a checkable commit boundary prevents, and what it costs—within a problem area ICLR has consistently covered. We have revised the contribution statements in the main text accordingly.