This brief paper presents the details necessary to prepare a paper for INET'99. The paper includes guidelines on style, acceptable formats and constructs. It also provides suggestions on how to prepare the paper. As in previous years, the Proceedings of INET'99 will be published on CD-ROM and on the Internet.
I M P O R T A N T R E M I N D E R
The Program Committee would kindly like to remind everyone that the INET audience is a professional audience, and not one of beginners. It is better to err on the side of "too technical" than "too general." That way, your comments will challenge the audience and be less likely to present them with a level of information with which many are already familiar. We thank you in advance for taking this important point to heart.
Table of Contents
- Key Submission Dates
- Paper Format
- Writing the Paper - Acceptable Styles
- Special Constructs
- Things Not To Use
- File Naming Conventions
- How To Submit
Key Submission Dates
22 February 1999
- Last day to submit full Papers for Program Committee review.
19 March 1999
- Authors notified of selected Papers.
3 April 1999
- Last day to submit final Papers and Panel Papers (after Post Acceptance Editing) for inclusion in the INETí99 Proceedings.
22-25 June 1999
- INETí99 : Setting the Foundations of Next Century's Knowledge Society
The Internet Global Summit
Paper FormatThe paper is expected to be 8-10 pages in length, about 4000 words. It is due on 22 February, 1999. Every paper must be submitted in HTML, the Hyper-Text Markup Language widely used on the World Wide Web. This will support a common presentation on CD-ROM and on the Web. For this reason, we obviously prefer that your paper is submitted in HTML.
Florencio Utreras (email@example.com)
Second Author NAME (Second.Author@email.address.org)
Second Author Affiliation
Second Author Country
Third Author NAME (Third.Author@email.address.com)
Third Author Affiliation
Third Author Country
Producing HTMLThere are a number of ways of producing HTML documents.
- Word Processors
- Many recent versions of popular word processors offer HTML as one of the export options. With such a word processor, prepare your paper in a style similar to this paper. When you are finished use the export function to create an HTML version. We recommend that you view your paper with a web browser before submitting it. (Most browsers allow you to open a local file as well as a URL.) This will allow you to double-check the paper's appearance.
- HTML Editors
- There are a number of shareware and commercial HTML editors available. A long list of such editors is maintained by the W3Consortium.
- Text Editors
- Since HTML is an embedded markup language it can be prepared using a basic text editor. (This document was written in notepad.) If you use this approach and haven't written HTML before you may wish to consult the W3 Consortium's information on learning and using HTML. A popular reference is Kevin Werbach's Bare Bones Guide to HTML.
- If you do not have a program that outputs HTML and do not want to learn to write it yourself, another approach is a filter. Filters exist to convert many standard formats into HTML. Again the W3 consortium maintains a list of such filters.
Alternatives to HTMLIf it is really not possible to produce HTML we will accept two alternatives:
- RTF or Rich Text Format. This is an available export format on most word processors. We will be able to automatically generate HTML from RTF, however, RTF does not support included graphics.
- ASCII text. If nothing else is available compose your paper in plain text.
Using This Paper as a TemplateTo use this paper as a template, find the Save or Save As command and select Source as the option. That will save this document as HTML. It can then be read by your word processor editor.
Post Acceptance EditingThe Internet Society will pass all accepted papers and panel papers to professional editors for production of the proceedings. Thus, your paper may change slightly from submission to the final proceedings.
Writing the Paper - Acceptable StylesThis section is intended as a guideline to the use of the various HTML markup commands. It is intended to give papers a consistent style.
Basic StylesFeel free to use both <B>bold</B> and <I>italics</I> for emphasis as needed. Similarly <EM>emphasis</EM>, <STRONG>strong emphasis</STRONG> and other text markup styles.
SectionsSections, sub-sections and sub-sub-sections should use the <H2>,<H3> and <H4> levels of HTML headings, respectively.
Use the <BLOCKQUOTE>to set off a passage of text like this.
Table of ContentsEvery paper should contain a Table of Contents. The entries in the Table of Contents should be links to the top level sections, but not sub- or sub-sub-sections.
ListsYou may use any of the lists common to HTML. Examples of each of the numbered list (<OL>), unnumbered list (<UL>), and descriptive list (<DL>) are found in this paper.
Special ConstructsThis section talks about various constructs you may wish to use in your paper.
URLsThe use of URLs presents possible problems with copyright restrictions. We have adopted the following policy with respect to the inclusion of URLs in INET'99 papers. URLs may be used in four ways in your paper.
This implies that you must use a level of indirection to point to another's work from within your paper. At the point where the work is mentioned, you include a URL to an entry in the References section. The entry may then contain a URL to the work. See the examples included in this paper.
- Links to another location within the paper as demonstrated in the Table of Contents.
- The MAILTO URL for the authors as shown at the start of the paper.
- Links to the author's own work.
- Within the references section properly attributed URLs may point to the work of others.
The Use of TablesWe would prefer that you did not use tables to achieve complex page layouts, however there are clearly times when tables are the appropriate way to present data. Here are a few things you always wanted to know about San Jose, California as an example of an acceptable use of tables in an INET'99 paper.
San Jose, California
Country United States of America State California 1990 Population 782,248
ImagesAll references to images should be to files in the same directory as your paper, e.g. the image in the table above was specified using<IMG SRC="fig1.gif">.
All images should be in GIF89a (without animation), or JPEG (JFIF).
Animations etc.Remember that you are submitting a paper, not a web page. No animated gifs, blinking words, movies etc. As stated above, you can include a URL reference to your own site which demonstrates these features if necessary.
Things Not To UseYour finished paper should not require support for any of the following:Blinking.If in doubt, keep it simple.
Plug ins, e.g. audio, video, etc.
File Naming ConventionsYour paper should consist of a single HTML file, but may be supplemented by images in GIF or JPEG files. Thus your submission may well be several files. We ask that you use the following naming convention to facilitate web access and to allow for anyone who may still be using Windows 3.1:
- Name the single HTML file index.htm, and
- Name all image files fig1.gif, fig2.jpg,etc. Please maintain the sequence fig1, fig2 with eitherthe .gif or .jpg suffix as appropriate.
How To SubmitAll paper and panel paper submissions should be sent by email to 99Papers@ISOC.ORG. Please send a separate email message for each paper you are submitting. The Subject line of the email message should identify your paper with the 5-digit numeric id assigned to your paper. All file components of your paper should be submitted as attachments to your email message. You will receive a brief acknowledgment of your submission within 3 business days. If it is somehow not possible to submit your paper via email, send a query to 99Papers@ISOC.ORG to make other arrangements. Any other queries should be directed to INET99@ISOC.ORG.
- World Wide Web Consortium, World Wide Web and HTML Tools, http://www.w3.org/pub/WWW/Tools/
- World Wide Web Consortium, HyperText Markup Language (HTML), http://www.w3.org/pub/WWW/MarkUp/
- Werbach, Kevin, The Bare Bones Guide to HTML, http://werbach.com/barebones/