1. Introduction

IW3C2 is committed to producing an online set of Proceedings for the complete set of WWW Conferences with the correct interlinking between volumes. IW3C2 also has a strong commitment to Web Standards and for that reason there is a requirement that papers submitted to the Conference are in current standard HTML format (which is currently XHTML). To aid in the production of the online version, the printed Conference Proceedings and the CD-ROM, it is important that authors produce their papers in a standard format in strict XHTML. By doing this the production process can be accelerated and this allows the date for final papers to be left as late as possible.

The proceedings are the records of the conference. ACM hopes to give these conference by-products a single, high-quality appearance. To do this, we ask that authors follow some simple guidelines. In essence, we ask you to make your paper look exactly like this document. Though much of the proposed style is explained here, please consult also the source of this document to correctly apply the formatting.

Papers should be formatted using standard XHTML elements (h1-h6, ul, ol, li, p etc). For a brief introduction to the XHTML syntax, please refer to Appendix A: XHTML Hints. Please incorporate the following line in the of your document's source code:

This Cascading Style Sheet will take care of much of the formatting for you, if you follow the rules described in this document.

2. General Notes

All paper submissions must be in English.

The total number of words should not exceed 8,000 words.

The HTML file and all relevant images should be compiled into a zip file and uploaded onto the WWW2003 conference paper submission site.

3. Paper Structure

Please adhere to the following layout order when writing your papers:

• Title
• Authors and Affiliations
• Abstract
• Keywords
• Section
• Main body of text
• Sub-sections (if applicable)
• Acknowledgements
• Appendix
• References
• Author vitae (optional)

4. The Metadata of the Paper

The whole metadata section at the top of this paper is enclosed in a div classed "metadata". Heading level 1 is used for the title, classed "title". The whole list of the authors is enclosed in a div classed as "authors". Individual authors are enclosed in divs classed "author". The data for one author looks like this: 1st level heading with class "author" for the name, 2nd level heading with class "affiliation" for the details of the institute, 3rd level heading with class "email" for the email address. (The similar details for authors from similar institutes should be repeated.) The ABSTRACT is headed by an h2 element of class "abstract" and contains a p element of class "abstract". The KEYWORDS section is headed by an h2 element of class "keywords" and contains a p element of class "keywords".

The metadata at the top of this paper looks like this in the source:

    

      
HTML Paper Submission Guidelines
      

        

          
Bob Hopgood
          
Oxford Brookes University,
          Headington Campus

          Gipsy Lane, Oxford OX3 0BP, United Kingdom
          

        
        

          
Gergo Kiss
          
Computer and Automation Research
          Institute,

          Hungarian Academy of Sciences

          Lagymanyosi u. 11, Budapest, H-1111, Hungary
          

        
      
      

        
Abstract
        
This document describes the HTML
        formatting guidelines for WWW2003 Proceedings. We do
        encourage authors to follow the formatting. This document
        has been formatted following these rules.
      
      

        
Keywords
        
Keywords are your own designated
        keywords. See the appendix for a suggested set of keywords
        to choose from.
      
    

5. Basic Formatting

5.1 Sections and Subsections

Format section titles as h2 elements. Format subsection titles as h3 elements.

5.2 Body Text

• Enclose your paragraphs between p tags. Using the www2003.css style sheet, the first line of paragraphs will get indented. To avoid this, set the paragraph's class to "noindent".
• Use blockquote to indent complete blocks of cited text.
• Use the pre tag to include code segments.
• Use the ul, ol and li tags to create listings

6. Paper Size

All material must be printable within a rectangle of 18 x 23.5 cm (7" x 9.25") from an XHTML enabled browser (see Appendix A.2 for a list of these) using the CSS style sheet specified earlier in this document.

7. Mathematics

Probably the hardest thing to get right in XHTML is mathematics. Some approaches are:

• Write the mathematics in MathML and then do a conversion of the formulae to an image format such as SVGor GIF/PNG. (SchemaSoft Custard translates MathML to SVG, but seems to work only on MathML's presentation markup, and not on content markup.)
• A similar process can be used if you define the mathematics in Word.
• For Unix users, there are a number of converters which vary in their competence. The ones that generate deeply nested XHTML tables are probably not the best approach.

8. Images

If you add images in GIF, PNG or JPEG format, it is probably be sensible to use the img element. Be sure to make it a valid XHTML element and make sure it has an alt attribute. For example:

Example Image

Which with the current style sheet would render as:

It is important to give the image's size in case some automatic rescaling is needed. We would prefer images not to exceed 1000 by 750 and we may scale them to fit on ther page.

For SVG graphics use:

For now this is probably the best approach. The SVG will be used if the browser supports SVG and otherwise the PNG image. SVG implementations like Batik will do the conversion to PNG for you.

Compile al images together with the HTML file into a zip file and upload onto the WWW2003 conference paper submission site.

9. Tables

The table element must have a summary attribute. Try and keep tables simple. A good format for a table with headings and an initial header column would look something like:

Example Table






First
Second
Third




Heading
Data
Data


Heading2
Data2
Data2

which would appear as:

10. Hyperlinks

Hyperlinks within the paper and to related files must follow a strict naming structure:

1. Use relative addresses and the id tag to link sections of the same file. Example:

   In addition to the many algorithms available, 
   there are also other methods...
   .
   .
   .
   Additional Resources
   

   Note that

   is used for anchor. The structure is not used any more.

2. Necessary external links must specify the full absolute pathname.
3. If the volunteer publishers want to build links among the papers in a conference, these should NOT be built in the version of the papers sent to ACM for inclusion in the Digital Library. Inter-article links cannot be supported in the DL.
4. Do not add navigation links in the articles, instead rely on the client browser's GO BACK feature to return readers to the Table of Contents.

   Note: Inclusion of HTML proceedings in the Digital Library is desirable. However, the experience of SIGs that have prepared HTML files in the past is that it is an extensive, resource intensive effort. Please consult with those SIGs that have already completed an HTML proceedings on the nature and extent of the work.

• Amaya: located at http://www.w3.org/Amaya, Amaya is a complete web browsing and authoring environment and comes equipped with a "WYSIWYG style" of interface, similar to that of the most popular commercial browsers. With such an interface, users can easily generate HTML and XHTML pages, as well as CSS style sheets, MathML expressions, and SVG drawings (full support of SVG is not yet available, though). It is also a good tool for checking against XHTML compliance.
• HTML Tidy: originally from W3C but now located at http://tidy.sourceforge.net/ will take HTML and will either list the errors or, if it can understand it, will convert it into XHTML for you. The following command will take your HTML file and convert it to XHTML:

  tidy -f errorfile.txt -m -asxml myfile.html

  Note this will overwrite your existing file so make a copy before you do this!

• XHTML Validator: located at http://validator.w3.org/ this will check a file you present it against the various versions of XHTML. You can upload your paper to it and check it against Strict XHTML and see if it passes and if not why not.
• Word: it is possible to generate XHTML of reasonable quality starting from a Word document. You have to realise that SAVE AS into an HTML file will not do the job. That will leave a large amount of Word information in the document to allow you to move back to a Word document. Microsoft provides a utility that you can download called HTML Filter. You then Export To the Compact HTML format. This will remove the Word specific parts of the file. If the file is then put through Tidy you will land up with a small compact XHTML document. The download site is currently although a search for Microsoft HTML Filter will find it.
• Latex: to be defined

Appendix B: Keywords for Technical Areas

Below is a suggested set of keywords and their sub-classes that have been used in previous Conferences.