icdt-artifact-evaluationUse when preparing the "artifact" of an ICDT (International Conference on Database Theory) paper, which at a pure-theory venue is the complete-proofs full version rather than a code package — covering why ICDT has no ACM-style artifact-badging or code-artifact track, what the marked appendix and the
icdt-author-responseUse when responding to ICDT (International Conference on Database Theory) referees — principally the first-cycle Revise-and-resubmit round, where you return a corrected paper that closes each identified proof gap, plus any short author-comment phase, keeping the response anonymous and mapping every
icdt-camera-readyUse when preparing the final LIPIcs camera-ready for an accepted ICDT (International Conference on Database Theory) paper — the lipics-v2021 final document, mandatory ACM CCS concepts and keywords, author ORCIDs, de-anonymization, complete proofs and the full-version link, CC-BY licensing, and passi
icdt-experimentsUse when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked examples and counterexamples that establish separations, and, only for papers with an algorithmic contribution, a proportion
icdt-related-workUse when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and complexity, delta-first positioning against the nearest prior theorem, honest treatment of overlapping bounds, and keeping
icdt-reproducibilityUse when strengthening the verifiability of an ICDT (International Conference on Database Theory) paper — the theory-venue analogue of reproducibility — covering complete and self-contained proofs, exact models and assumptions, claim-to-proof mapping, matching upper and lower bounds, consistency bet
icdt-review-processUse when reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision (Accept / Revise / Reject) decision, anonymous review since 2024, the cross-cycle resubmission restriction, proof-correctness
icdt-submissionUse when auditing an ICDT (International Conference on Database Theory) regular-paper submission for Microsoft CMT readiness, covering the two-step abstract-then-paper deadline in the correct submission cycle, the lipics-v2021 15-page limit excluding references, the clearly-marked appendix read at t
icdt-supplementaryUse when deciding how to split an ICDT (International Conference on Database Theory) paper between the 15-page lipics-v2021 body and the clearly-marked appendix that referees read at their discretion, given that online/external appendices are not allowed and every proof needed to certify the result
icdt-topic-selectionUse when deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track, a pure-TCS venue (LICS, ICALP, STACS), or a journal (ACM TODS, LMCS, TheoretiCS), and when distinguishing ICDT from its si
icdt-workflowUse when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICD
icdt-writing-styleUse when shaping the prose of an ICDT (International Conference on Database Theory) paper — the theorem-proof structure, stating the data model and computation model precisely, leading with the result and its data-management consequence, proof-sketch-then-appendix discipline within the lipics-v2021