TOP
Search the Dagstuhl Website
Looking for information on the websites of the individual seminars? - Then please:
Not found what you are looking for? - Some of our services have separate websites, each with its own search option. Please check the following list:
Schloss Dagstuhl - LZI - Logo
Schloss Dagstuhl Services
Seminars
Within this website:
External resources:
  • DOOR (for registering your stay at Dagstuhl)
  • DOSA (for proposing future Dagstuhl Seminars or Dagstuhl Perspectives Workshops)
Publishing
Within this website:
External resources:
dblp
Within this website:
External resources:
  • the dblp Computer Science Bibliography


LIPIcs image

Leibniz International Proceedings in Informatics (LIPIcs)


LIPIcs - Leibniz International Proceedings in Informatics is a series of high-quality conference proceedings across all fields in informatics established in cooperation with Schloss Dagstuhl - Leibniz Center for Informatics.

Publications
LIPIcs webportal: Archive of all published LIPIcs volumes.
LIPIcs @ dblp
Aims and Scope
The LIPIcs series aims at the provision of an OpenAccess and low cost publication venue for high-quality conferences. Key features of LIPIcs are
  • OpenAccess availability along with moderate fees for the conference organizers, and
  • the editorial selection by its international and renowned editorial board.
The scope of LIPIcs covers all fields of informatics.

