Second Forum on Parallel Computing Curricula
Sunday, June 22, 1997
Newport, RI

Guidelines for Proceedings Preparation
Version 1.1.1 of May 15, 1997

Samuel A. Rebelsky

Dartmouth College, Department of Computer Science

6211 Sudikoff Laboratory

Hanover, NH 03755

603-646-3266

samr@cs.dartmouth.edu

http://www.cs.dartmouth.edu/~samr/

Abstract

This document provides general guidelines for the final versions of papers for FPCC: The Second Forum on Parallel Computing Curricula [Kotz97]. Our primary goal is to have a uniform look to the papers in the proceedings. We have chosen for a simple layout for papers so as to support the greatest number of browsers.

Contents

• 1. Introduction
• 2. Basic Information
• 3. Specific Issues
• 4. Formatting References
• 4.1. A book or proceedings volume
• 4.2. An article in a journal or proceedings volume
• 4.3. An online document
• 4.4. Everything else
• 5. Reminders
• Notes
• References

1. Introduction

The program committee of the Second Forum on Parallel Computing Curricula has chosen to provide a web-only proceedings for the forum. There are a number of reasons for this decision, but wide accessibility is perhaps primary among them. This document is designed to help authors prepare uniform papers for the proceedings.

We request that all papers be prepared in HTML. If you do not know HTML, please contact the proceedings chair, Sam Rebelsky (samr@cs.dartmouth.edu) and he will aid you in your translation.

2. Basic Information

Although you are free to keep a copy of your paper on your own server, in whatever format you wish, we also intend to keep a permanent copy on the FPCC server. Please get the final version of your paper to Sam Rebelsky by June 1 so that the papers can be made available in time for the forum.

Because many readers will print your paper, we request that papers be prepared as one long HTML document. If necessary, we will segment your papers for online viewing.

We prefer information-oriented rather than layout-oriented papers. Hence, please do not use frames, and only use tables when they are tables that form part of your paper. You may feel free to include inlined images in your HTML documents.

Papers are to be prepared in the standard "research paper" order:

• Name and date of workshop (as at the top of this document)
• Title
• Author(s) and Affiliation(s)
• Abstract
• Contents
• Body
• End notes (optional)
• Acknowledgements (optional)
• References
• Appendices (optional)

3. Specific Issues

The following lines provide suggestions (which we would prefer that you follow) on how to format individual portions of your document. They are in alphabetical order for easy reference. You may refer to the list describing the order of components that appears above to determine what you might need to consider in formatting your paper.

Note that this set of guidelines follows the guidelines for FPCC (that is, this should look more-or-less the same as this paper, with obvious differences due to content and intent).

• Abstract: Preface your abstract with the word "Abstract" surrounded by H2 tags.
• Author: Enter the authors' names below in a description list (DL). Each author's name should be prefaced by a DT tag and each line of the address should be prefaced by a DD tag.
• Bibliography :
  • Preface the bibliography with <H2>References</H2>.
  • Use a description list (DL) for the bibliography.
  • Precede the reference "key" with the DT tag and the reference "body" with the DD tag.
  • The key should be named, as in <A NAME="Reb97">Reb97</A>
