DSub

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta name="google" content="notranslate"> <meta http-equiv="Content-Language" content="en"> <meta name="viewport" content="width=device-width, initial-scale=1" /> <meta name="csrf-token" content="Rri2v8ZuGjTmV2zlsyk2DRmJSkZdw3tej40w4pYN" /> <title>DSub</title> <link rel="icon" href="https://submission.dagstuhl.de/images/favicon.ico" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/fonts.css" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/bootstrap.css" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/app.css?2025-01-31" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/jquery-ui.css" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/jquery.qtip.min.css" /> </head> <body> <div id="app" data-release="2025-01-31"> <nav class="navbar navbar-static-top"> <div class="container"> <div class="navbar-header">  <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#app-navbar-collapse" aria-expanded="false"> <span class="sr-only">Toggle Navigation</span> <span class="glyphicon glyphicon-menu-hamburger"></span> </button>  <a class="navbar-brand" href="https://submission.dagstuhl.de" > D<sub>Sub</sub> </a> </div> <div class="collapse navbar-collapse" id="app-navbar-collapse">  <ul class="nav navbar-nav"> </ul>  <ul class="nav navbar-nav navbar-right">  <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"><span class="glyphicon glyphicon-book"></span>  Series <span class="caret"></span></a> <ul class="dropdown-menu"> <li><a href="https://submission.dagstuhl.de/series/details/LIPIcs">LIPIcs | Leibniz International Proceedings in Informatics</a></li> <li><a href="https://submission.dagstuhl.de/series/details/OASIcs">OASIcs | Open Access Series in Informatics</a></li> <li><a href="https://submission.dagstuhl.de/series/details/LITES">LITES | Leibniz Transactions on Embedded Systems</a></li> <li><a href="https://submission.dagstuhl.de/series/details/TGDK">TGDK | Transactions on Graph Data and Knowledge</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DARTS">DARTS | Dagstuhl Artifacts Series</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DagRep">DagRep | Dagstuhl Reports</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DagMan">DagMan | Dagstuhl Manifestos</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DFU">DFU | Dagstuhl Follow-Ups</a></li> </ul> </li> <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"><span class="glyphicon glyphicon-question-sign"></span>  Docs/Services <span class="caret"></span></a> <ul class="dropdown-menu"> <li><a href="https://submission.dagstuhl.de/documentation/authors">Instructions for Authors</a></li> <li><a href="https://submission.dagstuhl.de/documentation/editors">Instructions for Editors</a></li> <li role="separator" class="divider"></li> <li><a href="https://submission.dagstuhl.de/services/acm-subject-classification">ACM 2012 Subject Classification</a></li> <li><a href="https://submission.dagstuhl.de/services/capitalization">Title Capitalization Tool</a></li> <li role="separator" class="divider"></li> <li><a href="https://drops.dagstuhl.de/metadata">Metadata Export</a></li> </ul> </li> <li> <a href="https://www.dagstuhl.de/en/publishing/news" target="_blank"> <span class="glyphicon glyphicon-bullhorn"></span>  News </a> </li> <li> <a href="https://submission.dagstuhl.de/login"> <span class="glyphicon glyphicon-log-in"></span>  Login </a> </li> <li> <a href="https://submission.dagstuhl.de/register"> <span class="glyphicon glyphicon-link"></span> Register </a> </li> </ul> </div> </div> </nav> <ol class="breadcrumb"> <li><a href="/home">Home</a></li> <li>Series</li> <li>Open Access Series in Informatics</li> </ol> <h1> Open Access Series in Informatics (OASIcs) <img class="publishing-logo" src="/images/01oasics.png" height="24px" alt="Dagstuhl Publishing" style="max-height: 3rem;" /> </h1> <div class="subtitle"> <br/> </div> <div class="documentation"> <main class="col-12 col-md-12 py-md-3 pl-md-5 bd-content" role="main"> <div class="centered-content"> <ul class="nav nav-tabs" id="documentation" role="tablist"> <li class="nav-item active" role="presentation"> <a class="nav-link active" id="general-tab" data-toggle="tab" href="#general" role="tab" aria-controls="general" aria-selected="true"> General </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="editorialboard-tab" data-toggle="tab" href="#editorialboard" role="tab" aria-controls="editorialboard" aria-selected="false"> Editorial Board </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="selection-tab" data-toggle="tab" href="#selection" role="tab" aria-controls="selection" aria-selected="false"> Selection and Application </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="charge-tab" data-toggle="tab" href="#charge" role="tab" aria-controls="charge" aria-selected="false"> Processing Charge </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="author-tab" data-toggle="tab" href="#author" role="tab" aria-controls="author" aria-selected="false"> Author Instructions </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="editor-tab" data-toggle="tab" href="#editor" role="tab" aria-controls="editor" aria-selected="false"> Editor Instructions </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="recently-tab" data-toggle="tab" href="#recently" role="tab" aria-controls="recently" aria-selected="false"> Recently published </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="contact-tab" data-toggle="tab" href="#contact" role="tab" aria-controls="contact" aria-selected="false"> Contact </a> </li> </ul> <div class="tab-content" id="tab-contents"> <br /> <div class="tab-pane fade in active" id="general" role="tabpanel" aria-labelledby="general-tab"> <div class="row"> <div class="col-sm-2"> </div> <div class="col-sm-10"> <p>The <i>OpenAccess Series in Informatics</i> 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.</p> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Publications</h5> </div> <div class="col-sm-10"> All documents published in this series are available open access on <a href="https://drops.dagstuhl.de">DROPS</a>: <a href="https://drops.dagstuhl.de/entities/series/OASIcs" style="margin-left: 10px;"> <span class="btn btn-sm" style="text-align: center"> <span style="line-height: 2em">Browse OASIcs on DROPS</span><br> <img class="publishing-logo" src="/images/01oasics.png" height="24px" alt="OASIcs Logo" style="max-height: 3rem;" />   </span> </a> <br><br> Moreover, all papers are indexed in dblp: <a href="https://dblp.org/db/series/oasics">OASIcs @ dblp</a> </div> </div> <hr> <div class="row"> <div class="col-sm-2"> <h5>Aims and Scope</h5> </div> <div class="col-sm-10"> <p>The <em>OpenAccess Series in Informatics </em>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.</p> <p>The scope of the <em>OpenAccess Series in Informatics </em>comprises all research topics in informatics.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Open Access Policy</h5> </div> <div class="col-sm-10"> 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. Preprints (pre-review manuscripts), post prints (authors accepted manuscripts, AAM), and the version of record (VoR) can be deposited without restrictions. </div> </div> <div class="row"> <div class="col-sm-2"> <h5>License</h5> </div> <div class="col-sm-10"> Each article is published under a Creative Commons CC BY license (<a href="http://creativecommons.org/licenses/by/4.0/" title="Link zu http://creativecommons.org/licenses/by/4.0/" target="_blank">http://creativecommons.org/licenses/by/4.0/</a>).<br/> 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 (<a href="https://creativecommons.org/publicdomain/zero/1.0/legalcode" title="Link zu https://creativecommons.org/publicdomain/zero/1.0/legalcode" target="_blank">https://creativecommons.org/publicdomain/zero/1.0/legalcode</a>). </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Processing Charge</h5> </div> <div class="col-sm-10"> <ul><li>We charge the total cost of the entire volume to the conference organisation. We do not charge individual authors.</li><li>Processing Charge of 60 EUR (net) up to and including December 31, 2025 and of 80 EUR (net) starting from January 1, 2026 ...<ul><li>per published paper (if the average count of main text<sup>1</sup> pages per article is &leq; 20)</li><li>per block of 20 main text pages (otherwise).</li></ul></li><li>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: <p>Total cost(entire volume) = max(n,floor(P/20)) * APC (net).</p></li></ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>ISSN</h5> </div> <div class="col-sm-10"> <span>2190-6807</span> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Identifier</h5> </div> <div class="col-sm-10"> Each volumes is assigned an ISBN and a DOI.<br /> Each article is assigned a DOI and a URN.<br /> 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. </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Longterm Preservation</h5> </div> <div class="col-sm-10"> The digital archiving of each volume is done in cooperation with the Deutsche Nationalbibliothek/German National Library (<a href="http://www.dnb.de/" title="Link zu http://www.dnb.de/" target="_blank">http://www.dnb.de</a>). </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Publication Ethics</h5> </div> <div class="col-sm-10"> Dagstuhl Publishing as a division of Schloss Dagstuhl – Leibniz-Zentrum für Informatik GmbH (LZI, or Schloss Dagstuhl for short) and its series and journals adhere to <a target="_blank" href="https://publicationethics.org/core-practices">CORE practices guidance</a> laid by <a target="_blank" href="https://publicationethics.org/">COPE (Committee on Publication Ethics)</a> and are committed to the rules of good scientific practice in accordance with the <a target="_blank" href="https://www.leibniz-gemeinschaft.de/en/about-us/leibniz-integrity/good-scientific-practice-and-ombuds-services">guidelines of the Leibniz Association</a> and the <a target="_blank" href="https://wissenschaftliche-integritaet.de/en/">German Research Foundation (DFG)</a>. 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. Detailed information can be found on the <a target="_blank" href="https://www.dagstuhl.de/en/publishing/ethics">Publication Ethics website</a>. </div> </div> </div> <div class="tab-pane fade" id="editorialboard" role="tabpanel" aria-labelledby="editorialboard-tab"> <div class="row"> <div class="col-sm-2"> <h5>Editorial Board</h5> </div> <div class="col-sm-10"> <ul> <li> Daniel Cremers <a href="http://vision.in.tum.de/members/cremers">TU München, DE</a> </li> <li> Barbara Hammer <a href="http://www.techfak.uni-bielefeld.de/~bhammer/">Universität Bielefeld, DE</a> </li> <li> Marc Langheinrich <a href="http://uc.inf.usi.ch/team/langheinrich/">University of Lugano, CH</a> </li> <li> Dorothea Wagner <a href="http://i11www.iti.uni-karlsruhe.de/members/dorothea_wagner/index">KIT - Karlsruher Institut für Technologie, DE</a> </li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Constitution</h5> </div> <div class="col-sm-10"> </div> </div> </div> <div class="tab-pane fade" id="selection" role="tabpanel" aria-labelledby="selection-tab"> <div class="row"> <div class="col-sm-2"> <h5>Editorial Policy</h5> </div> <div class="col-sm-10"> <p>For publishing a volume in the <i>OASIcs</i> series, the workshop/conference organizers have to submit an informal proposal covering the following issues:<ul><li><b>Content:</b> Topics, size of the articles, number of articles, ...</li><li><b>Peer Review:</b> How is the peer review process organized?</li><li><b>Timeline:</b> Coarse schedule regarding the deadline for submission, duration of the peer review process or notification deadline, respectively, deadline for submission of camera-ready documents.</li></ul></p><p>Please note that the minimum number of articles per volume is 10. Information about the current processing charge is available on the dedicated tab <i>Processing Charge</i>.</p><p>Please send your proposal as a single PDF file to <a href='mailto:michael.wagner@dagstuhl.de '>Dr. Michael Wagner</a>.</p><p>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.</p> </div> </div> <hr /> </div> <div class="tab-pane fade" id="charge" role="tabpanel" aria-labelledby="charge-tab"> <div class="row"> <div class="col-sm-2"> <h5>In Short</h5> </div> <div class="col-sm-10"> <ul><li>We charge the total cost of the entire volume to the conference organisation. We do not charge individual authors.</li><li>Processing Charge of 60 EUR (net) up to and including December 31, 2025 and of 80 EUR (net) starting from January 1, 2026 ...<ul><li>per published paper (if the average count of main text<sup>1</sup> pages per article is &leq; 20)</li><li>per block of 20 main text pages (otherwise).</li></ul></li><li>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: <p>Total cost(entire volume) = max(n,floor(P/20)) * APC (net).</p></li></ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Background info concerning APC</h5> </div> <div class="col-sm-10"> <p>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.</p> <p> 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: <a href="https://www.dagstuhl.de/storage/media/0006/6339/increasing-apc-2026-information-letter.pdf">increasing-apc-2026-information-letter.pdf</a></p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Resulting Page-Limit Recommendation</h5> </div> <div class="col-sm-10"> <p>Given the above, we suggest 20 main text pages<sup>1</sup> 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 limit<sup>2</sup>.</p><p><sup>1</sup> 'Main-text pages' are all contents except the title page with title, authors, affiliations, abstracts, ..... and the bibliography.<br /><sup>2</sup> 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.</p> </div> </div> <hr /> </div> <div class="tab-pane fade" id="author" role="tabpanel" aria-labelledby="author-tab"> <div class="row"> <div class="col-sm-2"> <h5>Templates and Example Files</h5> </div> <div class="col-sm-10"> <p>Please download the current version of the OASIcs style along with an example file and detailed author instructions:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>oasics-v2021</b> <span class="label label-success "> v2021.1.3 </span> <aside style="display: inline-block; margin-left: 10px;"> <div class="btn-group"> <button type="button" class="btn btn-xs btn-default dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Download <span class="caret"></span> </button> <ul class="dropdown-menu"> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/authors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/authors/tgz"> as tar.gz-file </a> </li> </ul> </div> <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/88', '_blank', 'width=1024, height='+screen.availHeight)"> Instructions for Authors </span> </aside> </div> </div> <p> For <a href="https://github.com/dagstuhl-publishing/styles/releases">older releases</a> and an <a href="https://github.com/dagstuhl-publishing/styles/issues">issue tracker</a>, see our <a href="https://github.com/dagstuhl-publishing/styles">GitHub archive</a>. </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Typesetting instructions - Summary</h5> </div> <div class="col-sm-10"> <p> <p>The <i>OpenAccess Series in Informatics</i> 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.</p> 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. </p> <p> Please comply with the following instructions when preparing your article for a LIPIcs proceedings volume. (See <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/88', '_blank', 'width=1024, height='+screen.availHeight)"> Instructions for Authors </span> for more details.) </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Minimum requirements</h5> </div> <div class="col-sm-10"> <ul> <li>Use pdflatex and an up-to-date LaTeX system.</li> <li>Use further LaTeX packages and custom made macros carefully and only if required.</li> <li>Use the provided sectioning macros: <code>\section</code>, <code>\subsection</code>, <code>\subsubsection</code>, <code>\paragraph</code>, <code>\paragraph*</code>, and <code>\subparagraph*</code>.</li> <li>Provide suitable graphics of at least 300dpi (preferably in PDF format).</li> <li>Use BibTeX and keep the standard style (<a href="#" data-faq-id="22" class="_faq" tabindex="0"><code>\bibstyle{plainurl}</code> <span class="glyphicon glyphicon-question-sign"></span></a>) for the bibliography.</li> <li>Please try to keep the warnings log as small as possible. Avoid overfull <code>\hboxes</code> and any kind of warnings/errors with the referenced BibTeX entries.</li> <li>Use a spellchecker to correct typos.</li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Mandatory metadata macros</h5> </div> <div class="col-sm-10"> <p>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:</p> <ul> <li><code>\title</code> and, in case of long titles, <code>\titlerunning</code>.</li> <li><a href="#" data-faq-id="14" class="_faq" tabindex="0"><code>\author</code> <span class="glyphicon glyphicon-question-sign"></span></a> one for each author, even if two or more authors have the same affiliation.</li> <li><a href="#" data-faq-id="17" class="_faq" tabindex="0"><code>\authorrunning</code> <span class="glyphicon glyphicon-question-sign"></span></a> (abbreviated first names) and <a href="#" data-faq-id="16" class="_faq" tabindex="0"><code>\Copyright</code> <span class="glyphicon glyphicon-question-sign"></span></a> (concatenated full author names)</li> <li><a href="#" data-faq-id="18" class="_faq" tabindex="0"><code>\ccsdesc</code> <span class="glyphicon glyphicon-question-sign"></span></a> (ACM 2012 subject classification)</li> <li><a href="#" data-faq-id="15" class="_faq" tabindex="0"><code>\keywords</code> <span class="glyphicon glyphicon-question-sign"></span></a> (a comma-separated list of keywords).</li> <li><a href="#" data-faq-id="19" class="_faq" tabindex="0"><code>\relatedversion</code> <span class="glyphicon glyphicon-question-sign"></span></a> (if there is a related version, typically the "full version"); please make sure to provide a persistent URL, e.g., at arXiv.</li> <li><code>\begin{abstract}...\end{abstract}</code>.</li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Supplementary Material Statement</h5> </div> <div class="col-sm-10"> <p>Reproducibility is a key aspect of scientific research. Dagstuhl Publishing highly encourages that all <a href="#" data-faq-id="45" class="_faq" tabindex="0">relevant resources (e.g. research data, software, videos, ...) <span class="glyphicon glyphicon-question-sign"></span></a> for research articles are disclosed and documented in a <b>Supplementary Material Statement</b>. 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.</p> <p>The statement could be added to the article's metadata block using the macro <a href="#" data-faq-id="21" class="_faq" tabindex="0"><code>\supplementdetails</code> <span class="glyphicon glyphicon-question-sign"></span></a> for every supplementary resource. The publishing system supports authors in managing supplementary materials. </p> <div> Please find more information in our <a href="#" data-toggle="modal" data-target="#lipics-documentation-modal">documentation</a> <div class="modal fade" id="lipics-documentation-modal" tabindex="-1" role="dialog" aria-labelledby="lipics-documentation-modal-label" style="z-index: 10000;"> <div class="modal-dialog" role="document" style="width: 80vw; max-width: 1200px"> <div class="modal-content"> <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button> <h4 class="modal-title" id="lipics-documentation-modal-label">Publication Workflow for Authors</h4> </div> <div class="modal-body"> <iframe loading="lazy" src="https://dagstuhl.de/api/v1/articleIframe?permalink=publication-workflow-2025" style="width: 100%; height: 65vh; border: 0; padding: 0; margin: 0"></iframe> </div> <div class="modal-footer"> <button type="button" class="btn btn-primary" data-dismiss="modal">Close</button> </div> </div> </div> </div> which covers all steps of the publication workflow. </div> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Please do not ...</h5> </div> <div class="col-sm-10"> <p class="bodytext">Generally speaking, please <b>do not override the style defaults concerning spacing, font and color settings</b>. To be more specific, a short checklist also used by Dagstuhl Publishing during the final typesetting is given below. In case of <b>non-compliance</b> with these rules, Dagstuhl Publishing will remove the corresponding parts of LaTeX code and <b>replace it with the defaults</b>. In serious cases, we may reject the LaTeX-source and expect the corresponding author to revise the relevant parts.</p> <ul> <li>Do not use a different main font. (For example, the <code class="not-allowed">times</code> package is forbidden.)</li> <li>Do not alter the spacing of the provided style file.</li> <li>Do not use <code class="not-allowed">enumitem</code> and <code class="not-allowed">paralist</code>. (The <i>enumerate</i> package is preloaded, so you can use <code>\begin{enumerate}[(a)]</code> or the like.)</li> <li>Do not use "self-made" sectioning commands (e.g., <code class="not-allowed">\noindent{\bf My Paragraph}</code>).</li> <li>Do not hide large text blocks using comments or <code class="not-allowed">\iffalse ... \fi</code> constructions. </li> <li>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.</li> <li>Do not wrap figures and tables with text. In particular, the package <code class="not-allowed">wrapfig</code> is not supported. </li> <li>Do not change the bibliography style. In particular, do not use author-year citations. (The <code class="not-allowed">natbib</code> package is not supported.) </li> </ul> <p class="bodytext">This is only a summary containing the most relevant details. Please read the complete <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/88', '_blank', 'width=1024, height='+screen.availHeight)"> Instructions for Authors </span> for all details and don't hesitate to contact Dagstuhl Publishing (<a href="mailto:publishing@dagstuhl.de">publishing@dagstuhl.de</a>) in case of questions or comments. </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>FAQ</h5> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Submission</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-24-Submission-author"> <a class="collapsed" href="#FAQ-24-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-24-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">affiliation</span><span class="question">What are the <b>minimum requirements</b> on an affiliation?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-24-Submission-author" role="tabpanel" aria-labelledby="FAQ-24-Submission-author"> <div class="panel-body"> <p>In order to satisfy the standards of our series, please note that we expect an affiliation at least to contain a <b>city</b> and <b>country</b> (for locations in the United States also the <b>state</b>), so we usually <b>don't support requests asking for removing</b> this kind of information from an affiliation.</p> <p>For <b>organizations with multiple locations</b> please choose the location where you have been <b>most of the time physically</b> when carrying out this work.</p> <p>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.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/24"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/24</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-1-Submission-author"> <a class="collapsed" href="#FAQ-1-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-1-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorized user</span><span class="question">What is an <b>authorized user</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-1-Submission-author" role="tabpanel" aria-labelledby="FAQ-1-Submission-author"> <div class="panel-body"> An <b>authorized user</b> is any person (not necessarily an author) that has the <b>permission to edit the paper</b>. (Mostly, the list of authorized users is similar to the list of <b>corresponding authors</b>.) Please note: <ul> <li>Authorized users <b>only appear within the Submission Server</b> as far as the processing of the paper (submission, approval) is concerned.</li> <li>They <b>won't appear in the metadata</b> of the published article! (The metadata will be read from the submitted LaTeX code instead.)</li> <li>Authorized users marked with the <b>symbol <span class="glyphicon glyphicon-link"></span></b> are <b>already registered</b> to the system. Users without this symbol have been invited to the system but have not created a user account yet.</li> <li>Given the above, it is <b>not necessary to synchronize</b> 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).</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/1"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/1</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-2-Submission-author"> <a class="collapsed" href="#FAQ-2-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-2-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">Why the <b>list of authors</b> may change during the submission process</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-2-Submission-author" role="tabpanel" aria-labelledby="FAQ-2-Submission-author"> <div class="panel-body"> <p>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: </p> <ul> <li><b>Before the first successful upload</b> of the LaTeX sources of an article, the list of authors shows the authorized users or corresponding authors (if available).</li> <li><b>After each upload</b>, 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 <b>imported before Author Approval</b>. During Author Approval, you can request corrections on these data.</li> <li>Finally (usually 3 weeks <b>before the publication</b>), the authors are explicitly asked to approve the extracted metadata. At this stage, minor modifications or necessary corrections are still possible.</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/2"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/2</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-23-Submission-author"> <a class="collapsed" href="#FAQ-23-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-23-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">What if the <b>list of authors</b> is <b>incorrect</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-23-Submission-author" role="tabpanel" aria-labelledby="FAQ-23-Submission-author"> <div class="panel-body"> <ul> <li><b>No LaTeX source submitted yet?</b> Don't worry about any errors here. Every time you upload a LaTeX source, the list will automatically be updated according to the <code>\author</code> macros in your file.</li> <li><b>Otherwise</b>: Simply correct the <code>\author</code> macros in your LaTeX file and do a re-upload. If the error persists, please make sure that the <code>\author</code> macros are contained in the top level of your main LaTeX file (outside <code class="not-allowed">\if</code> conditionals) and contain plain data (i.e. preferably no self-defined macros).</li> <li><b>Note:</b> In any case, Dagstuhl Publishing asks you to confirm/correct the metadata before the work is officially published.</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/23"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/23</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-22-Submission-author"> <a class="collapsed" href="#FAQ-22-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-22-Submission-author" role="tabpanel" aria-labelledby="FAQ-22-Submission-author"> <div class="panel-body"> <p>Dagstuhl Publishing uses <code>BibTEX</code> to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (<code>\bibliographystyle{plainurl}</code>).</p> <ul> <li> The bibliographical entries should be <b>complete according to BibTEX standards</b>, (no warnings or errors should occur). <li> Whenever possible, references should contain an <b>external link</b>, e.g., <code>DOI</code> (preferred) or <code>URL</code> </li> <li> It is highly recommended to use <a href="https://dblp.uni-trier.de/">dblp</a> to enrich the references and, e.g., <b>add missing DOIs</b>. </li> <li> Please <b>do not change</b> the bibliographic style! Author-year citations are not allowed. (So the <code class="not-allowed">natbib</code> package is not supported by the current styles of Dagstuhl Publishing.) </li> <li> Unreferenced bibliography entries will be removed, <code class="not-allowed">\nocite{*}</code> is forbidden. </li> <li> Submitting a <code class="not-allowed">bbl-file only</code> or an <code class="not-allowed">inline-bibliography</code> is not sufficient. </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/22"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/22</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-46-Submission-author"> <a class="collapsed" href="#FAQ-46-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-46-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">DOI metadata</span><span class="question">Why can't I find any metadata for my <b>DOI</b> at <b>CrossRef</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-46-Submission-author" role="tabpanel" aria-labelledby="FAQ-46-Submission-author"> <div class="panel-body"> <p>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 <a href="https://www.doi.org/the-community/existing-registration-agencies/">https://www.doi.org/the-community/existing-registration-agencies/</a>).<p> <p>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 <a href="https://commons.datacite.org/">https://commons.datacite.org/</a>.</p> <p>Alternatively, you can of course retrieve the complete set of metada directly from us (<a href="https://drops.dagstuhl.de/metadata">https://drops.dagstuhl.de/metadata</a>) or the basic data set from dblp (<a href="https://dblp.org">https://dblp.org</a>).</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/46"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/46</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-25-Submission-author"> <a class="collapsed" href="#FAQ-25-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-25-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">funding</span><span class="question">There are two <b>different</b> kinds of <b>funding fields</b>. Where to place what?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-25-Submission-author" role="tabpanel" aria-labelledby="FAQ-25-Submission-author"> <div class="panel-body"> <p>Please note that in the metadata form there are funding fields at the bottom of <b>each author block</b> as well as a <b>general funding</b> field at the very bottom of the form (see "Additional Metadata").</p> <p>In the <b>PDF</b>, all of these <b>funding fields are merged</b> to one funding block on the title page, where the author-specific funding fields are automatically preceded by the author's name.</p> <p><code>Important!</code> Please <b>do not double funding information</b> by repeating in the general field what is already contained in the author specific ones and vice versa.</p> <p>As <b>general rule of how to distribute funding information</b> on the different fields consider the following: If a funding is <b>clearly assigned to an author</b>, please use the <b>author-specific</b> funding block. You should <b>only deviate</b> 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.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/25"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/25</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-48-Submission-author"> <a class="collapsed" href="#FAQ-48-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-48-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">left-aligned equations</span><span class="question">Why are <b>equations left-aligned</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-48-Submission-author" role="tabpanel" aria-labelledby="FAQ-48-Submission-author"> <div class="panel-body"> <p>The left justification of the equations is not random but part of the LIPIcs style and the other styles of Dagstuhl Publishing. We decided some years ago that we prefer text-like content (incl. equations and captions) to be left-justified and not centered. In contrast, figures and tables are centered. See also the LIPIcs Author Guidelines:<p> <p><a href="https://submission.dagstuhl.de/styles/instructions/lipics">https://submission.dagstuhl.de/styles/instructions/lipics</a></p> <p>The alignment of the equations is thus a deliberate style decision of the series. Therefore, we cannot comply with any request for centering.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/48"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/48</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-7-Submission-author"> <a class="collapsed" href="#FAQ-7-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-7-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata</span><span class="question">How can I <b>edit the metadata</b> in the submission process?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-7-Submission-author" role="tabpanel" aria-labelledby="FAQ-7-Submission-author"> <div class="panel-body"> Note that there is an <b>automatic extraction</b> of (most of the) metadata on every upload. On editing these metadata you have to distinguish two cases: <ul> <li>The values of the <b>grey (disabled) input fields</b> can only be modified by <b>editing the LaTeX source</b> code and performing a <b>re-upload</b> of the paper afterwards.</li> <li>For your convenience, the values of the <b>white input fields</b> (if any) can be <b>edited directly</b> in the corresponding web-form (no re-upload needed). We will process these changes later during the final typesetting.</li> </ul> <p>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.</p> <p><b>In any case we ask you to confirm/correct the metadata before the work is officially published</b>!</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/7"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/7</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-47-Submission-author"> <a class="collapsed" href="#FAQ-47-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-47-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">n-dash vs. m-dash</span><span class="question">Why should I use an <b>n-dash</b> instead of an <b>m-dash</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-47-Submission-author" role="tabpanel" aria-labelledby="FAQ-47-Submission-author"> <div class="panel-body"> <p>We try to harmonize dashes across the whole volume (even across the whole series). We clearly address this as one of our typesetting actions in the author guidelines - admittedly, at the very end, cf. p.1:21, Section 3.2 of our current author instructions for LIPIcs authors.</p> <p>However, seeking uniformity is always difficult if different style guides give different advice.</p> <p>The <a href="https://www.ox.ac.uk/sites/files/oxford/media_wysiwyg/University%20of%20Oxford%20Style%20Guide.pdf">University of Oxford Style Guide</a> explicitly says on p. 13:<p> <blockquote> m-dash<br/> Do not use; use an n-dash instead.<br/> <br/> n-dash<br/> Use in a pair in place of round brackets or commas, surrounded by spaces.<br/> Use singly and surrounded by spaces to link two parts of a sentence, in place of a colon.<br/> </blockquote> <p>Generally, it seems that in British English the " -- " variant is preferred over "---", whereas in American English it is just the opposite. (It seems, however, that there is no uniform opinion on this in either language area.)</p> <p>Hence our replacement ("---" -> " -- ") follows at least one of the accepted style guides.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/47"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/47</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-12-Submission-author"> <a class="collapsed" href="#FAQ-12-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-12-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">page limit</span><span class="question">Is there a <b>page limit</b> for LIPIcs/OASIcs papers?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-12-Submission-author" role="tabpanel" aria-labelledby="FAQ-12-Submission-author"> <div class="panel-body"> <p>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.</p> <p>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.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/12"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/12</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-4-Submission-author"> <a class="collapsed" href="#FAQ-4-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-4-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version</span><span class="question">What is a <b>related version</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-4-Submission-author" role="tabpanel" aria-labelledby="FAQ-4-Submission-author"> <div class="panel-body"> <p><code>\relatedversion{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/4"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/4</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-5-Submission-author"> <a class="collapsed" href="#FAQ-5-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-5-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version url</span><span class="question">Why is a <b>URL mandatory</b> for a related version?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-5-Submission-author" role="tabpanel" aria-labelledby="FAQ-5-Submission-author"> <div class="panel-body"> <p>As all metadata should be self-contained, please add a persistent URL, e.g. <code>\relatedversion{A full version of the paper is available at \url{...}.}</code>. This also simplifies the access for all readers. Additional to the URL, you might add a reference (<code>\cite{...}</code>).</p> <p>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.</p> <p>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.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/5"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/5</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-6-Submission-author"> <a class="collapsed" href="#FAQ-6-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-6-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">subject classifications</span><span class="question">How to handle <b>subject classifications </b> marked as <b>invalid</b>? </span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-6-Submission-author" role="tabpanel" aria-labelledby="FAQ-6-Submission-author"> <div class="panel-body"> <p>Please note that a subject classification contained in your LaTeX file may be <b>considered invalid</b> if we <b>cannot literally match</b> an entry from the 2012 ACM Computing Classification System in a <code>\ccsdesc{...}</code> macro in your LaTeX file. (That can have many causes.)</p> <p>To save you the trouble of a new upload, please find the <b>"Search ACM Classifications"</b>-input field in the upload form. There you can search for the corresponding valid classification. (By using <b>the last part</b> of the intended classification as a search term one usually ends up with a good pre-selection.) </p> <p>Note that invalid classifications will automatically be removed from the LaTeX code during the final typesetting by Dagstuhl Publishing.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/6"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/6</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-45-Submission-author"> <a class="collapsed" href="#FAQ-45-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-45-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">supplementary materials</span><span class="question">What are <b>supplementary materials</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-45-Submission-author" role="tabpanel" aria-labelledby="FAQ-45-Submission-author"> <div class="panel-body"> <p>Supplementary materials are all kinds of resources related to a scholarly article such as <b>research data</b>, <b>source code</b>, <b>research software</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">zenodo</a>, <a href="https://figshare.com/">figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/45"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/45</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Author Approval</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-30-AuthorApproval-author"> <a class="collapsed" href="#FAQ-30-AuthorApproval-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-AuthorApproval-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-30-AuthorApproval-author" role="tabpanel" aria-labelledby="FAQ-30-AuthorApproval-author"> <div class="panel-body"> <ul> <li>During this period (of usually 3 working days) authors are shown a <b>pdf preview</b> of their paper along with the <b>extracted metadata</b>.</li> <li>authors <b>approve</b> or <b>ask for (minor) corrections</b></li> <li>Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)</li> <li>Dagstuhl Publishing <b>checks</b> the correction requests and <b>revises</b> the papers (if possible)</li> <li> Authors are <b>informed at an early stage</b> on the dates and <b>can authorize other persons</b> to do the approval on behalf of them (if necessary). </li> <li> <b>Editors are not involved</b> in this process, but can see the revisions in a <b>change-log</b> (during the editor approval step). </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/30"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/30</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-28-AuthorApproval-author"> <a class="collapsed" href="#FAQ-28-AuthorApproval-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-28-AuthorApproval-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">LaTeX-changes</span><span class="question">What happens if I ask for <b>LaTeX</b>-changes in the approval step?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-28-AuthorApproval-author" role="tabpanel" aria-labelledby="FAQ-28-AuthorApproval-author"> <div class="panel-body"> <p>If you click on "Save and Finish Author Approval", we are <b>notified about your request</b>. </p> <p>Then we <b>check</b> if the proposed changes can be implemented. (Do they comply with the <b>standards</b> of the series? Are there no <b>consistency</b> issues? Are there no <b>technical limitations</b>, e.g. charset problems, ...).</p> <p>In case these <b>checks are positive</b>, we <b>implement</b> the changes both in the <b>metadata</b> (if necessary) <b>AND in the LaTeX</b> file.</p> <p>In any case, even if we cannot make the requested changes, you will be informed by E-mail.</p> <hr /> <code>IMPORTANT!</code> 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.) <b>Requests that exceed our processing capacities and thus endanger the timely publication of the whole volume may be rejected.</b> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/28"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/28</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-27-AuthorApproval-author"> <a class="collapsed" href="#FAQ-27-AuthorApproval-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-27-AuthorApproval-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata changes</span><span class="question">What happens if I ask for <b>metadata changes</b> in the approval process?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-27-AuthorApproval-author" role="tabpanel" aria-labelledby="FAQ-27-AuthorApproval-author"> <div class="panel-body"> <p>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 <b>notified about your request</b>. </p> <p>Then we <b>check</b> if the proposed changes can be implemented. (Do they comply with the <b>standards</b> of the series? Are there no <b>consistency</b> issues? Are there no <b>technical limitations</b>, e.g. charset problems, ...).</p> <p>In case these <b>checks are positive</b>, we <b>implement</b> the changes both in the <b>metadata AND in the LaTeX</b> file.</p> <hr> 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). </p> <hr> <p>In any case, even if we cannot make the requested changes, you will be informed by E-mail.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/27"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/27</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Publication Workflow</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-30-PublicationWorkflow-author"> <a class="collapsed" href="#FAQ-30-PublicationWorkflow-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-PublicationWorkflow-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-30-PublicationWorkflow-author" role="tabpanel" aria-labelledby="FAQ-30-PublicationWorkflow-author"> <div class="panel-body"> <ul> <li>During this period (of usually 3 working days) authors are shown a <b>pdf preview</b> of their paper along with the <b>extracted metadata</b>.</li> <li>authors <b>approve</b> or <b>ask for (minor) corrections</b></li> <li>Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)</li> <li>Dagstuhl Publishing <b>checks</b> the correction requests and <b>revises</b> the papers (if possible)</li> <li> Authors are <b>informed at an early stage</b> on the dates and <b>can authorize other persons</b> to do the approval on behalf of them (if necessary). </li> <li> <b>Editors are not involved</b> in this process, but can see the revisions in a <b>change-log</b> (during the editor approval step). </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/30"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/30</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>LaTeX Style</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-14-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-14-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-14-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author macro</span><span class="question">How to use the <code>\author</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-14-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-14-LaTeXStyle-author"> <div class="panel-body"> <p>Here is an example of a completely filled author macro:</p> <pre> \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.} </pre> <p>Please note:</p> <ul> <li>Use full first and last name.</li> <li> City and country belong to the <b>minimum requirements</b> on an affiliation. </li> <li> If an author has several different affiliations, please clearly separate them with the keyword <code>\and</code>. </li> <li> E-mail, ORCID, and funding are optional. </li> <li> <b>Author macros cannot be shared!</b> Please use separate author macros even if two or more authors have the same affiliation! </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/14"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/14</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-17-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-17-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-17-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorrunning macro</span><span class="question">How to use the <code>\authorrunning</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-17-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-17-LaTeXStyle-author"> <div class="panel-body"> <p>This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:</p> <pre> \authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example} </pre> <p> Please... <ul> <li>abbreviate first names</li> <li>in case of middle initials: use <code>\,</code> as illustrated in the example</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> <li>in case of overfull \hboxes: use the name of the first author and "et al."</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/17"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/17</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-22-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-22-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-22-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-22-LaTeXStyle-author"> <div class="panel-body"> <p>Dagstuhl Publishing uses <code>BibTEX</code> to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (<code>\bibliographystyle{plainurl}</code>).</p> <ul> <li> The bibliographical entries should be <b>complete according to BibTEX standards</b>, (no warnings or errors should occur). <li> Whenever possible, references should contain an <b>external link</b>, e.g., <code>DOI</code> (preferred) or <code>URL</code> </li> <li> It is highly recommended to use <a href="https://dblp.uni-trier.de/">dblp</a> to enrich the references and, e.g., <b>add missing DOIs</b>. </li> <li> Please <b>do not change</b> the bibliographic style! Author-year citations are not allowed. (So the <code class="not-allowed">natbib</code> package is not supported by the current styles of Dagstuhl Publishing.) </li> <li> Unreferenced bibliography entries will be removed, <code class="not-allowed">\nocite{*}</code> is forbidden. </li> <li> Submitting a <code class="not-allowed">bbl-file only</code> or an <code class="not-allowed">inline-bibliography</code> is not sufficient. </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/22"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/22</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-18-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-18-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-18-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">ccsdesc macro</span><span class="question">How to use the <code>\ccsdesc</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-18-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-18-LaTeXStyle-author"> <div class="panel-body"> <p><code>\ccsdesc{...}</code> is for classification information following the ACM 2012 Computing Classification System. Sample usage:</p> <pre> \ccsdesc{Theory of computation~Proof complexity} \ccsdesc{Theory of computation~Quantum complexity theory}</pre> <p> Please feel free to use our <a class="btn btn-sm btn-default" href="https://submission.dagstuhl.de/services/acm-subject-classification" target="_blank">ACM 2012 Subject Finder</a> to search for appropriate classifications and to generate the necessary LaTeX code. </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/18"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/18</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-16-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-16-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-16-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">copyright macro</span><span class="question">How to use the <code>\Copyright</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-16-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-16-LaTeXStyle-author"> <div class="panel-body"> <p>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:</p> <pre> \Copyright{John Q. Public, Adam E. Access, and Eve Example} </pre> <p> Please... <ul> <li>use <b>full</b> first and last names</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/16"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/16</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-20-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-20-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-20-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">funding macro</span><span class="question">How to use the <code>\funding</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-20-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-20-LaTeXStyle-author"> <div class="panel-body"> <p>This macro should be used to capture general (i.e. not author-specific) funding information.</p> <p>If a funding can be clearly assigned to an author, please use the last part of the <code>\author</code> macro instead.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/20"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/20</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-15-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-15-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-15-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">keywords macro</span><span class="question">How to use the <code>\keywords</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-15-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-15-LaTeXStyle-author"> <div class="panel-body"> <p>Sample usage:</p> <pre> \keywords{Theory of Everything, indefinite Metrics, abstract Nonsense} </pre> <p>Please note:</p> <ul> <li><b>comma</b> as delimiter</li> <li>first word and every proper noun should be capitalized</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/15"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/15</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-19-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-19-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-19-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">relatedversiondetails macro</span><span class="question">How to use the <code>\relatedversiondetails</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-19-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-19-LaTeXStyle-author"> <div class="panel-body"> <p><code>\relatedversiondetails{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:</p> <pre> \relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...} </pre> <p> 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. </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/19"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/19</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-21-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-21-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-21-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">supplementdetails macro</span><span class="question">How to use the <code>\supplementdetails</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-21-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-21-LaTeXStyle-author"> <div class="panel-body"> <p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">Zenodo</a>, <a href="https://figshare.com/">Figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}, swhid={...}]{Software}{https://github.com/...} </pre> <p> <ul><li>The <b>subcategory</b> is free text, while the <b>category</b> ("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.)</li> <li>The <b>swhid</b> (Software Heritage identifier) is optional and will usually be added by the publisher.</li> </ul> <p> Please note: <ul> <li>In case of a resource that may evolve over time (e.g., source code under active development), sufficient details must be provided for readers to find the specific relevant version.</li> <li>Relevant materials can be referred to via URLs (either directly in the text or in footnotes) or via a bibliographical reference in the text. Please ensure any URLs are formatted as such, i.e., clickable in the digital version of the article to visit the relevant page.</li> <li>Relevant resources included in this statement must be well-documented or otherwise self-explanatory for readers viewing the materials.</li> <li>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use of platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</li> </ul> </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/21"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/21</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Not found?</h5> </div> <div class="col-sm-10"> <p> Didn't find what you are looking for? Don't hesitate to leave us a message at <a href="mailto:publishing@dagstuhl.de">publishing@dagstuhl.de</a>! </p> </div> </div> </div> <div class="tab-pane fade" id="editor" role="tabpanel" aria-labelledby="editor-tab"> <div class="row"> <div class="col-sm-2"> <h5>Publication Workflow</h5> </div> <div class="col-sm-10"> <p>Since you are not logged in, we cannot provide any further information.</p> <div class="alert alert-warning alert-dismissable" role="alert"> <button type="button" class="close" data-dismiss="alert" aria-label="Close"><span aria-hidden="true">×</span></button> <code>IMPORTANT!</code> You are an editor of a OASIcs volume and already have a Dagstuhl Submission Server account? Then please <a href="https://submission.dagstuhl.de/login">log in </a> and you will find a step-by-step guideline through the preparation and publication process. (No account yet? <a href="https://submission.dagstuhl.de/register">Register Now!</a>) </div> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>General Workflow for Editors - An Overview</h5> </div> <div class="col-sm-10"> <ol> <li><b>Initial contact</b> (usually <span class="label label-success">6-12 months before the publication date</span>) <ul> <li> editors initially contact Dagstuhl Publishing by E-mail not later than 6 months before the planned publication date </li> <li> Dagstuhl Publishing invites editors to register at the Dagstuhl Submission Server </li> </ul> </li> <br/> <li><b>Specifying the details of the volume</b><br/> Dagstuhl Publishing initializes a new volume and asks editors to specify some necessary details, e.g. <ul> <li>the <b>schedule</b> (Dagstuhl Publishing sets some default values that can be adapted by the editors)</li> <li>the <b>paper categories</b> besides regular papers (like "Invited talk", "Short Paper", ...)</li> <li>a statement concerning <a href="#" data-faq-id="11" class="_faq" tabindex="0"><span>page limits </span><span class="glyphicon glyphicon-question-sign"></span></a></li> </ul> </li> <br /> <li><b>Invitation of Authors</b><br/> <ul> <li>editors import the papers from conference management software into the Submission Server</li> <li>Submission Server guides editors through the invitation of authors to submit their camera ready-version</li> </ul> </li> <br /> <li><b>Monitoring Author Submissions</b> (ends <span class="label label-success">≈ 11 weeks before</span> publication)<br/> <ul> <li>editors monitor the progress of paper submissions (there is an E-mail notification)</li> <li>editors <b>send reminders</b> (guided by the Submission Server) in case of incomplete submissions</li> <li>editors <b>check the page limits</b> (if any) and <b>encourage the authors to comply with the style guidelines</b></li> <li>editors write a <b>preface</b> and include it in a <b>pre-generated front matter template</b></li> <li>editors guarantee a <b>handing over of the volume</b> within the agreed deadline</li> <li><b>no need</b> to check the submitted LaTeX sources manually</li> <li><b>no need</b> to do any kind of typesetting</li> </ul> </li> <br /> <li><b>Final Typesetting (by Dagstuhl Publishing)</b> <ul> <li>revision of the LaTeX sources to comply with the <a href="https://submission.dagstuhl.de/series/details/OASIcs#author">OASIcs author guidelines</a></li> <li>extraction of metadata</li> </ul> </li> <br /> <li><b>Approval by Authors</b> (<span class="label label-success">≈ 3 weeks before</span> publication) <ul> <li>opportunity for authors to preview their articles along with the extracted metadata and to ask for minor corrections</li> </ul> </li> <br /> <li><b>Approval by Editors</b> (<span class="label label-success">≈ 1-2 weeks before</span> publication) <ul> <li>opportunity for editors to preview the web-site of the volume on the publication server and to ask for minor corrections</li> </ul> </li> <br /> <li><b>Official Publication of the Volume</b> <ul> <li>includes DOI registration, registration for long-term archiving, submission to indexing services like dblp or Google Scholar</li> <li>Dagstuhl Publishing provides <a href="https://submission.dagstuhl.de/services/metadata">HTML/XML-metadata</a>, e.g., for use in conference web-page</li> </ul> </li> </ol> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Front Matter Template and Example Files</h5> </div> <div class="col-sm-10"> <p>Please download the current version of the OASIcs front matter style along with an example file:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>oasicsmaster-v2021</b> <span class="label label-success "> v2021.1.3 </span> <aside style="display: inline-block; margin-left: 10px;"> <div class="btn-group"> <button type="button" class="btn btn-xs btn-default dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Download <span class="caret"></span> </button> <ul class="dropdown-menu"> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/editors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/editors/tgz"> as tar.gz-file </a> </li> </ul> </div> </aside> </div> </div> <p>Since you are not logged in, we cannot provide any further information.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>FAQ</h5> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Submission</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-24-Submission-editor"> <a class="collapsed" href="#FAQ-24-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-24-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">affiliation</span><span class="question">What are the <b>minimum requirements</b> on an affiliation?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-24-Submission-editor" role="tabpanel" aria-labelledby="FAQ-24-Submission-editor"> <div class="panel-body"> <p>In order to satisfy the standards of our series, please note that we expect an affiliation at least to contain a <b>city</b> and <b>country</b> (for locations in the United States also the <b>state</b>), so we usually <b>don't support requests asking for removing</b> this kind of information from an affiliation.</p> <p>For <b>organizations with multiple locations</b> please choose the location where you have been <b>most of the time physically</b> when carrying out this work.</p> <p>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.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/24"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/24</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-1-Submission-editor"> <a class="collapsed" href="#FAQ-1-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-1-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorized user</span><span class="question">What is an <b>authorized user</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-1-Submission-editor" role="tabpanel" aria-labelledby="FAQ-1-Submission-editor"> <div class="panel-body"> An <b>authorized user</b> is any person (not necessarily an author) that has the <b>permission to edit the paper</b>. (Mostly, the list of authorized users is similar to the list of <b>corresponding authors</b>.) Please note: <ul> <li>Authorized users <b>only appear within the Submission Server</b> as far as the processing of the paper (submission, approval) is concerned.</li> <li>They <b>won't appear in the metadata</b> of the published article! (The metadata will be read from the submitted LaTeX code instead.)</li> <li>Authorized users marked with the <b>symbol <span class="glyphicon glyphicon-link"></span></b> are <b>already registered</b> to the system. Users without this symbol have been invited to the system but have not created a user account yet.</li> <li>Given the above, it is <b>not necessary to synchronize</b> 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).</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/1"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/1</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-2-Submission-editor"> <a class="collapsed" href="#FAQ-2-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-2-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">Why the <b>list of authors</b> may change during the submission process</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-2-Submission-editor" role="tabpanel" aria-labelledby="FAQ-2-Submission-editor"> <div class="panel-body"> <p>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: </p> <ul> <li><b>Before the first successful upload</b> of the LaTeX sources of an article, the list of authors shows the authorized users or corresponding authors (if available).</li> <li><b>After each upload</b>, 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 <b>imported before Author Approval</b>. During Author Approval, you can request corrections on these data.</li> <li>Finally (usually 3 weeks <b>before the publication</b>), the authors are explicitly asked to approve the extracted metadata. At this stage, minor modifications or necessary corrections are still possible.</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/2"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/2</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-23-Submission-editor"> <a class="collapsed" href="#FAQ-23-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-23-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">What if the <b>list of authors</b> is <b>incorrect</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-23-Submission-editor" role="tabpanel" aria-labelledby="FAQ-23-Submission-editor"> <div class="panel-body"> <ul> <li><b>No LaTeX source submitted yet?</b> Don't worry about any errors here. Every time you upload a LaTeX source, the list will automatically be updated according to the <code>\author</code> macros in your file.</li> <li><b>Otherwise</b>: Simply correct the <code>\author</code> macros in your LaTeX file and do a re-upload. If the error persists, please make sure that the <code>\author</code> macros are contained in the top level of your main LaTeX file (outside <code class="not-allowed">\if</code> conditionals) and contain plain data (i.e. preferably no self-defined macros).</li> <li><b>Note:</b> In any case, Dagstuhl Publishing asks you to confirm/correct the metadata before the work is officially published.</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/23"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/23</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-22-Submission-editor"> <a class="collapsed" href="#FAQ-22-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-22-Submission-editor" role="tabpanel" aria-labelledby="FAQ-22-Submission-editor"> <div class="panel-body"> <p>Dagstuhl Publishing uses <code>BibTEX</code> to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (<code>\bibliographystyle{plainurl}</code>).</p> <ul> <li> The bibliographical entries should be <b>complete according to BibTEX standards</b>, (no warnings or errors should occur). <li> Whenever possible, references should contain an <b>external link</b>, e.g., <code>DOI</code> (preferred) or <code>URL</code> </li> <li> It is highly recommended to use <a href="https://dblp.uni-trier.de/">dblp</a> to enrich the references and, e.g., <b>add missing DOIs</b>. </li> <li> Please <b>do not change</b> the bibliographic style! Author-year citations are not allowed. (So the <code class="not-allowed">natbib</code> package is not supported by the current styles of Dagstuhl Publishing.) </li> <li> Unreferenced bibliography entries will be removed, <code class="not-allowed">\nocite{*}</code> is forbidden. </li> <li> Submitting a <code class="not-allowed">bbl-file only</code> or an <code class="not-allowed">inline-bibliography</code> is not sufficient. </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/22"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/22</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-46-Submission-editor"> <a class="collapsed" href="#FAQ-46-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-46-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">DOI metadata</span><span class="question">Why can't I find any metadata for my <b>DOI</b> at <b>CrossRef</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-46-Submission-editor" role="tabpanel" aria-labelledby="FAQ-46-Submission-editor"> <div class="panel-body"> <p>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 <a href="https://www.doi.org/the-community/existing-registration-agencies/">https://www.doi.org/the-community/existing-registration-agencies/</a>).<p> <p>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 <a href="https://commons.datacite.org/">https://commons.datacite.org/</a>.</p> <p>Alternatively, you can of course retrieve the complete set of metada directly from us (<a href="https://drops.dagstuhl.de/metadata">https://drops.dagstuhl.de/metadata</a>) or the basic data set from dblp (<a href="https://dblp.org">https://dblp.org</a>).</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/46"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/46</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-7-Submission-editor"> <a class="collapsed" href="#FAQ-7-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-7-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata</span><span class="question">How can I <b>edit the metadata</b> in the submission process?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-7-Submission-editor" role="tabpanel" aria-labelledby="FAQ-7-Submission-editor"> <div class="panel-body"> Note that there is an <b>automatic extraction</b> of (most of the) metadata on every upload. On editing these metadata you have to distinguish two cases: <ul> <li>The values of the <b>grey (disabled) input fields</b> can only be modified by <b>editing the LaTeX source</b> code and performing a <b>re-upload</b> of the paper afterwards.</li> <li>For your convenience, the values of the <b>white input fields</b> (if any) can be <b>edited directly</b> in the corresponding web-form (no re-upload needed). We will process these changes later during the final typesetting.</li> </ul> <p>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.</p> <p><b>In any case we ask you to confirm/correct the metadata before the work is officially published</b>!</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/7"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/7</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-4-Submission-editor"> <a class="collapsed" href="#FAQ-4-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-4-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version</span><span class="question">What is a <b>related version</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-4-Submission-editor" role="tabpanel" aria-labelledby="FAQ-4-Submission-editor"> <div class="panel-body"> <p><code>\relatedversion{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/4"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/4</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-5-Submission-editor"> <a class="collapsed" href="#FAQ-5-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-5-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version url</span><span class="question">Why is a <b>URL mandatory</b> for a related version?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-5-Submission-editor" role="tabpanel" aria-labelledby="FAQ-5-Submission-editor"> <div class="panel-body"> <p>As all metadata should be self-contained, please add a persistent URL, e.g. <code>\relatedversion{A full version of the paper is available at \url{...}.}</code>. This also simplifies the access for all readers. Additional to the URL, you might add a reference (<code>\cite{...}</code>).</p> <p>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.</p> <p>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.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/5"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/5</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-6-Submission-editor"> <a class="collapsed" href="#FAQ-6-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-6-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">subject classifications</span><span class="question">How to handle <b>subject classifications </b> marked as <b>invalid</b>? </span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-6-Submission-editor" role="tabpanel" aria-labelledby="FAQ-6-Submission-editor"> <div class="panel-body"> <p>Please note that a subject classification contained in your LaTeX file may be <b>considered invalid</b> if we <b>cannot literally match</b> an entry from the 2012 ACM Computing Classification System in a <code>\ccsdesc{...}</code> macro in your LaTeX file. (That can have many causes.)</p> <p>To save you the trouble of a new upload, please find the <b>"Search ACM Classifications"</b>-input field in the upload form. There you can search for the corresponding valid classification. (By using <b>the last part</b> of the intended classification as a search term one usually ends up with a good pre-selection.) </p> <p>Note that invalid classifications will automatically be removed from the LaTeX code during the final typesetting by Dagstuhl Publishing.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/6"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/6</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Publication Workflow</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-13-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-13-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-13-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">APC</span><span class="question">How much ist the <b>article processing charge (APC)</b> for a LIPIcs/OASIcs article?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-13-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-13-PublicationWorkflow-editor"> <div class="panel-body"> <ul> <li>We charge the total cost of the entire volume to the conference organization. We do not charge individual authors.</li> <li>The Processing Charge is 60 EUR (net) ... <ul> <li>per published paper (if the average count of main text (<span class="glyphicon glyphicon-star"></span>) pages per article is ≤ 20)</li> <li>per block of 20 main text pages (otherwise).</li> </ul> <li>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: <br>     <code>Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).</code> </li> <li>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. </li> </ul> <hr/> <p> (<span class="glyphicon glyphicon-star"></span>) "<b>Main-text pages</b>" are all contents except the title page with title, authors, affiliations, abstracts, ..... and the bibliography. </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/13"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/13</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-30-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-30-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-30-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-30-PublicationWorkflow-editor"> <div class="panel-body"> <ul> <li>During this period (of usually 3 working days) authors are shown a <b>pdf preview</b> of their paper along with the <b>extracted metadata</b>.</li> <li>authors <b>approve</b> or <b>ask for (minor) corrections</b></li> <li>Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)</li> <li>Dagstuhl Publishing <b>checks</b> the correction requests and <b>revises</b> the papers (if possible)</li> <li> Authors are <b>informed at an early stage</b> on the dates and <b>can authorize other persons</b> to do the approval on behalf of them (if necessary). </li> <li> <b>Editors are not involved</b> in this process, but can see the revisions in a <b>change-log</b> (during the editor approval step). </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/30"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/30</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-31-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-31-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-31-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">editor approval</span><span class="question">How does the <b>editor approval</b> work?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-31-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-31-PublicationWorkflow-editor"> <div class="panel-body"> Before the volume is officially published, Dagstuhl Publishing... <ul> <li> creates a <b>web-portal</b> on the Dagstuhl Publication Server <a href="http://drops.dagstuhl.de">DROPS</a> and communicates the link to the editors </li> <li> provides a detailed <b>change-log</b> for all papers </li> <li> asks the editors to <b>resolve open issues</b> that could not be clarified during the author approval (if any) </li> <li>waits for an <b>explicit approval</b> of the editors to expose the web-portal to the public</li> </li> </ul> <p>The editors <b>check everything carefully</b> and ask for minor changes, if necessary.</p> <p>When approved, the volume will be officially published.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/31"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/31</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-29-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-29-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-29-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">editor submission</span><span class="question">What are the editors' tasks between author and editor submission?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-29-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-29-PublicationWorkflow-editor"> <div class="panel-body"> <p>First note that there are <b>no automatic actions</b> 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.)</p> <p>Your tasks here are:</p> <ul> <li>checking for completeness and remind delayed authors on submitting their papers</li> <li>checking the <b>order of papers</b> (re-ordering, if necessary)</li> <li>checking for/setting the correct <b>paper categories</b> (e.g. <i>Invited Talk</i>, <i>Extended Abstract</i>, ...) </li> <li> writing a <b>preface</b> and including it into the <b>pre-generated</b> front matter provided by the Submission System </li> <li> handing over the volume at the specified date (editor submission deadline) to Dagstuhl Publishing </li> <li> <b>no need</b> to edit LaTeX sources submitted by the authors manually (although the possibility is given) </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/29"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/29</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-9-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-9-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-9-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">front matter</span><span class="question">What should/can be contained in the <b>front matter</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-9-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-9-PublicationWorkflow-editor"> <div class="panel-body"> 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. <br/> (due to a policy passed by the <a href="https://www.dagstuhl.de/en/publications/lipics/editorial-board/">LIPIcs editorial board</a> in 2019) </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/9"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/9</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-10-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-10-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-10-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">invited talks</span><span class="question">How to handle <b>invited talks</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-10-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-10-PublicationWorkflow-editor"> <div class="panel-body"> 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. <br /> (This is a recommendation of the <a href="https://www.dagstuhl.de/en/publications/lipics/editorial-board/">LIPIcs editorial board</a>.) </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/10"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/10</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-11-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-11-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-11-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">page limit</span><span class="question">Is there a <b>page limit</b> for LIPIcs/OASIcs papers?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-11-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-11-PublicationWorkflow-editor"> <div class="panel-body"> <p>As a <b>publicly funded</b> institution, we have to <b>recover the costs</b> 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 (<span class="glyphicon glyphicon-star"></span>). This amount was set <b>under the assumption that</b> the average <b>length of a paper does not</b> substantially <b>exceed 15 to 20 main text pages</b>, i.e., number of pages after typesetting <b>excluding title page and the bibliography</b>.</p> <p> Given the above, <b>we suggest 20 main text pages as a page limit</b>, 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 <b>only a recommendation</b> and it is up to the editors of the respective volume to decide on a policy regarding the page limit. Moreover, we expect a <b>certain flexibility concerning any page limit</b> (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and the Dagstuhl Editorial Office.</p> <hr/> <p>(<span class="glyphicon glyphicon-star"></span>) When specifying a page limit please have in mind the following facts about our APC: <ul> <li>Processing Charge of 60 EUR (net) ... <ul> <li>per published paper (if the average count of main text pages [as defined above] per article is ≤ 20)</li> <li>per block of 20 main text pages (otherwise).</li> </ul> <li>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: <br>     <code>Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).</code> </li> </ul> </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/11"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/11</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-8-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-8-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-8-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">paper submission</span><span class="question">What are the <b>editor's tasks</b> during the paper submission period?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-8-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-8-PublicationWorkflow-editor"> <div class="panel-body"> <p> First note that the specified author submission <b>deadline does not automatically trigger any actions</b> (like closing the submission). However, it is the deadline <b>communicated to the authors</b> in E-mails generated by the system. Actually, you decide on when to close the submission manually.</p> <p>The editor's tasks during paper submission are:</b> <ul> <li>editors monitor the progress of paper submissions (there is an E-mail notification)</li> <li>editors <b>send reminders</b> (guided by the Submission Server) in case of incomplete submissions</li> <li>editors <b>check the page limits</b> (if any) and <b>encourage the authors to comply with the style guidelines</b></li> <li>editors write a <b>preface</b> and include it in a <b>pre-generated front matter template</b></li> <li>editors guarantee a <b>handing over of the volume</b> within the agreed deadline</li> <li><b>no need</b> to check the submitted LaTeX sources manually (there are some automatic checks on upload)</li> <li><b>no need</b> to do any kind of typesetting</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/8"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/8</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-49-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-49-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-49-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">preliminary proceedings</span><span class="question">What are <b>preliminary proceedings</b>?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-49-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-49-PublicationWorkflow-editor"> <div class="panel-body"> <p>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".</p> <p>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.</p> <p>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. </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/49"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/49</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Author Approval</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-30-AuthorApproval-editor"> <a class="collapsed" href="#FAQ-30-AuthorApproval-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-AuthorApproval-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-30-AuthorApproval-editor" role="tabpanel" aria-labelledby="FAQ-30-AuthorApproval-editor"> <div class="panel-body"> <ul> <li>During this period (of usually 3 working days) authors are shown a <b>pdf preview</b> of their paper along with the <b>extracted metadata</b>.</li> <li>authors <b>approve</b> or <b>ask for (minor) corrections</b></li> <li>Dagstuhl Publishing asks authors to help with resolving issues detected during the final typesetting (if any)</li> <li>Dagstuhl Publishing <b>checks</b> the correction requests and <b>revises</b> the papers (if possible)</li> <li> Authors are <b>informed at an early stage</b> on the dates and <b>can authorize other persons</b> to do the approval on behalf of them (if necessary). </li> <li> <b>Editors are not involved</b> in this process, but can see the revisions in a <b>change-log</b> (during the editor approval step). </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/30"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/30</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-28-AuthorApproval-editor"> <a class="collapsed" href="#FAQ-28-AuthorApproval-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-28-AuthorApproval-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">LaTeX-changes</span><span class="question">What happens if I ask for <b>LaTeX</b>-changes in the approval step?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-28-AuthorApproval-editor" role="tabpanel" aria-labelledby="FAQ-28-AuthorApproval-editor"> <div class="panel-body"> <p>If you click on "Save and Finish Author Approval", we are <b>notified about your request</b>. </p> <p>Then we <b>check</b> if the proposed changes can be implemented. (Do they comply with the <b>standards</b> of the series? Are there no <b>consistency</b> issues? Are there no <b>technical limitations</b>, e.g. charset problems, ...).</p> <p>In case these <b>checks are positive</b>, we <b>implement</b> the changes both in the <b>metadata</b> (if necessary) <b>AND in the LaTeX</b> file.</p> <p>In any case, even if we cannot make the requested changes, you will be informed by E-mail.</p> <hr /> <code>IMPORTANT!</code> 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.) <b>Requests that exceed our processing capacities and thus endanger the timely publication of the whole volume may be rejected.</b> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/28"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/28</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-27-AuthorApproval-editor"> <a class="collapsed" href="#FAQ-27-AuthorApproval-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-27-AuthorApproval-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata changes</span><span class="question">What happens if I ask for <b>metadata changes</b> in the approval process?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-27-AuthorApproval-editor" role="tabpanel" aria-labelledby="FAQ-27-AuthorApproval-editor"> <div class="panel-body"> <p>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 <b>notified about your request</b>. </p> <p>Then we <b>check</b> if the proposed changes can be implemented. (Do they comply with the <b>standards</b> of the series? Are there no <b>consistency</b> issues? Are there no <b>technical limitations</b>, e.g. charset problems, ...).</p> <p>In case these <b>checks are positive</b>, we <b>implement</b> the changes both in the <b>metadata AND in the LaTeX</b> file.</p> <hr> 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). </p> <hr> <p>In any case, even if we cannot make the requested changes, you will be informed by E-mail.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/27"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/27</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>LaTeX Style</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-17-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-17-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-17-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorrunning macro</span><span class="question">How to use the <code>\authorrunning</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-17-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-17-LaTeXStyle-editor"> <div class="panel-body"> <p>This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:</p> <pre> \authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example} </pre> <p> Please... <ul> <li>abbreviate first names</li> <li>in case of middle initials: use <code>\,</code> as illustrated in the example</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> <li>in case of overfull \hboxes: use the name of the first author and "et al."</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/17"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/17</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-22-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-22-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-22-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-22-LaTeXStyle-editor"> <div class="panel-body"> <p>Dagstuhl Publishing uses <code>BibTEX</code> to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (<code>\bibliographystyle{plainurl}</code>).</p> <ul> <li> The bibliographical entries should be <b>complete according to BibTEX standards</b>, (no warnings or errors should occur). <li> Whenever possible, references should contain an <b>external link</b>, e.g., <code>DOI</code> (preferred) or <code>URL</code> </li> <li> It is highly recommended to use <a href="https://dblp.uni-trier.de/">dblp</a> to enrich the references and, e.g., <b>add missing DOIs</b>. </li> <li> Please <b>do not change</b> the bibliographic style! Author-year citations are not allowed. (So the <code class="not-allowed">natbib</code> package is not supported by the current styles of Dagstuhl Publishing.) </li> <li> Unreferenced bibliography entries will be removed, <code class="not-allowed">\nocite{*}</code> is forbidden. </li> <li> Submitting a <code class="not-allowed">bbl-file only</code> or an <code class="not-allowed">inline-bibliography</code> is not sufficient. </li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/22"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/22</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-18-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-18-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-18-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">ccsdesc macro</span><span class="question">How to use the <code>\ccsdesc</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-18-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-18-LaTeXStyle-editor"> <div class="panel-body"> <p><code>\ccsdesc{...}</code> is for classification information following the ACM 2012 Computing Classification System. Sample usage:</p> <pre> \ccsdesc{Theory of computation~Proof complexity} \ccsdesc{Theory of computation~Quantum complexity theory}</pre> <p> Please feel free to use our <a class="btn btn-sm btn-default" href="https://submission.dagstuhl.de/services/acm-subject-classification" target="_blank">ACM 2012 Subject Finder</a> to search for appropriate classifications and to generate the necessary LaTeX code. </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/18"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/18</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-16-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-16-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-16-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">copyright macro</span><span class="question">How to use the <code>\Copyright</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-16-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-16-LaTeXStyle-editor"> <div class="panel-body"> <p>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:</p> <pre> \Copyright{John Q. Public, Adam E. Access, and Eve Example} </pre> <p> Please... <ul> <li>use <b>full</b> first and last names</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/16"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/16</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-20-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-20-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-20-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">funding macro</span><span class="question">How to use the <code>\funding</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-20-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-20-LaTeXStyle-editor"> <div class="panel-body"> <p>This macro should be used to capture general (i.e. not author-specific) funding information.</p> <p>If a funding can be clearly assigned to an author, please use the last part of the <code>\author</code> macro instead.</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/20"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/20</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-15-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-15-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-15-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">keywords macro</span><span class="question">How to use the <code>\keywords</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-15-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-15-LaTeXStyle-editor"> <div class="panel-body"> <p>Sample usage:</p> <pre> \keywords{Theory of Everything, indefinite Metrics, abstract Nonsense} </pre> <p>Please note:</p> <ul> <li><b>comma</b> as delimiter</li> <li>first word and every proper noun should be capitalized</li> </ul> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/15"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/15</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-19-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-19-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-19-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">relatedversiondetails macro</span><span class="question">How to use the <code>\relatedversiondetails</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-19-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-19-LaTeXStyle-editor"> <div class="panel-body"> <p><code>\relatedversiondetails{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:</p> <pre> \relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...} </pre> <p> 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. </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/19"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/19</a></small> </div> </div> </div> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-21-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-21-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-21-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">supplementdetails macro</span><span class="question">How to use the <code>\supplementdetails</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-21-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-21-LaTeXStyle-editor"> <div class="panel-body"> <p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">Zenodo</a>, <a href="https://figshare.com/">Figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}, swhid={...}]{Software}{https://github.com/...} </pre> <p> <ul><li>The <b>subcategory</b> is free text, while the <b>category</b> ("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.)</li> <li>The <b>swhid</b> (Software Heritage identifier) is optional and will usually be added by the publisher.</li> </ul> <p> Please note: <ul> <li>In case of a resource that may evolve over time (e.g., source code under active development), sufficient details must be provided for readers to find the specific relevant version.</li> <li>Relevant materials can be referred to via URLs (either directly in the text or in footnotes) or via a bibliographical reference in the text. Please ensure any URLs are formatted as such, i.e., clickable in the digital version of the article to visit the relevant page.</li> <li>Relevant resources included in this statement must be well-documented or otherwise self-explanatory for readers viewing the materials.</li> <li>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use of platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</li> </ul> </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/21"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/21</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Not found?</h5> </div> <div class="col-sm-10"> <p> Didn't find what you are looking for? Don't hesitate to leave us message at <a href="mailto:publishing@dagstuhl.de">publishing@dagstuhl.de</a>! </p> </div> </div> </div> <div class="tab-pane fade" id="recently" role="tabpanel" aria-labelledby="recently-tab"> <div class="row"> <div class="col-sm-2"> <h5>Recently published volumes</h5> </div> <div class="col-sm-10"> <ul class="list-group"> <li class="list-group-item"> OASIcs, Vol. 126, <b>Symposium on Scaling AI Assessments (SAIA 2024)</b><br />September 30 to October 1, 2024 - Cologne, Germany <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-357-7"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Rebekka Görge, Elena Haedecke, Maximilian Poretschkin, and Anna Schmitz </li> <li class="list-group-item"> OASIcs, Vol. 125, <b>35th International Conference on Principles of Diagnosis and Resilient Systems (DX 2024)</b><br />November 4-7, 2024 - Vienna, Austria <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-356-0"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Ingo Pill, Avraham Natan, and Franz Wotawa </li> <li class="list-group-item"> OASIcs, Vol. 120, <b>13th Symposium on Languages, Applications and Technologies (SLATE 2024)</b><br />July 4-5, 2024 - Águeda, Portugal <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-321-8"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Mário Rodrigues, José Paulo Leal, and Filipe Portela </li> <li class="list-group-item"> OASIcs, Vol. 124, <b>Commit2Data</b><br />October 5, 2023 - <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-351-5"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Boudewijn R. Haverkort, Aldert de Jongste, Pieter van Kuilenburg, and Ruben D. Vromans </li> <li class="list-group-item"> OASIcs, Vol. 123, <b>24th Symposium on Algorithmic Approaches for Transportation Modelling, Optimization, and Systems (ATMOS 2024)</b><br />September 5-6, 2024 - Royal Holloway, London, United Kingdom <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-350-8"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Paul C. Bouman and Spyros C. Kontogiannis </li> <li class="list-group-item"> OASIcs, Vol. 122, <b>5th International Computer Programming Education Conference (ICPEC 2024)</b><br />June 27-28, 2024 - Lisbon, Portugal <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-347-8"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> André L. Santos and Maria Pinto-Albuquerque </li> <li class="list-group-item"> OASIcs, Vol. 121, <b>22nd International Workshop on Worst-Case Execution Time Analysis (WCET 2024)</b><br />July 9, 2024 - Lille, France <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-346-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Thomas Carle </li> <li class="list-group-item"> OASIcs, Vol. 119, <b>The Provenance of Elegance in Computation - Essays Dedicated to Val Tannen</b><br />May 24-25, 2024 - University of Pennsylvania, Philadelphia, PA, USA <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-320-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Antoine Amarilli and Alin Deutsch </li> <li class="list-group-item"> OASIcs, Vol. 118, <b>5th International Workshop on Formal Methods for Blockchains (FMBC 2024)</b><br />April 7, 2024 - Luxembourg City, Luxembourg <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-317-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Bruno Bernardo and Diego Marmsoler </li> <li class="list-group-item"> OASIcs, Vol. 117, <b>Fifth Workshop on Next Generation Real-Time Embedded Systems (NG-RES 2024)</b><br />January 17-19, 2024 - Munich, Germany <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-313-3"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Patrick Meumeu Yomsi and Stefan Wildermann </li> <li class="list-group-item"> OASIcs, Vol. 116, <b>15th Workshop on Parallel Programming and Run-Time Management Techniques for Many-Core Architectures and 13th Workshop on Design Tools and Architectures for Multicore Embedded Computing Platforms (PARMA-DITAM 2024)</b><br />January 18, 2024 - Munich, Germany <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-307-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> João Bispo, Sotirios Xydis, Serena Curzel, and Luís Miguel Sousa </li> <li class="list-group-item"> OASIcs, Vol. 111, <b>Joint Post-proceedings of the Third and Fourth International Conference on Microservices (Microservices 2020/2022)</b><br />May 10-12, 2022 - Paris, France <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-306-5"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Gokila Dorai, Maurizio Gabbrielli, Giulio Manzonetto, Aomar Osmani, Marco Prandini, Gianluigi Zavattaro, and Olaf Zimmerman </li> <li class="list-group-item"> OASIcs, Vol. 115, <b>23rd Symposium on Algorithmic Approaches for Transportation Modelling, Optimization, and Systems (ATMOS 2023)</b><br />September 7-8, 2023 - Amsterdam, The Netherlands <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-302-7"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Daniele Frigioni and Philine Schiewe </li> <li class="list-group-item"> OASIcs, Vol. 113, <b>12th Symposium on Languages, Applications and Technologies (SLATE 2023)</b><br />June 26-28, 2023 - Vila do Conde, Portugal <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-291-4"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Alberto Simões, Mario Marcelo Berón, and Filipe Portela </li> <li class="list-group-item"> OASIcs, Vol. 112, <b>4th International Computer Programming Education Conference (ICPEC 2023)</b><br />June 26-28, 2023 - Vila do Conde, Portugal <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-290-7"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Ricardo Alexandre Peixoto de Queirós and Mário Paulo Teixeira Pinto </li> <li class="list-group-item"> OASIcs, Vol. 114, <b>21st International Workshop on Worst-Case Execution Time Analysis (WCET 2023)</b><br />July 11, 2023 - Vienna, Austria <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-293-8"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Peter Wägemann </li> <li class="list-group-item"> OASIcs, Vol. 110, <b>4th International Conference on Blockchain Economics, Security and Protocols (Tokenomics 2022)</b><br />December 12-13, 2022 - Paris, France <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-274-7"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Yackolley Amoussou-Guenou, Aggelos Kiayias, and Marianne Verdier </li> <li class="list-group-item"> OASIcs, Vol. 109, <b>Eelco Visser Commemorative Symposium (EVCS 2023)</b><br />April 5, 2023 - Delft, The Netherlands <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-267-9"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Ralf Lämmel, Peter D. Mosses, and Friedrich Steimann </li> <li class="list-group-item"> OASIcs, Vol. 108, <b>Fourth Workshop on Next Generation Real-Time Embedded Systems (NG-RES 2023)</b><br />January 18, 2023 - Toulouse, France <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-268-6"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Federico Terraneo and Daniele Cattaneo </li> <li class="list-group-item"> OASIcs, Vol. 107, <b>14th Workshop on Parallel Programming and Run-Time Management Techniques for Many-Core Architectures and 12th Workshop on Design Tools and Architectures for Multicore Embedded Computing Platforms (PARMA-DITAM 2023)</b><br />January 17, 2023 - Toulouse, France <div class="pull-right"><a href="https://www.dagstuhl.de/dagpub/978-3-95977-269-3"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> João Bispo, Henri-Pierre Charles, Stefano Cherubin, and Giuseppe Massari </li> </ul> </div> </div> </div> <div class="tab-pane fade" id="contact" role="tabpanel" aria-labelledby="contact-tab"> <div class="row"> <div class="col-sm-2"> <h5>Contact Dagstuhl Publishing</h5> </div> <div class="col-sm-10"> <div class="card"> <div class="card-body"> <h5 class="card-title">Dagstuhl Publishing Team</h5> <div class="icons"> <a href="mailto:publishing@dagstuhl.de" class="card-link"><i class="bi bi-envelope"></i> publishing@dagstuhl.de</a> </div> </div> </div> </div> </div> </div> </div> <hr/> </div> </main> </div> </div> <div class="footer"> <a href="https://www.dagstuhl.de/en/publications/"> <img class="publishing-logo" src="/images/dagpub-wortmarke-grey-160x34.png" height="24px" alt="Dagstuhl Publishing"/> </a> <div> <span class="copyright">© 2019-2025 <a href="https://www.dagstuhl.de">Schloss Dagstuhl - LZI GmbH</a></span> <div> <span class="imprint"><a href="https://submission.dagstuhl.de/imprint" >Imprint</a></span> <span class="privacy"><a href="https://submission.dagstuhl.de/privacy" >Privacy</a></span> </div> </div> </div> <div class="loader-overlay -hidden"> <div class="centered-loader"> <div class="loader"></div> </div> </div> <script src="https://submission.dagstuhl.de/js/app.js?2025-01-31"></script> <script type="text/javascript"> $(document).ready(function() { const innerAnchors =[]; $('.tab-pane').find('[id]').each(function() { innerAnchors.push(this.getAttribute('id')); }); const anchors = []; $('a[role="tab"]').each(function() { anchors.push($(this).attr('aria-controls')); }); innerAnchors.forEach(function(anchor) { if ($('#'+anchor).length > 0) { anchors.push(anchor); } }); let selectedAnchor = window.location.hash.substring(1); if (anchors.indexOf(selectedAnchor) === -1) { selectedAnchor = 'general' } const innerAnchorIndex = innerAnchors.indexOf(selectedAnchor); // anchor sits inside tab -> open the tab first, then scroll to anchor if (innerAnchorIndex > -1) { const $tab = $('#'+selectedAnchor).closest('.tab-pane'); $('a.nav-link[aria-controls="'+$tab.attr('id')+'"]').click(); setTimeout(function() { $('#'+selectedAnchor)[0].scrollIntoView(); window.scrollBy(0, -100); }, 400); } // anchor references tab else { $('a.nav-link[aria-controls="'+selectedAnchor+'"]').click(); $(window).scrollTop(0); } $('a.nav-link').on('click', function() { $('#faq').find('[aria-describedby]').click(); }); }); </script> <script type="text/javascript"> $(document).ready(function() { $('[data-scroll-link]').on('click', function(e) { e.preventDefault(); const $target = $(e.currentTarget); const href = $target.attr('href'); console.log(href); $(href)[0].scrollIntoView(); window.scrollBy(0,-200); }); $('[data-tab-link]').on('click', function(e) { const $target = $(e.currentTarget); document.location.href = $target.attr('href'); document.location.reload(); }); }); </script> <script type="text/javascript"> $('document').ready(function() { var _faq = { initSingleFaq: function($this) { var id = $this.attr('data-faq-id'); if (id === undefined) { id = $this.attr('id').replace('_multi-faq-', ''); } $this.popover({ html: true, trigger: 'focus', placement: 'auto', container: 'body', title: function() { return $('[data-faq-stack-id="'+id+'"]').first().find('._title').html(); }, content: function() { return $('[data-faq-stack-id="'+id+'"]').first().find('._content').html(); } }); }, initialize: function() { // initialize single faqs $('[data-faq-id]').each(function() { _faq.initSingleFaq($(this)); }).on('click', function(e) { e.preventDefault(); // close multi faqs when clicking a single one // $('._multi-faq-close').click(); }); /* // initialize multiple faqs $('[data-multi-faq-id]').each(function() { var $this = $(this); var id = $this.attr('data-multi-faq-id'); var $stack = $('[data-multi-faq-stack-id="'+id+'"]').first(); $this.popover({ html: true, trigger: 'manual', placement: 'auto', container: 'body', title: function() { return $stack.find('._title').html(); }, content: function() { return $stack.find('._content').html(); } }); }).on('click', function(e) { e.stopPropagation(); $(e.currentTarget).popover('toggle'); $('.popover').find('a').on('click', function (e) { e.stopPropagation(); }); $('[id^=_multi-faq]').each(function () { _faq.initSingleFaq($(this)); }); $('._faq-close').off().on('click', function (e) { var id = $(e.currentTarget).parent().parent().attr('id'); $('[aria-describedby="' + id + '"]').popover('hide'); }); }); // finally close multiple $('body').on('click', function(e) { $('[data-multi-faq-id]').popover('hide'); }).on('mousedown', '.popover', function(e) { var id = $(e.currentTarget).attr('id'); var $anchor = $('[aria-describedby="' + id + '"]'); if (!$anchor.is('[data-multi-faq-id]')) { e.preventDefault(); return true; } }); */ } }; _faq.initialize(); window._faq = _faq; }); </script> <div data-faq-stack-id="22" style="display: none;"> <span class="_title">In which format should the <b>bibliography</b> be submitted?</span> <span class="_content"><p>Dagstuhl Publishing uses <code>BibTEX</code> to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (<code>\bibliographystyle{plainurl}</code>).</p> <ul> <li> The bibliographical entries should be <b>complete according to BibTEX standards</b>, (no warnings or errors should occur). <li> Whenever possible, references should contain an <b>external link</b>, e.g., <code>DOI</code> (preferred) or <code>URL</code> </li> <li> It is highly recommended to use <a href="https://dblp.uni-trier.de/">dblp</a> to enrich the references and, e.g., <b>add missing DOIs</b>. </li> <li> Please <b>do not change</b> the bibliographic style! Author-year citations are not allowed. (So the <code class="not-allowed">natbib</code> package is not supported by the current styles of Dagstuhl Publishing.) </li> <li> Unreferenced bibliography entries will be removed, <code class="not-allowed">\nocite{*}</code> is forbidden. </li> <li> Submitting a <code class="not-allowed">bbl-file only</code> or an <code class="not-allowed">inline-bibliography</code> is not sufficient. </li> </ul> </span> </div> <div data-faq-stack-id="14" style="display: none;"> <span class="_title">How to use the <code>\author</code> macro?</span> <span class="_content"><p>Here is an example of a completely filled author macro:</p> <pre> \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.} </pre> <p>Please note:</p> <ul> <li>Use full first and last name.</li> <li> City and country belong to the <b>minimum requirements</b> on an affiliation. </li> <li> If an author has several different affiliations, please clearly separate them with the keyword <code>\and</code>. </li> <li> E-mail, ORCID, and funding are optional. </li> <li> <b>Author macros cannot be shared!</b> Please use separate author macros even if two or more authors have the same affiliation! </li> </ul></span> </div> <div data-faq-stack-id="17" style="display: none;"> <span class="_title">How to use the <code>\authorrunning</code> macro?</span> <span class="_content"><p>This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:</p> <pre> \authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example} </pre> <p> Please... <ul> <li>abbreviate first names</li> <li>in case of middle initials: use <code>\,</code> as illustrated in the example</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> <li>in case of overfull \hboxes: use the name of the first author and "et al."</li> </ul> </span> </div> <div data-faq-stack-id="16" style="display: none;"> <span class="_title">How to use the <code>\Copyright</code> macro?</span> <span class="_content"><p>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:</p> <pre> \Copyright{John Q. Public, Adam E. Access, and Eve Example} </pre> <p> Please... <ul> <li>use <b>full</b> first and last names</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> </ul> </span> </div> <div data-faq-stack-id="18" style="display: none;"> <span class="_title">How to use the <code>\ccsdesc</code> macro?</span> <span class="_content"><p><code>\ccsdesc{...}</code> is for classification information following the ACM 2012 Computing Classification System. Sample usage:</p> <pre> \ccsdesc{Theory of computation~Proof complexity} \ccsdesc{Theory of computation~Quantum complexity theory}</pre> <p> Please feel free to use our <a class="btn btn-sm btn-default" href="https://submission.dagstuhl.de/services/acm-subject-classification" target="_blank">ACM 2012 Subject Finder</a> to search for appropriate classifications and to generate the necessary LaTeX code. </p></span> </div> <div data-faq-stack-id="15" style="display: none;"> <span class="_title">How to use the <code>\keywords</code> macro?</span> <span class="_content"><p>Sample usage:</p> <pre> \keywords{Theory of Everything, indefinite Metrics, abstract Nonsense} </pre> <p>Please note:</p> <ul> <li><b>comma</b> as delimiter</li> <li>first word and every proper noun should be capitalized</li> </ul></span> </div> <div data-faq-stack-id="19" style="display: none;"> <span class="_title">How to use the <code>\relatedversiondetails</code> macro?</span> <span class="_content"><p><code>\relatedversiondetails{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:</p> <pre> \relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...} </pre> <p> 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. </p></span> </div> <div data-faq-stack-id="45" style="display: none;"> <span class="_title">What are <b>supplementary materials</b>?</span> <span class="_content"><p>Supplementary materials are all kinds of resources related to a scholarly article such as <b>research data</b>, <b>source code</b>, <b>research software</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">zenodo</a>, <a href="https://figshare.com/">figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</p></span> </div> <div data-faq-stack-id="21" style="display: none;"> <span class="_title">How to use the <code>\supplementdetails</code> macro?</span> <span class="_content"><p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">Zenodo</a>, <a href="https://figshare.com/">Figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}, swhid={...}]{Software}{https://github.com/...} </pre> <p> <ul><li>The <b>subcategory</b> is free text, while the <b>category</b> ("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.)</li> <li>The <b>swhid</b> (Software Heritage identifier) is optional and will usually be added by the publisher.</li> </ul> <p> Please note: <ul> <li>In case of a resource that may evolve over time (e.g., source code under active development), sufficient details must be provided for readers to find the specific relevant version.</li> <li>Relevant materials can be referred to via URLs (either directly in the text or in footnotes) or via a bibliographical reference in the text. Please ensure any URLs are formatted as such, i.e., clickable in the digital version of the article to visit the relevant page.</li> <li>Relevant resources included in this statement must be well-documented or otherwise self-explanatory for readers viewing the materials.</li> <li>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use of platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</li> </ul> </p> </span> </div> <div data-faq-stack-id="11" style="display: none;"> <span class="_title">Is there a <b>page limit</b> for LIPIcs/OASIcs papers?</span> <span class="_content"><p>As a <b>publicly funded</b> institution, we have to <b>recover the costs</b> 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 (<span class="glyphicon glyphicon-star"></span>). This amount was set <b>under the assumption that</b> the average <b>length of a paper does not</b> substantially <b>exceed 15 to 20 main text pages</b>, i.e., number of pages after typesetting <b>excluding title page and the bibliography</b>.</p> <p> Given the above, <b>we suggest 20 main text pages as a page limit</b>, 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 <b>only a recommendation</b> and it is up to the editors of the respective volume to decide on a policy regarding the page limit. Moreover, we expect a <b>certain flexibility concerning any page limit</b> (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and the Dagstuhl Editorial Office.</p> <hr/> <p>(<span class="glyphicon glyphicon-star"></span>) When specifying a page limit please have in mind the following facts about our APC: <ul> <li>Processing Charge of 60 EUR (net) ... <ul> <li>per published paper (if the average count of main text pages [as defined above] per article is ≤ 20)</li> <li>per block of 20 main text pages (otherwise).</li> </ul> <li>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: <br>     <code>Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).</code> </li> </ul> </p></span> </div> </body> </html>

CINXE.COM

DSub