Open Access Policy
LIPIcs volumes are peer-reviewed and published according to the principle of OpenAccess, i.e., they are available online and free of charge. The authors retain their copyright.
License
Each article is published under a Creative Commons CC BY license (http://creativecommons.org/licenses/by/4.0/).
The metadata provided by Dagstuhl Publishing on its webpages, as well as their export formats (such as XML or BibTeX) available at our website, is released under the CC0 1.0 Public Domain Dedication license (https://creativecommons.org/publicdomain/zero/1.0/legalcode).

Processing Charge
  • We charge the total cost of the entire volume to the conference organisation. We do not charge individual authors.
  • Processing Charge of 60 EUR (net) ...
    • per published paper (if the average count of main text1 pages per article is ≤ 20)
    • per block of 20 main text pages (otherwise).
  • To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then:

    Total cost(entire volume) = max(n,floor(P/20)) * APC (net).


ISSN
1868-8969
Identifier
Each volumes is assigned an ISBN and a DOI.
Each article is assigned a DOI and a URN.
To facilitate author identification, the Open Researcher and Contributor ID (ORCID) is optionally included during upload so that authors can be uniquely linked to their ORCID iD.

Longterm Preservation
The digital archiving of each volume is done in cooperation with the Deutsche Nationalbibliothek/German National Library (http://www.dnb.de).

Publication Ethics
Dagstuhl Publishing as the publisher of the series adheres to the Core Practices of the the Committee on Publication Ethics (COPE) and the Guidelines for Safeguarding Good Research Practice released by the German Research Foundation (Deutsche Forschungsgemeinschaft - DFG). We expect all parties (so authors, editors, and reviewers) involved in the publication and review process of contributions to be published in the series to follow these core practises and the guidelines. Allegations of misconduct will be investigated in accordance with the COPE Best Practice Guidelines as far as is practicable. If notified of a potential breach of publication ethics, we encourage editors and authors to inform Dagstuhl Publishing contact as soon as possible.
Editorial Board

Constitution

The Scientific Advisory Board of Schloss Dagstuhl serves as a monitoring board for the Editorial Board.

In its initial configuration, the Editorial Board has 7 members, reflecting the setup of the two conferences that launched the LIPIcs series [1]: 6 belong to the main communities associated with these conferences, namely algorithms, automata, languages, combinatorics, logic and complexity. The 7-th member is the Scientific Director of Schloss Dagstuhl or his/her representative.

The Editorial Board elects its chairperson for a 2-year mandate, renewable twice. It is the chairperson’s responsibility to organize the Board’s deliberations in a timely fashion, and to record its decisions. An archive of the Editorial Board’s decisions is maintained by Schloss Dagstuhl.

Apart from the Scientific Director of Schloss Dagstuhl or his/her representative, the Editorial Board members have a 4-year mandate, renewable once. As an exception, three of the initial six members of the Editorial Board have a 6-year mandate, in order to ensure that the renewal of the Editorial Board is gradual. Former members may be nominated again, after a gap of at least 4 years.

New Editorial Board members must be selected when the mandate of current members terminates or when the Editorial Board needs to be expanded to include experts of branches of computer science not yet covered. In either case, new members are nominated and chosen by the current members of the Editorial Board, who will consult in the process Schloss Dagstuhl’s Scientific Advisory Board and relevant scientific associations. In the deliberation on the co-optation of new members of the Board, such considerations as nationality (or rather in which country one is professionally based) and gender shall also be taken into account, in order to avoid uniformity of any kind.

The Editorial Board functions as a whole and it is not its members’ mission to represent or defend a particular community. The Board’s deliberations are confidential and its decisions are reached by votes. The votes on selecting a new Board member or accepting a new conference in the LIPIcs series must be obtained with a 2/3 majority.

[1] FST&TCS (Foundations of Software Technology & Theoretical Computer Science) and STACS (Symposium on Theoretical Aspects of Computer Science)

Editorial Policy

The LIPIcs series will publish only high-quality conference proceedings, and the selection of these conferences is entrusted to the Editorial Board. The LIPIcs series is meant for recurring conferences, but isolated conferences of exceptional value may also be considered. In making its selection decisions, the Board will pay particular attention to the following criteria:

  • the international character of the conference (program committee, speakers, etc);
  • the attractiveness and selectivity of the conference (number of submissions, acceptance rate);
  • the importance of the conference in its domain;
  • whether the conference will justify indexation by all major relevant agencies (e.g., Clarivate CPCI, Elsevier Scopus, dblp).
In addition, the Editorial Board will examine
  • whether the steering committee of the conference is representative of a community or a professional association, and has an international composition;
  • the rules for the election of the members of the steering committee and the duration of their appointment.
The Editorial Board may also, at its discretion, make use of existing conference classifications (e.g. CORE, QUALIS, GII-GRIN-SCIE (GGS), etc.), of documents describing good practices (e.g. those from ACM SIGPLAN) and of any other relevant source of information.

Application Procedure for Conference Organizers

If the steering committee of a conference series is interested in publishing their proceedings as LIPIcs, please apply to LIPIcs Editorial Office at Dagstuhl.

An application is assumed to cover a 5-year period and should provide information related to the above mentioned criteria of the LIPIcs Editorial Policy. In particular, an application must give sufficient background on the conference, including:

  • information on the steering committee (members of the current steering committee, rotation policy, etc.),
  • the program committee,
  • list of related conferences and a description of how the event submitting the application differs from them,
  • the (expected) number of submissions and of accepted papers,
  • the peer-review process,
  • the expected attendance,
  • etc.

If the conference is part of a series, then the application should include those same elements of information on at least the three preceding editions of the conference, as well as links to the relevant websites and access to the proceedings of these past conferences.

The information concerning the application is passed on to the Editorial Board chair who consults the Editorial Board members and/or external experts, especially if the scope of the conference is not in the broad fields already represented in the series Editorial Board.

A positive decision for recurrent conferences is valid for (typically) five years. Afterwards a new application has to be made.


(Re-) Application

A (re-) application ideally contains the original application and a description of any changes with respect to the stated criteria, scope, nature of the proceedings, or organisation of the conference.


In Short
  • We charge the total cost of the entire volume to the conference organisation. We do not charge individual authors.
  • Processing Charge of 60 EUR (net) ...
    • per published paper (if the average count of main text1 pages per article is ≤ 20)
    • per block of 20 main text pages (otherwise).
  • To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then:

    Total cost(entire volume) = max(n,floor(P/20)) * APC (net).


Background info concerning APC
As a publicly funded institution, we have to recover the costs of our publishing activities so that there is no competitive advantage over commercial providers. For the cost recovery, we work with an article processing charge (APC), which currently is 60 EUR (net). This amount was set under the assumption that the average length of a paper does not substantially exceed 15 to 20 main text pages, i.e., number of pages after typesetting excluding title page and the bibliography.

Resulting Page-Limit Recommendation

Given the above, we suggest 20 main text pages1 as a page limit, which could for instance be in the form of 15 pages for the main body of paper plus up to 5 pages for appendices. Note that this is only a recommendation and it is up to the editors of the respective volume to decide on a policy regarding the page limit2.

Please read this letter from Raimund Seidel, explaining the background for the APC change over the years.

1 'Main-text pages' are all contents except the title page with title, authors, affiliations, abstracts, ..... and the bibliography.
2 Please note that we expect a certain flexibility concerning any page limit (+/- 1 page) to avoid too much extra effort to harmonize LIPIcs-compliant formatting and page limit for both authors and final typesetting by the LIPIcs Office.


Templates and Example Files

Please download the current version of the LIPIcs style along with an example file and detailed author instructions:

lipics-v2021 v2021.1.2

For older releases and an issue tracker, see our GitHub archive.


Typesetting instructions - Summary

LIPIcs - Leibniz International Proceedings in Informatics is a series of high-quality conference proceedings across all fields in informatics established in cooperation with Schloss Dagstuhl - Leibniz Center for Informatics.

In order to do justice to the high scientific quality of the conferences that publish their proceedings in the LIPIcs series, which is ensured by the thorough review process of the respective events, we believe that LIPIcs proceedings must have an attractive and consistent layout matching the standard of the series. Moreover, the quality of the metadata, the typesetting and the layout must also meet the requirements of other external parties such as indexing services, DOI registry, funding agencies, among others. The provided guidelines serve as the baseline for the authors, editors, and the publisher to create documents that meet as many different requirements as possible.

Please comply with the following instructions when preparing your article for a LIPIcs proceedings volume. (See Instructions for Authors for more details.)


Minimum requirements
  • Use pdflatex and an up-to-date LaTeX system.
  • Use further LaTeX packages and custom made macros carefully and only if required.
  • Use the provided sectioning macros: \section, \subsection, \subsubsection, \paragraph, \paragraph*, and \subparagraph*.
  • Provide suitable graphics of at least 300dpi (preferably in PDF format).
  • Use BibTeX and keep the standard style (\bibstyle{plainurl} ) for the bibliography.
  • Please try to keep the warnings log as small as possible. Avoid overfull \hboxes and any kind of warnings/errors with the referenced BibTeX entries.
  • Use a spellchecker to correct typos.

Mandatory metadata macros

Please set the values of the metadata macros carefully since the information parsed from these macros will be passed to publication servers, catalogues and search engines. Avoid placing macros inside the metadata macros. The following metadata macros/environments are mandatory:

  • \title and, in case of long titles, \titlerunning.
  • \author one for each author, even if two or more authors have the same affiliation.
  • \authorrunning (abbreviated first names) and \Copyright (concatenated full author names)
  • \ccsdesc (ACM 2012 subject classification)
  • \keywords (a comma-separated list of keywords).
  • \relatedversion (if there is a related version, typically the "full version"); please make sure to provide a persistent URL, e.g., at arXiv.
  • \begin{abstract}...\end{abstract}.

Please do not ...

Generally speaking, please do not override the style defaults concerning spacing, font and color settings. To be more specific, a short checklist also used by Dagstuhl Publishing during the final typesetting is given below. In case of non-compliance with these rules, Dagstuhl Publishing will remove the corresponding parts of LaTeX code and replace it with the defaults. In serious cases, we may reject the LaTeX-source and expect the corresponding author to revise the relevant parts.

  • Do not use a different main font. (For example, the times package is forbidden.)
  • Do not alter the spacing of the provided style file.
  • Do not use enumitem and paralist. (The enumerate package is preloaded, so you can use \begin{enumerate}[(a)] or the like.)
  • Do not use "self-made" sectioning commands (e.g., \noindent{\bf My Paragraph}).
  • Do not hide large text blocks using comments or \iffalse ... \fi constructions.
  • Do not use conditional structures to include/exclude content. Instead, please provide only the content that should be published - in one file - and nothing else.
  • Do not wrap figures and tables with text. In particular, the package wrapfig is not supported.
  • Do not change the bibliography style. In particular, do not use author-year citations. (The natbib package is not supported.)

This is only a summary containing the most relevant details. Please read the complete Instructions for Authors for all details and don't hesitate to contact Dagstuhl Publishing (publishing@dagstuhl.de) in case of questions or comments.


FAQ
Submission

In order to satisfy the standards of our series, please note that we expect an affiliation at least to contain a city and country (for locations in the United States also the state), so we usually don't support requests asking for removing this kind of information from an affiliation.

For organizations with multiple locations please choose the location where you have been most of the time physically when carrying out this work.

We hope that our completion of affiliations according to the above criteria facilitates the contacting of authors as well as the assignment of a work to individual locations, and - last but not least - serves the harmonization of affiliations across the entire volume.

An authorized user is any person (not necessarily an author) that has the permission to edit the paper. (Mostly, the list of authorized users is similar to the list of corresponding authors.) Please note:
  • Authorized users only appear within the Submission Server as far as the processing of the paper (submission, approval) is concerned.
  • They won't appear in the metadata of the published article! (The metadata will be read from the submitted LaTeX code instead.)
  • Authorized users marked with the symbol are already registered to the system. Users without this symbol have been invited to the system but have not created a user account yet.
  • Given the above, it is not necessary to synchronize name and email of authorized users in any way with the data of actual authors. (They rather synchronize automatically with the user accounts on the Submission Server).

At the beginning of the submission process, the submission system has only limited information about the actual authors of the article. But on each upload, the metadata of the paper (including authors) are updated. Before the publication, the authorized users are asked to confirm (or revise, if necessary) the metadata. In more detail:

  • Before the first successful upload of the LaTeX sources of an article, the list of authors shows the authorized users or corresponding authors (if available).
  • After each upload, the list of authors is temporarily extracted from the LaTeX sources. Since this automatic extraction could fail or be faulty, the final authors' information is only extracted by the Dagstuhl Publishing Team during the final typesetting and imported before Author Approval. During Author Approval, you can request corrections on these data.
  • Finally (usually 3 weeks before the publication), the authors are explicitly asked to approve the extracted metadata. At this stage, minor modifications or necessary corrections are still possible.
  • No LaTeX source submitted yet? Don't worry about any errors here. Every time you upload a LaTeX source, the list will automatically be updated according to the \author macros in your file.
  • Otherwise: Simply correct the \author macros in your LaTeX file and do a re-upload. If the error persists, please make sure that the \author macros are contained in the top level of your main LaTeX file (outside \if conditionals) and contain plain data (i.e. preferably no self-defined macros).
  • Note: In any case, Dagstuhl Publishing asks you to confirm/correct the metadata before the work is officially published.

Dagstuhl Publishing uses BibTEX to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}).

  • The bibliographical entries should be complete according to BibTEX standards, (no warnings or errors should occur).
  • Whenever possible, references should contain an external link, e.g., DOI (preferred) or URL
  • It is highly recommended to use dblp to enrich the references and, e.g., add missing DOIs.
  • Please do not change the bibliographic style! Author-year citations are not allowed. (So the natbib package is not supported by the current LIPIcs/OASIcs style.)
  • Unreferenced bibliography entries will be removed, \nocite{*} is forbidden.
  • Submitting a bbl-file only or an inline-bibliography is not sufficient.

Please note that in the metadata form there are funding fields at the bottom of each author block as well as a general funding field at the very bottom of the form (see "Additional Metadata").

In the PDF, all of these funding fields are merged to one funding block on the title page, where the author-specific funding fields are automatically preceded by the author's name.

Important! Please do not double funding information by repeating in the general field what is already contained in the author specific ones and vice versa.

As general rule of how to distribute funding information on the different fields consider the following: If a funding is clearly assigned to an author, please use the author-specific funding block. You should only deviate from this rule if the funding block on the title page of the PDF becomes unnecessarily long due to the fact that several authors have the same funding information.

Note that there is an automatic extraction of (most of the) metadata on every upload. On editing these metadata you have to distinguish two cases:
  • The values of the grey (disabled) input fields can only be modified by editing the LaTeX source code and performing a re-upload of the paper afterwards.
  • For your convenience, the values of the white input fields (if any) can be edited directly in the corresponding web-form (no re-upload needed). We will process these changes later during the final typesetting.

Since the automatic extraction could fail or be faulty, the final version of metadata will be extracted by the Dagstuhl Publishing Team after the typesetting is done.

In any case we ask you to confirm/correct the metadata before the work is officially published!

Please contact the editors of the respective volume concerning this question. It is up to them to decide on a policy regarding the page limit.

Note that there is a certain flexibility concerning any page limit (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and the Dagstuhl Editorial Office.

\relatedversion{...} may be used to denote a related version like a full version, extended version, or also a predecessor usually published in a reliable repository like arXiv or HAL.

As all metadata should be self-contained, please add a persistent URL, e.g. \relatedversion{A full version of the paper is available at \url{...}.}. This also simplifies the access for all readers. Additional to the URL, you might add a reference (\cite{...}).

Metadata should be self-contained as they are not only part of the document / PDF but also extracted and stored in a machine-readable format along with the actual document.

Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable / persistent file storage, we highly recommend to publish your document in a reliable repository like arXiv or HAL.

Please note that a subject classification contained in your LaTeX file may be considered invalid if we cannot literally match an entry from the 2012 ACM Computing Classification System in a \ccsdesc{...} macro in your LaTeX file. (That can have many causes.)

To save you the trouble of a new upload, please find the "Search ACM Classifications"-input field in the upload form. There you can search for the corresponding valid classification. (By using the last part of the intended classification as a search term one usually ends up with a good pre-selection.)

Note that invalid classifications will automatically be removed from the LaTeX code during the final typesetting by Dagstuhl Publishing.

Author Approval
  • During this period (of usually 3 working days) authors are shown a pdf preview of their paper along with the extracted metadata.
  • authors approve or ask for (minor) corrections
  • Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)
  • Dagstuhl Publishing checks the correction requests and revises the papers (if possible)
  • Authors are informed at an early stage on the dates and can authorize other persons to do the approval on behalf of them (if necessary).
  • Editors are not involved in this process, but can see the revisions in a change-log (during the editor approval step).

If you click on "Save and Finish Author Approval", we are notified about your request.

Then we check if the proposed changes can be implemented. (Do they comply with the standards of the series? Are there no consistency issues? Are there no technical limitations, e.g. charset problems, ...).

In case these checks are positive, we implement the changes both in the metadata (if necessary) AND in the LaTeX file.

In any case, even if we cannot make the requested changes, you will be informed by E-mail.


IMPORTANT! Please note that only minor corrections should be done at this stage. Here, "minor" also refers to the total number of changes. (We have already had inquiries with 50 change requests, most of them typos. Although each request is minor, the implementation is time-consuming in sum.) Requests that exceed our processing capacities and thus endanger the timely publication of the whole volume may be rejected.

As soon as some authorized user (usually you or your co-authors, if any) finishes the approval request and submits it to Dagstuhl Publishing (this happens at the end of Step 2), we are notified about your request.

Then we check if the proposed changes can be implemented. (Do they comply with the standards of the series? Are there no consistency issues? Are there no technical limitations, e.g. charset problems, ...).

In case these checks are positive, we implement the changes both in the metadata AND in the LaTeX file.


Note that, when submitting the approval, you can decide on if you want to see the changed document again or if you consider the document as approved after the changes have been made (without a further preview).


In any case, even if we cannot make the requested changes, you will be informed by E-mail.

Publication Workflow
  • During this period (of usually 3 working days) authors are shown a pdf preview of their paper along with the extracted metadata.
  • authors approve or ask for (minor) corrections
  • Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)
  • Dagstuhl Publishing checks the correction requests and revises the papers (if possible)
  • Authors are informed at an early stage on the dates and can authorize other persons to do the approval on behalf of them (if necessary).
  • Editors are not involved in this process, but can see the revisions in a change-log (during the editor approval step).
