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="0JwsVfYByLzduz0E7oqnMgWPCoYEeB6ISRIEFXom" /> <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>Dagstuhl Artifacts Series</li> </ol> <h1> Dagstuhl Artifacts Series (DARTS) <img class="publishing-logo" src="/images/05darts.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/Review </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>Dagstuhl Artifacts Series (DARTS)</i> publishes evaluated research data and artifacts in all areas of computer science. An artifact can be any kind of content related to computer science research, e.g., experimental data, source code, virtual machines containing a complete setup, test suites, or tools. In contrast to existing repositories for research data and artifacts like <a href="http://www.zenodo.org/">Zenodo</a> or <a href="https://figshare.com/">figshare</a>, DARTS focuses on artifacts that underwent an evaluation process before their publication.</p> <p>An artifact should be related to a research paper (which does not necessarily have to be published within a series of Dagstuhl Publishing but which should be clearly citable, e.g., by a DOI) and should help to verify the repeatability and correctness of the experiments/implementations described in the related paper.</p> <p>The series is organized as a periodical consisting of one volume per year. Each volume can consist of several issues. Thereby, DARTS currently focuses on special issues that are related to a conference.<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 journal are available open access on <a href="https://drops.dagstuhl.de">DROPS</a>: <a href="https://drops.dagstuhl.de/entities/journal/DARTS" style="margin-left: 10px;"> <span class="btn btn-sm" style="text-align: center"> <span style="line-height: 2em">Browse DARTS on DROPS</span><br> <img class="publishing-logo" src="/images/05darts.png" height="24px" alt="DARTS Logo" style="max-height: 3rem;" />   </span> </a> <br><br> Moreover, all papers are indexed in dblp: <a href="https://dblp.org/db/journals/darts">DARTS @ 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 DARTS series aims at the provision of a publication venue for evaluated research data and artifacts. An artifact can be any kind of content related to computer science research, e.g., experimental data, source code, virtual machines containing a complete setup, test suites, or tools. In contrast to existing repositories for research data and artifacts, DARTS focuses on artifacts that underwent an evaluation process before their publication.</p> <p>The scope of DARTS covers all areas of computer science.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Open Access Policy</h5> </div> <div class="col-sm-10"> Artifacts in DARTS are peer-reviewed and are published electronically according to the principles of open access, i.e., they are available online and free of charge. 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 artifact description 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 actual artifact is published under a Open Source license to be found in the artifact description.<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"> For DARTS, no fee is charged. </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>ISSN</h5> </div> <div class="col-sm-10"> <span>2509-8195</span> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Identifier</h5> </div> <div class="col-sm-10"> Each issue is assigned a DOI and a URN.<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"> </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> Raimund Seidel <a href="http://www-tcs.cs.uni-saarland.de/">Universität des Saarlandes - Saarbrücken, DE</a> </li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Constitution</h5> </div> <div class="col-sm-10"> <p>The editorial board oversees the selection of issues to be included in DARTS. The board is monitored by the Scientific Advisory Board of Schloss Dagstuhl. In its initial configuration, the board consists of at least 2 members with a background of artifact evaluation in computer science and the scientific director of Schloss Dagstuhl or his/her representative. The editorial board may give itself rules of internal procedures.</p> </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>To publish an issue in the Dagstuhl Artifacts Series (DARTS), the organizers of a conference must submit a proposal covering the following issues:<ul><li>Information about the conference<ul><li>Content: Topics, size of the articles, number of articles, ...</li><li>Peer Review: How is the peer review process organized?</li><li>Timeline: Coarse schedule regarding the deadline for submission, duration of the peer review process or notification deadline, respectively, deadline for submission of camera-ready documents for both research papers as well as research artifacts.</li><li>Proceedings: Where are the proceedings published?</li></ul></li><li>Artifact Evaluation Process: <ul><li>Description of the artifact evaluation process: Which parties are involved? How is the relation of the artifact evaluation committee and the regular program committee of the conference and how/when are decisions synchronized?</li><li> List of the artifact evaluation committee members.</li></ul></li></ul></p><p>The proposal will be processed by Dagstuhl's editorial office and then forwarded to the DARTS Editorial Board for a timely decision. The following decisions are possible: (1) acceptance, (2) request for revised re-submission, or (3) rejection.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Artifact Evaluation</h5> </div> <div class="col-sm-10"> <p>All artifacts to be published within DARTS need to undergo some sort of systematic evaluation process, typically administered by an evaluation committee. Thereby, it should be ensured that the artifact is well documented, easy to reuse, consistent, and complete with respect to the claims made in the related research paper.<br />It is up to the editors of a special issue to organize the evaluation process and to provide the methodology for the evaluation. As a suggestion, the guidelines for <i><a href='http://www.artifact-eval.org/'>Artifact Evaluation for Software Conferences</a></i> can serve as basis. The description of the artifact evaluation process has to be publicly available and is part of the preface of the issue and of the proposal.</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 DARTS style along with an example file and detailed author instructions:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>darts-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/darts/v2021.1.3/authors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/darts/v2021.1.3/authors/tgz"> as tar.gz-file </a> </li> </ul> </div> </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>Artifact Description</h5> </div> <div class="col-sm-10"> <p>Each artifact is published with a separate description which should</p> <ul> <li>contain information of the scope of the artifact,</li> <li>list the content of the artifact, </li> <li>provide information about the origin of the artifact (e.g., reference to version control platforms like <a href="https://github.com/">GitHub</a> including a version number (if applicable)),</li> <li>specify the platform on which the artifact has been tested (if applicable),</li> <li>provide a reference to the license of the artifact (DARTS requires the usage of free and open source software licenses. The license of the artifact can be different from the license of the artifact description. The description is released under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license (CC BY 4.0)</a>, i.e., the authors retain their copyright. For a incomplete list of free licenses, please visit <a href="http://www.gnu.org/licenses/license-list.en.html">http://www.gnu.org/licenses/license-list.en.html</a> and <a href="https://opensource.org/licenses/">https://opensource.org/licenses/</a>.),</li> <li>provide the MD5 sum of the artifact,</li> <li>contain the size of the artifact,</li> <li>specify keywords,</li> <li>provide the DOI, as well as</li> <li>provide a reference to the related research paper.</li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Metadata</h5> </div> <div class="col-sm-10"> <p>Each artifact is published with machine-readable metadata including the following information according to the <a href="http://doi.org/10.5438/0012">DataCite Metadata Schema</a>:</p> <ul> <li>title</li> <li>authors (The list of authors of the artifact may include people who are not authors of the related paper, but contributed to creating the artifact.)</li> <li>keywords \ subjects</li> <li>publisher</li> <li>publication date</li> <li>type (e.g., DataCite properties resourceTypeGeneral and resourceType)</li> <li>DOI</li><li>identifier (e.g., DOI) of the related research paper</li> <li>size</li><li>version (if applicable)</li> <li>license</li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5> File formats </h5> </div> <div class="col-sm-10"> <p>DARTS accepts any kind of data file formats for the artifacts. However, it can not guarantee continued access and preservation of obsolete or obscure formats. For that reason, open, non-proprietary and well-documented formats are highly recommended wherever possible. </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-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> </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-38-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-38-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-38-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">mdsum macro</span><span class="question">How to use the <code>\mdsum</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-38-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-38-LaTeXStyle-author"> <div class="panel-body"> <p>We expect you to provide your DARTS artifact as a single (compressed) file. To calculate the <b>md5-sum</b> of this file on your local machine, please type:</p> <ul> <li><code>md5 [artifact_filename]</code> in a Linux/Mac OS terminal</li> <li><code>CertUtil -hashfile [artifact_filename] MD5</code> in a Windows Shell</li> </ul> <p>The output should be a 32 byte hex string. Use this string as argument of the mdsum-macro, e.g., <code>\mdsum{b157da23549e1d718bb16d22ded6d941}</code>. </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/38"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/38</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 DARTS issue 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 issue</b><br/> Dagstuhl Publishing initializes a new issue 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> </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 of the artifact description and the artifact</li> </ul> </li> <br /> <li><b>Monitoring Author Submissions</b> (ends <span class="label label-success">≈ 6 weeks before</span> publication)<br/> <ul> <li>editors monitor the progress of description/artifact 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>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/DARTS#author">DARTS author guidelines</a></li> <li>extraction of metadata</li> </ul> </li> <br /> <li><b>Approval by Authors</b> (<span class="label label-success">≈ 2 weeks before</span> publication) <ul> <li>opportunity for authors to preview their artifact descriptions 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 week before</span> publication) <ul> <li>opportunity for editors to preview the web-site of the issue 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</h5> </div> <div class="col-sm-10"> <p>Each issue in the Dagstuhl Artifacts Series (DARTS) has a preface written by the chairs of the artifact evaluation committee that describes the artifact evaluation process. This description is also an essential part of the proposal. </p> </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 DARTS front matter style along with an example file:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>dartsmaster-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/darts/v2021.1.3/editors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/darts/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> <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-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>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>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-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-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> </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-38-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-38-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-38-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">mdsum macro</span><span class="question">How to use the <code>\mdsum</code> macro?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-38-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-38-LaTeXStyle-editor"> <div class="panel-body"> <p>We expect you to provide your DARTS artifact as a single (compressed) file. To calculate the <b>md5-sum</b> of this file on your local machine, please type:</p> <ul> <li><code>md5 [artifact_filename]</code> in a Linux/Mac OS terminal</li> <li><code>CertUtil -hashfile [artifact_filename] MD5</code> in a Windows Shell</li> </ul> <p>The output should be a 32 byte hex string. Use this string as argument of the mdsum-macro, e.g., <code>\mdsum{b157da23549e1d718bb16d22ded6d941}</code>. </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/38"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/38</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"> DARTS, Vol. 10, Issue 2, <b>Special Issue of the 38th European Conference on Object-Oriented Programming (ECOOP 2024)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-10-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Karine Even-Mendoza and Raphaël Monat </li> <li class="list-group-item"> DARTS, Vol. 10, Issue 1, <b>Special Issue of the 36th Euromicro Conference on Real-Time Systems (ECRTS 2024)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-10-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Matthias Becker and Catherine E. Nemitz </li> <li class="list-group-item"> DARTS, Vol. 9, Issue 2, <b>Special Issue of the 37th European Conference on Object-Oriented Programming (ECOOP 2023)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-9-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Hernán Ponce de León and Stefan Winter </li> <li class="list-group-item"> DARTS, Vol. 9, Issue 1, <b>Special Issue of the 35th Euromicro Conference on Real-Time Systems (ECRTS 2023)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-9-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Matthias Becker and Julien Forget </li> <li class="list-group-item"> DARTS, Vol. 8, Issue 1, <b>Special Issue of the 34th Euromicro Conference on Real-Time Systems (ECRTS 2022)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-8-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Angeliki Kritikakou and Matthias Becker </li> <li class="list-group-item"> DARTS, Vol. 8, Issue 2, <b>Special Issue of the 36th European Conference on Object-Oriented Programming (ECOOP 2022)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-8-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Alessandra Gorla and Stefan Winter </li> <li class="list-group-item"> DARTS, Vol. 7, Issue 2, <b>Special Issue of the 35th European Conference on Object-Oriented Programming (ECOOP 2021)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-7-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> William G. J. Halfond and Quentin Stiévenart </li> <li class="list-group-item"> DARTS, Vol. 7, Issue 1, <b>Special Issue of the 33rd Euromicro Conference on Real-Time Systems (ECRTS 2021)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-7-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Alessandro Biondi and Angeliki Kritikakou </li> <li class="list-group-item"> DARTS, Vol. 6, Issue 2, <b>Special Issue of the 34th European Conference on Object-Oriented Programming (ECOOP 2020)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-6-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Lisa Nguyen Quang Do and Manuel Rigger </li> <li class="list-group-item"> DARTS, Vol. 6, Issue 1, <b>Special Issue of the 32nd Euromicro Conference on Real-Time Systems (ECRTS 2020)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-6-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Alessandro V. Papadopoulos and Alessandro Biondi </li> <li class="list-group-item"> DARTS, Vol. 5, Issue 2, <b>Special Issue of the 33rd European Conference on Object-Oriented Programming (ECOOP 2019)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-5-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Maria Christakis and Manuel Rigger </li> <li class="list-group-item"> DARTS, Vol. 5, Issue 1, <b>Special Issue of the 31st Euromicro Conference on Real-Time Systems (ECRTS 2019)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-5-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Sophie Quinton, Sebastian Altmeyer, and Alessandro Papadopoulos </li> <li class="list-group-item"> DARTS, Vol. 4, Issue 3, <b>Special Issue of the 32nd European Conference on Object-Oriented Programming (ECOOP 2018)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-4-issue-3"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Maria Christakis, Philipp Haller, and Marianna Rapoport </li> <li class="list-group-item"> DARTS, Vol. 4, Issue 2, <b>Special Issue of the 30th Euromicro Conference on Real-Time Systems (ECRTS 2018)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-4-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Sebastian Altmayer and Martina Maggio </li> <li class="list-group-item"> DARTS, Vol. 4, Issue 1, <b>Special Issue of the 13th International Symposium on Software Engineering for Adaptive and Self-Managing Systems (SEAMS 2018)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-4-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Philipp Haller, Michael Pradel, and Tijs van der Storm </li> <li class="list-group-item"> DARTS, Vol. 3, Issue 2, <b>Special Issue of the 31st European Conference on Object-Oriented Programming (ECOOP 2017)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-3-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Philipp Haller, Michael Pradel, and Tijs van der Storm </li> <li class="list-group-item"> DARTS, Vol. 3, Issue 1, <b>Special Issue of the 12th International Symposium on Software Engineering for Adaptive and Self-Managing Systems (SEAMS 2017)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-3-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Javier Cámara, Bashar Nuseibeh, and David Garlan </li> <li class="list-group-item"> DARTS, Vol. 1, Issue 1, <b>Special Issue of the 29th European Conference on Object-Oriented Programming (ECOOP 2015)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-1-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Camil Demetrescu </li> <li class="list-group-item"> DARTS, Vol. 2, Issue 1, <b>Special Issue of the 30th European Conference on Object-Oriented Programming (ECOOP 2016)</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DARTS-volume-2-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Matthew Flatt and Tijs van der Storm </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> </body> </html>

CINXE.COM

DSub