• Code: When listing program code, please use an appropriate monospace font. For in-text code, you should use the CODE tag. For long sections of code, you should use the PRE tag.
• Contents: The table of contents is an unnumbered list. Subsections should also be in their own unnumbered lists. Each element of the table of contents is a link (given by the A HREF="#..." tag).
• Endnotes: We suggest that you number your endnotes and surround them by brackets. [1] You should also make each endnote reference a link to the corresponding endnote in the endnotes section.
• Figures: Center figures and their captions. Number figures consecutively. Use relative links to the corresponding image files.
• Footnotes: Use endnotes rather than footnotes.
• Paragraphs: Surround paragraphs with <P> and </P>: tags. Do not use <P> to separate paragraphs. For lists, do what you think is best (I've chosen to treat my list as one paragraph; you may choose to make each item a separate paragraph).
• References: We prefer that you use alphanumeric references, such as [Reb97]. Each in-text reference should include a link to the corresponding entry in the bibliography, as in [<A HREF="#Reb97">Reb97</A>].
• Sections:
  • Use H2 tags for section titles, H3 tags for subsections, and so on and so forth.
  • Number your sections consecutively (and number subsections within the sections numbering).
  • Make sure to name each section with a <A NAME="..."> tag.
  • Section titles should have each word capitalized
  • Subsection (and below) titles should only have the initial word capitalized.
• Tables: We would prefer that you use HTML's table tags to format your tables. However, you may use images for your tables if you deem that necessary.
• Title: Use H1 for your document title in the body of the document. You will probably use a slightly different title in the header, preferably the last name of the authors and an abbreviated version of the document title.

4. Formatting References

In our experience, bibliographies are quite inconsistent and have gotten even more so with the introduction of electronic documents and markup languages.

HTML has the added disadvantage that it does not include specific bibliography tags, such as <bibentry>, or <journaltitle>. We believe that the format we have chosen (which can be identified by looking at the source of this document) serves many of the needs of readers and writers.

Of course, HTML and the WWW provide more opportunities for bibliography usage and we strongly encourage authors to make the references in the body of their text links to the bibliography. In addition, any references to online documents in the bibliography should be links to those documents.

We encourage, but do not require, the abbreviated name/year format for labeling bibliography entries. It is sufficiently small not to impede the flow of text, but provides sufficient information that readers need not always look to the bibliography. We recommend against numbers, as they are hard to distinguish from footnotes [2].

The following are samples of various types of references to help you use a uniform format for references. See the source code for this document to see how they are annotated.

4.1. A book or proceedings volume

[Glo93]

Peter A. Gloor, Fillia Makedon, and James W. Matthews, editors. Parallel Computation: Practical Implementation of Algorithms and Machines. Springer-Verlag/Telos, 1993.

4.2. An article in a journal or proceedings volume

[Reb95]

Samuel A. Rebelsky. "Designing Interactive Conference Proceedings." IEEE Multimedia, Summer 1995, pp. 75-79.

4.3. An online document

[Reb97]

Samuel A. Rebelsky. "Second Forum on Parallel Computing Curricula: Guidelines for Proceedings Preparation." Online document available at URL http://www.cs.dartmouth.edu/FPCC/papers/guidelines.html. 1997.

4.4. Everything else

Try to follow the models above for other types of documents. In general, we request that you

• Put the title of an article in quotation marks.
• Put the title of a volume (book, journal, or proceedings) in italics or emphasized face.
• Write authors' in a first-name-first style, with names as they appear on the original paper (i.e., don't abbreviate unless the authors abbreviate).
• Don't abbreviate journal or conference names.
• Include all pertinant information.

5. Reminders and Tips

These are intended to provide a short summary of some of the issues described above. They also try to provide some motivation for a few particular issues.

• Prepare a single HTML document (with associated images as appropriate).
• If using images, use relative links to files in the same directory.
• Send your paper to Samuel A. Rebelsky (samr@cs.dartmouth.edu). If using more than one file, tar and uuencode everything before sending.
• Do not use frames.
• Do not use <P> to separate paragraphs.
• Name all appropriate components (sections, entries in the bibliography, etc.) and include links to those components.
• Put approximately thirty blank lines, surrounded by <PRE> and </PRE> tags at the end of your document. This makes it easier for some browsers to correctly link to pieces of text at the end of your document. Note that the PRE tags should each by on their own line.
• We strongly suggest that every paper have a table of contents that includes links to the individual sections and subsections. Research shows that tables of contents better prepare readers to understand papers. In addition, in electronic documents, tables of contents give readers the opportunity to quickly jump to an appropriate section.

End Notes

[1] The brackets around an end note number make it easier to identify as such.

[2] Now, didn't that look a little like a reference?

References

[Kotz97]

David Kotz, editor. Proceedings of the Second Forum on Parallel Computing Curricula. Online document available at URL http://www.cs.dartmouth.edu/FPCC/index.html. 1997.

[Reb97]

Samuel A. Rebelsky. "Second Forum on Parallel Computing Curricula: Guidelines for Proceedings Preparation." Online document available at URL http://www.cs.dartmouth.edu/FPCC/papers/guidelines.html. 1997.