OASIcs, Volume 135
SLATE 2025, June 26-27, 2025, Faro, Portugal
Editors: Jorge Baptista and José Barateiro
OASIcs, Volume 134
Programming 2025, June 2-6, 2025, Prague 1, Czechia
Editors: Jonathan Edwards, Roly Perera, and Tomas Petricek
OASIcs, Volume 133
ICPEC 2025, July 10-11, 2025, PORTIC, Polytechnic of Porto, Portugal
Editors: Ricardo Queirós, Mário Pinto, Filipe Portela, and Alberto Simões
OASIcs, Volume 132
Grossi's Festschrift, July 25, 2025, Venice, Italy
Editors: Alessio Conte, Andrea Marino, Giovanna Rosone, and Jeffrey Scott Vitter
OASIcs, Volume 131
Manzini's Festschrift, July 25, 2025, Venice, Italy
Editors: Paolo Ferragina, Travis Gagie, and Gonzalo Navarro
OASIcs, Volume 130
SpaceCHI 2025, June 23-24, 2025, European Astronaut Centre (EAC), Cologne, Germany
Editors: Leonie Bensch, Tommy Nilsson, Martin Nisser, Pat Pataranutaporn, Albrecht Schmidt, and Valentina Sumini
OASIcs, Volume 129
FMBC 2025, May 4, 2025, Hamilton, Canada
Editors: Diego Marmsoler and Meng Xu
OASIcs, Volume 128
NG-RES 2025, January 20, 2025, Barcelona, Spain
Editors: Patrick Meumeu Yomsi and Stefan Wildermann
OASIcs, Volume 127
PARMA-DITAM 2025, January 22, 2025, Barcelona, Spain
Editors: Daniele Cattaneo, Maria Fazio, Leonidas Kosmidis, and Gabriele Morabito
OASIcs, Volume 126
SAIA 2024, September 30 to October 1, 2024, Cologne, Germany
Editors: Rebekka Görge, Elena Haedecke, Maximilian Poretschkin, and Anna Schmitz
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.
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.
Total cost(entire volume) = max(n,floor(P/20)) * APC (net).
For publishing a volume in the OASIcs series, the workshop/conference organizers have to submit an informal proposal covering the following issues:
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.
Total cost(entire volume) = max(n,floor(P/20)) * APC (net).
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.
Effective 1 January 2026, the APC will be increased from EUR 60 (net) to EUR 80 (net) due to the significant increase in operating costs (in particular wages and energy). You can find a detailed explanation of the increase in this document: increasing-apc-2026-information-letter.pdf
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 the 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.
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.
Please download the current version of the OASIcs style along with an example file and detailed author instructions:
For older releases and an issue tracker, see our GitHub archive.
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 Instructions for Authors for more details.)
\section
, \subsection
, \subsubsection
, \paragraph
, \paragraph*
, and \subparagraph*
.\bibstyle{plainurl}
) for the bibliography.\hboxes
and any kind of warnings/errors with the referenced BibTeX entries.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}
.Reproducibility is a key aspect of scientific research. Dagstuhl Publishing highly encourages that all relevant resources (e.g. research data, software, videos, ...) for research articles are disclosed and documented in a Supplementary Material Statement. This enhances reproducibility, allows the community to build on these resources, and helps readers verify or understand additional details. If resources cannot be published, authors should justify this.
The statement could be added to the article's metadata block using the macro \supplementdetails
for every supplementary resource. The publishing system supports authors in managing supplementary materials.
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.
times
package is forbidden.)enumitem
and paralist
. (The enumerate package is preloaded, so you can use \begin{enumerate}[(a)]
or the like.)\noindent{\bf My Paragraph}
).\iffalse ... \fi
constructions. wrapfig
is not supported. 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.
Didn't find what you are looking for? Don't hesitate to leave us message at publishing@dagstuhl.de!
Please download the current version of the OASIcs front matter style along with an example file:
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.
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:
\author
macros in your file.\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).Dagstuhl Publishing uses BibTEX
to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}
).
DOI
(preferred) or URL
natbib
package is not supported by the current styles of Dagstuhl Publishing.)
\nocite{*}
is forbidden.
bbl-file only
or an inline-bibliography
is not sufficient.
The metadata associated with a DOI may not be available in all services, especially in the context of Crossref. The reason for this is that we use DataCite as our DOI registry and not CrossRef. CrossRef is certainly the largest registry for DOIs, but there are a few others (see https://www.doi.org/the-community/existing-registration-agencies/).
However, our data can be retrieved in a number of ways. DataCite offers several search options and APIs that are similar to those of CrossRef, see for example https://commons.datacite.org/.
Alternatively, you can of course retrieve the complete set of metada directly from us (https://drops.dagstuhl.de/metadata) or the basic data set from dblp (https://dblp.org).
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.
You may wonder why algorithms appear as vector graphics in the HTML version of many documents instead of being an integral part of the HTML output. The reason is the following:
Algorithms combine graphics-like output and text in a way that an accurate HTML-conversion is difficult to obtain in the general case. In particular, we observed major layout issues regarding nested structures (e.g., loops, conditionals, ...) and noticed that the line numbers of the LaTeXML output often do not match the line numbers in the PDF (an inaccuracy which we consider not acceptable).
Whenever necessary by the above reasons, we prefer to embed algorithms as vector graphics (more precisely, as SVG) to guarantee in particular that line breaks and line numbering are consistent between the two document versions (PDF/HTML).
Our LaTeX-to-HTML conversion is based on the open-source tool LaTeXML, as is the case with arXiv.
Since not all LaTeX packages are supported by LaTeXML and many authors use custom macros or LaTeX hacks,
it may frequently happen that the direct LaTeXML output contains unacceptable display errors. In severe cases, HTML generation fails completely.
As arXiv also points out, the quality of the HTML output depends largely on best practices in LaTeX use (see arXiv: Submit LaTeX Best Practices).
We collect suggestions for authors on how to create LaTeX that is as suitable as possible for HTML generation in the following FAQ:
Based on feedback from authors, we document the most common problems there and try to gradually expand coverage.
In order to improve the resulting HTML and increase coverage, and to meet our high quality standards as well as those of our authors and readers, Dagstuhl Publishing - unlike arXiv - relies on a semi-automatic transformation process: First, we attempt to resolve incompatibilities manually (at the LaTeX level) in order to enable or improve the conversion. Subsequently, a visual check is performed to identify and correct remaining inconsistencies. This significant additional effort is very promising but also cost-intensive.
Of the over 1000 documents processed so far, 90% have been successfully converted into HTML suitable for publication. However, the significant additional costs are currently not covered by the APC, which already barely covers costs. HTML conversion is therefore currently being run as an experimental project. Only after a thorough evaluation of the project after a minimum period of one year, a decision will be made on whether to continue HTML support.
Please note that there are currently no plans to retroactively generate HTML files for documents published before 2025.
PDF remains the primary output format at Dagstuhl Publishing. However, starting in 2025, we will also offer HTML, as HTML content is significantly more accessible on screen readers, screen magnifiers, and mobile devices. While PDFs were developed primarily for true-to-print display, HTML allows for flexible adaptation to users with different needs (e.g. enlarged text, high-contrast display or linear reading aloud by screen readers).
By providing HTML, we want to break down barriers and improve access to our publications.
Please note that there are currently no plans to retroactively generate HTML files for documents published before 2025.
HTML (or XML) currently offers the most reliable way to make document content accessible:
ArXiv also refers to HTML as the most promising way to make scientific content accessible (see arXiv HTML as an accessible format for papers
).
See also the related FAQ "Why are we not (yet) using PDF/UA as an accessible format?"
The quality of the HTML output depends heavily on how consistent and standard-compliant a LaTeX document is structured. Some packages or self-defined macros can make conversion difficult or impossible. The following tips are based on arXiv's best practices:
LaTeX hacksor workarounds that are not documented.
\section
, \subsection
, etc. – not just with manual formatting (\textbf
, \large
). $...$
(inline) or \[...\]
/ equation environments.\includegraphics
in a figure environment and – if possible – add \caption
.\includegraphics[alt={plain-text description of image}]{example-image-a}
In short: The cleaner
the structure of a LaTeX document, the more likely it is that the HTML conversion will be successful and of high quality.
There are various reasons why an HTML version of a document may not have been published (yet).
If the article (the PDF) was published only recently (up to 3 months ago), it is very likely that HTML production for the volume has not been completed. Once the HTML version has been published, all authors will be informed accordingly.
If your article (the PDF) was published after 1 January 2025 (and not within the last 3 months), the conversion of the article to HTML was probably unsuccessful. There may be various reasons for this. Please read the FAQs for more information:
Of course, you can also contact the publisher at any time.
Please note that there are currently no plans to retroactively generate HTML files for documents published before 2025.
PDF/UA (Universal Accessibility) is the ISO standard for accessible PDF documents. Since 2021, our publications have been published in PDF/A (Archivable) format, which is optimised for long-term archiving. In theory, it is possible to create a document that is both PDF/A and PDF/UA compliant. In practice, however, this is currently hardly feasible with LaTeX, as the necessary tools and workflows are not yet mature.
The current status of the LaTeX project for creating Tagged PDF (the basis for PDF/UA) is still experimental (see LaTeX tagging project). A stable version does not yet exist. Before widespread use, extensive compatibility tests would also have to be carried out with the numerous LaTeX packages that our authors use in addition to the classes provided.
We evaluate developments regularly, but currently see no practical way of reliably generating PDF/UA with our LaTeX-based publication process.
LaTeXML already supports a large number of LaTeX packages, but not all of them. Please see this website for the list of packages currently supported by LaTeXML. As a general rule:
In such cases, we recommend:
In short: All packages provided by Dagstuhl Publishing as standard are safe. For additional packages, authors themselves or together with the LaTeXML community can contribute to improving support.
Here we collect packages that are currently incompatible, along with possible alternatives and workarounds:
\frac
and \partial
instead, like \frac{\partial f}{\partial t}
NOTE: Problems with various packages used to generate diagrams, images or similar can be resolved by first externalising the results of these packages as standalone PDFs using the document class standalone and then embedding the PDFs as images instead of the code used to generate them. See also the FAQ How do I use the standalone
class to create separate images?
With the standalone class, any TeX code, e.g. for generating a graphic or diagram, can be converted into a separate PDF. This image can then be easily integrated into the main document as usual using \includegraphics
command.
\documentclass{standalone} \usepackage{xyz} \begin{document} \begin{somepicture} \somedrawingcommands \end{somepicture} \end{document}
\includegraphics{sample.pdf}
.It is also possible to generate several images with one standalone
file. To do this, you only need to define a corresponding environment in the documentclass option, e.g. \documentclass[multi=newFigure]{standalone}
, and wrap the code for each of the separate images with this environment, so \begin{newFigure}…\end{newFigure}
. To include the images into the main document, please use then the page
option of the grahics command, e.g. \includegraphics[page=1]{sample.pdf}
.
For more detailed instructions, please see the package document on CTAN. However, please don't use the commands provided by standalone package within the main document to include the separated code, e.g.
as this is currently not yet supported by our LaTeX processing workflow. Instead please include the pre-compiled, resulting PDF.\includestandalone[...]{sample.tex}
Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).
() "Main-text pages" are all contents except the title page with title, authors, affiliations, abstracts, ..... and the bibliography.
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:
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:
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:
Dagstuhl Publishing usually needs between six and eight weeks from submission of the camera-ready versions to publication, depending on the seasonal workload. If a conference is unable to meet this time requirement, there is a middle way in the form of "preliminary proceedings" in addition to the classic option of "post-proceedings".
Preliminary proceedings will not be published on our publication server but will only be made temporarily accessible on a separate webpage. This page requires the user to input a CAPTCHA, thus creating a barrier to prevent webcrawlers like Google etc. from accessing and indexing the papers of the preliminary proceedings (it would be quite difficult to "repair" this afterwards). Furthermore, the PDFs are watermarked, indicating that the version is preliminary, and include a URL where the officially published version will eventually be available). The preliminary proceedings thus consist of an overview page with rudimentary metadata (title + authors) and the preliminary PDFs of the papers.
Camera-ready versions should be submitted at least two weeks prior to the event in order for the preliminary proceedings to be ready in time. The official publication will then take place in the weeks following the event.
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.
In any case, even if we cannot make the requested changes, you will be informed by E-mail.
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...
\,
as illustrated in the example\author
macrosDagstuhl Publishing uses BibTEX
to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}
).
DOI
(preferred) or URL
natbib
package is not supported by the current styles of Dagstuhl Publishing.)
\nocite{*}
is forbidden.
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...
\author
macrosThis 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:
\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}, swhid={...}]{Software}{https://github.com/...}
Please note:
Didn't find what you are looking for? Don't hesitate to leave us message at publishing@dagstuhl.de!