LaTeX Style

Here is an example of a completely filled author macro:

\author{John Q. Public}
{Institute of Pure Nonsense, Dummy University, Atlantis
 \and \url{http://www.myhomepage.edu}}
{johnqpublic@dummyuni.org}
{https://orcid.org/0000-0002-1825-0097}
{funded by the man in the moon.}

Please note:

  • Use full first and last name.
  • City and country belong to the minimum requirements on an affiliation.
  • If an author has several different affiliations, please clearly separate them with the keyword \and.
  • E-mail, ORCID, and funding are optional.
  • Author macros cannot be shared! Please use separate author macros even if two or more authors have the same affiliation!

This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:

\authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example}

Please...

  • abbreviate first names
  • in case of middle initials: use \, as illustrated in the example
  • be consistent with the \author macros
  • in case of 2 authors: concatenate with " and "
  • in case of 3 or more authors, see the sample for concatenation
  • in case of overfull \hboxes: use the name of the first author and "et al."

Dagstuhl Publishing uses BibTEX to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}).

  • The bibliographical entries should be complete according to BibTEX standards, (no warnings or errors should occur).
  • Whenever possible, references should contain an external link, e.g., DOI (preferred) or URL
  • It is highly recommended to use dblp to enrich the references and, e.g., add missing DOIs.
  • Please do not change the bibliographic style! Author-year citations are not allowed. (So the natbib package is not supported by the current LIPIcs/OASIcs style.)
  • Unreferenced bibliography entries will be removed, \nocite{*} is forbidden.
  • Submitting a bbl-file only or an inline-bibliography is not sufficient.

