ComSIS Latex Intructions
ComSIS Latex Intructions
DOI: N/A
Abstract. The abstract should summarize the contents of the paper and should
contain at least 70 and at most 150 words. It should be set using the abstract
environment.
Keywords: computer science, information systems, LATEX, typesetting.
1. Introduction
These instructions and the corresponding LATEX style are based on the corresponding
Springer instructions and LATEX document class for preparing camera ready papers to be
published in the Springer series Lecture Notes in Computer Science.
The preparation of manuscripts which are to be reproduced by photo-offset requires
special care. Papers submitted in a technically unsuitable form will be returned for retyping, or canceled if the volume cannot otherwise be finished on time.
2. Manuscript Preparation
You are encouraged to use LATEX for the preparation of your camera-ready manuscript
together with the corresponding document class comsis.cls (see Sect. 3), and send all necessary source files. Please follow these instructions closely in order to make the volume
look as uniform as possible. Please also send a corresponding pdf file.
We would like to stress that the class/style files should not be manipulated and that
the guidelines regarding font sizes and format should be adhered to. This is to ensure that
the end product is as homogeneous as possible.
Example
Authors Instructions. . .
1. Introduction
LATEX command
\title
\section
\subsection
\subsubsection
\paragraph
Here are some examples of headings: Criteria to Disprove Context-Freeness of Collage Languages, On Correcting the Intrusion of Tracing Non-deterministic Programs
by Software, A User-Friendly and Extendable Data Distribution System, Multi-flip
Networks: Parallelizing GenSAT, Self-determinations of Man.
Lemmas, Propositions, and Theorems. The numbers accorded to lemmas, propositions,
and theorems etc. should appear in consecutive order, starting with the number 1, and not,
for example, with the number 11.
2.3. Figures and Photographs
Please produce your figures electronically, if possible, and refer to them from your source
file using, for example, the \includegraphics command from package graphicx.
Format the figures using the standard figure environment, and center them horizontally.
Authors Instructions
Check that in line drawings, lines are not interrupted and have constant width. Grids
and details within the figures must be clearly readable and may not be written one on
top of the other. Line drawings should have a resolution of at least 800dpi (preferably
1200dpi). For digital halftones 300dpi is usually sufficient. The lettering in figures should
have a height of 2mm (10-point type). Figures should be scaled up or down accordingly.
Please do not use any absolute coordinates in figures. If possible, the files of figures (e.g.
eps files) should not contain binary data, but be saved in ASCII format.
Figures should be numbered and should have a caption which should always be positioned under the figures, in contrast to the caption belonging to a table, which should
always appear above the table. The final sentence of a caption, be it for a table or a figure,
should end without a period. The \caption command will center the captions between
the margins and set them in 9-point type (Fig. 1 shows an example). The distance between
text and figure should be about 8mm, the distance between figure and caption about 5mm.
Fig. 1. One kernel at xs (dotted kernel) or two kernels at xi and xj (left and right) lead to
the same summed estimate at xs . This shows a figure consisting of different types of lines.
Elements of the figure described in the caption should be set in italics, in parentheses, as
shown in this sample caption. The last sentence of a figure caption should generally end
without a period
Remark 1. In the printed volumes, illustrations are generally black and white (halftones),
and only in exceptional cases, and if the author is prepared to cover the extra cost for color
reproduction, are color pictures accepted. If color illustrations are necessary, please send
us color-separated files if possible. Color pictures are welcome in the electronic version
at no additional cost.
(1)
Please punctuate a displayed equation in the same way as ordinary text but with a
small space before the end punctuation.
2.5. Program Code
Program listings or program commands in the text are normally set in typewriter font
(Courier).
Example of a Computer Program from Jensen K., Wirth N. (1991) Pascal user manual
and report. Springer, New York:
program Inflation (Output)
{Assuming annual inflation rates of 7%, 8%, and
10%,...
years};
const MaxYears = 10;
var
Year: 0..MaxYears;
Factor1, Factor2, Factor3: Real;
begin
Year := 0;
Factor1 := 1.0; Factor2 := 1.0; Factor3 := 1.0;
WriteLn(Year 7% 8% 10%); WriteLn;
repeat
Year := Year + 1;
Factor1 := Factor1 * 1.07;
Factor2 := Factor2 * 1.08;
Factor3 := Factor3 * 1.10;
WriteLn(Year:5,Factor1:7:3,Factor2:7:3,
Factor3:7:3)
until Year = MaxYears
end.
2.6. Footnotes
The superscript numeral used to refer to a footnote appears in the text either directly
after the word to be discussed or in relation to a phrase or a sentence following the
Authors Instructions
punctuation sign (comma, semicolon, or period). Footnotes are set at the bottom of the
normal text area, with a line of about 5cm immediately above them.5
2.7. Citations
The list of references is headed References and is not assigned a number in the decimal
system of headings. The list should be set in small print and placed at the end of your
contribution, in front of the appendix, if one exists. Please do not insert a pagebreak before
the list of references if the page is not completely filled. An example is given at the end
of this information sheet. For citations in the text please use the \cite command, and
organize your references using BibTEX, with \bibliographystyle{splncs03},
producing numbered citations in square brackets, such as: [1], [2], [3], . . .
2.8. Page Numbering and Running Heads
Page numbers and running heads are automatically generated by LATEX. If the title of your
paper is too long for the header please specify a running title using the \titlerunning
command. Other parameters will be allocated by the publisher.
2.9. Printing Quality
You are normally not expected to send a printed copy of your manuscript if you provide
the source and pdf files matching exactly each other when printed. Only in exceptional
cases, you will be asked to send sheets which are printed on one side only. In such a case,
please use a high-resolution printer, preferably a laser printer with at least 300dpi. We
prefer the text to be centered on the pages (i.e., equal margins left and right and top and
bottom). The format of the paper (A4, Letter, etc.) is irrelevant.
3. Using LATEX
We encourage using LATEX for preparing final manuscripts. We provide the document class
comsis.cls to help LATEX users prepare their camera-ready manuscript and to enable us to
use their source files. The necessary style files and documentation can be downloaded
from the ComSIS Web page at http://www.comsis.org/information.php.
4. Supplementary Material
If you wish to include color illustrations in the electronic version in place of or in addition
to any black and white illustrations in the printed version, please provide the managing
editor and the editorial assistant with the appropriate files.
If you have supplementary material, e.g., executable files, video clips, or audio recordings, on your server, simply send the managing editor and the editorial assistant a short
description of the supplementary material and inform them of the URL at which it can be
5
The footnote numeral is set flush left and the text follows with the usual word spacing. Second
and subsequent lines are indented. Footnotes should end with a period.
found. We will add the description of the supplementary material to the online version of
the corresponding ComSIS volume and create a link to your server. Alternatively, if this
supplementary material is not to be updated at any stage, then it can be sent directly to the
managing editor and the editorial assistant, together with all the other files.
5. Copyright Form
For details regarding the transfer of copyright, please see the Copyright and Use Agreement section under Information for Contributors at the ComSIS Web page. Generally,
we ask contributing authors to complete and sign the Transfer of Copyright agreement
before the paper may be published. (It is sufficient if one author from each contribution
signs the form on behalf of all the other authors.) The copyright form is located on our
Web page at http://www.comsis.org/download/ComSISCopyright.doc.
The printed form should be completed and signed and sent to the editorial assistant by
normal mail. Alternatively, a scanned copy of the form may be sent by e-mail.
6. Checklist
When submitting your camera-ready manuscript to the managing editor and the editorial
assistant, please make sure you include the following:
your source (input) files, including the figures;
a single-sided printout (not a photocopy) of the final version of your contribution, if
requested by the managing editor;
any style files, templates, and special fonts you may have used;
the completed and signed copyright form.
If supplementary material is available, please provide the editorial assistant with:
a short description of the supplementary material;
the supplementary material or the URL at which it can be found;
the files of color figures for the electronic version.
References
1. Agrawal, R., Srikant, R.: Fast algorithms for mining association rules. In: Proceedings of the
20th International Conference on Very Large Databases. pp. 487499. Morgan Kaufmann, Santiago, Chile (1994)
2. Bruce, K.B., Cardelli, L., Pierce, B.C.: Comparing object encodings. In: Abadi, M., Ito, T. (eds.)
Theoretical Aspects of Computer Software, Lecture Notes in Computer Science, vol. 1281, pp.
415438. Springer-Verlag, Berlin Heidelberg New York (1997)
3. Garcia-Molina, H., Ullman, D.J., Widom, J.: Database Systems: The Complete Book. Prentice
Hall, New Jersey, USA (2002)
4. van Leeuwen, J. (ed.): Computer Science Today. Recent Trends and Developments, Lecture
Notes in Computer Science, vol. 1000. Springer-Verlag, Berlin Heidelberg New York (1995)
5. Ribicre, M., Charlton, P.: Ontology overview. Motorola Labs, Paris (2002), [Online]. Available:
http://www.fipa.org/docs/input/f-in-00045/f-in-00045.pdf (current October 2003)
6. Wang, X., Bettini, C., Brodsky, A., Jajoida, S.: Logical design for temporal databases with multiple granularities. ACM Transactions on Database Systems 22(2), 115170 (1997)