NOTE! OOPSLA200 is over. I'm leaving this site up for a while because it contains a few things that still may be of interest. But it will disappear soon.I'm the program chair for OOPSLA 2000. Here are some notes and answers to questions people have been asking me. More information about some of them is or will be listed in the CFP and web site.
You can submit between 1 February 2000 and 3 April 2000. All submissions use an online submission and review process that is accessible from the OOPSLA 2000 web site. Deadlines for some kinds of submissions (for example posters) are different; see the web site.
To accommodate all of our pacific islander submitters (:-), you have until midnight April 3 anywhere on earth, which is noon GMT (7AM EST) 4 April.
Please do not ask for an extension. Our submission system is automated in such a way that we cannot grant them.
Please first check the sample walk-through to see if you misinterpreted any of the instructions. If you still have problems, feel free to get in touch with me.
Some people have reported problems trying to use "Upload" on the "Add files to a technical paper" page when using some browsers and paper formats. If this happens to you, use the "FTP" alternative on that page.
Yes, but I'm likely to just scan it briefly and tell you whether it fits within the topic, format, etc., guidelines for submission.
It would be a better idea to directly contact the people chairing the appropriate committes. See the OOPSLA 2000 web site to find out who to contact.
No.
No. Only postscript or PDF. Please be sure that your file displays properly in common viewers such as Adobe acroread and ghostscript. While PDF is preferable because it is easier for most people to view and print, some postscript-to-pdf converters (also vice-versa) seem not to work right, so please carefully check the results of any conversion you do.
I do not know of a commonly-used word-processor program that does not have some way to generate PS or PDF. On some systems, this is done by "printing to a file".
For more information about creating PDF across various platforms see for example the NSF PDF instructions and guidelines.
Because no one at ACM headquarters uses frame, so they cannot support it. But you can use this MIF frame file that I adapted from previous ones, that obeys current ACM format rules.
Note that ACM format rules currently use 9pt body fonts. (Most previous versions were 10pt.)
You can use this StarOffice SDW file that I adapted from the ACM MSWord template.
Well, if your paper is accepted, the final published version will have to be in the required format. You and we will probably be happier if you had formatted your submission this way originally. If you can't or don't want to use latex, wp, word, staroffice, frame, or other programs that can import their formats, here's what you need to know to do the formatting. (Margins are listed for USLetter. Adjust approriately for A4.)
| Title | Centered 18 pt, Bold, Helvetica |
| Author, ACM Fellow | Centered 12 pt, Helvetica |
| Affiliation | Centered 10 pt, Helvetica |
| Centered 12 pt, Helvetica | |
| Abstract | Flush Left 12 pt, Bold, Times Roman |
| Section (heading 1) | Flush Left 12 pt, Bold, Times Roman, numbered- ex: 1 |
| Subsection (heading 2) | Flush Left 12 pt, Bold, Times Roman, numbered- ex 1.2 |
| Subsubsection (heading 3) | Flush Left 11 pt, Italics, Times Roman, numbered- ex 1.2.3 |
| Subsubsubsection (heading 4) | Flush Left 11 pt, Italics, Times Roman, numbered- ex 1.2.3.4 |
| Subsubsubsubsection (heading 5) | Flush Left 11 pt, Italics, Times Roman, numbered- ex 1.2.3.4.5 |
| Text | 2 column, justified, size of type 9 pt. space between lines 10 pt |
| Text Font | Times Roman |
| Column width | 3.33" (8.45 cm) |
| 2 column gutter | .33"(.83 cm) |
| Top Margin | 1" (2.54 cm) |
| Right Margin | From edge .75" (1.9 cm) |
| Left Margin | From edge .75" (1.9 cm) |
| Bottom Margin | 1" (2.54 cm) |
| Copyright space on 1st page | lower left column 1.5" (3.81 cm) |
| Paragraph indentation | Flush Left |
| Footnote/Citation | 9 pt, Times Roman |
| Bibliography/Reference | 9 pt. Use the standard CACM format for references, i.e., a numbered list at the end of the article, ordered alphabetically by first author, and referenced by number in brackets [2]. Reference number in brackets positioned as a negative indent. Text aligned .25" (.63 cm) in from margin, ragged right margin. |
| Subsequent pages | For pages other than the first, start at the top margin and continue in double-column format. |
| Tables/Figures/Images | Placed in text as close to reference as possible. May extend across both columns to a maximum width of 7"(17.78 cm). |
| Captions | 9 pt, bold, Times Roman, numbered (ex. "Table 1." or "Figure 2."), and centered beneath each table, figure or image. |
First, there ARE Practitioner's Reports (see below). But the distinction between research-based technical papers and experience-based technical papers has blurred so much over the past few years that there is no longer any reason to place them in different categories. (For example, is a paper discussing design patterns a research paper or an experience paper?)
Practitioner Reports are short papers describing particular development projects. They are a valuable means of communicating experiences especially at the "bleeding edge" of technology -- many attendees want to find out what it is like to adopt a new language, use new engineering methods, etc.
The submission and review process is also very different for Practitioner Reports. Practitioner Reports are solicited, reviewed, and shepherded with the goal of providing timely case studies and insights of interest to developers, while technical papers are reviewed with respect to more traditional criteria aimed at advancing the state of the art. The Practitioner Report process is designed to be helpful especially for people who are still in the midst of the development projects they are reporting on.
All kinds! Well, all kinds dealing with object-oriented systems, languages, and applications. OOPSLA is a very diverse conference.
There are lots of approaches and styles. The following resources list some advice.