\ccsdesc{...} is for classification information following the ACM 2012 Computing Classification System. Sample usage:

\ccsdesc{Theory of computation~Proof complexity}
\ccsdesc{Theory of computation~Quantum complexity theory}

Please feel free to use our ACM 2012 Subject Finder to search for appropriate classifications and to generate the necessary LaTeX code.

Using this macro, you specify the copyright holder (appearing at the bottom of the title page) which is usually the team of authors. Sample usage:

\Copyright{John Q. Public, Adam E. Access, and Eve Example}

Please...

  • use full first and last names
  • be consistent with the \author macros
  • in case of 2 authors: concatenate with " and "
  • in case of 3 or more authors, see the sample for concatenation

This macro should be used to capture general (i.e. not author-specific) funding information.

If a funding can be clearly assigned to an author, please use the last part of the \author macro instead.

Sample usage:

\keywords{Theory of Everything, indefinite Metrics, abstract Nonsense}

Please note:

  • comma as delimiter
  • first word and every proper noun should be capitalized

\relatedversiondetails{...} may be used to denote a related version like a full version, extended version, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:

\relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...}

As all metadata should be self-contained, please add a persistent URL to the cited version (as illustrated above). This also simplifies the access for all readers.

\supplementdetails{...} may be used to denote supplements like related research data, source code, posters, slides, ... hosted on a repository like zenodo, figshare, ..., Software Heritage.

Sample usage:

