OASIcs, Volume 121
WCET 2024, July 9, 2024, Lille, France
Editors: Thomas Carle
OASIcs, Volume 119
Tannen's Festschrift, May 24-25, 2024, University of Pennsylvania, Philadelphia, PA, USA
Editors: Antoine Amarilli and Alin Deutsch
OASIcs, Volume 118
FMBC 2024, April 7, 2024, Luxembourg City, Luxembourg
Editors: Bruno Bernardo and Diego Marmsoler
OASIcs, Volume 117
NG-RES 2024, January 17-19, 2024, Munich, Germany
Editors: Patrick Meumeu Yomsi and Stefan Wildermann
OASIcs, Volume 116
PARMA-DITAM 2024, January 18, 2024, Munich, Germany
Editors: João Bispo, Sotirios Xydis, Serena Curzel, and Luís Miguel Sousa
OASIcs, Volume 115
ATMOS 2023, September 7-8, 2023, Amsterdam, The Netherlands
Editors: Daniele Frigioni and Philine Schiewe
OASIcs, Volume 114
WCET 2023, July 11, 2023, Vienna, Austria
Editors: Peter Wägemann
OASIcs, Volume 113
SLATE 2023, June 26-28, 2023, Vila do Conde, Portugal
Editors: Alberto Simões, Mario Marcelo Berón, and Filipe Portela
OASIcs, Volume 112
ICPEC 2023, June 26-28, 2023, Vila do Conde, Portugal
Editors: Ricardo Alexandre Peixoto de Queirós and Mário Paulo Teixeira Pinto
OASIcs, Volume 111
Microservices 2020/2022, May 10-12, 2022, Paris, France
Editors: Gokila Dorai, Maurizio Gabbrielli, Giulio Manzonetto, Aomar Osmani, Marco Prandini, Gianluigi Zavattaro, and Olaf Zimmermann
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).
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.
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}
.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 ([email protected]) in case of questions or comments.
Didn't find what you are looking for? Don't hesitate to leave us message at [email protected]!
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.
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.
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:
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}]{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 [email protected]!