Formatting instructions for the Unitech 2010 proceedings
Faculty of Engineering, Oslo University College, P.O.Box4 St. Olavs plass, N-0130 Oslo, Norway
MediaLT, Jerikoveien 22, N-1067 Oslo, Norway
Abstract
This document describes the formatting instructions for the papers to be included in the Unitech 2010 proceedings. These instructions are formatted as a quasi-paper to better illustrate how a paper should be formatted. You may select “view source” in your browser and use it as a template. Also, all paper should have an abstract briefly describing the outline of the paper. You may view this document using print preview in your browser to see approximately how the printed version of the paper will look. Note that this style has only been tested with print preview in Firefox (with autoscaling turned off).
1. Introduction
This document describes the formatting instructions for the papers to be included in the Unitech 2010 proceedings. Our prime goal is to make these proceedings accessible. We have therefore decided to use html as this seems to among the most accessible formats available today. This is not unproblematic as html was not intended for typesetting scientific papers. We therefore had to make several decisions that partially break with scientific traditions and partially the intended use of html. Note that we welcome to suggestions for improvements, and that these instructions are likely to be revised based on feedback from its users. Moreover, should you have any questions or problems then please do not hesitate to contact us.
The source file generated by the authors will be published online in its original form and a special CSS-file will be used to generate the paper format for the printed version of the proceedings so that we achieve a uniform look.
2. Contents
The contents should adhere to the norms of technical conferences. The papers should have a title, an abstract, an introduction presenting the problem, a background section presenting related work, a methods section, results, discussion, conclusions and references. Note however, that papers may take several forms depending on the contents and that the authors are not restricted to just this structure. As a general rule of thumb: use the format most suitable for your particular genre of paper.
3. Approach
For those of you who are not used to coding html directly these instructions may seem daunting. We therefore recommend that you prepare your manuscript In two steps. In the first step you focus on the content and therefore write it in your favorite word processor or editor. Once you are happy with the content you may move to the second step, namely the formatting using these instructions. The simplest approach is probably to view this document as source in your browser and copy the content and save it into a text file. Then you edit this file. By renaming the file with the extension html you will be able to check your work by clicking on the file and viewing it in your browser.
The first source lines of this document may look off-putting, but please ignore these. The real content of the document starts after the body-tag - everything before this tag can be ignored.
4. Frontmatter
H1-tags are used to indicate the paper title. A paper must only have one title and this should appear at the top of the document. The h1-tag is used as follows:
<h1>Paper title</h1>
Next, the authors are included in a separate authors section using p-tags with an author class. Next the affiliations are indicated with a separate p-tag using an affiliation class.
Next, after the author list follows the abstract. The abstract opens with the h2-title "Abstract" using the abstractHeading class. The abstract text is listed as a separate paragraph using a p-tag with an abstract class. The frontmatter as it appears in this examplew with title, author, affiliation and abstract is therefore marked-up as follows
<h1>Formatting instructions for the Unitech 2010 proceedings</h1>
<p class="author">
Frode Eika Sandnes
</p>
<p class="affiliation">
Faculty of Engineering, Oslo University College,
P.O.Box4 St. Olavs plass, N-0130 Oslo, Norway
</p>
<p class="author">
Morten Tollefsen
</p>
<p class="affiliation">
Media LT, Jerikoveien 22,
N-1067 Oslo, Norway
</p>
<h2 class="abstractHeading">Abstract</h2>
<p class="abstract">
This document describes the formatting instructions for the
papers to be included in the Unitech 2010 proceedings. These
instructions are formatted as a quasi-paper to better illustrate
how a paper should be formatted. You may select “view source” in
your browser and use it as a template. Also, all paper should
have an abstract briefly describing the outline of the paper.
You may view this document using print preview in your browser
to see approximately how the printed version of the paper will
look. Note that this style has only been tested with print
preview in Firefox (with autoscaling turned off).
</p>
Remember to put the "Abstract: " at the beginning of the abstract
5. Section headings
5.1 Section headings
H2-tags are used to indicate first level section headings. For example:
<h2>2. A first level heading</h2>
Note that h1-tags are used for indicating the paper title and there should therefore only be one h1-section in the paper. H3-tags are used to indicate second level headings. Note that we encourage the authors to not use more than second level headings for the papers. For example:
<h3>2.1 A second level heading</h3>
All section titles should be numbered consecutively as in this document and the numbering is done manually.
6. Body text
Paragraphs of text should be embedded in p (paragraph)-tags as illustrated in the following example.
<p>The first paragraph of text….</p> <p>The second paragraph of text….</p>
7. Bullets and lists
Use the html UL and OL-tags to created unnumbered and numbered lists. However, bullets and lists should be used sparingly. Unnumbered lists such as:
- First unnumbered item
- Second unnumbered item
- Third unnumbered item
Are coded using:
<ul>
<li>First unnumbered item</li>
<li>Second unnumbered item</li>
<li>Third unnumbered item</li>
</ul>
Numbered, or ordered, lists are such as
- First numbered item
- Another numbered item
- Yet another numbered item
are coded as
<ol>
<li>First numbered item</li>
<li>Another numbered item</li>
<li>Yet another numbered item</li>
</ol>
8. Figures
Figures are included using img-tags and the Figure caption is provided in the alt-attribute of the img-tag. This is illustrated in the following examples:
Figure 1. Design cycle
Figure 2. Experimental results
The source for these figures are as follows:
<img src="design.gif"
alt="The figure shows the design cycle where the process starts
with design, prototype development and evaluation with
users and starts over." />
<p class="figure">Figure 1. Design cycle</p>
<img src="plot.gif"
alt="The figure shows the results of the experiment where
results are plotted as a bar graph comprising two bars. The
left bar illustrates a measurement of 3 second and the
right bar illustrates a measurement of 4 seconds." />
<p class="figure">Figure 2. Design cycle</p>
Figures captions should be numbered consecutively with Figure 1. ..., Figure 2. ..., etc as in the example shown.
9. Tables
Whenever possible tables are preferred over diagrams as they are more accessible. However, it is important to use the built in mechanisms for headings in tables. Also a caption should be used to describe the contents of the table. These should be also given consecutively running lables such as Table 1, Table 2, etc. A simple example table is given below:
| Test subject | Measurement (seconds) |
|---|---|
| Participant 1 | 3 seconds |
| Participant 2 | 4 seconds |
The source for this table is given below
<table>
<caption>Table 1. An example table with headings</caption>
<tr>
<th>Test subject</th>
<th>Measurement (seconds)</th>
</tr>
<tr>
<td>Participant 1</td>
<td>3 seconds</td>
</tr>
<tr>
<td>Participant 2</td>
<td>4 seconds</td>
</tr>
</table>
10. Equations
Equations make papers hard to read and should be avoided if possible. However, they are sometimes necessary. If you need to include equations then we recommend that these are prepared in your favorite software package such as Word, Latex or Matematica and then exported as images. Then, in the alt tag of the image you provide a textual description of the equation. The following example illustrates this:
The above equation summarizes Fitt’s law where T is the average time taken to complete the movement, a represents the start/stop time of the device and b stands for the inherent speed of the device, D is the distance from the starting point to the center of the target and W is the width of the target measured along the axis of motion. The source for this is:
<img src="eq1.gif"
alt="Equation: T=a+b log2(1+D/W)" />
11. Displaying code
To display code in the document the example XMP tag can be used. The xmp-tag must embrace the code to be displayed.12. References
The authors are encouraged to cite references using the APA or Harward style, where the first author’s surname and year separated by a space are listed in parentheses as part of the running text, for example (Sandnes 2009). This style of citation will give the reader at better clue about the reference compared to the common number format where references are cited in increasing number format, such as [1, 2, 3].
If there are more than one work cited at the same time the various citations are separated by a semicolon, for example (Sandnes 2009; Tollefsen 2008; Lunde 2007). If there are more than one paper from the same author in one year then the year is post-fixed by a letter, for example (Sandnes 2009a; Sandnes 2009b).
The references should be listed in a separate “references” section at the end of the paper. Each reference is formatted using a list of items with the reference style (see the examples below). The format of the reference content to be used is as follows:
- Periodical/journal: All authors (Year), “Title”, Journal name, Volume, Issue, pages.
- Conference Proceedings: All authors (Year), “Title”, Conference name, Publisher, pages.
- Book: All authors (Year), “Title”, Publisher.
- Book chapter: All authors (Year), “Title”, Book-title and editor, publisher, pages.
- Web-site: Author/organization, “Title”, Downloaded date, URL (as a hyperlink).
Note that material on the web that has not been subject to peer-review quality control should be avoided if possible. The following are examples of the above format:
- Sandnes, F. E. (2008), "Directional bias in scrolling tasks: A study of users' scrolling behaviour using a mobile text-entry strategy", Behaviour & Information Technology, Vol. 27, No. 5, pp. 387-393.
- Sandnes, F. E. (2006), "Can Spatial Mnemonics Accelerate the Learning of Text Input Chords?", Proceedings of the Working Conference on Advanced Visual Interfaces, ACM Press, pp. 245-249.
- Saffer, D. (2008), “Designing Gestural Interfaces”, O’Reilly.
- Sandnes, F. E., Jian, H.-L. and Hagen, S. (2008), "Student Evaluation a Learning Management System from an HCI Perspective" in INNOVATIONS 2008: World Innovations in Engineering Education and Research, Win Aung, Josef Mecsi, Jerzy Moscinski, Ian Rouse and Peter Willmot (eds), Begell House Publishers pp. 473-486.
- Norwegian Network on Universal ICT, “The Unitech 2010 website”, Downloaded December 10, 2010, http://www.unitech2010.org/
The most important part of the references is that sufficient information is provided such that interested readers can find the reference.
Each reference is placed in a list block using a li-tag with the reference-class as shown in the followin example (note that all the li-tags needs to be placed within a ul-block):
<ul>
<li class="reference">
Sandnes, F. E. (2008),
"Directional bias in scrolling tasks: A study of users'
scrolling behaviour using a mobile text-entry strategy",
Behaviour & Information Technology,
Vol. 27, No. 5, pp. 387-393.
</li>
<li class="reference">
Sandnes, F. E. (2006),
"Can Spatial Mnemonics Accelerate the Learning of Text
Input Chords?",
Proceedings of the Working Conference on Advanced Visual
Interfaces,
ACM Press, pp. 245-249.
</li>
<li class="reference">
Saffer, D. (2008),
“Designing Gestural Interfaces”,
O’Reilly.
</li>
<li class="reference">
Sandnes, F. E., Jian, H.-L. and Hagen, S. (2008),
"Student Evaluation a Learning Management System from an
HCI Perspective"
in INNOVATIONS 2008: World Innovations in Engineering
Education and Research, Win Aung, Josef Mecsi, Jerzy
Moscinski, Ian Rouse and Peter Willmot (eds),
Begell House Publishers pp. 473-486.
</li>
<li class="reference">
Norwegian Network on Universal ICT,
“The Unitech 2010 website”,
Downloaded December 10, 2010,
<a href=”http://www.unitech2010.org/”>
http://www.unitech2010.org/</a></li>
</li>
</ul>
13. Submission
All the files including the main html-document, and the images should be packed into a zip-file, and this zip file should be submitted.
For those of you who are thml-savvy please avoid the temptation of using other html-markup not mentioned in this document. This will help us maintain a uniform format and efficient processing of the manuscript. However, please contact us if you have any particular thoughts on the formatting.
14. Margins, footers and headings
The margins, footers and headings are considered "outside" the html document. Therefore, do not worry about these. We will ensure that the correct margings, footers and headers (including page numbers) are set when preparing the proceedings for printing.