\supplementdetails[subcategory={Source Code}]{Software}{https://github.com/...}

The subcategory is free text, while the category (Software in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.)

Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable/persistent file storage, we highly recommend to publish your document in a reliable repository.

Not found?

Didn't find what you are looking for? Don't hesitate to leave us message at publishing@dagstuhl.de!

General Workflow for Editors - An Overview
  1. Initial contact (usually 6-12 months before the publication date)
    • editors initially contact Dagstuhl Publishing by E-mail not later than 6 months before the planned publication date
    • Dagstuhl Publishing invites editors to register at the Dagstuhl Submission Server

  2. Specifying the details of the volume
    Dagstuhl Publishing initializes a new volume and asks editors to specify some necessary details, e.g.
    • the schedule (Dagstuhl Publishing sets some default values that can be adapted by the editors)
    • the paper categories besides regular papers (like "Invited talk", "Short Paper", ...)
    • a statement concerning page limits

  3. Invitation of Authors
    • editors import the papers from conference management software into the Submission Server
    • Submission Server guides editors through the invitation of authors to submit their camera ready-version

  4. Monitoring Author Submissions (ends ≈ 11 weeks before publication)
    • editors monitor the progress of paper submissions (there is an E-mail notification)
    • editors send reminders (guided by the Submission Server) in case of incomplete submissions
    • editors check the page limits (if any) and encourage the authors to comply with the style guidelines
    • editors write a preface and include it in a pre-generated front matter template
    • editors guarantee a handing over of the volume within the agreed deadline
    • no need to check the submitted LaTeX sources manually
    • no need to do any kind of typesetting

  5. Final Typesetting (by Dagstuhl Publishing)
    • revision of the LaTeX sources to comply with the author guidelines of the underlying series (see LIPIcs / OASIcs)
    • extraction of metadata

  6. Approval by Authors (≈ 3 weeks before publication)
    • opportunity for authors to preview their articles along with the extracted metadata and to ask for minor corrections

  7. Approval by Editors (≈ 1-2 weeks before publication)
    • opportunity for editors to preview the web-site of the volume on the publication server and to ask for minor corrections

  8. Official Publication of the Volume
    • includes DOI registration, registration for long-term archiving, submission to indexing services like dblp or Google Scholar
    • Dagstuhl Publishing provides HTML/XML-metadata, e.g., for use in conference web-page

Front Matter Template and Example Files

Please download the current version of the LIPIcs front matter style along with an example file:

lipicsmaster-v2021 v2021.1.2

FAQ
Submission

In order to satisfy the standards of our series, please note that we expect an affiliation at least to contain a city and country (for locations in the United States also the state), so we usually don't support requests asking for removing this kind of information from an affiliation.

For organizations with multiple locations please choose the location where you have been most of the time physically when carrying out this work.

We hope that our completion of affiliations according to the above criteria facilitates the contacting of authors as well as the assignment of a work to individual locations, and - last but not least - serves the harmonization of affiliations across the entire volume.

An authorized user is any person (not necessarily an author) that has the permission to edit the paper. (Mostly, the list of authorized users is similar to the list of corresponding authors.) Please note:
  • Authorized users only appear within the Submission Server as far as the processing of the paper (submission, approval) is concerned.
  • They won't appear in the metadata of the published article! (The metadata will be read from the submitted LaTeX code instead.)
  • Authorized users marked with the symbol are already registered to the system. Users without this symbol have been invited to the system but have not created a user account yet.
  • Given the above, it is not necessary to synchronize name and email of authorized users in any way with the data of actual authors. (They rather synchronize automatically with the user accounts on the Submission Server).

At the beginning of the submission process, the submission system has only limited information about the actual authors of the article. But on each upload, the metadata of the paper (including authors) are updated. Before the publication, the authorized users are asked to confirm (or revise, if necessary) the metadata. In more detail:

  • Before the first successful upload of the LaTeX sources of an article, the list of authors shows the authorized users or corresponding authors (if available).
  • After each upload, the list of authors is temporarily extracted from the LaTeX sources. Since this automatic extraction could fail or be faulty, the final authors' information is only extracted by the Dagstuhl Publishing Team during the final typesetting and imported before Author Approval. During Author Approval, you can request corrections on these data.
  • Finally (usually 3 weeks before the publication), the authors are explicitly asked to approve the extracted metadata. At this stage, minor modifications or necessary corrections are still possible.
  • No LaTeX source submitted yet? Don't worry about any errors here. Every time you upload a LaTeX source, the list will automatically be updated according to the \author macros in your file.
  • Otherwise: Simply correct the \author macros in your LaTeX file and do a re-upload. If the error persists, please make sure that the \author macros are contained in the top level of your main LaTeX file (outside \if conditionals) and contain plain data (i.e. preferably no self-defined macros).
  • Note: In any case, Dagstuhl Publishing asks you to confirm/correct the metadata before the work is officially published.

Dagstuhl Publishing uses BibTEX to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}).

  • The bibliographical entries should be complete according to BibTEX standards, (no warnings or errors should occur).
  • Whenever possible, references should contain an external link, e.g., DOI (preferred) or URL
  • It is highly recommended to use dblp to enrich the references and, e.g., add missing DOIs.
  • Please do not change the bibliographic style! Author-year citations are not allowed. (So the natbib package is not supported by the current LIPIcs/OASIcs style.)
  • Unreferenced bibliography entries will be removed, \nocite{*} is forbidden.
  • Submitting a bbl-file only or an inline-bibliography is not sufficient.
Note that there is an automatic extraction of (most of the) metadata on every upload. On editing these metadata you have to distinguish two cases:
  • The values of the grey (disabled) input fields can only be modified by editing the LaTeX source code and performing a re-upload of the paper afterwards.
  • For your convenience, the values of the white input fields (if any) can be edited directly in the corresponding web-form (no re-upload needed). We will process these changes later during the final typesetting.

Since the automatic extraction could fail or be faulty, the final version of metadata will be extracted by the Dagstuhl Publishing Team after the typesetting is done.

In any case we ask you to confirm/correct the metadata before the work is officially published!

\relatedversion{...} may be used to denote a related version like a full version, extended version, or also a predecessor usually published in a reliable repository like arXiv or HAL.

As all metadata should be self-contained, please add a persistent URL, e.g. \relatedversion{A full version of the paper is available at \url{...}.}. This also simplifies the access for all readers. Additional to the URL, you might add a reference (\cite{...}).

Metadata should be self-contained as they are not only part of the document / PDF but also extracted and stored in a machine-readable format along with the actual document.

Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable / persistent file storage, we highly recommend to publish your document in a reliable repository like arXiv or HAL.

