How to Publish in J.UCS Hermann Maurer (Graz University of Technology, Austria hmaurer@iicm.tu-graz.ac.at) Klaus Schmaranz (Graz University of Technology, Austria kschmar@iicm.tu-graz.ac.at) Abstract: J.UCS - the Journal for Universal Computer Science is an electronic hypermedia journal. This paper is a guide for authors who want to submit articles to J.UCS. Since J.UCS has to be able to deal with articles of many different wordprocessing systems we accept PostScript as primary format, but further interfaces for HTF, LaTeX and DVI are provided. A special style sheet for J.UCS authors was designed to ensure a uniform layout of articles published in J.UCS and to make the task of automatic creation of hyperlinks easier. NOTE: The first test issue of J.UCS (vol. 0, no. 0) will appear November 94. Regular service - for which submissions are solicited as of now - will start January 95. Key Words: J.UCS, Hyper-G, style sheet, file formats, electronic journals, electronic publishing Category: A.0 1 Introduction J.UCS - the Journal for Universal Computer Science will be published in 12 yearly issues starting January 1995. Research contributions and in depth survey in all areas of computer science are welcome. J.UCS can be read (and individual contributions printed) using one of the Hyper-G clients that are available, free of charge, by anonymous ftp at iicm.tu-graz.ac.at. To peruse J.UCS you do not log into one particular server but you can choose a server geographically convenient for you. Indeed, organisations are encouraged to install their own J.UCS server (the necessary software is also available free of charge). For more information on J.UCS in general send an (empty) email to JUCS@iicm.tu-graz.ac.at, Subject: [info]. For more information on how to use J.UCS send an (empty) email to JUCS@iicm.tu-graz.ac.at, Subject: [howto]. To obtain the latest version of the style sheet send an (empty) email to JUCS@iicm.tu-graz.ac.at, Subject: [format]. To subscribe to regular informations on J.UCS send an (empty) email to JUCS@iicm.tu-graz.ac.at, Subject: [subscribe]. To unsubscribe from these informations send an (empty) email to JUCS@iicm.tu-graz.ac.at, Subject: [unsubscribe]. Send submissions to J.UCS as email (if necessary uuencoded) to JUCS@iicm.tu-graz.ac.at, Subject: [submissions]. For a list of acceptable file formats see [Chapter 3]. A very wide variety of wordprocessing systems can be used for writing articles since our preferred file format is PostScript and nearly every wordprocessor has at least a PostScript printer driver. Other formats accepted are RTF, LaTeX and DVI. However, since J.UCS contributions cannot only be viewed and printed on a variety of platforms, but J.UCS is also available from Springer both in printed form and on CD-ROM it is essential that certain conventions are strictly followed as set out in the style sheet below. Note that contributions in J.UCS can be annotated. The process of annotation and of adding additional hypermedia links will be described in a contribution in Volume 0 of J.UCS [see Maurer and Schmaranz (1994)] that will be available end of November 94. This volume will also contain much further information on the philosophy, on J.UCS editors and servers and on technical details and future extensions of J.UCS 2 Style Sheet The style sheet for J.UCS described in this chapter is to be used as template for articles published in J.UCS. Following the rules proposed here enables us to have a uniform layout for J.UCS and to automate the steps necessary to convert a submitted article to a finished hypermedia document. Please note that this article itself is written following our style guidelines, with exception of the font rules, since the distribution is done as plain ASCII text. 2.1 Page Layout Use a printing area of 12.2 x 19.3 cm (4.8 x 7.6 in). Use only a one-column layout. Place pictures, figures and tables centered between the margins without any text flowing around them. Do not start a new page for new sections (chapters) or subsections. Do not insert page numbers; they are assigned by the volume editor. Also notice that no form of running heads is allowed. Use footnotes only, if it is unavoidable. 2.2 Structure 2.2.1 Title The title part of a paper consists of the title itself, capitalized, unnumbered and centered between the margins (by capitalized we mean that all words except for short connectives should start with a capital letter). Use a serif typeface (e.g. Times), 14 point, bold as font for the title. Leave 2 blank lines after it. Next come the authors, capitalized and centered between the margins, in the form First Name Second Name. Multiple authors should be delimited by a single blank line. Use a serif typeface (e.g. Times), 10 point. Every author is followed by his/her location and email address, centered between the margins. Use a serif typeface (e.g. Times), 9 point. Leave at least three blank lines after the last author. Please do not put any acknowledgements or thanks here, but place them in the optional Acknowledgement section at the end of the document. Example: The Knowledge of Special Formats Aladin Claus Wonko (University of Auckland, New Zealand awonko@cs.aukuni.ac.nz) Fojin Tsio (Graz University of Technology, Austria ftsio@iicm.tu-graz.ac.at) 2.2.2 Abstract Start the abstract with the sequence "Abstract:" (without the quotes) in 9 point bold-face without a line break after "Abstract:". Since readers can just look at the abstract in a "browsing" mode, the Abstract is obligatory and should contain enough information about the text to decide whether accessing further parts of the document makes sense (Note: we don't have superfast information highways everywhere yet). 2.2.3 Key Words and Categories Either a key words section or a category section or both is necessary for the volume editor to decide to which category the article belongs. For this purpose start a new line in the abstract and precede this line with either the sequence "Key Words:" or the sequence "Category:" in 9 point bold-face. The category must be one of the categories used in ACM Computing Reviews. A complete overview of the possible categories is given in every January edition of ACM Computing Reviews [see ACM 1994]. We prefer if you specify categories, since reviewers will be selected on that basis. If you use key words only, the managing editor of J.UCS may erroneously assign the wrong reviewers, making the reviewing process less reliable and longer, and making it more difficult to locate papers in a certain area. Observe, that J.UCS viewers will support, among other search criteria, boolean combinations of ACM Computing Reviews categories. 2.2.4 Text The text part of an article contains structured text, divided into numbered sections (chapters), starting usually with "1 Introduction", that may be subdivided. Please use expressive section names. 2.2.5 Literature References Start the literature references with the single numbered first level header "References" (see [2.3.1 Headings] below for a detailed description of the first level header format). 2.2.6 Acknowledgements This is an optional section. Put every form of thanks and acknowledgements here. Start the acknowledgements section with the sequence "Acknowledgements" in 10 point bold-face, left justified, followed by a single blank line. 2.3 Typeface and Size 2.3.1 Headings: Use a typeface with serifs for all levels of headings. It is recommended to use Times or a similar typeface. Leave sufficient place for the title to stand out clearly. Leave 2 lines blank above and 1 line below the headings. If a heading is directly followed by a lower level heading the 2 blank lines before the lower level heading should be omitted. All headings should be capitalized (i.e. all words except for short connectives should have a capital initial). The title should be centered between the margins, all lower level headings should be left-justified. Font sizes, numbering and styles for the different types of headings: Title: unnumbered, centered, 14 point, bold Example: Computer Theory (centered) 1st-level heading: single numbered, left-justified, 12 point, bold Example: 1 Introduction 2nd-level heading: double numbered, left-justified, 10 point, bold Example: 2.2 Flow Charts 3rd-level heading: triple numbered, left-justified, 10 point, bold Example: 2.2.1 Nodes 4th-level heading: quadruple numbered, left-justified, 10 point, italic Example: 2.2.1.2 Input Nodes 2.3.2 Running Text: Use a typeface with serifs for running text. It is recommended to use Times or a similar typeface. Use 10-point type size and one line spacing for normal text and 9-point type size for small text (abstract, literature references and acknowledgements). Use italic print to emphasize words. Note: bold type and underlining should be avoided. The text should always be justified to occupy the full line width, so that the right margin is not ragged. 2.3.3 Computer programs: For Computer programs both sans-serif and serif typefaces are allowed. Use 10-point type size and one line spacing. 2.4 Special Formats 2.4.1 Markups Insert the sequence "[ Name <(>year<)>]" (without the quotes) into the running text for a markup to a literature reference. Name is the second name of the author and year is the year of printing. Also a markup to several authors is allowed. In this case the single authors must be delimited either by commas or the word "and". The phrase "et al." is also valid. The year can either be written in short form or in long form (i.e. 92 and 1992 are both valid entries) is a possible lower case literal, if you refer to more than one article of an author of the same year. The word "see" and the brackets around the year are optional. Example: ...this special form [see Wonko and Tsio 1999b] is very... ...as described in [Wonko (99a)]... ...and this algorithm [Tsio et al. 1999c] is used... Insert the sequence "[ Fig. n]" (without the quotes) into the running text for a markup to a Figure contained in the current document. Insert the sequence "[ Tab. n]" (without the quotes) into the running text for a markup to a table contained in the current document. When placing a markup to a chapter of the actual document use either the form [ Chapter n] or [ Section n] or refer to the section name by using the special sequence [
n SectionName] or [ n SectionName]. Example: ...we will discuss this later in [Chapter 4]. ...see [Section 4] for further details on... ...see [Chapter 4 Publishing] for further details on... ...chapter [4 Publishing] provides more information... For a markup to a footnote use the form [ n], where n is the unique number of the footnote [see 2.4.5 Footnotes]. Please note that footnotes should only be used when unavoidable. Please use exactly the format given here to allow us to insert Hypertext links automatically by searching for these special sequences. (Note: everything enclosed in '<' and '>' is optional.) 2.4.2 Literature References: Every Reference must start with the sequence "[Name <(>year<)>]" (without the quotes). Name and year must match the markup in the running text [see 2.4.1 Markups] to be able to automatically detect the matching markup-reference pairs. The single information fields of a Reference (Author1, Author2, Title...) should be divided by commas or semicolons. The brackets around the year are optional. Four examples for the different main types of documents should serve as a template: - referencing Books: [Goll (99)] Goll, J.: "The Guide to Hyper-G"; Springer, Heidelberg / New York (1999) - referencing Journals: [Wonko and Tsio 99b] Wonko, A. C., Tsio, F.: "Extended Use of Hyperlinks"; J.UCS (Journal for Universal Computer Science), 5, 3 (1999), 225-327. The form 5, 3 (1999) indicates volume number 5, issue number 3 1999. 225-327 indicate the page numbering. - referencing Proceedings: [Tsio 99a] Tsio, F.: "Hypermedia Systems in the Future"; Proc. Ed-MEDIA'99, AACE Publishing, Vancouver (1999), 115-123. - referencing Reports: [Mollester, Goll 99c] Mollester, K., Goll, J.: "Information Landscapes and their Advantages in Large Hypermedia Systems"; IIG Report 998, Graz, Austria (1999), also appeared as electronic version, anonymous FTP autnet.org, in publications/June-99-online. 2.4.3 Figures: Center the figures between the margins with one blank line above. Insert the text "Figure n: description" (without the quotes) after each Figure (n is a unique number that identifies the figure; description is a short description about the contents of Figure n. Please use an expressive description for your figures to allow finding them in a keyword search). Use a 10 point italic font for this text. 2.4.4 Tables: Center the tables between the margins with one blank line above. Insert the text "Table n: description" (without the quotes) after the table (n is a unique number that identifies the table; description is a short description about the contents of Table n. Please use an expressive description for your figures to allow finding them in a keyword search). Use a 10 point italic font for this text. 2.4.5 Footnotes: Seperate footnotes from the preceding main text by a line from the left to the center of the page. Start the footnote with the sequence "[n]", where n is the unique number of that footnote (unique means, that this number can only appear once on a page, not throughout the whole document). Use a 9 point font for footnote text. Example: _________________________________ [1] as we mentioned earlier this is how to write footnotes 3 Accepted File Formats To provide an interface to a wide variety of wordprocessors we decided to accept PostScript as our main file format. However you can also submit articles as RTF, LaTeX or DVI files. Submitted files can be compressed using the following methods: compress, gzip, zip, arj, arc, pak, zoo, lzh. You should not have problems generating a file in one of those formats, no matter which wordprocessor you are using. When submitting a file, please follow the rules given below, allowing us to be able to read and convert your article. 3.1 PostScript You MUST include every font information in the PostScript output file to make sure that all the fonts are available for us when converting the document. Depending on the program you use for generating the PostScript file there is either a commandline switch for this purpose, or in the case you generate the file with a printer device driver there should be an option not to use built in printer fonts, but download all Fonts instead. MS-Windows Users: We tested all PS Printer Drivers available to us, and they all worked. But be careful when configuring your printer driver - There MUST be a PS Header sent with the printing job. - You MUST use the substitution table for fonts and and you MUST enter "download font" for every font used in the document. DVIPS users: No problems were detected, the only thing is that you MUST NOT use the M option. If you want to make sure that the document you submit is in the correct format, you may try, whether ghostscript (or ghostview) can correctly deal with it, since ghostscript is the kernel of our conversion software. Ghostscript is a PostScript Interpreter available on many ftp servers worldwide for various platforms including most of the UNIX derivates, MS-Windows, OS/2 and Windows-NT. You may also submit a testfile (e.g. the first page of the paper) as email to JUCS@iicm.tu-graz.ac.at with the Subject [testfile]. We will test its compatibility to our conversion software and send you an email about the test result. 3.2 RTF Please use common fonts found on most computers. Please do not use decorative typefaces. 3.3 LaTeX If you use a special LaTeX style file, please submit it together with your article. We recommend to use our prepared style sheet for J.UCS you can obtain by sending email to JUCS@iicm.tu-graz.ac.at, Subject: [latex]. This style file will be ready by 08-1994. 3.4 DVI Please use common fonts found on most computers. Please do not use decorative typefaces. 4 References [Maurer and Schmaranz 1994] Maurer, H., Schmaranz, K.: "J.UCS - The Next Generation in Electronic Journal Publishing"; J.UCS (Journal for Universal Computer Science) 0, 0 (1994), 2-20. [ACM 1994] "The Full Computing Reviews Classification System"; Computing Reviews 35, 1 (1994), 6-16. Acknowledgements We acknowledge the kind permission of ACM to use their classification system and the fact that ACM is actively encouraging J.UCS by operating a foundation server.