Networked Learning International Conference 2002: Paper Format Template
David McConnell
University of Sheffield 
d.mcconnell@shef.ac.uk 
ABSTRACT
In this paper, we describe the formatting requirements for the Networked Learning Networked 2002 Conference, and we offer a number of suggestions on writing style for  readership.
Keywords
Guidelines, formatting instructions, author's kit, conference publications
INTRODUCTION
The Conference Papers will provide a record of the event. We hope to give the book 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. 
The easiest way to do this is simply to use this template and replace the content with your own text and graphics, being careful not to add any new styles or redefine the template styles. You may want to open this document in Word and then Save As “NLC 2002 template.dot” by saving the Change As Type pull-down list to Document Template. When you have completed the paper, save it in your own name (eg Bloggs.doc) so that we can easily identify it when you email it to us at nlc@shef.ac.uk by 15th February, 2002.
If your paper is part of a proposed symposium, you should send the completed paper to the symposium chair/organiser, who will then send all the associated symposium papers to us at nlc@shef.ac.uk. Please ensure you send it in time for the symposium organiser to collate all the papers and send them to us at Sheffield. The symposium organiser should also provide a short Introduction explaining the focus and purpose of the symposium.
PAGE SIZE
All material on each page should be centered on a A4 page with 1 inch margins all around.
It is important to check these margins even if you use this Word template, because they might have been overwritten by your local settings.
TOTAL NUMBER OF PAGES
Full papers should be no longer than 8 pages. This includes everything: from the title to the references. Longer papers will not be included in the Conference Book. 
Workshop and poster descriptions should be 500 words in length.
FORMATTED TEXT
Carefully format your submission using the following styles:
Normal Text
Please use a 10-point Times New Roman font, or other Roman font with serifs, as close as possible in appearance to Times New Roman in which these guidelines have been set. The goal is to have a 10-point text, as you see here. Please use sans-serif or non-proportional fonts only for special purposes, such as distinguishing source code text. The Press 10-point font available to users of Script is a good substitute for Times Roman. If Times Roman is not available, try the font named Computer Modern Roman. On a Macintosh, use the font named Times.
Title and Authors
The title (Helvetica 18-point bold), authors' names (Times New Roman 12-point bold) and affiliations (Times New Roman 12-point not-bold) run across the full width of the page. We also recommend you add your e-mail address using the affiliations style. If only one address is needed, center all address text. For two addresses, use two centered tabs, and so on. For more than three authors, you may have to improvise. 
Abstract and Keywords
Every submission should begin with an abstract of about 100 words, followed by a set of keywords. The abstract should be a concise statement of the problem, approach, findings, and conclusions of the work described.
References and Citations
Use the standard APA format for references – that is, a list at the end of the article, ordered alphabetically by first author, and referenced by publication year in parentheses. See the examples of references at the end of this document. Within this template file, use the style named references for the text of your references. Within your text, cite the references with (author, year).
References should be published materials accessible to the public. Internal technical reports may be cited only if they are easily accessible (i.e., you give an Internet address within your citation). Proprietary information may not be cited. Private communications should be acknowledged, not referenced, e.g., “(Robertson, personal communication).”
Page Numbering, Headers and Footers
Do NOT include headers, footers or page numbers in your submission. These will be added when the publications are assembled.
SECTIONS
The heading of a section should be in Helvetica 12-point bold in all-capitals. Sections should NOT be numbered.
Subsections
The heading of subsections should be in Helvetica 10-point bold with only the initial letters capitalized. (Note: For sub-sections and sub-subsections, a word like the or a is not capitalized unless it is the first word of the heading.)
Sub-subsections
The heading for sub-subsections should be in Helvetica 10-point italic with initial letters capitalized.
FIGURES
Figures should be inserted at the appropriate point in your text. Each figure should have a figure caption in Normal Times New Roman 10 point font.
Please note that the papers will be printed in black and white. Therefore you should make sure that all graphics look good in black and white. You may use colored figures for the sake of the version on the Web, as long as it also looks good in grayscale.
LANGUAGE, STYLE AND CONTENT
Please make sure that your paper is in clear, readable, proper English. Have it reviewed by a professional technical writer or native English speaker.
Spelling and punctuation may consistently use any dialect of English (e.g., British, Canadian or US). Hyphenation is optional. Please write for an international audience:
•	Write in a straightforward style. Use simple sentence structure. Try to avoid long sentences and complex sentence structures. Use semicolons carefully.
•	Use common and basic vocabulary (e.g., use the word “unusual” rather than the word “arcane”).
•	Briefly define or explain all technical terms.
•	Explain all acronyms the first time they are used in your text.
•	Explain local references (e.g., not everyone knows all city names in a particular country).
•	Explain “insider” comments. Ensure that your whole audience understands any reference whose meaning you do not describe (e.g., do not assume that everyone has used a Macintosh or a particular application).
•	Explain colloquial language and puns. Understanding phrases like ”red herring” requires a cultural knowledge of English. Humor and irony are difficult to translate.
•	Use unambiguous forms for culturally localized concepts, such as times, dates, currencies and numbers (e.g., “1-5-99” or “5/1/99” may mean January 5th or May 1st, and “seven o'clock” may mean 7:00 am or 19:00).
•	Be careful with the use of gender-specific pronouns (he, she) and other gendered words (chairman, manpower, man-months). Use inclusive language (e.g., she or he, s/he, they, chair, staff, staff-hours, person-years) that is gender-neutral. If necessary , you may be able to use “he” and “she” in alternating sentences, so that the two genders occur equally often. See (Schwartz, et al., 1995) for further advice and examples regarding gender and other personal attributes.
ACKNOWLEDGMENTS
We thank Gerry Stahl of CSCL 2002 who wrote an earlier version of this document. 
REFERENCES
Anderson, R. E. (1992) Social impacts of computing: Codes of professional ethics. Social Science Computing Review, 10, 2, 453-469.
Conger., S., and Loch, K. D. (Eds.) (1995) Ethics and computer use. Communications of the ACM, 38, 12 (entire issue).
Mackay, W. E. (1995) Ethics, lies and videotape. Proceedings of CHI '95 (Denver, CO, May 1995), ACM Press, 138-145.
Schwartz, M., and Task Force on Bias-Free Language (1995) Guidelines for Bias-Free Writing. Indiana University Press, Bloomington, IN.