Please note that a subject classification contained in your LaTeX file may be considered invalid if we cannot literally match an entry from the 2012 ACM Computing Classification System in a \ccsdesc{...} macro in your LaTeX file. (That can have many causes.)

To save you the trouble of a new upload, please find the "Search ACM Classifications"-input field in the upload form. There you can search for the corresponding valid classification. (By using the last part of the intended classification as a search term one usually ends up with a good pre-selection.)

Note that invalid classifications will automatically be removed from the LaTeX code during the final typesetting by Dagstuhl Publishing.

Publication Workflow
  • We charge the total cost of the entire volume to the conference organization. We do not charge individual authors.
  • The Processing Charge is 60 EUR (net) ...
    • per published paper (if the average count of main text () pages per article is ≤ 20)
    • per block of 20 main text pages (otherwise).
  • To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then:
        Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).
  • Please note that we expect a certain flexibility concerning any page limit (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and final typesetting by the Dagstuhl Editorial Office.

() "Main-text pages" are all contents except the title page with title, authors, affiliations, abstracts, ..... and the bibliography.

  • During this period (of usually 3 working days) authors are shown a pdf preview of their paper along with the extracted metadata.
  • authors approve or ask for (minor) corrections
  • Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)
  • Dagstuhl Publishing checks the correction requests and revises the papers (if possible)
  • Authors are informed at an early stage on the dates and can authorize other persons to do the approval on behalf of them (if necessary).
  • Editors are not involved in this process, but can see the revisions in a change-log (during the editor approval step).
Before the volume is officially published, Dagstuhl Publishing...
  • creates a web-portal on the Dagstuhl Publication Server DROPS and communicates the link to the editors
  • provides a detailed change-log for all papers
  • asks the editors to resolve open issues that could not be clarified during the author approval (if any)
  • waits for an explicit approval of the editors to expose the web-portal to the public

The editors check everything carefully and ask for minor changes, if necessary.

When approved, the volume will be officially published.

First note that there are no automatic actions triggered when the editor submission deadline has passed! You actually decide on when to hand over the volume to Dagstuhl Publishing. (However, if you miss the deadline, we cannot guarantee a timely publication.)

Your tasks here are:

  • checking for completeness and remind delayed authors on submitting their papers
  • checking the order of papers (re-ordering, if necessary)
  • checking for/setting the correct paper categories (e.g. Invited Talk, Extended Abstract, ...)
  • writing a preface and including it into the pre-generated front matter provided by the Submission System
  • handing over the volume at the specified date (editor submission deadline) to Dagstuhl Publishing
  • no need to edit LaTeX sources submitted by the authors manually (although the possibility is given)
The front matter should contain the preface, table of contents and information about the conference organisation, but no other content. Information on the conference should include the list of invited speakers and the titles of their talks.
(due to a policy passed by the LIPIcs editorial board in 2019)
For the sake of the dissemination of science, we recommend that conference organisers encourage invited speakers to provide full write-ups for their invited talks to be published as articles (labelled as "Invited Paper") in the proceedings of the conference. In case invited speakers are only willing to provide an (extended) abstract of their invited talks, LIPIcs recommends that those be also published as short papers, explicitly labelled as "Abstract of Invited Talk" in the PDF and metadata to avoid confusion with contributed articles. All papers related to the invited talks will be included in the proceedings, along with the contributed articles, and will attract the APC. This policy ensures that, independent of their lengths, the contributions accompanying invited talks can be easily referenced and also have full metadata including a DOI.
(This is a recommendation of the LIPIcs editorial board.)

As a publicly funded institution, we have to recover the costs of our publishing activities so that there is no competitive advantage over commercial providers. For the cost recovery we work with an article processing charge (APC), which currently is 60 EUR (net); for more details, see below (). This amount was set under the assumption that the average length of a paper does not substantially exceed 15 to 20 main text pages, i.e., number of pages after typesetting excluding title page and the bibliography.

Given the above, we suggest 20 main text pages as a page limit, which could for instance be in the form of 15 pages for the main body of paper plus up to 5 pages for appendices. Note that this is only a recommendation and it is up to the editors of the respective volume to decide on a policy regarding the page limit. Moreover, we expect a certain flexibility concerning any page limit (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and the Dagstuhl Editorial Office.


() When specifying a page limit please have in mind the following facts about our APC:

  • Processing Charge of 60 EUR (net) ...
    • per published paper (if the average count of main text pages [as defined above] per article is ≤ 20)
    • per block of 20 main text pages (otherwise).
  • To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then:
        Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).

First note that the specified author submission deadline does not automatically trigger any actions (like closing the submission). However, it is the deadline communicated to the authors in E-mails generated by the system. Actually, you decide on when to close the submission manually.

The editor's tasks during paper submission are:

  • editors monitor the progress of paper submissions (there is an E-mail notification)
  • editors send reminders (guided by the Submission Server) in case of incomplete submissions
  • editors check the page limits (if any) and encourage the authors to comply with the style guidelines
  • editors write a preface and include it in a pre-generated front matter template
  • editors guarantee a handing over of the volume within the agreed deadline
  • no need to check the submitted LaTeX sources manually (there are some automatic checks on upload)
  • no need to do any kind of typesetting
Author Approval
  • During this period (of usually 3 working days) authors are shown a pdf preview of their paper along with the extracted metadata.
  • authors approve or ask for (minor) corrections
  • Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)
  • Dagstuhl Publishing checks the correction requests and revises the papers (if possible)
  • Authors are informed at an early stage on the dates and can authorize other persons to do the approval on behalf of them (if necessary).
  • Editors are not involved in this process, but can see the revisions in a change-log (during the editor approval step).

If you click on "Save and Finish Author Approval", we are notified about your request.

Then we check if the proposed changes can be implemented. (Do they comply with the standards of the series? Are there no consistency issues? Are there no technical limitations, e.g. charset problems, ...).

