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:
##### Seminars
###### External resources:
• DOOR (for registering your stay at Dagstuhl)
• DOSA (for proposing future Dagstuhl Seminars or Dagstuhl Perspectives Workshops)
##### dblp
###### External resources:
• the dblp Computer Science Bibliography

# Open Access Series in Informatics (OASIcs)

The OpenAccess Series in Informatics offers a venue for the Open Access and online publication of peer-reviewed proceedings based on international scientific events (workshops, symposia, conferences, ...) that took place outside of Schloss Dagstuhl.

##### Publications
OASIcs webportal: Archive of all published OASIcs volumes.
OASIcs @ dblp
##### Aims and Scope

The OpenAccess Series in Informatics aims at a suitable publication venue to publish peer-reviewed collections of papers emerging from an international scientific event that took place outside of Schloss Dagstuhl.

The scope of the OpenAccess Series in Informatics comprises all research topics in informatics.

##### Open Access Policy
OASIcs 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.
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).

2190-6807
##### 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.

tba

##### Editorial Policy

For publishing a volume in the OASIcs series, the workshop/conference organizers have to submit an informal proposal covering the following issues:

• Content: Topics, size of the articles, number of articles, ...
• Peer Review: How is the peer review process organized?

Please note that the minimum number of articles per volume is 10. Information about the current processing charge is available on the dedicated tab Processing Charge.

Please send your proposal as a single PDF file to Dr. Michael Wagner.

The proposal will be checked internally and then forwarded to the Editorial Board which will take a decision in a little while. The following decisions are possible: (1) acceptance, (2) request for revised re-submission, or (3) rejection. Please note that there is no general right to acceptance.

##### 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 OASIcs style along with an example file and detailed author instructions:

oasics-v2021 v2021.1.2

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

##### Typesetting instructions - Summary

The OpenAccess Series in Informatics offers a venue for the Open Access and online publication of peer-reviewed proceedings based on international scientific events (workshops, symposia, conferences, ...) that took place outside of Schloss Dagstuhl.

In order to do justice to the high scientific quality of the conferences that publish their proceedings in the OASIcs series, which is ensured by the thorough review process of the respective events, we believe that OASIcs 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 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.

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:

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 for all details and don't hesitate to contact Dagstuhl Publishing (publishing@dagstuhl.de) in case of questions or comments.

##### 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.
• 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.}


• 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}


• 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 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}


• 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}


• 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.

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)

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

oasicsmaster-v2021 v2021.1.2

##### 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.
• 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.)

• 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}


• 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 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}


• 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}


• 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.

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

##### Recently published volumes
• OASIcs, Vol. 105, 4th International Workshop on Formal Methods for Blockchains (FMBC 2022)
August 11, 2022 - Haifa, Israel

Zaynah Dargaye and Clara Schneidewind
• OASIcs, Vol. 106, 22nd Symposium on Algorithmic Approaches for Transportation Modelling, Optimization, and Systems (ATMOS 2022)
September 8-9, 2022 - Potsdam, Germany

Mattia D'Emidio and Niels Lindner
• OASIcs, Vol. 104, 11th Symposium on Languages, Applications and Technologies (SLATE 2022)
July 14-15, 2022 - Universidade da Beira Interior, Covilhã, Portugal

João Cordeiro, Maria João Pereira, Nuno F. Rodrigues, and Sebastião Pais
• OASIcs, Vol. 103, 20th International Workshop on Worst-Case Execution Time Analysis (WCET 2022)
July 5, 2022 - Modena, Italy

Clément Ballabriga
• OASIcs, Vol. 102, Third International Computer Programming Education Conference (ICPEC 2022)
June 2-3, 2022 - Polytechnic Institute of Cávado and Ave (IPCA), Barcelos, Portugal

Alberto Simões and João Carlos Silva
• OASIcs, Vol. 101, 5th International Symposium on Foundations and Applications of Blockchain 2022 (FAB 2022)
June 3, 2022 - Berkeley, CA, USA

Sara Tucci-Piergiovanni and Natacha Crooks
• OASIcs, Vol. 98, Third Workshop on Next Generation Real-Time Embedded Systems (NG-RES 2022)
June 22, 2022 - Budapest, Hungary

Marko Bertogna, Federico Terraneo, and Federico Reghenzani
• OASIcs, Vol. 100, 13th Workshop on Parallel Programming and Run-Time Management Techniques for Many-Core Architectures and 11th Workshop on Design Tools and Architectures for Multicore Embedded Computing Platforms (PARMA-DITAM 2022)
June 22, 2022 - Budapest, Hungary

Francesca Palumbo, João Bispo, and Stefano Cherubin
• OASIcs, Vol. 99, International Research School in Artificial Intelligence in Bergen (AIB 2022)
June 7-11, 2022 - University of Bergen, Norway

Camille Bourgaux, Ana Ozaki, and Rafael Peñaloza
• OASIcs, Vol. 97, 3rd International Conference on Blockchain Economics, Security and Protocols (Tokenomics 2021)
November 18-19, 2021 - New York University, USA (Virtual Conference)

Vincent Gramoli, Hanna Halaburda, and Rafael Pass
• OASIcs, Vol. 95, 3rd International Workshop on Formal Methods for Blockchains (FMBC 2021)
July 18-19, 2021 - Los Angeles, California, USA (Virtual Conference)

Bruno Bernardo and Diego Marmsoler
• OASIcs, Vol. 96, 21st Symposium on Algorithmic Approaches for Transportation Modelling, Optimization, and Systems (ATMOS 2021)
September 9-10, 2021 - Lisbon, Portugal (Virtual Conference)

Matthias Müller-Hannemann and Federico Perea
• OASIcs, Vol. 93, 3rd Conference on Language, Data and Knowledge (LDK 2021)
September 1-3, 2021 - Zaragoza, Spain

Dagmar Gromann, Gilles Sérasset, Thierry Declerck, John P. McCrae, Jorge Gracia, Julia Bosque-Gil, Fernando Bobillo, and Barbara Heinisch
• OASIcs, Vol. 94, 10th Symposium on Languages, Applications and Technologies (SLATE 2021)
July 1-2, 2021 - Vila do Conde/Póvoa de Varzim, Portugal

Ricardo Queirós, Mário Pinto, Alberto Simões, Filipe Portela, and Maria João Pereira
• OASIcs, Vol. 91, Second International Computer Programming Education Conference (ICPEC 2021)
May 27-28, 2021 - University of Minho, Braga, Portugal

Pedro Rangel Henriques, Filipe Portela, Ricardo Queirós, and Alberto Simões
• OASIcs, Vol. 90, 27th IFIP WG 1.5 International Workshop on Cellular Automata and Discrete Complex Systems (AUTOMATA 2021)
July 12-14, 2021 - Aix-Marseille University, France

Alonso Castillo-Ramirez, Pierre Guillon, and Kévin Perrot
• OASIcs, Vol. 92, 4th International Symposium on Foundations and Applications of Blockchain 2021 (FAB 2021)
May 7, 2021 - University of California, Davis, California, USA (Virtual Conference)