OASIcs

<!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="Cp9a84yx12LI4fI5JaJchKFoBqzhtaJxOcgjIf5Z" /> <link rel="canonical" href="https://drops.dagstuhl.de/entities/series/OASIcs" /> <title>OASIcs</title> <link rel="icon" href="https://drops.dagstuhl.de/favicon.ico" /> <link rel="stylesheet" href="https://drops.dagstuhl.de/css/app.css?drops-core-2024-10-22" /> <style >[wire\:loading][wire\:loading], [wire\:loading\.delay][wire\:loading\.delay], [wire\:loading\.inline-block][wire\:loading\.inline-block], [wire\:loading\.inline][wire\:loading\.inline], [wire\:loading\.block][wire\:loading\.block], [wire\:loading\.flex][wire\:loading\.flex], [wire\:loading\.table][wire\:loading\.table], [wire\:loading\.grid][wire\:loading\.grid], [wire\:loading\.inline-flex][wire\:loading\.inline-flex] {display: none;}[wire\:loading\.delay\.none][wire\:loading\.delay\.none], [wire\:loading\.delay\.shortest][wire\:loading\.delay\.shortest], [wire\:loading\.delay\.shorter][wire\:loading\.delay\.shorter], [wire\:loading\.delay\.short][wire\:loading\.delay\.short], [wire\:loading\.delay\.default][wire\:loading\.delay\.default], [wire\:loading\.delay\.long][wire\:loading\.delay\.long], [wire\:loading\.delay\.longer][wire\:loading\.delay\.longer], [wire\:loading\.delay\.longest][wire\:loading\.delay\.longest] {display: none;}[wire\:offline][wire\:offline] {display: none;}[wire\:dirty]:not(textarea):not(input):not(select) {display: none;}:root {--livewire-progress-bar-color: #2299dd;}[x-cloak] {display: none !important;}</style> </head> <body> <nav class="navbar main fixed-top navbar-expand-lg navbar-light bg-light"> <div class="container-fluid"> <a class="navbar-brand" href="https://www.dagstuhl.de"> <img class="lzi-logo" src="https://drops.dagstuhl.de/images/LZI-Logo.jpg" width="84" height=62" alt="Schloss Dagstuhl - LZI - Logo" /> </a> <button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation"> <span class="navbar-toggler-icon"></span> </button> <div class="collapse navbar-collapse" id="navbarSupportedContent"> <ul class="navbar-nav me-auto mb-2 mb-lg-0"> <li class="nav-item" style="white-space: nowrap"> <a class="nav-link" href="https://drops.dagstuhl.de"> <i class="bi bi-house large-icon"></i> DROPS </a> </li> <li class="nav-item dropdown"> <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownSeries" role="button" data-bs-toggle="dropdown" aria-expanded="false"> <i class="bi bi-journals large-icon"></i> Series </a> <ul class="dropdown-menu" aria-labelledby="navbarDropdown"> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/series/LIPIcs"> LIPIcs – Leibniz International Proceedings in Informatics </a> </li> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/series/OASIcs"> OASIcs – Open Access Series in Informatics </a> </li> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/series/DFU"> Dagstuhl Follow-Ups </a> </li> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/series/DagAnnRep"> Schloss Dagstuhl Jahresbericht </a> </li> <li class="dropdown-divider"></li> <li> <a class="dropdown-item" href="/#discontinued-series">Discontinued Series</a> </li> </ul> </li> <li class="nav-item dropdown"> <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownJournals" role="button" data-bs-toggle="dropdown" aria-expanded="false"> <i class="bi bi-journal large-icon"></i> Journals </a> <ul class="dropdown-menu" aria-labelledby="navbarDropdown"> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/journal/DARTS"> DARTS – Dagstuhl Artifacts Series </a> </li> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/journal/DagRep"> Dagstuhl Reports </a> </li> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/journal/DagMan"> Dagstuhl Manifestos </a> </li> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/journal/LITES"> LITES – Leibniz Transactions on Embedded Systems </a> </li> <li><a class="dropdown-item" href="https://drops.dagstuhl.de/entities/journal/TGDK"> TGDK – Transactions on Graph Data and Knowledge </a> </li> </ul> </li> <li class="nav-item dropdown"> <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownConferences" role="button" data-bs-toggle="dropdown" aria-expanded="false"> <i class="bi bi-people large-icon"></i> Conferences </a> <ul class="dropdown-menu conference-dropdown" aria-labelledby="navbarDropdown"> <div class="row"> <div class="col-sm-4 nav-conference-col"> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/AFT"> AFT </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/AIB"> AIB </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/AofA"> AofA </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/APPROX"> APPROX </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ATMOS"> ATMOS </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/CALCO"> CALCO </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/CCC"> CCC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/CONCUR"> CONCUR </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/COSIT"> COSIT </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/CP"> CP </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/CPM"> CPM </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/CSL"> CSL </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/DISC"> DISC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/DITAM"> DITAM </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/DNA"> DNA </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ECOOP"> ECOOP </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ECRTS"> ECRTS </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ESA"> ESA </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/FAB"> FAB </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/FMBC"> FMBC </a> </li> </div> <div class="col-sm-4 nav-conference-col"> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/FORC"> FORC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/FSCD"> FSCD </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/FSTTCS"> FSTTCS </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/FUN"> FUN </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/GD"> GD </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/GIScience"> GIScience </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ICALP"> ICALP </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ICDT"> ICDT </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ICPEC"> ICPEC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/IPEC"> IPEC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/iPMVM"> iPMVM </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ISAAC"> ISAAC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ITC"> ITC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ITCS"> ITCS </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/ITP"> ITP </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/LDK"> LDK </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/MFCS"> MFCS </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/Microservices"> Microservices </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/NG-RES"> NG-RES </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/OPODIS"> OPODIS </a> </li> </div> <div class="col-sm-4 nav-conference-col"> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/PARMA"> PARMA </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/RANDOM"> RANDOM </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/SAND"> SAND </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/SAT"> SAT </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/SEA"> SEA </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/SLATE"> SLATE </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/SNAPL"> SNAPL </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/SoCG"> SoCG </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/STACS"> STACS </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/SWAT"> SWAT </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/TIME"> TIME </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/Tokenomics"> Tokenomics </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/TQC"> TQC </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/TYPES"> TYPES </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/WABI"> WABI </a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/conference/WCET"> WCET </a> </li> </div> </div> </ul> </li> <li class="nav-item"> <a class="nav-link" href="https://drops.dagstuhl.de/docs/about" id="navbarAbout"> <i class="bi bi-info-circle large-icon"></i><span class="nav-text-about-drops"> About DROPS</span> </a> </li> </ul> <form class="navbar-search d-flex" action="https://drops.dagstuhl.de/search" method="post"> <input type="hidden" name="_token" value="Cp9a84yx12LI4fI5JaJchKFoBqzhtaJxOcgjIf5Z" autocomplete="off"> <div class="input-group"> <input class="form-control" type="search" placeholder="Search" aria-label="Search" name="term" autocomplete="off" maxlength="600"> <button class="btn btn-outline-success" type="submit"> <i class="bi bi-search" style="color: #000"></i> </button> </div> </form> <ul class="navbar-nav nav-metadata"> <li class="nav-item dropdown"> <a class="nav-link dropdown-toggle" id="navbarDropdownMetadata" role="button" data-bs-toggle="dropdown" aria-expanded="false"> <i class="bi bi-database-down large-icon"></i><span class="nav-text-metadata">Metadata Export</span> </a> <ul class="dropdown-menu dropdown-metadata" aria-labelledby="navbarDropdownMetadata"> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/metadata">Metadata Export</a> </li> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/oai?verb=Identify" target="_blank">OAI Interface</a> </li> </ul> </li> </ul> </div> </div> </nav> <div id="app" data-release="drops-core-2024-10-22" class="container "> <div id="_top-of-page"></div> <div class="fixed-search-button"><i class="bi bi-search"></i></div> <div class="series-details"> <br> <div class="entity-type series"> <div> <span class="entity-type-name"> <i class="bi bi-journals"></i> Series </span> <span class="sharing-section"> <span class="sharing-buttons"> <span class="dropdown"> <a class="btn sharing-btn metadata dropdown-toggle" href="#" role="button" data-bs-toggle="dropdown" aria-expanded="false"><i class="bi bi-download"></i></a> <ul class="dropdown-menu dropdown-menu-end"> <li> <a class="dropdown-item" href="https://drops.dagstuhl.de/entities/series/OASIcs/metadata/schema-org"> Export Schema.org </a> </li> </ul> </span> </span> </span> </div> </div> <hr> <div class="text-center"> <img style="" src="https://drops.dagstuhl.de/images/OASIcs-logo.png" alt="OASIcs-logo" class="oasics-logo"/> <h1 class="mt-4">Open Access Series in Informatics</h1> <small style="margin-right: 2em">ISSN 2190-6807</small> </div> <hr> <div class="mt-5"> <ul class="nav nav-tabs" id="series-documentation" role="tablist"> <li class="nav-item" role="presentation"> <a class="nav-link active" id="publications-tab" data-bs-toggle="tab" href="#publications" role="tab" aria-controls="publications" aria-selected="false"> Publications </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="general-tab" data-bs-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-bs-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-bs-toggle="tab" href="#selection" role="tab" aria-controls="selection" aria-selected="false"> Selection and Application </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="charge-tab" data-bs-toggle="tab" href="#charge" role="tab" aria-controls="charge" aria-selected="false"> Processing Charge </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="author-tab" data-bs-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-bs-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="contact-tab" data-bs-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 show active" id="publications" role="tabpanel" aria-labelledby="publications-tab"> <div class="row mt-2"> <div class="col-sm-8 mt-2"> <h2 class="mt-3">Conferences / Workshops </h2> <div class="conferences"> <div style="margin: 1em auto auto auto;"> <a href="https://drops.dagstuhl.de/entities/conference/AIB"><span class="badge bg-secondary conference-btn">AIB</span></a> <a href="https://drops.dagstuhl.de/entities/conference/ATMOS"><span class="badge bg-secondary conference-btn">ATMOS</span></a> <a href="https://drops.dagstuhl.de/entities/conference/DITAM"><span class="badge bg-secondary conference-btn">DITAM</span></a> <a href="https://drops.dagstuhl.de/entities/conference/FAB"><span class="badge bg-secondary conference-btn">FAB</span></a> <a href="https://drops.dagstuhl.de/entities/conference/FMBC"><span class="badge bg-secondary conference-btn">FMBC</span></a> <a href="https://drops.dagstuhl.de/entities/conference/ICPEC"><span class="badge bg-secondary conference-btn">ICPEC</span></a> <a href="https://drops.dagstuhl.de/entities/conference/iPMVM"><span class="badge bg-secondary conference-btn">iPMVM</span></a> <a href="https://drops.dagstuhl.de/entities/conference/LDK"><span class="badge bg-secondary conference-btn">LDK</span></a> <a href="https://drops.dagstuhl.de/entities/conference/Microservices"><span class="badge bg-secondary conference-btn">Microservices</span></a> <a href="https://drops.dagstuhl.de/entities/conference/NG-RES"><span class="badge bg-secondary conference-btn">NG-RES</span></a> <a href="https://drops.dagstuhl.de/entities/conference/PARMA"><span class="badge bg-secondary conference-btn">PARMA</span></a> <a href="https://drops.dagstuhl.de/entities/conference/SLATE"><span class="badge bg-secondary conference-btn">SLATE</span></a> <a href="https://drops.dagstuhl.de/entities/conference/Tokenomics"><span class="badge bg-secondary conference-btn">Tokenomics</span></a> <a href="https://drops.dagstuhl.de/entities/conference/WCET"><span class="badge bg-secondary conference-btn">WCET</span></a> </div> </div> <br/><br/> <h2 class="mt-3">Volumes</h2> <div class="documents"> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 125</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-125">35th International Conference on Principles of Diagnosis and Resilient Systems (DX 2024)</a></h5> <p class="card-text small subtitle"> DX 2024, November 4-7, 2024, Vienna, Austria </p> <p class="card-text small editors"> <b>Editors:</b> Ingo Pill, Avraham Natan, and Franz Wotawa </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 124</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-124">Commit2Data</a></h5> <p class="card-text small editors"> <b>Editors:</b> Boudewijn R. Haverkort, Aldert de Jongste, Pieter van Kuilenburg, and Ruben D. Vromans </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 123</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-123">24th Symposium on Algorithmic Approaches for Transportation Modelling, Optimization, and Systems (ATMOS 2024)</a></h5> <p class="card-text small subtitle"> ATMOS 2024, September 5-6, 2024, Royal Holloway, London, United Kingdom </p> <p class="card-text small editors"> <b>Editors:</b> Paul C. Bouman and Spyros C. Kontogiannis </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 122</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-122">5th International Computer Programming Education Conference (ICPEC 2024)</a></h5> <p class="card-text small subtitle"> ICPEC 2024, June 27-28, 2024, Lisbon, Portugal </p> <p class="card-text small editors"> <b>Editors:</b> André L. Santos and Maria Pinto-Albuquerque </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 121</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-121">22nd International Workshop on Worst-Case Execution Time Analysis (WCET 2024)</a></h5> <p class="card-text small subtitle"> WCET 2024, July 9, 2024, Lille, France </p> <p class="card-text small editors"> <b>Editors:</b> Thomas Carle </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 120</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-120">13th Symposium on Languages, Applications and Technologies (SLATE 2024)</a></h5> <p class="card-text small subtitle"> SLATE 2024, July 4-5, 2024, Águeda, Portugal </p> <p class="card-text small editors"> <b>Editors:</b> Mário Rodrigues, José Paulo Leal, and Filipe Portela </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 119</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-119">The Provenance of Elegance in Computation - Essays Dedicated to Val Tannen</a></h5> <p class="card-text small subtitle"> Tannen's Festschrift, May 24-25, 2024, University of Pennsylvania, Philadelphia, PA, USA </p> <p class="card-text small editors"> <b>Editors:</b> Antoine Amarilli and Alin Deutsch </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 118</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-118">5th International Workshop on Formal Methods for Blockchains (FMBC 2024)</a></h5> <p class="card-text small subtitle"> FMBC 2024, April 7, 2024, Luxembourg City, Luxembourg </p> <p class="card-text small editors"> <b>Editors:</b> Bruno Bernardo and Diego Marmsoler </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 117</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-117">Fifth Workshop on Next Generation Real-Time Embedded Systems (NG-RES 2024)</a></h5> <p class="card-text small subtitle"> NG-RES 2024, January 17-19, 2024, Munich, Germany </p> <p class="card-text small editors"> <b>Editors:</b> Patrick Meumeu Yomsi and Stefan Wildermann </p> </div> </div> <div class="entity-list-item volume card m-3" data-show="1"> <div class="entity-type"><i class="bi bi-book-half"></i> Volume</div> <div class="card-body"> <p class="card-text intro">OASIcs, Volume 116</p> <h5 class="card-title"><a href="https://drops.dagstuhl.de/entities/volume/OASIcs-volume-116">15th Workshop on Parallel Programming and Run-Time Management Techniques for Many-Core Architectures and 13th Workshop on Design Tools and Architectures for Multicore Embedded Computing Platforms (PARMA-DITAM 2024)</a></h5> <p class="card-text small subtitle"> PARMA-DITAM 2024, January 18, 2024, Munich, Germany </p> <p class="card-text small editors"> <b>Editors:</b> João Bispo, Sotirios Xydis, Serena Curzel, and Luís Miguel Sousa </p> </div> </div> <nav> <ul class="pagination"> <li class="page-item disabled" aria-disabled="true" aria-label="« Previous"> <span class="page-link" aria-hidden="true">&lsaquo;</span> </li> <li class="page-item active" aria-current="page"><span class="page-link">1</span></li> <li class="page-item"><a class="page-link" href="?page=2">2</a></li> <li class="page-item"><a class="page-link" href="?page=3">3</a></li> <li class="page-item"><a class="page-link" href="?page=4">4</a></li> <li class="page-item"><a class="page-link" href="?page=5">5</a></li> <li class="page-item"><a class="page-link" href="?page=6">6</a></li> <li class="page-item"><a class="page-link" href="?page=7">7</a></li> <li class="page-item"><a class="page-link" href="?page=8">8</a></li> <li class="page-item"><a class="page-link" href="?page=9">9</a></li> <li class="page-item"><a class="page-link" href="?page=10">10</a></li> <li class="page-item"><a class="page-link" href="?page=11">11</a></li> <li class="page-item"><a class="page-link" href="?page=12">12</a></li> <li class="page-item"><a class="page-link" href="?page=13">13</a></li> <li class="page-item"> <a class="page-link" href="?page=2" rel="next" aria-label="Next »">&rsaquo;</a> </li> </ul> </nav> </div> </div> <div class="col-sm-4 mt-2"> <h2 class="mt-3">Access Numbers</h2> <ul> <li> <a href="#" class="btn-statistics" data-entity="series/OASIcs" data-title="Open Access Series in Informatics"> <i class="bi bi-graph-up"></i> Detailed Access Statistics available here </a> </li> <li> Total Document Accesses (updated on a weekly basis): <div class="stats-total"> <div class="stats total-downloads"> <div class="circle"> <div class="number" data-number="0">0</div> </div> <div class="label">PDF Downloads</div> </div> <div class="stats total-metadata-views"> <div class="circle"> <div class="number" data-number="0">0</div> </div> <div class="label">Metadata Views</div> </div> </div>  </li> </ul> <br> <h2 class="mt-3">Authors</h2> <div wire:snapshot="{"data":{"term":"","matches":[[],{"s":"arr"}],"searchHasBeenClicked":false},"memo":{"id":"i2U1t1X2DnnoPk8SIEoR","name":"drops-core::author-search","path":"entities\/series\/OASIcs","method":"GET","children":[],"scripts":[],"assets":[],"errors":[],"locale":"en"},"checksum":"43b8e51960f032d6063ce3712d26d346164996e87306f4a50d909487c173bac7"}" wire:effects="[]" wire:id="i2U1t1X2DnnoPk8SIEoR" class="author-search"> <form wire:submit="searchClicked()" class="author-search navbar-search d-flex"> <div class="input-group" style="position: relative"> <input class="form-control" type="search" placeholder="Search Authors" aria-label="Search" wire:model.live.debounce.300ms="term" maxlength="600"> <span wire:loading class="spin author-loader"> <i class="bi bi-arrow-repeat"></i> </span> <span class="btn btn-outline-success" wire:click="searchClicked()"> <i class="bi bi-search" style="color: #000"></i> </span> </div> </form> <div class="results mb-2" style="min-height: 1.5em">  </div> </div> <div wire:snapshot="{"data":{"metadataKey":"dagstuhl.contributor.author:keyword","context":"series\/OASIcs","size":16,"route":"https:\/\/drops.dagstuhl.de\/search\/documents?author="},"memo":{"id":"sJbqeXCAlgSxv2WXdSyC","name":"drops-core::aggregation-list","path":"entities\/series\/OASIcs","method":"GET","children":[],"scripts":[],"assets":[],"errors":[],"locale":"en"},"checksum":"bf362469d7989b5292fc1a867760775dd28ad194f0337c1df675acf980b69cd7"}" wire:effects="[]" wire:id="sJbqeXCAlgSxv2WXdSyC" class="aggregation-list"> <ul class="list-group">   <li class="list-group-item filter-item"> <span class="badge bg-secondary">50</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Henriques, Pedro Rangel">Henriques, Pedro Rangel</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">47</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Queirós, Ricardo">Queirós, Ricardo</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">45</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Leal, José Paulo">Leal, José Paulo</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">40</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Simões, Alberto">Simões, Alberto</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">29</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Schöbel, Anita">Schöbel, Anita</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">24</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Borndörfer, Ralf">Borndörfer, Ralf</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">22</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Almeida, José João">Almeida, José João</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">21</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Gonçalo Oliveira, Hugo">Gonçalo Oliveira, Hugo</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">20</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Müller-Hannemann, Matthias">Müller-Hannemann, Matthias</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">18</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Pereira, Maria João Varanda">Pereira, Maria João Varanda</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">18</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Portela, Filipe">Portela, Filipe</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">15</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Lisper, Björn">Lisper, Björn</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">15</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Rochange, Christine">Rochange, Christine</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">14</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Batista, Fernando">Batista, Fernando</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">13</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Reineke, Jan">Reineke, Jan</a>  </li>   <li class="list-group-item filter-item"> <span class="badge bg-secondary">13</span>  <a href="https://drops.dagstuhl.de/search/documents?author=Schoeberl, Martin">Schoeberl, Martin</a>  </li>   <li class="filter-item list-group-item list-group-item-secondary" wire:click="showMore()"> <i class="bi bi-plus"></i> Show More... </li>   </ul> </div> </div> </div> </div> <div class="tab-pane fade" id="general" role="tabpanel" aria-labelledby="general-tab"> <div class="row"> <div class="col-sm-2"> </div> <div class="col-sm-10"> <p>The <i>OpenAccess Series in Informatics</i> offers a venue for the Open Access and online publication of peer-reviewed proceedings based on international scientific events (workshops, symposia, conferences, ...) that took place outside of Schloss Dagstuhl.</p> </div> </div> <hr> <div class="row"> <div class="col-sm-2"> <h5>Aims and Scope</h5> </div> <div class="col-sm-10"> <p>The <em>OpenAccess Series in Informatics </em>aims at a suitable publication venue to publish peer-reviewed collections of papers emerging from an international scientific event that took place outside of Schloss Dagstuhl.</p> <p>The scope of the <em>OpenAccess Series in Informatics </em>comprises all research topics in informatics.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Open Access Policy</h5> </div> <div class="col-sm-10"> OASIcs volumes are peer-reviewed and published according to the principle of OpenAccess, i.e., they are available online and free of charge. The authors retain their copyright. Preprints (pre-review manuscripts), post prints (authors accepted manuscripts, AAM), and the version of record (VoR) can be deposited without restrictions. </div> </div> <div class="row"> <div class="col-sm-2"> <h5>License</h5> </div> <div class="col-sm-10"> Each article is published under a Creative Commons CC BY license (<a href="http://creativecommons.org/licenses/by/4.0/" title="Link zu http://creativecommons.org/licenses/by/4.0/" target="_blank">http://creativecommons.org/licenses/by/4.0/</a>).<br/> The metadata provided by Dagstuhl Publishing on its webpages, as well as their export formats (such as XML or BibTeX) available at our website, is released under the CC0 1.0 Public Domain Dedication license (<a href="https://creativecommons.org/publicdomain/zero/1.0/legalcode" title="Link zu https://creativecommons.org/publicdomain/zero/1.0/legalcode" target="_blank">https://creativecommons.org/publicdomain/zero/1.0/legalcode</a>). </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Processing Charge</h5> </div> <div class="col-sm-10"> <ul><li>We charge the total cost of the entire volume to the conference organisation. We do not charge individual authors.</li><li>Processing Charge of 60 EUR (net) ...<ul><li>per published paper (if the average count of main text<sup>1</sup> pages per article is &leq; 20)</li><li>per block of 20 main text pages (otherwise).</li></ul></li><li>To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then: <p>Total cost(entire volume) = max(n,floor(P/20)) * APC (net).</p></li></ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>ISSN</h5> </div> <div class="col-sm-10"> <span>2190-6807</span> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Identifier</h5> </div> <div class="col-sm-10"> Each volumes is assigned an ISBN and a DOI.<br /> Each article is assigned a DOI and a URN.<br /> To facilitate author identification, the Open Researcher and Contributor ID (ORCID) is optionally included during upload so that authors can be uniquely linked to their ORCID iD. </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Longterm Preservation</h5> </div> <div class="col-sm-10"> The digital archiving of each volume is done in cooperation with the Deutsche Nationalbibliothek/German National Library (<a href="http://www.dnb.de/" title="Link zu http://www.dnb.de/" target="_blank">http://www.dnb.de</a>). </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Publication Ethics</h5> </div> <div class="col-sm-10"> Dagstuhl Publishing as a division of Schloss Dagstuhl – Leibniz-Zentrum für Informatik GmbH (LZI, or Schloss Dagstuhl for short) and its series and journals adhere to <a target="_blank" href="https://publicationethics.org/core-practices">CORE practices guidance</a> laid by <a target="_blank" href="https://publicationethics.org/">COPE (Committee on Publication Ethics)</a> and are committed to the rules of good scientific practice in accordance with the <a target="_blank" href="https://www.leibniz-gemeinschaft.de/en/about-us/leibniz-integrity/good-scientific-practice-and-ombuds-services">guidelines of the Leibniz Association</a> and the <a target="_blank" href="https://wissenschaftliche-integritaet.de/en/">German Research Foundation (DFG)</a>. We expect all parties (so authors, editors, and reviewers) involved in the publication and review process of contributions to be published in the series to follow these core practises and the guidelines. Allegations of misconduct will be investigated in accordance with the COPE Best Practice Guidelines as far as is practicable. If notified of a potential breach of publication ethics, we encourage editors and authors to inform Dagstuhl Publishing contact as soon as possible. Detailed information can be found on the <a target="_blank" href="https://www.dagstuhl.de/en/publishing/ethics">Publication Ethics website</a>. </div> </div> </div> <div class="tab-pane fade" id="editorialboard" role="tabpanel" aria-labelledby="editorialboard-tab"> <div class="row"> <div class="col-sm-2"> <h5>Editorial Board</h5> </div> <div class="col-sm-10"> <ul> <li> Daniel Cremers <a href="http://vision.in.tum.de/members/cremers">TU München, DE</a> </li> <li> Barbara Hammer <a href="http://www.techfak.uni-bielefeld.de/~bhammer/">Universität Bielefeld, DE</a> </li> <li> Marc Langheinrich <a href="http://uc.inf.usi.ch/team/langheinrich/">University of Lugano, CH</a> </li> <li> Dorothea Wagner <a href="http://i11www.iti.uni-karlsruhe.de/members/dorothea_wagner/index">KIT - Karlsruher Institut für Technologie, DE</a> </li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Constitution</h5> </div> <div class="col-sm-10"> </div> </div> </div> <div class="tab-pane fade" id="selection" role="tabpanel" aria-labelledby="selection-tab"> <div class="row"> <div class="col-sm-2"> <h5>Editorial Policy</h5> </div> <div class="col-sm-10"> <p>For publishing a volume in the <i>OASIcs</i> series, the workshop/conference organizers have to submit an informal proposal covering the following issues:<ul><li><b>Content:</b> Topics, size of the articles, number of articles, ...</li><li><b>Peer Review:</b> How is the peer review process organized?</li><li><b>Timeline:</b> Coarse schedule regarding the deadline for submission, duration of the peer review process or notification deadline, respectively, deadline for submission of camera-ready documents.</li></ul></p><p>Please note that the minimum number of articles per volume is 10. Information about the current processing charge is available on the dedicated tab <i>Processing Charge</i>.</p><p>Please send your proposal as a single PDF file to <a href='mailto:michael.wagner@dagstuhl.de '>Dr. Michael Wagner</a>.</p><p>The proposal will be checked internally and then forwarded to the Editorial Board which will take a decision in a little while. The following decisions are possible: (1) acceptance, (2) request for revised re-submission, or (3) rejection. Please note that there is no general right to acceptance.</p> </div> </div> <hr /> </div> <div class="tab-pane fade" id="charge" role="tabpanel" aria-labelledby="charge-tab"> <div class="row"> <div class="col-sm-2"> <h5>In Short</h5> </div> <div class="col-sm-10"> <ul><li>We charge the total cost of the entire volume to the conference organisation. We do not charge individual authors.</li><li>Processing Charge of 60 EUR (net) ...<ul><li>per published paper (if the average count of main text<sup>1</sup> pages per article is &leq; 20)</li><li>per block of 20 main text pages (otherwise).</li></ul></li><li>To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then: <p>Total cost(entire volume) = max(n,floor(P/20)) * APC (net).</p></li></ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Background info concerning APC</h5> </div> <div class="col-sm-10"> As a publicly funded institution, we have to recover the costs of our publishing activities so that there is no competitive advantage over commercial providers. For the cost recovery, we work with an article processing charge (APC), which currently is 60 EUR (net). This amount was set under the assumption that the average length of a paper does not substantially exceed 15 to 20 main text pages, i.e., number of pages after typesetting excluding title page and the bibliography. </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Resulting Page-Limit Recommendation</h5> </div> <div class="col-sm-10"> <p>Given the above, we suggest 20 main text pages<sup>1</sup> as a page limit, which could for instance be in the form of 15 pages for the main body of paper plus up to 5 pages for appendices. Note that this is only a recommendation and it is up to the editors of the respective volume to decide on a policy regarding the page limit<sup>2</sup>.</p><p><sup>1</sup> 'Main-text pages' are all contents except the title page with title, authors, affiliations, abstracts, ..... and the bibliography.<br /><sup>2</sup> Please note that we expect a certain flexibility concerning any page limit (+/- 1 page) to avoid too much extra effort to harmonize LIPIcs-compliant formatting and page limit for both authors and final typesetting by the LIPIcs Office.</p> </div> </div> <hr /> </div> <div class="tab-pane fade" id="author" role="tabpanel" aria-labelledby="author-tab"> <div class="row"> <div class="col-sm-2"> <h5>Templates and Example Files</h5> </div> <div class="col-sm-10"> <p>Please download the current version of the OASIcs style along with an example file and detailed author instructions:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>oasics-v2021</b> <span class="label label-success "> v2021.1.3 </span> <aside style="display: inline-block; margin-left: 10px;"> <div class="btn-group"> <button type="button" class="btn btn-xs btn-default dropdown-toggle" data-bs-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Download <span class="caret"></span> </button> <ul class="dropdown-menu"> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/authors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/authors/tgz"> as tar.gz-file </a> </li> </ul> </div> <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/88', '_blank', 'width=1024, height='+screen.availHeight)"> Instructions for Authors </span> </aside> </div> </div> <p> For <a href="https://github.com/dagstuhl-publishing/styles/releases">older releases</a> and an <a href="https://github.com/dagstuhl-publishing/styles/issues">issue tracker</a>, see our <a href="https://github.com/dagstuhl-publishing/styles">GitHub archive</a>. </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Typesetting instructions - Summary</h5> </div> <div class="col-sm-10"> <p> <p>The <i>OpenAccess Series in Informatics</i> offers a venue for the Open Access and online publication of peer-reviewed proceedings based on international scientific events (workshops, symposia, conferences, ...) that took place outside of Schloss Dagstuhl.</p> In order to do justice to the high scientific quality of the conferences that publish their proceedings in the OASIcs series, which is ensured by the thorough review process of the respective events, we believe that OASIcs proceedings must have an attractive and consistent layout matching the standard of the series. Moreover, the quality of the metadata, the typesetting and the layout must also meet the requirements of other external parties such as indexing services, DOI registry, funding agencies, among others. The provided guidelines serve as the baseline for the authors, editors, and the publisher to create documents that meet as many different requirements as possible. </p> <p> Please comply with the following instructions when preparing your article for a LIPIcs proceedings volume. (See <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/88', '_blank', 'width=1024, height='+screen.availHeight)"> Instructions for Authors </span> for more details.) </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Minimum requirements</h5> </div> <div class="col-sm-10"> <ul> <li>Use pdflatex and an up-to-date LaTeX system.</li> <li>Use further LaTeX packages and custom made macros carefully and only if required.</li> <li>Use the provided sectioning macros: <code>\section</code>, <code>\subsection</code>, <code>\subsubsection</code>, <code>\paragraph</code>, <code>\paragraph*</code>, and <code>\subparagraph*</code>.</li> <li>Provide suitable graphics of at least 300dpi (preferably in PDF format).</li> <li>Use BibTeX and keep the standard style (<a href="#" data-faq-id="22" class="_faq" tabindex="0"><code>\bibstyle{plainurl}</code> <i class="bi bi-question-circle-fill"></i></a>) for the bibliography.</li> <li>Please try to keep the warnings log as small as possible. Avoid overfull <code>\hboxes</code> and any kind of warnings/errors with the referenced BibTeX entries.</li> <li>Use a spellchecker to correct typos.</li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Mandatory metadata macros</h5> </div> <div class="col-sm-10"> <p>Please set the values of the metadata macros carefully since the information parsed from these macros will be passed to publication servers, catalogues and search engines. Avoid placing macros inside the metadata macros. The following metadata macros/environments are mandatory:</p> <ul> <li><code>\title</code> and, in case of long titles, <code>\titlerunning</code>.</li> <li><a href="#" data-faq-id="14" class="_faq" tabindex="0"><code>\author</code> <i class="bi bi-question-circle-fill"></i></a> one for each author, even if two or more authors have the same affiliation.</li> <li><a href="#" data-faq-id="17" class="_faq" tabindex="0"><code>\authorrunning</code> <i class="bi bi-question-circle-fill"></i></a> (abbreviated first names) and <a href="#" data-faq-id="16" class="_faq" tabindex="0"><code>\Copyright</code> <i class="bi bi-question-circle-fill"></i></a> (concatenated full author names)</li> <li><a href="#" data-faq-id="18" class="_faq" tabindex="0"><code>\ccsdesc</code> <i class="bi bi-question-circle-fill"></i></a> (ACM 2012 subject classification)</li> <li><a href="#" data-faq-id="15" class="_faq" tabindex="0"><code>\keywords</code> <i class="bi bi-question-circle-fill"></i></a> (a comma-separated list of keywords).</li> <li><a href="#" data-faq-id="19" class="_faq" tabindex="0"><code>\relatedversion</code> <i class="bi bi-question-circle-fill"></i></a> (if there is a related version, typically the "full version"); please make sure to provide a persistent URL, e.g., at arXiv.</li> <li><code>\begin{abstract}...\end{abstract}</code>.</li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Please do not ...</h5> </div> <div class="col-sm-10"> <p class="bodytext">Generally speaking, please <b>do not override the style defaults concerning spacing, font and color settings</b>. To be more specific, a short checklist also used by Dagstuhl Publishing during the final typesetting is given below. In case of <b>non-compliance</b> with these rules, Dagstuhl Publishing will remove the corresponding parts of LaTeX code and <b>replace it with the defaults</b>. In serious cases, we may reject the LaTeX-source and expect the corresponding author to revise the relevant parts.</p> <ul> <li>Do not use a different main font. (For example, the <code class="not-allowed">times</code> package is forbidden.)</li> <li>Do not alter the spacing of the provided style file.</li> <li>Do not use <code class="not-allowed">enumitem</code> and <code class="not-allowed">paralist</code>. (The <i>enumerate</i> package is preloaded, so you can use <code>\begin{enumerate}[(a)]</code> or the like.)</li> <li>Do not use "self-made" sectioning commands (e.g., <code class="not-allowed">\noindent{\bf My Paragraph}</code>).</li> <li>Do not hide large text blocks using comments or <code class="not-allowed">\iffalse ... \fi</code> constructions. </li> <li>Do not use conditional structures to include/exclude content. Instead, please provide only the content that should be published - in one file - and nothing else.</li> <li>Do not wrap figures and tables with text. In particular, the package <code class="not-allowed">wrapfig</code> is not supported. </li> <li>Do not change the bibliography style. In particular, do not use author-year citations. (The <code class="not-allowed">natbib</code> package is not supported.) </li> </ul> <p class="bodytext">This is only a summary containing the most relevant details. Please read the complete <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/88', '_blank', 'width=1024, height='+screen.availHeight)"> Instructions for Authors </span> for all details and don't hesitate to contact Dagstuhl Publishing (<a href="mailto:publishing@dagstuhl.de">publishing@dagstuhl.de</a>) in case of questions or comments. </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>FAQ</h5> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Submission</h5> </div> <div class="col-sm-10"> <div class="accordion" id="accordion-Submission"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-24-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-24-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-24-Submission-author"> <span> <span class="label label-info">affiliation</span> <span class="question">What are the <b>minimum requirements</b> on an affiliation?</span> </span> </button> </h2> <div id="FAQ-24-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-24-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-1-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-1-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-1-Submission-author"> <span> <span class="label label-info">authorized user</span> <span class="question">What is an <b>authorized user</b>?</span> </span> </button> </h2> <div id="FAQ-1-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-1-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-2-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-2-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-2-Submission-author"> <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> </button> </h2> <div id="FAQ-2-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-2-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-23-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-23-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-23-Submission-author"> <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> </button> </h2> <div id="FAQ-23-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-23-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-22-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-22-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-22-Submission-author"> <span> <span class="label label-info">bibliography</span> <span class="question">In which format should the <b>bibliography</b> be submitted?</span> </span> </button> </h2> <div id="FAQ-22-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-22-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-25-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-25-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-25-Submission-author"> <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> </button> </h2> <div id="FAQ-25-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-25-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-7-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-7-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-7-Submission-author"> <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> </button> </h2> <div id="FAQ-7-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-7-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-12-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-12-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-12-Submission-author"> <span> <span class="label label-info">page limit</span> <span class="question">Is there a <b>page limit</b> for LIPIcs/OASIcs papers?</span> </span> </button> </h2> <div id="FAQ-12-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-12-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-body"> <p>Please contact the editors of the respective volume concerning this question. It is up to them to decide on a policy regarding the page limit.</p> <p>Note that there is a certain flexibility concerning any page limit (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and the Dagstuhl Editorial Office.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/12"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/12</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-4-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-4-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-4-Submission-author"> <span> <span class="label label-info">related version</span> <span class="question">What is a <b>related version</b>?</span> </span> </button> </h2> <div id="FAQ-4-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-4-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-body"> <p><code>\relatedversion{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/4"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/4</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-5-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-5-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-5-Submission-author"> <span> <span class="label label-info">related version url</span> <span class="question">Why is a <b>URL mandatory</b> for a related version?</span> </span> </button> </h2> <div id="FAQ-5-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-5-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-body"> <p>As all metadata should be self-contained, please add a persistent URL, e.g. <code>\relatedversion{A full version of the paper is available at \url{...}.}</code>. This also simplifies the access for all readers. Additional to the URL, you might add a reference (<code>\cite{...}</code>).</p> <p>Metadata should be self-contained as they are not only part of the document / PDF but also extracted and stored in a machine-readable format along with the actual document.</p> <p>Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable / persistent file storage, we highly recommend to publish your document in a reliable repository like arXiv or HAL.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/5"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/5</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-6-Submission-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-6-Submission-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-6-Submission-author"> <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> </button> </h2> <div id="FAQ-6-Submission-author" class="accordion-collapse collapse" aria-labelledby="heading-6-Submission-author" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion" id="accordion-Author Approval"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-30-AuthorApproval-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-30-AuthorApproval-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-30-AuthorApproval-author"> <span> <span class="label label-info">author approval</span> <span class="question">How does <b>author approval</b> work?</span> </span> </button> </h2> <div id="FAQ-30-AuthorApproval-author" class="accordion-collapse collapse" aria-labelledby="heading-30-AuthorApproval-author" data-bs-parent="#accordion-AuthorApproval"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-28-AuthorApproval-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-28-AuthorApproval-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-28-AuthorApproval-author"> <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> </button> </h2> <div id="FAQ-28-AuthorApproval-author" class="accordion-collapse collapse" aria-labelledby="heading-28-AuthorApproval-author" data-bs-parent="#accordion-AuthorApproval"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-27-AuthorApproval-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-27-AuthorApproval-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-27-AuthorApproval-author"> <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> </button> </h2> <div id="FAQ-27-AuthorApproval-author" class="accordion-collapse collapse" aria-labelledby="heading-27-AuthorApproval-author" data-bs-parent="#accordion-AuthorApproval"> <div class="accordion-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="card-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="accordion" id="accordion-Publication Workflow"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-30-PublicationWorkflow-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-30-PublicationWorkflow-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-30-PublicationWorkflow-author"> <span> <span class="label label-info">author approval</span> <span class="question">How does <b>author approval</b> work?</span> </span> </button> </h2> <div id="FAQ-30-PublicationWorkflow-author" class="accordion-collapse collapse" aria-labelledby="heading-30-PublicationWorkflow-author" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-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="card-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="accordion" id="accordion-LaTeX Style"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-14-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-14-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-14-LaTeXStyle-author"> <span> <span class="label label-info">author macro</span> <span class="question">How to use the <code>\author</code> macro?</span> </span> </button> </h2> <div id="FAQ-14-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-14-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-17-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-17-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-17-LaTeXStyle-author"> <span> <span class="label label-info">authorrunning macro</span> <span class="question">How to use the <code>\authorrunning</code> macro?</span> </span> </button> </h2> <div id="FAQ-17-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-17-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-22-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-22-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-22-LaTeXStyle-author"> <span> <span class="label label-info">bibliography</span> <span class="question">In which format should the <b>bibliography</b> be submitted?</span> </span> </button> </h2> <div id="FAQ-22-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-22-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-18-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-18-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-18-LaTeXStyle-author"> <span> <span class="label label-info">ccsdesc macro</span> <span class="question">How to use the <code>\ccsdesc</code> macro?</span> </span> </button> </h2> <div id="FAQ-18-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-18-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-16-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-16-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-16-LaTeXStyle-author"> <span> <span class="label label-info">copyright macro</span> <span class="question">How to use the <code>\Copyright</code> macro?</span> </span> </button> </h2> <div id="FAQ-16-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-16-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-20-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-20-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-20-LaTeXStyle-author"> <span> <span class="label label-info">funding macro</span> <span class="question">How to use the <code>\funding</code> macro?</span> </span> </button> </h2> <div id="FAQ-20-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-20-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-15-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-15-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-15-LaTeXStyle-author"> <span> <span class="label label-info">keywords macro</span> <span class="question">How to use the <code>\keywords</code> macro?</span> </span> </button> </h2> <div id="FAQ-15-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-15-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-19-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-19-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-19-LaTeXStyle-author"> <span> <span class="label label-info">relatedversiondetails macro</span> <span class="question">How to use the <code>\relatedversiondetails</code> macro?</span> </span> </button> </h2> <div id="FAQ-19-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-19-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-body"> <p><code>\relatedversiondetails{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:</p> <pre> \relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...} </pre> <p> As all metadata should be self-contained, please add a persistent URL to the cited version (as illustrated above). This also simplifies the access for all readers. </p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/19"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/19</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-21-LaTeXStyle-author"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-21-LaTeXStyle-author" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-21-LaTeXStyle-author"> <span> <span class="label label-info">supplementdetails macro</span> <span class="question">How to use the <code>\supplementdetails</code> macro?</span> </span> </button> </h2> <div id="FAQ-21-LaTeXStyle-author" class="accordion-collapse collapse" aria-labelledby="heading-21-LaTeXStyle-author" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-body"> <p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">zenodo</a>, <a href="https://figshare.com/">figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}]{Software}{https://github.com/...} </pre> <p> <p>The <b>subcategory</b> is free text, while the <b>category</b> (Software in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.) </p> <p> Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable/persistent file storage, we highly recommend to publish your document in a <b>reliable repository</b>. </p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/21"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/21</a></small> </div> </div> </div> </div> </div> </div> <br> <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="editor" role="tabpanel" aria-labelledby="editor-tab"> <div class="row"> <div class="col-sm-2"> <h5>General Workflow for Editors - An Overview</h5> </div> <div class="col-sm-10"> <ol> <li><b>Initial contact</b> (usually <span class="label label-success">6-12 months before the publication date</span>) <ul> <li> editors initially contact Dagstuhl Publishing by E-mail not later than 6 months before the planned publication date </li> <li> Dagstuhl Publishing invites editors to register at the Dagstuhl Submission Server </li> </ul> </li> <br/> <li><b>Specifying the details of the volume</b><br/> Dagstuhl Publishing initializes a new volume and asks editors to specify some necessary details, e.g. <ul> <li>the <b>schedule</b> (Dagstuhl Publishing sets some default values that can be adapted by the editors)</li> <li>the <b>paper categories</b> besides regular papers (like "Invited talk", "Short Paper", ...)</li> <li>a statement concerning <a href="#" data-faq-id="11" class="_faq" tabindex="0"><span>page limits </span><i class="bi bi-question-circle-fill"></i></a></li> </ul> </li> <br /> <li><b>Invitation of Authors</b><br/> <ul> <li>editors import the papers from conference management software into the Submission Server</li> <li>Submission Server guides editors through the invitation of authors to submit their camera ready-version</li> </ul> </li> <br /> <li><b>Monitoring Author Submissions</b> (ends <span class="label label-success">≈ 11 weeks before</span> publication)<br/> <ul> <li>editors monitor the progress of paper submissions (there is an E-mail notification)</li> <li>editors <b>send reminders</b> (guided by the Submission Server) in case of incomplete submissions</li> <li>editors <b>check the page limits</b> (if any) and <b>encourage the authors to comply with the style guidelines</b></li> <li>editors write a <b>preface</b> and include it in a <b>pre-generated front matter template</b></li> <li>editors guarantee a <b>handing over of the volume</b> within the agreed deadline</li> <li><b>no need</b> to check the submitted LaTeX sources manually</li> <li><b>no need</b> to do any kind of typesetting</li> </ul> </li> <br /> <li><b>Final Typesetting (by Dagstuhl Publishing)</b> <ul> <li>revision of the LaTeX sources to comply with the <a href="https://submission.dagstuhl.de/series/details/OASIcs#author">OASIcs author guidelines</a></li> <li>extraction of metadata</li> </ul> </li> <br /> <li><b>Approval by Authors</b> (<span class="label label-success">≈ 3 weeks before</span> publication) <ul> <li>opportunity for authors to preview their articles along with the extracted metadata and to ask for minor corrections</li> </ul> </li> <br /> <li><b>Approval by Editors</b> (<span class="label label-success">≈ 1-2 weeks before</span> publication) <ul> <li>opportunity for editors to preview the web-site of the volume on the publication server and to ask for minor corrections</li> </ul> </li> <br /> <li><b>Official Publication of the Volume</b> <ul> <li>includes DOI registration, registration for long-term archiving, submission to indexing services like dblp or Google Scholar</li> <li>Dagstuhl Publishing provides <a href="https://submission.dagstuhl.de/services/metadata">HTML/XML-metadata</a>, e.g., for use in conference web-page</li> </ul> </li> </ol> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Front Matter Template and Example Files</h5> </div> <div class="col-sm-10"> <p>Please download the current version of the OASIcs front matter style along with an example file:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>oasicsmaster-v2021</b> <span class="label label-success "> v2021.1.3 </span> <aside style="display: inline-block; margin-left: 10px;"> <div class="btn-group"> <button type="button" class="btn btn-xs btn-default dropdown-toggle" data-bs-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Download <span class="caret"></span> </button> <ul class="dropdown-menu"> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/editors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/oasics/v2021.1.3/editors/tgz"> as tar.gz-file </a> </li> </ul> </div> </aside> </div> </div> </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="accordion" id="accordion-Submission"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-24-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-24-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-24-Submission-editor"> <span> <span class="label label-info">affiliation</span> <span class="question">What are the <b>minimum requirements</b> on an affiliation?</span> </span> </button> </h2> <div id="FAQ-24-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-24-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-1-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-1-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-1-Submission-editor"> <span> <span class="label label-info">authorized user</span> <span class="question">What is an <b>authorized user</b>?</span> </span> </button> </h2> <div id="FAQ-1-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-1-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-2-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-2-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-2-Submission-editor"> <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> </button> </h2> <div id="FAQ-2-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-2-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-23-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-23-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-23-Submission-editor"> <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> </button> </h2> <div id="FAQ-23-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-23-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-22-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-22-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-22-Submission-editor"> <span> <span class="label label-info">bibliography</span> <span class="question">In which format should the <b>bibliography</b> be submitted?</span> </span> </button> </h2> <div id="FAQ-22-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-22-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-7-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-7-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-7-Submission-editor"> <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> </button> </h2> <div id="FAQ-7-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-7-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-4-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-4-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-4-Submission-editor"> <span> <span class="label label-info">related version</span> <span class="question">What is a <b>related version</b>?</span> </span> </button> </h2> <div id="FAQ-4-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-4-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-body"> <p><code>\relatedversion{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/4"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/4</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-5-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-5-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-5-Submission-editor"> <span> <span class="label label-info">related version url</span> <span class="question">Why is a <b>URL mandatory</b> for a related version?</span> </span> </button> </h2> <div id="FAQ-5-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-5-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-body"> <p>As all metadata should be self-contained, please add a persistent URL, e.g. <code>\relatedversion{A full version of the paper is available at \url{...}.}</code>. This also simplifies the access for all readers. Additional to the URL, you might add a reference (<code>\cite{...}</code>).</p> <p>Metadata should be self-contained as they are not only part of the document / PDF but also extracted and stored in a machine-readable format along with the actual document.</p> <p>Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable / persistent file storage, we highly recommend to publish your document in a reliable repository like arXiv or HAL.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/5"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/5</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-6-Submission-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-6-Submission-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-6-Submission-editor"> <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> </button> </h2> <div id="FAQ-6-Submission-editor" class="accordion-collapse collapse" aria-labelledby="heading-6-Submission-editor" data-bs-parent="#accordion-Submission"> <div class="accordion-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="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/6"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/6</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Publication Workflow</h5> </div> <div class="col-sm-10"> <div class="accordion" id="accordion-Publication Workflow"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-13-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-13-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-13-PublicationWorkflow-editor"> <span> <span class="label label-info">APC</span> <span class="question">How much ist the <b>article processing charge (APC)</b> for a LIPIcs/OASIcs article?</span> </span> </button> </h2> <div id="FAQ-13-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-13-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-body"> <ul> <li>We charge the total cost of the entire volume to the conference organization. We do not charge individual authors.</li> <li>The Processing Charge is 60 EUR (net) ... <ul> <li>per published paper (if the average count of main text (<span class="glyphicon glyphicon-star"></span>) pages per article is ≤ 20)</li> <li>per block of 20 main text pages (otherwise).</li> </ul> <li>To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then: <br>     <code>Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).</code> </li> <li>Please note that we expect a certain flexibility concerning any page limit (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and final typesetting by the Dagstuhl Editorial Office. </li> </ul> <hr/> <p> (<span class="glyphicon glyphicon-star"></span>) "<b>Main-text pages</b>" are all contents except the title page with title, authors, affiliations, abstracts, ..... and the bibliography. </p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/13"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/13</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-30-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-30-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-30-PublicationWorkflow-editor"> <span> <span class="label label-info">author approval</span> <span class="question">How does <b>author approval</b> work?</span> </span> </button> </h2> <div id="FAQ-30-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-30-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-31-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-31-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-31-PublicationWorkflow-editor"> <span> <span class="label label-info">editor approval</span> <span class="question">How does the <b>editor approval</b> work?</span> </span> </button> </h2> <div id="FAQ-31-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-31-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-29-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-29-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-29-PublicationWorkflow-editor"> <span> <span class="label label-info">editor submission</span> <span class="question">What are the editors' tasks between author and editor submission?</span> </span> </button> </h2> <div id="FAQ-29-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-29-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-9-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-9-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-9-PublicationWorkflow-editor"> <span> <span class="label label-info">front matter</span> <span class="question">What should/can be contained in the <b>front matter</b>?</span> </span> </button> </h2> <div id="FAQ-9-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-9-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-body"> The front matter should contain the preface, table of contents and information about the conference organisation, but no other content. Information on the conference should include the list of invited speakers and the titles of their talks. <br/> (due to a policy passed by the <a href="https://www.dagstuhl.de/en/publications/lipics/editorial-board/">LIPIcs editorial board</a> in 2019) </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/9"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/9</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-10-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-10-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-10-PublicationWorkflow-editor"> <span> <span class="label label-info">invited talks</span> <span class="question">How to handle <b>invited talks</b>?</span> </span> </button> </h2> <div id="FAQ-10-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-10-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-body"> For the sake of the dissemination of science, we recommend that conference organisers encourage invited speakers to provide full write-ups for their invited talks to be published as articles (labelled as "Invited Paper") in the proceedings of the conference. In case invited speakers are only willing to provide an (extended) abstract of their invited talks, LIPIcs recommends that those be also published as short papers, explicitly labelled as "Abstract of Invited Talk" in the PDF and metadata to avoid confusion with contributed articles. All papers related to the invited talks will be included in the proceedings, along with the contributed articles, and will attract the APC. This policy ensures that, independent of their lengths, the contributions accompanying invited talks can be easily referenced and also have full metadata including a DOI. <br /> (This is a recommendation of the <a href="https://www.dagstuhl.de/en/publications/lipics/editorial-board/">LIPIcs editorial board</a>.) </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/10"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/10</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-11-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-11-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-11-PublicationWorkflow-editor"> <span> <span class="label label-info">page limit</span> <span class="question">Is there a <b>page limit</b> for LIPIcs/OASIcs papers?</span> </span> </button> </h2> <div id="FAQ-11-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-11-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-body"> <p>As a <b>publicly funded</b> institution, we have to <b>recover the costs</b> of our publishing activities so that there is no competitive advantage over commercial providers. For the cost recovery we work with an article processing charge (APC), which currently is 60 EUR (net); for more details, see below (<span class="glyphicon glyphicon-star"></span>). This amount was set <b>under the assumption that</b> the average <b>length of a paper does not</b> substantially <b>exceed 15 to 20 main text pages</b>, i.e., number of pages after typesetting <b>excluding title page and the bibliography</b>.</p> <p> Given the above, <b>we suggest 20 main text pages as a page limit</b>, which could for instance be in the form of 15 pages for the main body of paper plus up to 5 pages for appendices. Note that this is <b>only a recommendation</b> and it is up to the editors of the respective volume to decide on a policy regarding the page limit. Moreover, we expect a <b>certain flexibility concerning any page limit</b> (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and the Dagstuhl Editorial Office.</p> <hr/> <p>(<span class="glyphicon glyphicon-star"></span>) When specifying a page limit please have in mind the following facts about our APC: <ul> <li>Processing Charge of 60 EUR (net) ... <ul> <li>per published paper (if the average count of main text pages [as defined above] per article is ≤ 20)</li> <li>per block of 20 main text pages (otherwise).</li> </ul> <li>To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then: <br>     <code>Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).</code> </li> </ul> </p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/11"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/11</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-8-PublicationWorkflow-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-8-PublicationWorkflow-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-8-PublicationWorkflow-editor"> <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> </button> </h2> <div id="FAQ-8-PublicationWorkflow-editor" class="accordion-collapse collapse" aria-labelledby="heading-8-PublicationWorkflow-editor" data-bs-parent="#accordion-PublicationWorkflow"> <div class="accordion-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="card-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>Author Approval</h5> </div> <div class="col-sm-10"> <div class="accordion" id="accordion-Author Approval"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-30-AuthorApproval-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-30-AuthorApproval-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-30-AuthorApproval-editor"> <span> <span class="label label-info">author approval</span> <span class="question">How does <b>author approval</b> work?</span> </span> </button> </h2> <div id="FAQ-30-AuthorApproval-editor" class="accordion-collapse collapse" aria-labelledby="heading-30-AuthorApproval-editor" data-bs-parent="#accordion-AuthorApproval"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-28-AuthorApproval-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-28-AuthorApproval-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-28-AuthorApproval-editor"> <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> </button> </h2> <div id="FAQ-28-AuthorApproval-editor" class="accordion-collapse collapse" aria-labelledby="heading-28-AuthorApproval-editor" data-bs-parent="#accordion-AuthorApproval"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-27-AuthorApproval-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-27-AuthorApproval-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-27-AuthorApproval-editor"> <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> </button> </h2> <div id="FAQ-27-AuthorApproval-editor" class="accordion-collapse collapse" aria-labelledby="heading-27-AuthorApproval-editor" data-bs-parent="#accordion-AuthorApproval"> <div class="accordion-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="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/27"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/27</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>LaTeX Style</h5> </div> <div class="col-sm-10"> <div class="accordion" id="accordion-LaTeX Style"> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-17-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-17-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-17-LaTeXStyle-editor"> <span> <span class="label label-info">authorrunning macro</span> <span class="question">How to use the <code>\authorrunning</code> macro?</span> </span> </button> </h2> <div id="FAQ-17-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-17-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-22-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-22-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-22-LaTeXStyle-editor"> <span> <span class="label label-info">bibliography</span> <span class="question">In which format should the <b>bibliography</b> be submitted?</span> </span> </button> </h2> <div id="FAQ-22-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-22-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-18-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-18-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-18-LaTeXStyle-editor"> <span> <span class="label label-info">ccsdesc macro</span> <span class="question">How to use the <code>\ccsdesc</code> macro?</span> </span> </button> </h2> <div id="FAQ-18-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-18-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-16-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-16-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-16-LaTeXStyle-editor"> <span> <span class="label label-info">copyright macro</span> <span class="question">How to use the <code>\Copyright</code> macro?</span> </span> </button> </h2> <div id="FAQ-16-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-16-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-20-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-20-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-20-LaTeXStyle-editor"> <span> <span class="label label-info">funding macro</span> <span class="question">How to use the <code>\funding</code> macro?</span> </span> </button> </h2> <div id="FAQ-20-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-20-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-15-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-15-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-15-LaTeXStyle-editor"> <span> <span class="label label-info">keywords macro</span> <span class="question">How to use the <code>\keywords</code> macro?</span> </span> </button> </h2> <div id="FAQ-15-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-15-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-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="card-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="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-19-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-19-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-19-LaTeXStyle-editor"> <span> <span class="label label-info">relatedversiondetails macro</span> <span class="question">How to use the <code>\relatedversiondetails</code> macro?</span> </span> </button> </h2> <div id="FAQ-19-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-19-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-body"> <p><code>\relatedversiondetails{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:</p> <pre> \relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...} </pre> <p> As all metadata should be self-contained, please add a persistent URL to the cited version (as illustrated above). This also simplifies the access for all readers. </p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/19"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/19</a></small> </div> </div> </div> <div class="accordion-item faq-list-item"> <h2 class="accordion-header" id="heading-21-LaTeXStyle-editor"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#FAQ-21-LaTeXStyle-editor" style="background-color: #eee" aria-expanded="false" aria-controls="FAQ-21-LaTeXStyle-editor"> <span> <span class="label label-info">supplementdetails macro</span> <span class="question">How to use the <code>\supplementdetails</code> macro?</span> </span> </button> </h2> <div id="FAQ-21-LaTeXStyle-editor" class="accordion-collapse collapse" aria-labelledby="heading-21-LaTeXStyle-editor" data-bs-parent="#accordion-LaTeXStyle"> <div class="accordion-body"> <p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">zenodo</a>, <a href="https://figshare.com/">figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}]{Software}{https://github.com/...} </pre> <p> <p>The <b>subcategory</b> is free text, while the <b>category</b> (Software in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.) </p> <p> Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable/persistent file storage, we highly recommend to publish your document in a <b>reliable repository</b>. </p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/21"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/21</a></small> </div> </div> </div> </div> </div> </div> <br> <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="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> <div data-faq-stack-id="22" style="display: none;"> <span class="_title">In which format should the <b>bibliography</b> be submitted?</span> <span class="_content"><p>Dagstuhl Publishing uses <code>BibTEX</code> to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (<code>\bibliographystyle{plainurl}</code>).</p> <ul> <li> The bibliographical entries should be <b>complete according to BibTEX standards</b>, (no warnings or errors should occur). <li> Whenever possible, references should contain an <b>external link</b>, e.g., <code>DOI</code> (preferred) or <code>URL</code> </li> <li> It is highly recommended to use <a href="https://dblp.uni-trier.de/">dblp</a> to enrich the references and, e.g., <b>add missing DOIs</b>. </li> <li> Please <b>do not change</b> the bibliographic style! Author-year citations are not allowed. (So the <code class="not-allowed">natbib</code> package is not supported by the current styles of Dagstuhl Publishing.) </li> <li> Unreferenced bibliography entries will be removed, <code class="not-allowed">\nocite{*}</code> is forbidden. </li> <li> Submitting a <code class="not-allowed">bbl-file only</code> or an <code class="not-allowed">inline-bibliography</code> is not sufficient. </li> </ul> </span> </div> <div data-faq-stack-id="14" style="display: none;"> <span class="_title">How to use the <code>\author</code> macro?</span> <span class="_content"><p>Here is an example of a completely filled author macro:</p> <pre> \author{John Q. Public} {Institute of Pure Nonsense, Dummy University, Atlantis \and \url{http://www.myhomepage.edu}} {johnqpublic@dummyuni.org} {https://orcid.org/0000-0002-1825-0097} {funded by the man in the moon.} </pre> <p>Please note:</p> <ul> <li>Use full first and last name.</li> <li> City and country belong to the <b>minimum requirements</b> on an affiliation. </li> <li> If an author has several different affiliations, please clearly separate them with the keyword <code>\and</code>. </li> <li> E-mail, ORCID, and funding are optional. </li> <li> <b>Author macros cannot be shared!</b> Please use separate author macros even if two or more authors have the same affiliation! </li> </ul></span> </div> <div data-faq-stack-id="17" style="display: none;"> <span class="_title">How to use the <code>\authorrunning</code> macro?</span> <span class="_content"><p>This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:</p> <pre> \authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example} </pre> <p> Please... <ul> <li>abbreviate first names</li> <li>in case of middle initials: use <code>\,</code> as illustrated in the example</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> <li>in case of overfull \hboxes: use the name of the first author and "et al."</li> </ul> </span> </div> <div data-faq-stack-id="16" style="display: none;"> <span class="_title">How to use the <code>\Copyright</code> macro?</span> <span class="_content"><p>Using this macro, you specify the copyright holder (appearing at the bottom of the title page) which is usually the team of authors. Sample usage:</p> <pre> \Copyright{John Q. Public, Adam E. Access, and Eve Example} </pre> <p> Please... <ul> <li>use <b>full</b> first and last names</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> </ul> </span> </div> <div data-faq-stack-id="18" style="display: none;"> <span class="_title">How to use the <code>\ccsdesc</code> macro?</span> <span class="_content"><p><code>\ccsdesc{...}</code> is for classification information following the ACM 2012 Computing Classification System. Sample usage:</p> <pre> \ccsdesc{Theory of computation~Proof complexity} \ccsdesc{Theory of computation~Quantum complexity theory}</pre> <p> Please feel free to use our <a class="btn btn-sm btn-default" href="https://submission.dagstuhl.de/services/acm-subject-classification" target="_blank">ACM 2012 Subject Finder</a> to search for appropriate classifications and to generate the necessary LaTeX code. </p></span> </div> <div data-faq-stack-id="15" style="display: none;"> <span class="_title">How to use the <code>\keywords</code> macro?</span> <span class="_content"><p>Sample usage:</p> <pre> \keywords{Theory of Everything, indefinite Metrics, abstract Nonsense} </pre> <p>Please note:</p> <ul> <li><b>comma</b> as delimiter</li> <li>first word and every proper noun should be capitalized</li> </ul></span> </div> <div data-faq-stack-id="19" style="display: none;"> <span class="_title">How to use the <code>\relatedversiondetails</code> macro?</span> <span class="_content"><p><code>\relatedversiondetails{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:</p> <pre> \relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...} </pre> <p> As all metadata should be self-contained, please add a persistent URL to the cited version (as illustrated above). This also simplifies the access for all readers. </p></span> </div> <div data-faq-stack-id="11" style="display: none;"> <span class="_title">Is there a <b>page limit</b> for LIPIcs/OASIcs papers?</span> <span class="_content"><p>As a <b>publicly funded</b> institution, we have to <b>recover the costs</b> of our publishing activities so that there is no competitive advantage over commercial providers. For the cost recovery we work with an article processing charge (APC), which currently is 60 EUR (net); for more details, see below (<span class="glyphicon glyphicon-star"></span>). This amount was set <b>under the assumption that</b> the average <b>length of a paper does not</b> substantially <b>exceed 15 to 20 main text pages</b>, i.e., number of pages after typesetting <b>excluding title page and the bibliography</b>.</p> <p> Given the above, <b>we suggest 20 main text pages as a page limit</b>, which could for instance be in the form of 15 pages for the main body of paper plus up to 5 pages for appendices. Note that this is <b>only a recommendation</b> and it is up to the editors of the respective volume to decide on a policy regarding the page limit. Moreover, we expect a <b>certain flexibility concerning any page limit</b> (+/- 1 page) to avoid too much extra effort to harmonize style-compliant formatting and page limit for both authors and the Dagstuhl Editorial Office.</p> <hr/> <p>(<span class="glyphicon glyphicon-star"></span>) When specifying a page limit please have in mind the following facts about our APC: <ul> <li>Processing Charge of 60 EUR (net) ... <ul> <li>per published paper (if the average count of main text pages [as defined above] per article is ≤ 20)</li> <li>per block of 20 main text pages (otherwise).</li> </ul> <li>To give a precise formula for calculating the charge for the entire proceedings volume, let P be the total number of main text pages from the n papers in the volume. Then: <br>     <code>Total cost(entire volume) = max(n, floor(P/20)) * 60 EUR (net).</code> </li> </ul> </p></span> </div> </div> <div class="offcanvas offcanvas-bottom" tabindex="-1" id="statistics-offcanvas" aria-labelledby="statistics-offcanvas"> <div class="offcanvas-header"> <h5 class="offcanvas-title"></h5> <button type="button" class="btn-close text-reset" data-bs-dismiss="offcanvas" aria-label="Close"></button> </div> <div class="offcanvas-body small" data-context="Open Access Series in Informatics"> <div style="margin-top: 20vh" class="centered-loader"><div class="loader"></div></div> <iframe class="-hidden"></iframe> </div> </div> </div> </div> <span class="_feedback-button"> <i class="bi bi-question-circle"></i> <span class="text">Questions / Remarks / Feedback</span> </span> <div class="_feedback-form -hidden"> <span class="_feedback-close">X</span> <p>Feedback for Dagstuhl Publishing</p> <div> <textarea class="form-control" name="_feedback"></textarea> <input class="form-control" type="text" name="name" autocomplete="off" placeholder="Name (optional)" maxlength="60" /> <input class="form-control" type="email" name="email" autocomplete="off" placeholder="Email (optional)" maxlength="60" /> <br/> <button class="btn btn-sm btn-default">Send</button> </div> </div> <div class="alert alert-success _feedback-success -hidden"> <span class="glyphicon glyphicon-ok"></span> <h3>Thanks for your feedback!</h3> <div>Feedback submitted</div> <button class="btn btn-white _feedback-done">OK</button> </div> <div class="alert alert-danger _feedback-error -hidden"> <span class="glyphicon glyphicon-remove"></span> <h3>Could not send message</h3> <div>Please try again later or send an <a href="mailto:publishing@dagstuhl.de">E-mail</a></div> <button class="btn btn-white _feedback-done">OK</button> </div> <a class="scroll-up-button -hidden" href="#_top-of-page"> <i class="bi bi-arrow-up-circle"></i> </a> <footer class="page-footer dark"> <div class="container"> <h5>About DROPS</h5> <p>Schloss Dagstuhl - Leibniz Center for Informatics has been operating the Dagstuhl Research Online Publication Server (short: DROPS) since 2004. DROPS enables publication of the latest research findings in a fast, uncomplicated manner, in addition to providing unimpeded, open access to them. All the requisite metadata on each publication is administered in accordance with general guidelines pertaining to online publications (cf. Dublin Core). This enables the online publications to be authorized for citation and made accessible to a wide readership on a permanent basis. Access is free of charge for readers following the open access idea which fosters unimpeded access to scientific publications. </p> </div> <div class="container"> <div class="row"> <div class="col-lg-6"> <h5>Instructions for Authors</h5> <div class="row"> <div class="col-sm-6"> <b>Dagstuhl Series</b><br> <ul> <li><a href="https://submission.dagstuhl.de/series/details/lipics#author">LIPIcs</a></li> <li><a href="https://submission.dagstuhl.de/series/details/oasics#author">OASIcs</a></li> <li><a href="https://submission.dagstuhl.de/series/details/dfu#author">Dagstuhl Follow-Ups</a></li> </ul> </div> <div class="col-sm-6"> <b>Dagstuhl Journals</b><br> <ul> <li><a href="https://submission.dagstuhl.de/series/details/darts#author">DARTS – Dagstuhl Artifacts Series</a></li> <li><a href="https://submission.dagstuhl.de/series/details/dagrep#author">Dagstuhl Reports</a></li> <li><a href="https://submission.dagstuhl.de/series/details/dagman#author">Dagstuhl Manifestos</a></li> <li><a href="https://submission.dagstuhl.de/series/details/lites#author">LITES</a></li> <li><a href="https://submission.dagstuhl.de/series/details/tgdk#author">TGDK – Transactions on Graph Data and Knowledge</a></li> </ul> </div> </div> </div> <div class="col-lg-6"> <h5>Instructions for Editors</h5> <div class="row"> <div class="col-sm-6"> <b>Dagstuhl Series</b><br> <ul> <li><a href="https://submission.dagstuhl.de/series/details/lipics#editor">LIPIcs</a></li> <li><a href="https://submission.dagstuhl.de/series/details/oasics#editor">OASIcs</a></li> <li><a href="https://submission.dagstuhl.de/series/details/dfu#editor">Dagstuhl Follow-Ups</a></li> </ul> </div> <div class="col-sm-6"> <b>Dagstuhl Journals</b><br> <ul> <li><a href="https://submission.dagstuhl.de/series/details/darts#editor">DARTS – Dagstuhl Artifacts Series</a></li> <li><a href="https://submission.dagstuhl.de/series/details/dagrep#editor">Dagstuhl Reports</a></li> <li><a href="https://submission.dagstuhl.de/series/details/dagman#editor">Dagstuhl Manifestos</a></li> <li><a href="https://submission.dagstuhl.de/series/details/lites#editor">LITES</a></li> <li><a href="https://submission.dagstuhl.de/series/details/tgdk#editor">TGDK – Transactions on Graph Data and Knowledge</a></li> </ul> </div> </div> </div> </div> </div> </footer> <div class="copyright"> © 2023-2024 <a href="https://www.dagstuhl.de">Schloss Dagstuhl – LZI GmbH</a> <a href="https://drops.dagstuhl.de/docs/imprint">Imprint</a> <a href="https://drops.dagstuhl.de/docs/privacy">Privacy</a> <a href="https://www.dagstuhl.de/en/publishing/team">Contact</a> </div> <script type="text/javascript" src="https://drops.dagstuhl.de/js/jquery-3.6.0.min.js"></script> <script type="text/javascript" src="https://drops.dagstuhl.de/js/app.js?drops-core-2024-10-22"></script> <script type="text/javascript" src="https://drops.dagstuhl.de/js/popper.min.js"></script> <script type="text/javascript"> $(document).ready(function() { const statistics = { statsServer: 'https://drops-stats.dagstuhl.de', showStatistics: function(e) { e.preventDefault(); const $offCanvas = $('#statistics-offcanvas'); const $iframe = $offCanvas.find('iframe'); const $loader = $offCanvas.find('.centered-loader'); $iframe.addClass('-hidden'); $loader.removeClass('-hidden'); $iframe[0].onload = function () { $iframe.removeClass('-hidden'); $loader.addClass('-hidden'); }.bind(this); const modeParameter = ''; const $target = $(e.currentTarget); const entityId = $target.attr('data-entity'); const title = $target.attr('data-title'); const embedUrl = statistics.statsServer + '/embed/external/drops2/' + entityId + modeParameter; let context = $offCanvas.find('.offcanvas-body').attr('data-context'); if (context === title) { context = ''; } if (context !== '') { context += '<br>'; } $offCanvas.find('.offcanvas-title').html(context + '<h2 style="font-weight: bold">' + title + '</h2>'); $offCanvas.offcanvas('show'); $offCanvas.find('iframe').attr('src', embedUrl); return false; }, initialize: function() { $('.btn-statistics').on('click', this.showStatistics); } }; statistics.initialize(); }); </script> <script type="text/javascript" src="https://drops.dagstuhl.de/js/circle-progress.js"></script> <script type="text/javascript"> $(document).ready(function() { const view = { statsServer: 'https://drops-stats.dagstuhl.de', animationStarted: false, isScrolledIntoView: function (elem) { const rect = elem.getBoundingClientRect(); const elemTop = rect.top; //const elemBottom = rect.bottom; // const elemHeight = rect.height; return (elemTop >= 0) && (elemTop <= window.innerHeight); }, progressCircle: function ($el) { $el.find('.circle').circleProgress({ value: 1, size: 80, fill: { color: '#555' }, animation: { duration: 1200 } }); }, countUp: function($el) { $el.find('.number').each(function() { const $this = $(this); const number = parseInt($this.attr('data-number')); let suffix = ''; if (number > 90000) { $this.text(Math.ceil(number/1000)+' k'); suffix = ' k'; } else if (number > 90000000) { $this.text(Math.ceil(number/1000000)+' m'); suffix = ' m'; } else { $this.text(Math.ceil(number)) } $({ Counter: 0 }).animate({ Counter: $this.text().replace(suffix, '').replace(',', '') }, { duration: 1000, easing: 'swing', step: function() { $this.text(Math.ceil(this.Counter).toString().replace(/\B(?=(\d{3})+(?!\d))/g, ",") + suffix); } }); }); }, checkVisibility: function() { const $container = $('.stats-total'); if (view.isScrolledIntoView($container[0])) { if (!view.animationStarted) { view.animationStarted = true; view.progressCircle($container); setTimeout(function() { view.countUp($container) }, 200); } } }, initialize: function() { $.ajax({ type: 'get', url: view.statsServer + '/api/external/drops2/series/OASIcs/-/stats', success: function (result) { $('.total-downloads .number').attr('data-number', result.total.downloads); $('.total-metadata-views .number').attr('data-number', result.total.clicks); window.addEventListener('scroll', view.checkVisibility); view.checkVisibility(); }, error: function () { $('.total-downloads .number').text(0); $('.total-metadata-views .number').text(0); window.addEventListener('scroll', view.checkVisibility); view.checkVisibility(); } }); } }; view.initialize(); }); </script>  <script src="/livewire/livewire.js?id=38dc8241" data-csrf="Cp9a84yx12LI4fI5JaJchKFoBqzhtaJxOcgjIf5Z" data-update-uri="/livewire/update" data-navigate-once="true"></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(); }); } }; _faq.initialize(); window._faq = _faq; }); </script> <script type="text/javascript"> function _enableFeedback() { var $feedbackButton = $('._feedback-button, .fixed-beta-button'); var $feedbackClose = $('._feedback-close'); var $feedbackForm = $('._feedback-form'); var $feedbackSubmit = $('._feedback-form button'); var $textarea = $feedbackForm.find('textarea'); var $feedbackSuccess = $('._feedback-success'); var $feedbackError = $('._feedback-error'); var $feedbackDoneButton = $('._feedback-done'); $feedbackButton.addClass('_show'); $feedbackButton.on('click', function () { $feedbackButton.addClass('-hidden'); $feedbackForm.removeClass('-hidden'); $textarea.focus(); }); $feedbackClose.on('click', function () { $feedbackSuccess.addClass('-hidden'); $feedbackForm.addClass('-hidden'); $feedbackButton.removeClass('-hidden'); }); $feedbackDoneButton.on('click', function () { $feedbackError.addClass('-hidden'); $feedbackSuccess.addClass('-hidden'); $feedbackForm.addClass('-hidden'); $feedbackButton.removeClass('-hidden'); }); $feedbackSubmit.on('click', function () { var message = $textarea.val(); if (message === undefined) { message = ''; } if (message.trim() !== '') { $.ajax({ url: '/api/v1/feedback', type: 'post', data: { content: message, context: window.location.href, name: $('input[name="name"]').val(), email: $('input[name="email"]').val(), }, success: function (result) { if (result === 'success') { $textarea.val(''); $feedbackSuccess.removeClass('-hidden'); } else { $feedbackError.removeClass('-hidden'); } }, error: function () { $feedbackError.removeClass('-hidden'); } }); } }); } var _defer_counter = 0; function _defer(method) { if (window.jQuery) { method(); } else { if (_defer_counter < 20) { setTimeout(function () { _defer(method); console.log(_defer_counter); _defer_counter++; }, 500); } } } setTimeout(function() { _defer(_enableFeedback); }, 1000); </script> <script type="text/javascript"> $(document).ready(function() { const app = { maxScrollPos: window.innerWidth < 500 ? 100 // mobile : 400, // desktop $el : { navbarSearch: $('nav .navbar-search'), fixedSearchButton: $('.fixed-search-button'), copyToClipboard: $('.copy-to-clipboard') }, methods: { hideMenuOnScroll: function(scrollPos) { const $menu = $('nav.navbar.main'); const $stickySearch = $('.search.sticky'); const $banner = $('#_banner'); const $fixedSearchButton = $('.fixed-search-button'); if (scrollPos > app.maxScrollPos) { $menu.addClass('-hide'); $banner.addClass('-hide'); $stickySearch.addClass('-top'); $fixedSearchButton.addClass('-show'); } else { app.methods.showMenu(null, false); } }, showMenu: function(e, focus) { const $menu = $('nav.navbar.main'); const $stickySearch = $('.search.sticky'); const $banner = $('#_banner'); const $fixedSearchButton = $('.fixed-search-button'); $menu.removeClass('-hide'); $banner.removeClass('-hide'); $stickySearch.removeClass('-top'); $fixedSearchButton.removeClass('-show'); if (focus !== false) { $('.navbar-search').find('input[name="term"]').focus(); } }, showUpLinkOnScroll: function(scrollPos) { const $upLink = $('.scroll-up-button'); if (scrollPos > app.maxScrollPos) { $upLink.removeClass('-hidden'); } else { $upLink.addClass('-hidden'); } }, scrollHandler: function() { const scrollPos = $(document).scrollTop(); app.methods.hideMenuOnScroll(scrollPos); app.methods.showUpLinkOnScroll(scrollPos); }, copyToClipboard: function(e) { e.preventDefault(); const $current = $(e.currentTarget); // console.log($current.attr('data-selector')); const element = $('#'+$current.attr('data-selector'))[0]; console.log(element); element.select(); document.execCommand("copy"); const $success = $current.find('.bi-check'); $success.removeClass('-hidden'); setTimeout(function() { $success.addClass('-hidden'); }, 1000); }, initTooltips: function() { const tooltipTriggerList = [].slice.call(document.querySelectorAll('[data-bs-toggle="tooltip"]')) const tooltipList = tooltipTriggerList.map(function (tooltipTriggerEl) { return new bootstrap.Tooltip(tooltipTriggerEl) }); }, expandSearch: function() { app.$el.navbarSearch.addClass('expanded'); }, collapseSearch: function(e) { if (!$(e.currentTarget).is('button.btn-outline-success')) { app.$el.navbarSearch.removeClass('expanded'); } }, initDeepLinksTabs: function() { const innerAnchors = [ 'resource-articles', 'cfp-si-resources', 'cfp-si-autonomous-systems-and-knowledge-graphs' ]; let anchors = []; $('a[role="tab"]').each(function() { anchors.push($(this).attr('aria-controls')); }); innerAnchors.forEach(function(anchor) { if ($('#'+anchor).length > 0) { anchors.push(anchor); } }); if (anchors.length === 0) { return; } let selectedAnchor = window.location.hash.substring(1); if (anchors.indexOf(selectedAnchor) === -1) { $('#publications-tab').tab('show'); window.scrollTo(0,0); return; } if (selectedAnchor !== 'publications') { 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'); console.log($tab); try { $('#'+$tab.attr('id')+'-tab').tab('show'); } catch (e) { } setTimeout(function () { $('#' + selectedAnchor)[0].scrollIntoView(); }, 800); } else { try { $('#' + selectedAnchor + '-tab').tab('show'); } catch (e) { } window.scrollTo(0, 0); } } $('[data-tab-link]').on('click', function(e) { const $target = $(e.currentTarget); let href = $target.attr('href'); let scrollLink = null; if (href === '#cfp-si-list') { scrollLink = href; href = '#cfp'; } try { console.log(href); $(href+'-tab').tab('show'); } catch(e) { } console.log(scrollLink); if (scrollLink !== null) { setTimeout(function() { $(scrollLink)[0].scrollIntoView(); }, 200); } else { setTimeout(function() { window.scrollTo(0,0); }, 200); } }); } }, initialize: function() { $(window).on('scroll', app.methods.scrollHandler); $(window).on('scroll-to-top', function() { window.scrollTo(0,0) }); $(document).trigger('scroll'); // set correct status for scroll-related parts (navbar/back-to-top) on page reload app.$el.copyToClipboard.on('click', app.methods.copyToClipboard); app.$el.fixedSearchButton.on('click', app.methods.showMenu); app.$el.navbarSearch.find('input').on('click', app.methods.expandSearch) app.$el.navbarSearch.find('input').on('blur', app.methods.collapseSearch); app.methods.initTooltips(); app.methods.initDeepLinksTabs(); } }; app.initialize(); }); </script> </body> </html>

CINXE.COM

OASIcs