In case these checks are positive, we implement the changes both in the metadata (if necessary) AND in the LaTeX file.

In any case, even if we cannot make the requested changes, you will be informed by E-mail.


IMPORTANT! Please note that only minor corrections should be done at this stage. Here, "minor" also refers to the total number of changes. (We have already had inquiries with 50 change requests, most of them typos. Although each request is minor, the implementation is time-consuming in sum.) Requests that exceed our processing capacities and thus endanger the timely publication of the whole volume may be rejected.

As soon as some authorized user (usually you or your co-authors, if any) finishes the approval request and submits it to Dagstuhl Publishing (this happens at the end of Step 2), we are notified about your request.

Then we check if the proposed changes can be implemented. (Do they comply with the standards of the series? Are there no consistency issues? Are there no technical limitations, e.g. charset problems, ...).

In case these checks are positive, we implement the changes both in the metadata AND in the LaTeX file.


Note that, when submitting the approval, you can decide on if you want to see the changed document again or if you consider the document as approved after the changes have been made (without a further preview).


In any case, even if we cannot make the requested changes, you will be informed by E-mail.

LaTeX Style

This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:

\authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example}

Please...

  • abbreviate first names
  • in case of middle initials: use \, as illustrated in the example
  • be consistent with the \author macros
  • in case of 2 authors: concatenate with " and "
  • in case of 3 or more authors, see the sample for concatenation
  • in case of overfull \hboxes: use the name of the first author and "et al."

Dagstuhl Publishing uses BibTEX to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}).

  • The bibliographical entries should be complete according to BibTEX standards, (no warnings or errors should occur).
  • Whenever possible, references should contain an external link, e.g., DOI (preferred) or URL
  • It is highly recommended to use dblp to enrich the references and, e.g., add missing DOIs.
  • Please do not change the bibliographic style! Author-year citations are not allowed. (So the natbib package is not supported by the current LIPIcs/OASIcs style.)
  • Unreferenced bibliography entries will be removed, \nocite{*} is forbidden.
  • Submitting a bbl-file only or an inline-bibliography is not sufficient.

\ccsdesc{...} is for classification information following the ACM 2012 Computing Classification System. Sample usage:

\ccsdesc{Theory of computation~Proof complexity}
\ccsdesc{Theory of computation~Quantum complexity theory}

Please feel free to use our ACM 2012 Subject Finder to search for appropriate classifications and to generate the necessary LaTeX code.

Using this macro, you specify the copyright holder (appearing at the bottom of the title page) which is usually the team of authors. Sample usage:

\Copyright{John Q. Public, Adam E. Access, and Eve Example}

Please...

  • use full first and last names
  • be consistent with the \author macros
  • in case of 2 authors: concatenate with " and "
  • in case of 3 or more authors, see the sample for concatenation

This macro should be used to capture general (i.e. not author-specific) funding information.

If a funding can be clearly assigned to an author, please use the last part of the \author macro instead.

Sample usage:

\keywords{Theory of Everything, indefinite Metrics, abstract Nonsense}

Please note:

  • comma as delimiter
  • first word and every proper noun should be capitalized

\relatedversiondetails{...} may be used to denote a related version like a full version, extended version, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:

\relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...}

As all metadata should be self-contained, please add a persistent URL to the cited version (as illustrated above). This also simplifies the access for all readers.

\supplementdetails{...} may be used to denote supplements like related research data, source code, posters, slides, ... hosted on a repository like zenodo, figshare, ..., Software Heritage.

Sample usage:

