IJCAI 25 Formatting Instructions
IJCAI 25 Formatting Instructions
Author Name
Affiliation
[email protected]
1 The IJCAI–25 Proceedings will be printed from Print manuscripts two columns to a page, in the manner in 38
2 electronic manuscripts submitted by the authors. which these instructions are printed. The exact dimensions 39
9 (Portable Document Format) files formatted for 8-1/2′′ × 11′′ • bottom margin: 1.25 ′′
46
10 paper.
• column height—first page: 6.625′′ 47
27 As detailed below, IJCAI has prepared and made available a in the preamble.2 63
28 set of LATEX macros and a Microsoft Word template for use in Additionally, it is of utmost importance to specify the let- 64
29 formatting your paper. If you are using some other word pro- ter format (corresponding to 8-1/2′′ × 11′′ ) when formatting 65
30 cessing software, please follow the format instructions given the paper. When working with dvips, for instance, one 66
31 below and ensure that your final paper looks as much like this should specify -t letter. 67
32 sample as possible.
2.3 Papers Submitted for Review vs. 68
33 2 Style and Format Camera-ready Papers 69
34 LATEX and Word style files that implement these instructions In this document, we distinguish between papers submitted 70
35 can be retrieved electronically. (See Section 9 for instructions for review (henceforth, submissions) and camera-ready ver- 71
36 on how to obtain these files.) 2
You may want to also use the package latexsym, which de-
1
https://proceedings.ijcai.org/info fines all symbols known from the old LATEX version.
72 sions, i.e., accepted papers that will be included in the con- Affiliations 124
73 ference proceedings. The present document provides infor- After all authors, start the affiliations section by using the 125
74 mation to be used by both types of papers (submissions / \affiliations command. Each affiliation must be termi- 126
75 camera-ready). There are relevant differences between the nated by a newline \\ command. Make sure that you include 127
76 two versions. Find them next. the newline after the last affiliation, too. 128
84 Submissions numeric math superscripts ${ˆi, j, . . .}$. You must use num- 136
85 The following instructions apply to submissions: bers, not symbols, because those are reserved for footnotes in 137
this section (should you need them). Check the authors defi- 138
86 • If your track requires submissions to be anonymous, nition in this example for reference. 139
87 they must be fully anonymized as discussed in the Mod-
88 ifications for Blind Review subsection below; in this Emails 140
89 case, Acknowledgements and Contribution Statement This section is optional, and can be omitted entirely if you 141
90 sections are not allowed. prefer. If you want to include e-mails, you should either in- 142
91 • If your track requires non-anonymous submissions, you clude all authors’ e-mails or just the contact author(s)’ ones. 143
92 should provide all author information at the time of Start the e-mails section with the \emails command. Af- 144
93 submission, just as for camera-ready papers (see be- ter that, write all emails you want to include separated by a 145
94 low); Acknowledgements and Contribution Statement comma and a space, following the order used for the authors 146
95 sections are allowed, but optional. (i.e., the first e-mail should correspond to the first author, the 147
second e-mail to the second author and so on). 148
96 • Submissions must include line numbers to facilitate You may “contract” consecutive e-mails on the same do- 149
97 feedback in the review process . Enable line numbers by main as shown in this example (write the users’ part within 150
98 uncommenting the command \linenumbers in the curly brackets, followed by the domain name). Only e- 151
99 preamble. mails of the exact same domain may be contracted. For 152
100 • The limit on the number of content pages is strict. All instance, you cannot contract “[email protected]” and 153
101 papers exceeding the limits will be desk rejected. “[email protected]” because the domains are differ- 154
ent. 155
102 Camera-Ready Papers
103 The following instructions apply to camera-ready papers: Modifications for Blind Review 156
104 • Authors and affiliations are mandatory. Explicit self- When submitting to a track that requires anonymous submis- 157
105 references are allowed. It is strictly forbidden to add sions, in order to make blind reviewing possible, authors must 158
106 authors not declared at submission time. omit their names, affiliations and e-mails. In place of names, 159
affiliations and e-mails, you can optionally provide the sub- 160
107 • Acknowledgements and Contribution Statement sec- mission number and/or a list of content areas. When referring 161
108 tions are allowed, but optional. to one’s own work, use the third person rather than the first 162
109 • Line numbering must be disabled. To achieve this, com- person. For example, say, “Previously, Gottlob [1992] has 163
110 ment or disable \linenumbers in the preamble. shown that. . . ”, rather than, “In our previous work [Gottlob, 164
1992], we have shown that. . . ” Try to avoid including any 165
111 • For some of the tracks, you can exceed the page limit by
information in the body of the paper or references that would 166
112 purchasing extra pages.
identify the authors or their institutions, such as acknowl- 167
113 2.4 Title and Author Information edgements. Such information can be added post-acceptance 168
to be included in the camera-ready version. Please also make 169
114 Center the title on the entire width of the page in a 14-point
sure that your paper metadata does not reveal the authors’ 170
115 bold font. The title must be capitalized using Title Case. For
identities. 171
116 non-anonymous papers, author names and affiliations should
117 appear below the title. Center author name(s) in 12-point bold 2.5 Abstract 172
118 font. On the following line(s) place the affiliations. ′′
Place the abstract at the beginning of the first column 3 from 173
119 Author Names the top of the page, unless that does not leave enough room 174
120 Each author name must be followed by: for the title and author information. Use a slightly smaller 175
121 • A newline \\ command for the last author. width than in the body of the paper. Head the abstract with 176
“Abstract” centered above the body of the abstract in a 12- 177
122 • An \And command for the second to last author. point bold font. The body of the abstract should be in the 178
123 • An \and command for the other authors. same font as the body of the paper. 179
180 The abstract should be a concise, one-paragraph summary content. Appendix sections must use letters instead of Ara- 234
181 describing the general thesis and conclusion of your paper. A bic numerals. In LATEX, you can use the \appendix com- 235
182 reader should be able to learn the purpose of the paper and mand to achieve this followed by \section{Appendix} 236
183 the reason for its importance from the abstract. The abstract for your appendix sections. 237
184 should be no more than 200 words long.
Ethical Statement 238
185 2.6 Text Ethical Statement is optional. You may include an Ethical 239
186 The main body of the text immediately follows the abstract. Statement to discuss the ethical aspects and implications of 240
187 Use 10-point type in a clear, readable font with 1-point lead- your research. The section should be titled Ethical Statement 241
188 ing (10 on 11). and be typeset like any regular section but without being num- 242
189 Indent when starting a new paragraph, except after major bered. This section may be placed on the References pages. 243
192 When necessary, headings should be used to separate major Acknowledgements 246
193 sections of your paper. (These instructions use many head- Acknowledgements are optional. In the camera-ready version 247
194 ings to demonstrate their appearance; your paper should have you may include an unnumbered acknowledgments section, 248
195 fewer headings.). All headings should be capitalized using including acknowledgments of help from colleagues, finan- 249
196 Title Case. cial support, and permission to publish. This is not allowed 250
198 Print section headings in 12-point bold type in the style shown must be in a dedicated, unnumbered section appearing after 252
199 in these instructions. Leave a blank space of approximately all regular sections but before references. This section may 253
200 10 points above and 4 points below section headings. Number be placed on the References pages. 254
203 Print subsection headings in 11-point bold type. Leave a to typeset the acknowledgements section in LATEX. 257
204 blank space of approximately 8 points above and 3 points be-
205 low subsection headings. Number subsections with the sec- Contribution Statement 258
206 tion number and the subsection number (in Arabic numerals) Contribution Statement is optional. In the camera-ready ver- 259
207 separated by a period. sion you may include an unnumbered Contribution Statement 260
section, explicitly describing the contribution of each of the 261
208 Subsubsection Headings co-authors to the paper. This is not allowed in the anonymous 262
209 Print subsubsection headings in 10-point bold type. Leave a submission. If present, Contribution Statement must be in 263
210 blank space of approximately 6 points above subsubsection a dedicated, unnumbered section appearing after all regular 264
211 headings. Do not number subsubsections. sections but before references. This section may be placed on 265
212 Titled paragraphs. You should use titled paragraphs if and the References pages. 266
213 only if the title covers exactly one paragraph. Such para- Use 267
214 graphs should be separated from the preceding content by at
\section*{Contribution Statement} 268
215 least 3pt, and no more than 6pt. The title should be in 10pt
216 bold font and to end with a period. After that, a 1em horizon- to typeset the Contribution Statement section in LATEX. 269
217 tal space should follow the title before the paragraph’s text.
218 In LATEX titled paragraphs should be typeset using References 270
220 2.8 Special Sections sample list of references is given at the end of these instruc- 273
tions. Use a consistent format for references. The reference 274
221 Appendices
list should not include publicly unavailable work. 275
222 You may move some of the contents of the paper into one
223 or more appendices that appear after the main content, but Order of Sections 276
224 before references. These appendices count towards the page Sections should be arranged in the following order: 277
225 limit and are distinct from the supplementary material that
226 can be submitted separately through CMT. Such appendices 1. Main content sections (numbered) 278
227 are useful if you would like to include highly technical mate- 2. Appendices (optional, numbered using capital letters) 279
228 rial (such as a lengthy calculation) that will disrupt the flow of
229 the paper. They can be included both in papers submitted for 3. Ethical statement (optional, unnumbered) 280
230 review and in camera-ready versions; in the latter case, they 4. Acknowledgements (optional, unnumbered) 281
231 will be included in the proceedings (whereas the supplemen-
232 tary materials will not be included in the proceedings). Ap- 5. Contribution statement (optional, unnumbered) 282
233 pendices are optional. Appendices must appear after the main 6. References (required, unnumbered) 283
284 2.9 Citations Scenario δ Runtime
Paris 0.1s 13.65ms
285 Citations within the text should include the author’s last name
Paris 0.2s 0.01ms
286 and the year of publication, for example [Gottlob, 1992]. Ap-
New York 0.1s 92.50ms
287 pend lowercase letters to the year in cases of ambiguity. Treat
Singapore 0.1s 33.33ms
288 multiple authors as in the following examples: [Abelson et al.,
Singapore 0.2s 23.01ms
289 1985] or [Baumgartner et al., 2001] (for more than two au-
290 thors) and [Brachman and Schmolze, 1985] (for two authors). Table 1: Latex default table
291 If the author portion of a citation is obvious, omit it, e.g.,
292 Nebel [2000]. Collapse multiple citations as follows: [Gott-
293 lob et al., 2002; Levesque, 1984a]. Scenario δ (s) Runtime (ms)
Paris 0.1 13.65
294 2.10 Footnotes 0.2 0.01
295 Place footnotes at the bottom of the page in a 9-point font. New York 0.1 92.50
296 Refer to them with superscript numbers.3 Separate them from Singapore 0.1 33.33
297 the text by a short line.4 Avoid footnotes as much as possible; 0.2 23.01
298 they interrupt the flow of the text.
Table 2: Booktabs table
299 3 Illustrations
300 Place all illustrations (figures, drawings, tables, and pho- 2. Numeric columns are right-aligned, making it easier to 335
301 tographs) throughout the paper at the places where they are compare the numbers. Make sure to also right-align the 336
302 first discussed, rather than at the end of the paper. corresponding headers, and to use the same precision for 337
303 They should be floated to the top (preferred) or bottom of all numbers. 338
304 the page, unless they are an integral part of your narrative 3. We avoid unnecessary repetition, both between lines (no 339
305 flow. When placed at the bottom or top of a page, illustra- need to repeat the scenario name in this case) as well as 340
306 tions may run across both columns, but not when they appear in the content (units can be shown in the column header). 341
307 inline.
308 Illustrations must be rendered electronically or scanned 5 Formulas 342
309 and placed directly in your document. They should be IJCAI’s two-column format makes it difficult to typeset long 343
310 cropped outside LATEX, otherwise portions of the image could formulas. A usual temptation is to reduce the size of the for- 344
311 reappear during the post-processing of your paper. When pos- mula by using the small or tiny sizes. This doesn’t work 345
312 sible, generate your illustrations in a vector format. When correctly with the current LATEX versions, breaking the line 346
313 using bitmaps, please use 300dpi resolution at least. All il- spacing of the preceding paragraphs and title, as well as the 347
314 lustrations should be understandable when printed in black equation number sizes. The following equation demonstrates 348
315 and white, albeit you can use colors to enhance them. Line the effects (notice that this entire paragraph looks badly for- 349
316 weights should be 1/2-point or thicker. Avoid screens and matted, and the line numbers no longer match the text): 350
321 bers and captions under illustrations. Leave a margin of 1/4- strongly recommend authors to split formulas in multiple 352
322 inch around the area covered by the illustration and caption. lines when they don’t fit in a single line. This is the easi- 353
323 Use 9-point type for captions, labels, and other text in illustra- est approach to typeset those formulas and provides the most 354
324 tions. Captions should always appear below the illustration. readable output 355
n X
Y n n X
Y n n X
Y n n X
Y n
325 4 Tables x= ji + ij + ji + ij +
i=1 j=1 i=1 j=1 i=1 j=1 i=1 j=1
326 Tables are treated as illustrations containing data. Therefore,
n X n
327 they should also appear floated to the top (preferably) or bot- Y
328 tom of the page, and with the captions below them. + ji . (2)
i=1 j=1
329 If you are using LATEX, you should use the booktabs
330 package, because it produces tables that are better than the If a line is just slightly longer than the column width, you 356
331 standard ones. Compare Tables 1 and 2. The latter is clearly may use the resizebox environment on that equation. The 357
332 more readable for three reasons: result looks better and doesn’t interfere with the paragraph’s 358
333 1. The styling is better thanks to using the booktabs line spacing: 359
371 Examples, definitions, theorems, corollaries and similar must illustrations, they should appear floated to the top (preferably) 408
372 be written in their own paragraph. The paragraph must be or bottom of the page. However, their caption should appear 409
373 separated by at least 2pt and no more than 5pt from the pre- in the header, left-justified and enclosed between horizontal 410
374 ceding and succeeding paragraphs. They must begin with lines, as shown in Algorithm 1. The algorithm body should 411
375 the kind of item written in 10pt bold font followed by their be terminated with another horizontal line. It is up to the 412
376 number (e.g.: Theorem 1), optionally followed by a ti- authors to decide whether to show line numbers or not, how 413
377 tle/summary between parentheses in non-bold font and ended to format comments, etc. 414
378 with a period (in bold). After that the main body of the item In LATEX algorithms may be typeset using the algorithm 415
379 follows, written in 10 pt italics font (see below for examples). and algorithmic packages, but you can also use one of 416
380 In LATEX we strongly recommend that you define envi- the many other packages for the task. 417
387 Example 1 (How to write an example). Examples should be and the BibTEX files are named.bst and ijcai25.bib. 423
388 written using the example environment defined in this tem- The LATEX style file is for version 2e of LATEX, and the BibTEX 424
389 plate. style file is for version 0.99c of BibTEX (not version 0.98i). . 425
The Microsoft Word style file consists of a single file, 426
390 Theorem 1. This is an example of an untitled theorem. ijcai25.docx. 427
391 You may also include a title or description using these en- These Microsoft Word and LATEX files contain the source of 428
392 vironments as shown in the following theorem. the present document and may serve as a formatting sample. 429
Further information on using these styles for the prepara- 430
393 Theorem 2 (A titled theorem). This is an example of a titled tion of papers for IJCAI–25 can be obtained by contacting 431
394 theorem. [email protected]. 432
396 Proofs must be written in their own paragraph(s) separated by There are no ethical issues. 434
397 at least 2pt and no more than 5pt from the preceding and suc-
398 ceeding paragraphs. Proof paragraphs should start with the Acknowledgments 435
399 keyword “Proof.” in 10pt italics font. After that the proof fol- The preparation of these instructions and the LAT
400 lows in regular 10pt font. At the end of the proof, an unfilled EX and 436
BibTEX files that implement them was supported by Schlum- 437
401 square symbol (qed) marks the end of the proof. berger Palo Alto Research, AT&T Bell Laboratories, and 438
402 In LATEX proofs should be typeset using the \proof envi- Morgan Kaufmann Publishers. Preparation of the Microsoft 439
403 ronment. Word file was supported by IJCAI. An early version of this 440
document was created by Shirley Jowell and Peter F. Patel- 441
404 Proof. This paragraph is an example of how a proof looks Schneider. It was subsequently modified by Jennifer Ballen- 442
405 like using the \proof environment. tine, Thomas Dean, Bernhard Nebel, Daniel Pagenstecher, 443
444 Kurt Steinkraus, Toby Walsh, Carles Sierra, Marc Pujol-
445 Gonzalez, Francisco Cruz-Mencia and Edith Elkind.
446 References
447 [Abelson et al., 1985] Harold Abelson, Gerald Jay Sussman,
448 and Julie Sussman. Structure and Interpretation of Com-
449 puter Programs. MIT Press, Cambridge, Massachusetts,
450 1985.
451 [Baumgartner et al., 2001] Robert Baumgartner, Georg Got-
452 tlob, and Sergio Flesca. Visual information extraction with
453 Lixto. In Proceedings of the 27th International Conference
454 on Very Large Databases, pages 119–128, Rome, Italy,
455 September 2001. Morgan Kaufmann.
456 [Brachman and Schmolze, 1985] Ronald J. Brachman and
457 James G. Schmolze. An overview of the KL-ONE knowl-
458 edge representation system. Cognitive Science, 9(2):171–
459 216, April–June 1985.
460 [Gottlob et al., 2002] Georg Gottlob, Nicola Leone, and
461 Francesco Scarcello. Hypertree decompositions and
462 tractable queries. Journal of Computer and System Sci-
463 ences, 64(3):579–627, May 2002.
464 [Gottlob, 1992] Georg Gottlob. Complexity results for non-
465 monotonic logics. Journal of Logic and Computation,
466 2(3):397–425, June 1992.
467 [Levesque, 1984a] Hector J. Levesque. Foundations of a
468 functional approach to knowledge representation. Artifi-
469 cial Intelligence, 23(2):155–212, July 1984.
470 [Levesque, 1984b] Hector J. Levesque. A logic of implicit
471 and explicit belief. In Proceedings of the Fourth Na-
472 tional Conference on Artificial Intelligence, pages 198–
473 202, Austin, Texas, August 1984. American Association
474 for Artificial Intelligence.
475 [Nebel, 2000] Bernhard Nebel. On the compilability and
476 expressive power of propositional planning formalisms.
477 Journal of Artificial Intelligence Research, 12:271–315,
478 2000.