webconf-artifact-evaluationUse when packaging datasets, models, or code for the Web Conference (WWW) Artifacts Available badge or for reviewer scrutiny, covering archival-repository choice, the light-verification bar, web-data licensing and takedown realities, anonymized artifacts during review, and what the badge does and do
webconf-author-responseUse when drafting the Web Conference (WWW) rebuttal inside its one-week window, triaging reviews from the venue's mixed systems/mining/social-science reviewer pool, answering misread-track objections, protecting anonymity, and deciding what can honestly be promised for the camera-ready versus what n
webconf-camera-readyUse when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored acknowledgements, ACM e-rights and TAPS production, ACM Open cost exposure, author registration, and the artifact-badging submission that
webconf-experimentsUse when designing or auditing the empirical section of a Web Conference (WWW) paper — matching evidence to the claim's scale, choosing datasets with provenance and freshness, blocking temporal and popularity leakage, running honest baselines from the sibling circuit, and deciding when live-platform
webconf-related-workUse when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit, handling the venue's preprint-non-citation rule, and budgeting references against the shared 12-page P
webconf-reproducibilityUse when hardening the reproducibility of a Web Conference (WWW) paper whose evidence rests on crawls, platform APIs, live systems, or user logs — covering dataset decay, temporal snapshots, seed and environment reporting, the reproducibility appendix inside the 12-page PDF, and honest claims when t
webconf-review-processUse when reasoning about how the Web Conference (WWW) evaluates papers — track-scoped double-blind review, the rebuttal-to-notification pipeline, how the ten research tracks shape reviewer expectations, main versus companion proceedings outcomes, and what authors can and cannot influence at each sta
webconf-submissionUse when auditing a Web Conference (WWW) research-tracks submission before the abstract or full-paper deadline, covering track choice among the ten research tracks, the single-PDF 8+references+appendix page arithmetic within 12 pages, EasyChair profile completeness, the author-list freeze, the 7-sub
webconf-supplementaryUse when deciding what belongs in the Web Conference (WWW) appendix versus the 8 main pages versus an external artifact, under the single-PDF 12-page ceiling where references and appendix share the tail, reviewers need not read past page 8, and no separate supplementary upload exists in the research
webconf-topic-selectionUse when deciding whether a project belongs at the Web Conference (WWW) at all, which of the ten research tracks should review it, whether the short-paper or Web4Good lane fits better, and when the work should instead route to WSDM, SIGIR, CIKM, KDD, ICWSM, WebSci, or an ML flagship.
webconf-workflowUse when planning a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the short-paper and Web4Good fallback windows inside the same edition, venue-volatility contingencies, and rerouting after rejection.
webconf-writing-styleUse when drafting or revising a Web Conference (WWW) paper's prose — building the web-native framing that answers "why is this a WWW paper" on page one, writing for a mixed computing/social-science/economics readership, compressing into 8 self-contained pages, and handling scale numbers and platform