\supplementdetails[subcategory={Source Code}]{Software}{https://github.com/...}

The subcategory is free text, while the category (Software in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.)

Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable/persistent file storage, we highly recommend to publish your document in a reliable repository.

Not found?

Didn't find what you are looking for? Don't hesitate to leave us message at publishing@dagstuhl.de!

FAQ
General
  • APPROX - International Conference on Approximation Algorithms for Combinatorial Optimization Problems (since 2014) [dblp]
  • AofA - International Conference on Probabilistic, Combinatorial and Asymptotic Methods for the Analysis of Algorithms (since 2018) [dblp]
  • CALCO - Conference on Algebra and Coalgebra in Computer Science (since 2015) [dblp]
  • CCC - Computational Complexity Conference (since 2015) [dblp]
  • CONCUR - International Conference on Concurrency Theory (since 2015) [dblp]
  • COSIT - Conference on Spatial Information Theory (since 2017) [dblp]
  • CP - International Conference on Principles and Practice of Constraint Programming (since 2021) [dblp]
  • CPM - Annual Symposium on Combinatorial Pattern Matching (since 2016) [dblp]
  • CSL - Computer Science Logic (since 2011) [dblp]
  • DISC - International Symposium on Distributed Computing (since 2017) [dblp]
  • DNA - International Conference on DNA Computing and Molecular Programming (since 2020) [dblp]
  • ECOOP - European Conference on Object-Oriented Programming (since 2016) [dblp]
  • ECRTS - Euromicro Conference on Real-Time Systems (since 2018) [dblp]
  • ESA - European Symposium on Algorithms (since 2016) [dblp]
  • FORC - Symposium on Foundations of Responsible Computing (since 2020)
  • FSCD - Formal Structures for Computation and Deduction (since 2016) [dblp]
  • FSTTCS - IARCS Annual Conference on Foundations of Software Technology and Theoretical Computer Science (since 2008) [dblp]
  • FUN - International Conference on Fun with Algorithms (since 2016) [dblp]
  • GIScience - International Conference on Geographic Information Science (since 2018) [dblp]
  • ICALP - International Colloquium on Automata, Languages, and Programming (since 2016) [dblp]
  • ICDT - International Conference on Database Theory (since 2015) [dblp]
  • IPEC - International Symposium on Parameterized and Exact Computation (since 2015) [dblp]
  • ISAAC - International Symposium on Algorithms and Computation (since 2016) [dblp]
  • ITC - Conference on Information-Theoretic Cryptography (since 2020) [dblp]
  • ITCS - Innovations in Theoretical Computer Science Conference (since 2017) [dblp]
  • ITP - International Conference on Interactive Theorem Proving (since 2019) [dblp]
  • MFCS - Mathematical Foundations of Computer Science (since 2016) [dblp]
  • OPODIS - International Conference on Principles of Distributed Systems (since 2016) [dblp]
  • RANDOM - International Conference on Randomization and Computation (since 2014) [dblp]
  • SEA - International Symposium on Experimental Algorithms (since 2017) [dblp]
  • STACS - Symposium on Theoretical Aspects of Computer Science (since 2008) [dblp]
  • SWAT - Scandinavian Symposium and Workshops on Algorithm Theory (since 2016) [dblp]
  • SoCG - Symposium on Computational Geometry (since 2015) [dblp]
  • TIME - International Symposium on Temporal Representation and Reasoning (since 2017) [dblp]
  • TQC - Conference on the Theory of Quantum Computation, Communication and Cryptography (since 2013) [dblp]
  • TYPES - International Conference on Types for Proofs and Programs (since 2013) [dblp]
  • WABI - International Workshop on Algorithms in Bioinformatics (since 2017) [dblp]
Not found?

Didn't find what you are looking for? Don't hesitate to leave us message at publishing@dagstuhl.de!

Recently published volumes
  • LIPIcs, Vol. 250, 42nd IARCS Annual Conference on Foundations of Software Technology and Theoretical Computer Science (FSTTCS 2022)
    December 18-20, 2022 - IIT Madras, Chennai, India
    Anuj Dawar and Venkatesan Guruswami
  • LIPIcs, Vol. 248, 33rd International Symposium on Algorithms and Computation (ISAAC 2022)
    December 19-21, 2022 - Seoul, Korea
    Sang Won Bae and Heejin Park
  • LIPIcs, Vol. 249, 17th International Symposium on Parameterized and Exact Computation (IPEC 2022)
    September 7-9, 2022 - Potsdam, Germany
    Holger Dell and Jesper Nederlof
  • LIPIcs, Vol. 247, 29th International Symposium on Temporal Representation and Reasoning (TIME 2022)
    November 7-9, 2022 - Virtual Conference
    Alexander Artikis, Roberto Posenato, and Stefano Tonetta
  • LIPIcs, Vol. 246, 36th International Symposium on Distributed Computing (DISC 2022)
    October 25-27, 2022 - Augusta, Georgia, USA
    Christian Scheideler
  • LIPIcs, Vol. 245, Approximation, Randomization, and Combinatorial Optimization. Algorithms and Techniques (APPROX/RANDOM 2022)
    September 19-21, 2022 - University of Illinois, Urbana-Champaign, USA (Virtual Conference)
    Amit Chakrabarti and Chaitanya Swamy
  • LIPIcs, Vol. 243, 33rd International Conference on Concurrency Theory (CONCUR 2022)
    September 12-16, 2022 - Warsaw, Poland
    Bartek Klin, Sławomir Lasota, and Anca Muscholl
  • LIPIcs, Vol. 244, 30th Annual European Symposium on Algorithms (ESA 2022)
    September 5-9, 2022 - Berlin/Potsdam, Germany
    Shiri Chechik, Gonzalo Navarro, Eva Rotenberg, and Grzegorz Herman
  • LIPIcs, Vol. 242, 22nd International Workshop on Algorithms in Bioinformatics (WABI 2022)
    September 5-7, 2022 - Potsdam, Germany
    Christina Boucher and Sven Rahmann
  • LIPIcs, Vol. 241, 47th International Symposium on Mathematical Foundations of Computer Science (MFCS 2022)
    August 22-26, 2022 - Vienna, Austria
    Stefan Szeider, Robert Ganian, and Alexandra Silva
  • LIPIcs, Vol. 240, 15th International Conference on Spatial Information Theory (COSIT 2022)
    September 5-9, 2022 - Kobe, Japan
    Toru Ishikawa, Sara Irina Fabrikant, and Stephan Winter
  • LIPIcs, Vol. 239, 27th International Conference on Types for Proofs and Programs (TYPES 2021)
    June 14-18, 2021 - Leiden, The Netherlands (Virtual Conference)
    Henning Basold, Jesper Cockx, and Silvia Ghilezan
  • LIPIcs, Vol. 238, 28th International Conference on DNA Computing and Molecular Programming (DNA 28)
    August 8-12, 2022 - University of New Mexico, Albuquerque, New Mexico, USA
    Thomas E. Ouldridge and Shelley F. J. Wickham
  • LIPIcs, Vol. 237, 13th International Conference on Interactive Theorem Proving (ITP 2022)
    August 7-10, 2022 - Haifa, Israel
    June Andronick and Leonardo de Moura
  • LIPIcs, Vol. 236, 25th International Conference on Theory and Applications of Satisfiability Testing (SAT 2022)
    August 2-5, 2022 - Haifa, Israel
    Kuldeep S. Meel and Ofer Strichman
  • LIPIcs, Vol. 235, 28th International Conference on Principles and Practice of Constraint Programming (CP 2022)
    July 31 to August 8, 2022 - Haifa, Israel
    Christine Solnon
  • LIPIcs, Vol. 218, 3rd Symposium on Foundations of Responsible Computing (FORC 2022)
    June 6-8, 2022 - Cambridge, MA, USA
    L. Elisa Celis
  • LIPIcs, Vol. 234, 37th Computational Complexity Conference (CCC 2022)
    July 20-23, 2022 - Philadelphia, PA, USA
    Shachar Lovett
  • LIPIcs, Vol. 233, 20th International Symposium on Experimental Algorithms (SEA 2022)
    July 25-27, 2022 - Heidelberg, Germany
    Christian Schulz and Bora Uçar
  • LIPIcs, Vol. 232, 17th Conference on the Theory of Quantum Computation, Communication and Cryptography (TQC 2022)
    July 11-15, 2022 - Urbana Champaign, Illinois, USA
    François Le Gall and Tomoyuki Morimae