 |
 |
 |
I N E T 2 0 0 0
The Internet Global Summit
Global Distributed Intelligence for Everyone
The 10th Annual Internet Society Conference
18-21 July 2000
Pacifico Yokohama Conference Center
Yokohama, Japan
<inet2000@ISOC.ORG>
|
Preparing a Paper for INET 2000
Sample & Instructions
Abstract
This brief paper presents the details necessary to prepare a paper
for INET 2000. 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 2000 will be published on CD-ROM and
on the Internet. A listing of abstracts submitted to date is available at http://mc-net.jtbcom.co.jp/inet2000/submit/listtop.html.
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.
INET 2000 Theme
Global Distributed Knowledge for Everyone
Paper Format
The paper is expected to be 8-10 pages in length, about 4000 words. It is due
on 25 January, 2000. 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.
Author Listing
Please list all authors of the paper as per the example below:
Florencio Utreras (inet-program-chair@isoc.org)
REUNA
Chile
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 HTML
There 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[1].
- 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[2].
A popular reference is Kevin Werbach's Bare Bones Guide to HTML[3].
- Filters
- 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[1].
Alternatives to HTML
If it is really not possible to produce HTML we will accept the following alternative:
- ASCII text. If producing HTML is not possible, compose your paper in
plain text.
Using This Paper as a Template
To 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 Editing
The 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 Styles
This 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 Styles
Feel 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.
Sections
Sections, 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 Contents
Every 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.
Lists
You 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 Constructs
This section talks about various constructs you may wish to use in your paper.
URLs
The use of URLs presents possible problems with copyright restrictions. We have
adopted the following policy with respect to the inclusion of URLs in INET 2000
papers. URLs may be used in four ways in your 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.
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.
The Use of Tables
We 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 2000 paper.
| San Jose, California |
| Country |
United States of America |
| State |
California |
| 1990 Population |
782,248 |
|
 |
Images
All 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 .
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 Use
Your finished paper should not require support for any of the following:
Blinking.
Animated graphics.
Frames.
Plug ins, e.g. audio, video, etc.
Vendor-specific extensions.
If in doubt, keep it simple.
File Naming Conventions
Your 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 Submit
All authors will be asked to make paper submissions through a web enabled form.
This form will be available to accept submissions from mid-January to January
25 only - no extensions will be made. A separate email will be forthcoming in
early January relating the URL of the submission form, the exact opening date
for submissions and specifics on how to use the form.
References
- 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/
|
|
1775 Wiehle Ave.,
Suite 102, Reston, VA, USA 20190-5108
Tel: +1 703 326 9880 Fax: +1 703 326 9881
4, rue des Falaises, CH-1205, Geneva, Switzerland
Tel: +41 22 807 1444 Fax: +41 22 807 1445
This document
<http://www.isoc.org/inet2000/paper.shtml>
was last updated Thursday, 28-Oct-2004 13:42:41 EDT.
Copyright © 2006 Internet Society. All Rights Reserved.
Webmaster@ISOC.ORG
Privacy Statement
|