Important dates

Deadline for submission (extended)
April 29th, 2016
Notification to authors
June 1st, 2016
Camera-ready version
June 15th, 2016
July 25th-28th, 2016


Authors are invited to submit papers presenting original and unpublished research. The proceedings will be published in the Springer-Verlag Lecture Notes in Computer Science Series (LNCS).


Simultaneous submission to journals or other conferences with published proceedings is not allowed. Extended versions of selected papers from the proceedings will appear in a special issue of the International Journal of Foundations of Computer Science (IJFCS).

Submitted papers should not exceed 12 pages and should follow the LNCS-style LaTeX2e. All proofs omitted due to space constraints should be given in an appendix or made accessible through a reliable link to a freely available electronic preprint. Papers should be submitted electronically in PDF through the EasyChair system:


Final paper instructions

Preparation steps

  • Please take carefully into account the suggestions of the reviewers and make the necessary modifications to your paper.
  • Follow the technical instructions (described in the next section); prepare your bibliography using BibTex together with the style splncs03.bst provided by Springer.
  • There is a strict limit of 12 pages. This limit can not be exceeded in any case.
  • Fill in the copyright form. It is sufficient for one of the authors to sign the copyright form.
  • Pack your working files (tex file(s), pictures, splncs03.bst, a bibliography (.bib) file, the signed copyright form and a pdf version of your paper) into a zip archive named, where XX is the number of your submission in the Easychair system. Make sure that all files are in the same directory (i.e. there is no subdirectory). Also, for sake of simplicity for the editors, please rename the main tex file by main.tex.
  • Send your archive to
  • At least one author per paper should register.

Technical instructions

Instructions for LNCS authors are available here. Before submitting your files please verify the following checkpoints. The next recommendations follow the order we construct our document.

  • Use as few .tex files as possible, a single file is best, name it main.tex, it helps the assembling task.
  • Use \documentclass[runningheads, envcountsame, a4paper]{llncs} and only these options; some packages modify the paper format to letter if a4 is not specified.
  • pdflatex processes a bit better than the sequence latex, dvips, pspdf. You might find useful to add \usepackage{epstopdf}, \usepackage[hyphens]{url} and \usepackage{microtype}.
  • Titles: In English, the first word and the last word of titles should be capitalized. In addition, all nouns, pronouns, adjectives, verbs, adverbs, and subordinate conjunctions should be capitalized. Articles and coordinating conjunctions are not capitalized. Traditionally, prepositions are not capitalized. Use the same conventions for all titles of sections, subsection, etc.
  • In \author use \and as separator between authors names.
  • Give all the affiliation, department, university, street address, country, e-mail.
  • In email if you use {author1,author2,...}@... please use \email{$\{$author1,... $\}$@...}.
  • Use \fnmsep (i.e. footnote mark separator) to separate \thanks by \inst.
  • \titlerunning could be shorter than the title, please check to see if it fits in the header, if not, then you should shorten it up.
  • Inside the \authorrunning{} field of your article, please use only the initial of your first name, followed by a dot. The word "and" between two authors is used without a comma. If there are three or more authors, there is a comma before "and". If headings with author names are not fitting well in the page, then you should use "et al." after the first author.
  • Use \toctitle and \tocauthor, they are important fields defining your paper in the proceedings Table Of Contents.
  • For \tocauthor use ~ between first name and name to avoid a break line inside author's names.
  • After \maketitle, add \setcounter{footnote}{0} to start footnotes from 1 after \thanks.
  • LNCS recommends keywords, within the abstract (before \end{abstract} just type \keywords{your list}. The new LNCS style has internally defined this command. Do not newcommand{keywords}... (not needed titlecase for keywords). Please , use significant keywords.
  • Normally, captions of tables, figures, should end without a dot. If you feel that dots are needed, please be consistent along the whole article. Table captions are above the tables, while figures have captions below.
  • For Acknowledge please use \section*.
  • Please use BIBTEX: it is a computer program taking care about consistency of bibliography, (within the paper and cross papers). For information about using BIBTEX please consult this link. There exists also an automatic conversion tool from bibitem to bibtex, yet not all formats are recognized. Note that Googling for a title together with the word "bibtex" usually gives good results.
  • Check the names in bibliography, some accents could be missing, no capital letter for Turing, RNA, etc., wrong hyphenations, etc. To correct we should add a new level of {...} in the bib file.
  • Check spelling errors and English mistakes for the whole paper. You are the last one checking for spelling errors before your paper is published.
  • Do not change the default font of the document (that is do not \usepackage{times} or other fonts), or use too many variations on fonts.
  • Do not \usepackage[...]{babel}.
  • Do not use whatever fancy signs as in mathabx.
  • Do not modify \qed.
  • Do not use a4wide or geometric.
  • Avoid using \vspace, and in any case \vspace with a negative argument. If things are not going as we wish, instead of negative \vspace there should be another solution.
  • Do not use \newpage for formatting reasons, trying to fit floating figures or tables.
  • Do not use frames around figures, algorithms, other elements of your paper.
  • Do not use a complicated directory structure for your document, usually for a short paper things can be solved with a single source file.