CINXE.COM

<!DOCTYPE html><html lang="de"><head><meta charset="UTF-8" /><title>Leibniz Transactions on Embedded Systems (LITES)</title><meta name="description" content="" /><meta name="keywords" content="" /><meta name="robots" content="index,follow" /><link rel="canonical" href="https://drops.dagstuhl.de/entities/journal/LITES" /><script type="application/ld+json">{"@context":"http:\/\/schema.org\/","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.dagstuhl.de\/de"},{"@type":"ListItem","position":2,"name":"Publishing","item":"https:\/\/www.dagstuhl.de\/de\/publishing"},{"@type":"ListItem","position":3,"name":"Die Serien im \u00dcberblick","item":"https:\/\/www.dagstuhl.de\/de\/publishing\/series"},{"@type":"ListItem","position":4,"name":"Details zur Serie","item":"https:\/\/www.dagstuhl.de\/de\/publishing\/series\/details"}]}</script><meta http-equiv="x-ua-compatible" content="ie=edge" /><meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="copyright" content="Schloss Dagstuhl - Leibniz-Zentrum für Informatik GmbH, 66687 Wadern" /><meta name="author" content="Schloss Dagstuhl - Leibniz-Zentrum für Informatik GmbH, 66687 Wadern" /><meta name="revisit-after" content="10" /><meta name="DC.Description" content="Schloss Dagstuhl - Leibniz-Zentrum für Informatik GmbH (LZI), Wadern" /><meta name="DC.Subject" content="LZI,Schloss,Dagstuhl,Wadern,Informatik,Forschung" /><meta name="DC.Rights" content="Schloss Dagstuhl - Leibniz-Zentrum für Informatik GmbH, 66687 Wadern" /><meta name="DC.Creator" content="Schloss Dagstuhl - Leibniz-Zentrum für Informatik GmbH, 66687 Wadern" /><link rel="schema.dc" href="http://purl.org/metadata/dublin_core_elements" /><link rel="icon" href="/_Resources/Static/Packages/Dagstuhl.Site/Frontend/favicon.ico?v2" type="image/x-icon" /><link rel="stylesheet" href="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/bootstrap/bootstrap.min.css?bust=8ed2d635" media="all" /><link rel="stylesheet" href="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/slick/slick-1.8.1.min.css?bust=17de6d74" media="all" /><script src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/jquery/jquery-3.5.1.slim.min.js?bust=cf8d9821"></script><script defer src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/bootstrap/bootstrap.bundle.min.js?bust=0363cb58"></script><script defer src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/js/mark.min.js?bust=33fff94c"></script><script defer src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/js/cookie.min.js?bust=66615816"></script><script defer src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/slick/slick-1.8.1.min.js?bust=3b41b3bc"></script><link rel="stylesheet" href="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/index.css?bust=60367462?h=60367462" /></head><body class><nav class="navbar main navbar-expand-lg navbar-light bg-light d-print-none" role="navigation"><a class="navbar-brand" href="/"><img class="lzi-logo" width="83" height="61" src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/images/LZI-Logo.jpg?bust=b988b355" alt="Schloss Dagstuhl - LZI - Logo" /></a><button class="navbar-toggler" type="button" data-toggle="collapse" data-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 mr-auto"><li class="nav-item dropdown normal"><a href="#" class="nav-link dropdown-toggle" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">Das Institut</a><div class="dropdown-menu" aria-labelledby="navbarDropdown"><a href="/de" class="dropdown-item link-node"><b>Übersicht</b></a><div class="dropdown-divider"></div><a href="/de/institute/news" class="dropdown-item link-node">Aktuelles</a><a href="/de/institute/organization" class="dropdown-item link-node">Konzept und Organisation</a><a href="/de/institute/team" class="dropdown-item link-node">Team</a><a href="/de/institute/committees" class="dropdown-item link-node">Gremien</a><a href="/de/institute/funding-and-financing" class="dropdown-item link-node">Förderung und Finanzierung</a><a href="/de/institute/projects" class="dropdown-item link-node">Projekte</a><a href="/de/institute/press" class="dropdown-item link-node">Presse</a><a href="/de/institute/dagstuhls-impact" class="dropdown-item link-node">Dagstuhl's Impact</a><a href="/de/institute/jobs" class="dropdown-item link-node">Stellenangebote</a><a href="/de/institute/gender-equality" class="dropdown-item link-node">Gleichstellungsplan</a><a href="/de/institute/ethics" class="dropdown-item link-node">Gute wissenschaftliche Praxis</a><a href="/de/institute/code-of-conduct" class="dropdown-item link-node">Code of Conduct</a></div></li><li class="nav-item dropdown normal"><a href="#" class="nav-link dropdown-toggle" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">Seminare</a><div class="dropdown-menu" aria-labelledby="navbarDropdown"><a href="/de/seminars" class="dropdown-item link-node"><b>Übersicht</b></a><div class="dropdown-divider"></div><a href="/de/seminars/seminar-calendar" class="dropdown-item link-node">Seminar-Kalender</a><a href="/de/seminars/news" class="dropdown-item link-node">News Seminarwesen</a><a href="/de/seminars/team" class="dropdown-item link-node">Mitarbeiter Seminarwesen</a><a href="/de/seminars/dagstuhl-seminars" class="dropdown-item link-node">Dagstuhl-Seminare</a><a href="/de/seminars/dagstuhl-perspectives" class="dropdown-item link-node">Dagstuhl-Perspektiven</a><a href="/de/seminars/gi-dagstuhl-seminars" class="dropdown-item link-node">GI-Dagstuhl-Seminare</a><a href="/de/seminars/summer-schools" class="dropdown-item link-node">Sommerschulen</a><a href="/de/seminars/research-meetings" class="dropdown-item link-node">Forschungstreffen</a><a href="/de/seminars/research-guests" class="dropdown-item link-node">Forschungsgäste</a><a href="/de/seminars/ethics" class="dropdown-item link-node">Gute wissenschaftliche Praxis</a></div></li><li class="nav-item dropdown active"><a href="#" class="nav-link dropdown-toggle" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">Publishing</a><div class="dropdown-menu" aria-labelledby="navbarDropdown"><a href="/de/publishing" class="dropdown-item link-node"><b>Übersicht</b></a><div class="dropdown-divider"></div><a rel="noopener" target="_self" href="https://drops.dagstuhl.de/" class="dropdown-item link-external">Zu den Publikationen</a><a href="/de/publishing/news" class="dropdown-item link-node">Publishing News</a><a href="/de/publishing/team" class="dropdown-item link-node">Mitarbeiter Publishing</a><a href="/de/publishing/series" class="dropdown-item link-node">Die Serien im Überblick</a><a href="/de/publishing/series/details/LIPIcs" class="dropdown-item link-app">LIPIcs</a><a href="/de/publishing/series/details/OASIcs" class="dropdown-item link-app">OASIcs</a><a href="/de/publishing/series/details/LITES" class="dropdown-item link-app">LITES</a><a href="/de/publishing/series/details/TGDK" class="dropdown-item link-app">TGDK</a><a href="/de/publishing/series/details/DagRep" class="dropdown-item link-app">Dagstuhl Reports</a><a href="/de/publishing/open-access-policy" class="dropdown-item link-node">Open Access Policy</a><a href="/de/publishing/ethics" class="dropdown-item link-node">Publication Ethics</a><a href="/de/publishing/advisory-board" class="dropdown-item link-node">Publishing Beirat</a></div></li><li class="nav-item dropdown normal"><a href="#" class="nav-link dropdown-toggle" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">dblp</a><div class="dropdown-menu" aria-labelledby="navbarDropdown"><a href="/de/dblp" class="dropdown-item link-node"><b>Übersicht</b></a><div class="dropdown-divider"></div><a rel="noopener" target="_self" href="https://dblp.org/" class="dropdown-item link-external">Zur Datenbank</a><a href="/de/dblp/news" class="dropdown-item link-node">dblp-News</a><a href="/de/dblp/team" class="dropdown-item link-node">dblp-Team</a><a href="/de/dblp/advisory-board" class="dropdown-item link-node">dblp-Beirat</a><a href="/de/dblp/ethics" class="dropdown-item link-node">dblp-Ethik</a></div></li><li class="nav-item dropdown normal"><a href="#" class="nav-link dropdown-toggle" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">Gastinformation</a><div class="dropdown-menu" aria-labelledby="navbarDropdown"><a href="/de/guests" class="dropdown-item link-node"><b>Übersicht</b></a><div class="dropdown-divider"></div><a href="/de/guests/planning-your-visit" class="dropdown-item link-node">Infos zum Aufenthalt</a><a href="/de/guests/how-to-get-to-schloss-dagstuhl" class="dropdown-item link-node">Anreise</a><a href="/de/guests/sars-cov2-prevention-measures" class="dropdown-item link-node">Covid-19 Vorbeugung</a><a href="/de/guests/expenses" class="dropdown-item link-node">Kosten</a><a href="/de/guests/childcare" class="dropdown-item link-node">Kinderbetreuung</a><a href="/de/guests/library" class="dropdown-item link-node">Bibliothek</a><a href="/de/guests/art" class="dropdown-item link-node">Kunst</a><a href="/de/guests/history" class="dropdown-item link-node">Geschichte</a></div></li><li class="nav-item normal"><a href="/de/contact" class="nav-link link-node">Kontakt</a></li></ul><div class="navbar-search form-inline my-2 my-lg-0"><div class="input-group"><input class="nav-search form-control sm-2" type="search" name="search" placeholder="Search" aria-label="Search" maxlength="1024" /><div class="input-group-append"><button class="btn btn-outline-success" type="submit" aria-label="Search"><i class="bi bi-search" style="color: #000"></i></button></div></div></div><div class="language-menu"><div class="btn-group btn-group-toggle" data-toggle="buttons"><label class="btn-language btn btn-sm btn-secondary "><a href="/publishing/series/en/publishing/series/details/lites">EN</a><input type="radio" name="lang" /></label><label class="btn-language btn btn-sm btn-secondary active"><a href="/publishing/series/de/publishing/series/details/lites">DE</a><input type="radio" name="lang" checked="checked" /></label></div></div></div></nav><span class="__no-index-start"></span><nav aria-label="breadcrumb" class="breadcrumb-nav d-print-none"><ol class="breadcrumb"><li class="normal breadcrumb-item"><a href="/de"><i class="bi bi-house-fill"></i></a></li><li class="active breadcrumb-item"><a href="/de/publishing">Publishing</a></li><li class="active breadcrumb-item"><a href="/de/publishing/series">Die Serien im Überblick</a></li><li class="current breadcrumb-item"><a href="/de/publishing/series/details">Details zur Serie</a></li></ol><div class="breadcrumb-margin"></div></nav><div id="_top-of-page">TOP</div><div class="search-overlay d-print-none"><button type="button" class="close" aria-label="Close"><span aria-hidden="true">×</span></button><form class="search-expanded form-inline mt-3" method="post" action="/de/search-results"><h5 style="text-align: center;width: 100%; margin-top: 2em;">Suche auf der Schloss Dagstuhl Webseite</h5><div class="input-group"><input style="position: fixed; top: -100px; left: 0;" name="start-date" value="2022-12-14" maxlength="10" aria-label="Do not touch" /><input style="position: fixed; top: -100px; left: 0;" name="end-date" value maxlength="10" aria-label="Do not touch" /><input class="expanded-search form-control sm-2" type="search" name="search" placeholder="Bitte Suchbegriff eingeben" autocomplete="off" aria-label="Search" maxlength="1024" /><div class="input-group-append"><button class="btn btn-outline-success" type="submit" aria-label="Submit Search Form"><i class="bi bi-search" style="color: #000"></i></button></div></div><div class="mt-2 add-seminars">Sie suchen nach Informationen auf den Webseiten der einzelnen Seminare? - Dann: <div class="form-check" style><input class="form-check-input" type="checkbox" name="include-seminars" id="include-seminars" /><label class="form-check-label" for="include-seminars">Schließen Sie unser Seminarprogramm in die Suche mit ein</label></div></div></form><div style="text-align: center; color: #fff; margin-top: 3em"><b>Nicht fündig geworden? - Einige unserer Dienste laufen auf separaten Webseiten mit jeweils eigener Suche. Bitte beachten Sie folgende Liste:</b></div><div class="row" style="margin-top: 3em"><div class="card col-sm-10 offset-1 dagstuhl-services-header"><div class="card-body"><img style="position: absolute; top: 0; left: 0; height: 100%;" src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/images/LZI-Logo.jpg?bust=b988b355" alt="Schloss Dagstuhl - LZI - Logo" /><h5><span>Schloss</span> Dagstuhl Services</h5></div></div></div><div class="row dagstuhl-services"><div class="card offset-1"><div class="card-body"><h5 class="card-title">Seminare</h5><h6 class="card-subtitle mb-2 mt-2 text-muted">Innerhalb dieser Seite:</h6><ul><li>siehe <a href="/de/seminars">Seminare und Veranstaltungen</a></li><li>und <a href="/de/guests">Informationen für Gäste und Besucher</a></li></ul><h6 class="card-subtitle mb-2 mt-3 text-muted">Externe Seiten:</h6><ul><li><a href="https://door.dagstuhl.de/">DOOR</a> (zum Registrieren eines Dagstuhl Aufenthaltes)</li><li><a href="https://www.dagstuhl.de/dosa">DOSA</a> (zum Beantragen künftiger Dagstuhl Seminare oder Dagstuhl Perspektiven Workshops)</li></ul></div></div><div class="card"><div class="card-body"><h5 class="card-title">Publishing</h5><h6 class="card-subtitle mb-2 mt-2 text-muted">Innerhalb dieser Seite:</h6><ul><li>siehe <a href="/de/publishing">Über Publishing</a> und Unterseiten</li></ul><h6 class="card-subtitle mb-2 mt-3 text-muted">Externe Seiten:</h6><ul class="card-text"><li><a href="https://drops.dagstuhl.de">DROPS</a> (der Publikationsserver von Dagstuhl)</li><li>die Webseite der Zeitschrift <a class="link" href="https://ojs.dagstuhl.de">LITES</a></li><li>der <a href="https://submission.dagstuhl.de">Dagstuhl Submission Server</a> (zum Einreichen von LIPIcs/OASIcs/DARTS Beiträgen)</li></ul></div></div><div class="card"><div class="card-body"><h5 class="card-title">dblp</h5><h6 class="card-subtitle mb-2 mt-2 text-muted">Innerhalb dieser Seite:</h6><ul><li>siehe <a href="/de/dblp">Über dblp</a> und Unterseiten</li></ul><h6 class="card-subtitle mb-2 mt-3 text-muted">Externe Seiten:</h6><ul class="card-text"><li>die Informatik-Bibliographiedatenbank <a href="https://dblp.org">dblp</a></li></ul></div></div></div><br /><br /><button type="button" class="close" aria-label="Close"><span aria-hidden="true">×</span></button></div><span class="__no-index-end"></span><span class="__no-index-start"></span><div class="quick-links-overlay -hidden"></div><div class="quick-links aside d-print-none -hidden"><div class="list-container"><div class="role-details empty" style="text-align: center; margin-top: 2em">Bitte wählen Sie ihre Rolle aus, <br /> um passende Quick-Links zu erhalten.</div><div style="padding: 20px;"><select class="form-select role-select" aria-label="Select Your Role"><option selected value="empty">Ich bin...</option><option value="orga-seminar">Organisator eines Dagstuhl Seminars</option><option value="participant-seminar">Teilnehmer eines Seminars/Events</option><option value="proposer-seminar">Antragsteller eines Seminars/Events</option><option value="editor-lipics-oasics">Editor eines LIPIcs/OASIcs Bandes</option><option value="author-lipics-oasics">Autor eines LIPIcs/OASIcs Artikels</option><option value="looking-for-article">auf der Suche nach Artikeln/Reports</option><option value="dblp-user">ein dblp Nutzer</option><option value="journalist">ein Journalist</option><option value="interested-citizen">ein:e interessierte:r Bürger:in</option></select></div><div class="role-details orga-seminar -hidden"><ul class="list"><li><a href="/de/seminars/dagstuhl-seminars/infos-for-organizers">Infos for Organisatoren</a></li><li><a href="/de/guests/planning-your-visit">Planung des Aufenthaltes</a></li><li><a href="/de/guests/how-to-get-to-schloss-dagstuhl">Anreiseinformationen</a></li><li><a href="/de/guests/sars-cov2-prevention-measures">SARS-CoV2 Vorbeugungsmaßnahmen</a></li></ul></div><div class="role-details participant-seminar -hidden"><ul class="list"><li><a href="https://door.dagstuhl.de">DOOR (zum Registrieren des Aufenthaltes)</a></li><li><a href="/de/guests/planning-your-visit">Planung des Aufenthaltes</a></li><li><a href="/de/guests/how-to-get-to-schloss-dagstuhl">Anreiseinformationen</a></li><li><a href="/de/guests/sars-cov2-prevention-measures">SARS-CoV2 Vorbeugungsmaßnahmen</a></li><li><a href="/de/guests/library">Bibliothek</a></li><li><a href="/de/guests/expenses">Kosten</a></li></ul></div><div class="role-details proposer-seminar -hidden"><ul class="list"><li><a href="/de/seminars">Überblick Seminar-/Event-Typen</a></li><li><a href="/de/seminars/dagstuhl-seminars/composition-of-a-proposal">Aufbau eines Dagstuhl Seminar Proposals</a></li><li><a href="/de/seminars/dagstuhl-seminars/infos-for-organizers">Infos for Organisatoren</a></li><li><a href="https://dosa.dagstuhl.de">DOSA (Einreichung eines Proposals)</a></li></ul></div><div class="role-details editor-lipics-oasics -hidden"><ul class="list"><li><a href="https://submission.dagstuhl.de/series/details/LIPIcs#editor">Veröffentlichungsprozess (LIPIcs)</a></li><li><a href="https://submission.dagstuhl.de/series/details/LIPIcs#editor">Veröffentlichungsprozess (OASIcs)</a></li><li><a href="https://submission.dagstuhl.de">Dagstuhl Submission Server</a></li><li><a href="https://drops.dagstuhl.de/opus/institut_lipics.php">LIPIcs Webportal</a></li><li><a href="https://drops.dagstuhl.de/opus/institut_oasics.php">OASIcs Webportal</a></li></ul></div><div class="role-details author-lipics-oasics -hidden"><div class="m-2">Als LIPIcs/OASIcs Autor werden Sie per e-mail eingeladen, sich am Dagstuhl Submission Server zu registrierem. Der Server führt Sie dann durch den Veröffentlichungsprozess. Vorabinformationen finden Sie hier:</div><ul class="list"><li><a href="https://submission.dagstuhl.de/series/details/LIPIcs#author">Anleitung für LIPIcs Autoren</a></li><li><a href="https://submission.dagstuhl.de/series/details/OASIcs#author">Anleitung for OASIcs Autoren</a></li><li><a href="https://submission.dagstuhl.de">Dagstuhl Submission Server</a></li></ul></div><div class="role-details looking-for-article -hidden"><div>Suchen Sie...</div><ul class="list"><li><a href="https://dblp.org">Bibliographische Metadaten?<br /> dblp-Suche</a></li><li><a href="https://drops.dagstuhl.de">Über Dagstuhl veröffentlichte Dokumente?<br /> DROPS, der Publikationsserver von Dagstuhl</a></li></ul></div><div class="role-details dblp-user -hidden"><ul class="list"><li><a href="https://dblp.org">dblp-Suche</a></li><li><a href="https://dblp.org/faq/index.html">dblp-FAQ</a></li></ul></div><div class="role-details journalist -hidden"><ul class="list"><li><a href="/de/institute/press/press-releases">Pressemitteilungen</a></li><li><a href="/de">Über das Institut (Überblick)</a></li><li><a href="/de/institute/organization">Konzept und Organisation</a></li><li><a href="/de/guests">Das Seminarzentrum im Überblick</a></li><li><a href="/de/guests/history">Geschichte des Gebäudes</a></li></ul></div><div class="role-details interested-citizen -hidden"><ul class="list"><li><a href="/de">About the Institute (Overview)</a></li><li><a href="/de/institute/organization">Konzept und Organisation</a></li><li><a href="/de/guests">Das Seminarzentrum im Überblick</a></li><li><a href="/de/seminars/seminar-calendar">Das aktuelle Seminarprogramm</a></li><li><a href="/de/guests/history">Geschichte des Gebäudes</a></li><li><a href="/de/guests/library">Bibliothek</a></li></ul></div></div><a href="#" class="quick-links-handle">Quick Links<span class="down"><br /><i class="bi bi-chevron-compact-down"></i></span><span class="up"><br /><i class="bi bi-chevron-compact-up"></i></span></a></div><span class="__no-index-end"></span><main class="main"><div class="static-content"><div class="neos-contentcollection"></div></div><div> <header class="style: text-center"> <img src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/images/publishing/07lites.png?bust=0d73bfc4" alt="LITES image" class="card-img-top" style="max-width: 10rem; margin-bottom: 1.5rem" /> <h1>Leibniz Transactions on Embedded Systems</h1> </header> <div class="container mb-5"> <ul class="nav nav-tabs" id="documentation" role="tablist"> <li class="nav-item" role="presentation"> <a class="nav-link active" id="general-tab" data-toggle="tab" href="#general" role="tab" aria-controls="general" aria-selected="true"> General </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="editorialboard-tab" data-toggle="tab" href="#editorialboard" role="tab" aria-controls="editorialboard" aria-selected="false"> Editorial Board </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="selection-tab" data-toggle="tab" href="#selection" role="tab" aria-controls="selection" aria-selected="false"> Selection/Review </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="cfp-tab" data-toggle="tab" href="#cfp" role="tab" aria-controls="cfp" aria-selected="true"> Call for Papers </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="si-tab" data-toggle="tab" href="#si" role="tab" aria-controls="si" aria-selected="true"> Special Issues </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="author-tab" data-toggle="tab" href="#author" role="tab" aria-controls="author" aria-selected="false"> Author Instructions </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="editor-tab" data-toggle="tab" href="#editor" role="tab" aria-controls="editor" aria-selected="false"> Editor Instructions </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="recently-tab" data-toggle="tab" href="#recently" role="tab" aria-controls="recently" aria-selected="false"> Recently published </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="contact-tab" data-toggle="tab" href="#contact" role="tab" aria-controls="contact" aria-selected="false"> Contact </a> </li> </ul> <div class="tab-content" id="tab-contents"> <br /> <div class="tab-pane fade show active" id="general" role="tabpanel" aria-labelledby="general-tab"> <div class="row"> <div class="col-sm-2"> </div> <div class="col-sm-10"> <p>LITES publishes original articles on all aspects of embedded computing systems according to the principles of <a href="https://openaccess.mpg.de/Berlin-Declaration">Open Access</a>. The journal is published by the <a href="http://www.edaa.com/">European Design and Automation Association (EDAA)</a> \ <a href="http://www.emsig.net/">EMbedded Systems Special Interest Group (EMSIG)</a> and <a href="http://www.dagstuhl.de/dagpub">Schloss Dagstuhl -- Leibniz-Zentrum für Informatik GmbH, Dagstuhl Publishing</a></p> <p>LITES aims at efficient reviewing procedures to ensure that articles are published within one year of submission. LITES is continuously open for submission.</p> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Publications</h5> </div> <div class="col-sm-10"> LITES is an open-access journal — all papers published in LITES are freely available in the <a href="https://drops.dagstuhl.de">DROPS</a> publication repository. <a href="https://drops.dagstuhl.de/entities/journal/LITES" style="margin-left: 10px;"> <span class="btn" style="border: 1px solid #555; white-space: nowrap;"" style="text-align: center"> <span style="line-height: 2em">Browse LITES on DROPS</span><br> <img src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/images/publishing/07lites.png" height="24px" alt="LITES Logo" style="max-height: 3rem;" />   </span> </a> <br><br> Moreover, all papers are indexed in dblp: <a href="https://dblp.org/db/journals/lites">LITES @ dblp</a> </div> </div> <hr> <div class="row"> <div class="col-sm-2"> <h5>Aims and Scope</h5> </div> <div class="col-sm-10"> <p><em>Leibniz Transactions on Embedded Systems (LITES)</em> aims to publish high-quality scholarly articles and to ensure efficient submission, reviewing, and publishing procedures that will result in timely publication. All articles are published open access, i.e., are accessible online at no cost to the reader. All rights are retained by the author(s).</p> <p>LITES publishes original articles on all aspects of embedded computing systems.</p> <p>The journal is flexible in the types of articles it publishes. The range includes (but is not limited to) regular technical papers, literature surveys, historical perspectives, position papers, tools papers, and companion papers to open-access research artifacts (such as open-source software and hardware designs, data sets, case studies, challenge problems and competitions, etc.). All contributions that advance the state of the art and/or the scientific discourse on embedded computing systems are welcome.</p> <p>Topics of interest include (but are not limited to):</p> <ul> <li>the design, implementation, testing, validation, and verification of embedded software and hardware systems,</li> <li>their temporal and logical correctness,</li> <li>resource efficiency,</li> <li>embedded security,</li> <li>design space exploration and optimization,</li> <li>embedded artificial intelligence (AI),</li> <li>formal foundations of embedded systems,</li> <li>embedded systems in the context of larger cyber-physical systems (CPS) and networked systems, and - specific application domains (e.g., automotive systems, avionics, robotics, healthcare, autonomous systems, etc.).</li> </ul> <p>LITES welcomes all methods of scientific inquiry, including (but not limited to) systems building and empirical evaluation, mathematical modeling and rigorous proof, formal methods, deployment studies and reflections on “lessons learned” in practice, as well as statistical and empirical methods, surveys of industry practice, and user studies.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Open Access Policy</h5> </div> <div class="col-sm-10"> LITES articles are peer-reviewed and published according to the principle of Open Access, 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"> <p>Schloss Dagstuhl, the publisher of LITES, charges a moderate article-processing charge (APC) of 100€ (net) upon acceptance, which typically is paid by the author or his/her institution. Authors without institutional support or facing financial hardship may apply for an APC waiver.</p> <p>Schloss Dagstuhl is a publicly funded nonprofit organization. The modest APC serves to offset only the real costs incurred during the publication process and does not generate any profits.</p> <p>Additionally, the first 20 accepted papers each year automatically receive a FULL APC WAIVER thanks to financial support by EMSIG.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>ISSN</h5> </div> <div class="col-sm-10"> <span>2199-2002</span> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Identifier</h5> </div> <div class="col-sm-10"> Each issue is assigned a DOI and a URN.<br /> Each article is assigned a DOI and a URN.<br /> To facilitate author identification, the Open Researcher and Contributor ID (ORCID) is optionally included during upload so that authors can be uniquely linked to their ORCID iD. </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Longterm Preservation</h5> </div> <div class="col-sm-10"> LITES is digitally archived 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> Yasmina Abdeddaïm <a href="https://perso.esiee.fr/~abdedday/">Université Gustave Eiffel, ESIEE Paris, FR</a> </li> <li> Matthias Becker <a href="https://www.kth.se/profile/mabecker/">KTH Royal Institute of Technology, SW</a> </li> <li> Alessandro Biondi <a href="https://retis.sssup.it/~a.biondi/">Scuola Superiore Sant'Anna - Pisa, IT</a> </li> <li> Björn B. Brandenburg <a href="https://people.mpi-sws.org/~bbb/">MPI-SWS - Kaiserslautern, DE</a> - <span>Editor-in-Chief</span> </li> <li> Christian Dietrich <a href="https://osg.tuhh.de/People/dietrich/">Hamburg University of Technology (TUHH), DE</a> </li> <li> Martin Fränzle <a href="http://www.uni-oldenburg.de/informatik/hs/mitarbeiterinnen-und-mitarbeiter/prof-dr-martin-fraenzle/">Universität Oldenburg, DE</a> </li> <li> Giovani Gracioli <a href="http://www.lisha.ufsc.br/Giovani">Federal University of Santa Catarina, BR</a> </li> <li> Zhishan Guo <a href="https://zguo32.wordpress.ncsu.edu">North Carolina State University, US</a> </li> <li> Jing Li <a href="https://web.njit.edu/~jingli/">New Jersey Institute of Technology, US</a> </li> <li> Renato Mancuso <a href="https://cs-people.bu.edu/rmancuso/">Boston University, US</a> </li> <li> Alessandro Papadopoulos <a href="http://www.idt.mdh.se/~aps01/">Mälardalen University, Västerås, SE</a> </li> <li> Heechul Yun <a href="http://www.ittc.ku.edu/~heechul/">University of Kansas, Lawrence, US</a> </li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Constitution</h5> </div> <div class="col-sm-10"> <p>LITES shall have an editor-in-chief and an editorial board consisting of 10 to 20 associate editors. LITES is operated not-for-profit. All editors and reviewers are unpaid volunteers. The APC is charged to compensate the real costs and can be waived in exceptional circumstances on a case-by-case basis for authors without institutional support and for who the APC would result in undue financial hardship.</p> <h6>Duties of the editorial board</h6> <ul><li>The editors shall find competent reviewers for submissions and assign submissions to these reviewers, monitor the reviews respecting the timelines. They shall respect the COPE (Committee on Publication Ethics) Code of Conduct for Journal Editors/Journal Publishers (see <a href='http://publicationethics.org'>http://publicationethics.org</a>).</li><li>The editors will be supported by a submission management system.</li><li>The terms for editors last 4 years, renewable once.</li></ul> </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>Review Policy</h5> </div> <div class="col-sm-10"> <p>Decisions are taken by the associate editor in charge of a submission. A minimum number of 3 reviews for each submissions required. The journal uses a single-anonymous peer-review process (i.e., authors do not know who the reviewers are, but reviewers do know who the authors are).</p><p>The editor-in-chief (EiC) assigns each new submission to a responsible associate editor, taking into account possible conflicts of interest (CoI), and has the final responsibility for decisions about acceptance and rejection of submissions.<p>The associate editors</p><ul><li>filter out inadequate submissions (out of scope, inappropriate presentation, 'spam'),</li><li>depending on the case, trigger consultation with the editor-in-chief,</li><li>select, assign, and invite reviewers,</li><li>keep track of pending reviews,</li><li>ensure that reviewers do not have any conflicts of interests,</li><li>in case of ambiguous reviews<ul><li>trigger clarification among conflicting reviewers, and/or</li><li>organize additional reviews.</li></ul></li></ul><p>Reviewers provide</p><ul><li>a detailed review judging the scientic value and relevance of the submitted work according to the criteria set out below,</li><li>a decision whether an article should be accepted, revised, or rejected,</li><li>a decision whether the submitted article would need language- and copy-editing in case of acceptance.</li></ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Review Criteria</h5> </div> <div class="col-sm-10"> <p>Manuscripts are reviewed based on the following criteria:</p><ul><li>Novelty — does the paper make a well-argued new contribution to<ul><li>the state of the art in embedded computing systems, broadly construed, and/or</li><li>to the scientific discourse on the study of embedded computing systems?</li></ul></li><li>Validity of conclusions — are all claims made in the paper, either formally or informally, appropriately substantiated by rigorous proof, convincing argument, and/or experimental validation (as appropriate for the paper’s specific contributions)?</li><li>Technical correctness — are all derivations and methods technically sound?</li><li>Reproducibility — does the paper present sufficient information (ideally, accompanying research artifacts) for others to reproduce and build on its findings?</li></ul><p>Papers are <b>not</b> reviewed on their perceived significance or expected impact, which are ultimately guesswork and best left to history.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Conflicts of Interest</h5> </div> <div class="col-sm-10"> <p>A conflict of interest (CoI) exists between a reviewer or editor and the authors if they:</p><ul><li>had at any time a supervisor/PhD student relationship,</li><li>are both from the same institution, or have worked at the same institution in the past 36 months at the time of submission,</li><li>are currently working together on a research paper, project, or funding proposal, or have done so during the past 36 months at the time of submission,</li><li>are related, close personal friends, or unable to assess the work objectively (e.g., due to prior conflict), or</li><li>are in some form of financial relationship, or have been at some point during the past 36 months at the time of submission.</li></ul><p>Further information can be found on the <a target='_blank' href='https://www.dagstuhl.de/en/publishing/ethics'>Publication Ethics website of Dagstuhl Publishing</a>.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Publication Timeline</h5> </div> <div class="col-sm-10"> <p>The target timelines for handling submissions are:</p><ul><li>Max. 1 year overall from submission to publication.</li><li>6 months in case of reviews recommending<em> Minor Revision</em>.</li><li>Max. 1 month for reviewer assignment</li><li>Max. 4 months from reviewer assignment to review.</li><li>Max. 3 months for author corrections to final version.</li></ul> </div> </div> <hr /> </div> <div class="tab-pane fade" id="cfp" role="tabpanel" aria-labelledby="cfp-tab"> <div class="row"> <div class="col-sm-2"> <h5 style="margin-top: 0;">Regular Call for Papers</h5> </div> <div class="col-sm-10"> <p>(<span style="font-style:italic">Here we provide the Regular Call for Papers. See also our <span style="font-weight:bold"><a data-tab-link href="#si">list of Special Issues open for submissions</a></span></span>.)</p> <p><b>LITES</b> publishes <b>original articles on all aspects of embedded computing systems</b>. Topics of interest include (but are not limited to):</p> <ul> <li>the design, implementation, testing, validation, and verification of embedded software and hardware systems,</li> <li>their temporal and logical correctness,</li> <li>resource efficiency and optimization,</li> <li>time-sensitive networking,</li> <li>embedded security,</li> <li>design space exploration and design automation,</li> <li>embedded artificial intelligence (AI),</li> <li>formal foundations of embedded systems,</li> <li>embedded systems in the context of larger cyber-physical systems (CPS), and</li> <li>application domains and deployment scenarios (e.g., automotive systems, avionics, robotics, healthcare, autonomous systems, etc.).</li> </ul> <p> The journal is flexible in the types of articles it publishes. The range of acceptable contributions includes (but is not limited to) regular technical papers, industrial experience reports, replication studies, literature surveys, historical perspectives, position papers, tools papers, and companion papers to open-access research artifacts (such as open-source software and hardware designs, data sets, case studies, challenge problems and competitions, etc.). </p> <p> LITES welcomes all methods of scientific inquiry, including (but not limited to) systems building and empirical evaluation, mathematical modeling and rigorous proof, formal methods, deployment studies and reflections on “lessons learned” in practice, as well as statistical and empirical methods, surveys of industry practice, and user studies. </p> <h5>Why Publish with LITES?</h5> <p> As the only fully open-access, truly nonprofit journal on embedded systems backed by an established publisher, LITES offers the best deal to authors, readers, and the community alike: </p> <ol> <li>LITES is fully <b>open access</b>: All published articles are available online free of charge (without a paywall or registration).</li> <li>LITES publishes <b>quality science</b>: The Editorial Board ensures high-quality, professional peer review. Authors receive quality feedback in a timely manner. The journal has a 10-year record of publishing exclusively high-quality scholarly articles.</li> <li>Authors <b>retain full rights</b> to their articles (papers are published under a Creative Commons license).</li> <li>Community and publisher have <b>fully aligned incentives</b>: Published by EMSIG in collaboration with Dagstuhl Publishing, a publicly funded nonprofit publisher, LITES is about the science _and only about the science_. There is no hidden profit motive; LITES does not have to generate revenue.</li> <li>The work volunteered by reviewers and editors furthers the ideals of <b>open science</b>, not the publisher’s bottom line.</li> <li>LITES is <b>cost-efficient</b>: Unlike certain other commercial publishers and computing associations, LITES collects a modest article processing charge (APC) that offsets only the actual costs incurred during the publication process and does not generate any profits. Authors facing financial hardship or without institutional support may apply for an APC waiver. Additionally, the first 20 accepted papers each year automatically receive a <b>full APC waiver</b> thanks to financial support by EMSIG.</li> </ol> </div> </div> </div> <div class="tab-pane fade" id="si" role="tabpanel" aria-labelledby="si-tab"> <div class="row" id="cfp-si-list"> <div class="col-sm-2"> <h5 style="margin-top: 0;">Special Issues</h5> </div> <div class="col-sm-10"> <p>The following special issues are <span style="font-weight: bold">currently open for submissions</span>:</p> <ul> <li><a href="#cfp-si-industrial-real-time-systems" data-scroll-link>Special Issue: Industrial Real-Time Systems</a></li> </ul> </div> </div> <hr /> <div class="row" id="cfp-si-industrial-real-time-systems"> <div class="col-sm-2"> <h5 style="margin-top: 0;">Special Issue</h5> </div> <div class="col-sm-10"> <div class="main"> <h5 style="margin-top: 0;">Industrial Real-Time Systems</h5> The open-access journal Leibniz Transactions on Embedded Systems (LITES) is soliciting original articles for a <b>special issue on Industrial Real-Time Systems</b>.<br><br> <b>Submission deadline</b>: March, 14 2025 <br><br> <b>Submission portal</b>: <a href="https://ojs.dagstuhl.de/index.php/lites/login">LITES OJS Login</a> / <a href="https://ojs.dagstuhl.de/index.php/lites/user/register">LITES OJS Registration</a> <br><br> <h5>Guest editors</h5> Daniel Casini, PhD<br> Scuola Superiore Sant'Anna – Pisa, Italy<br><br> Qingxu Deng, PhD<br> Northeastern University, Shenyang, China<br><br> Zhishan Guo, PhD (Leading)<br> NC State University, North Carolina, USA<br><br> Wei Jiang, PhD<br> University of Electronic Science and Technology of China, Chengdu, China<br><br> Haibo Zeng, PhD<br> Virginia Tech, Virginia, USA<br><br> <h5>Editor-in-Chief</h5> Björn Brandenburg, PhD<br> Max Planck Institute for Software Systems, Kaiserslautern, Germany<br><br> <h5>Scope of the special issue</h5> <p>Real-time systems and their industrial applications are facing new challenges due to the increasing use of AI/ML techniques, which are extremely complex and often lacking in explainability, and the introduction of connectivity, which creates a larger attack surface for malicious adversaries to exploit. In addition, real-time systems often need to operate with limited resources (e.g., low energy and power envelopes) while maintaining high fidelity (e.g., safety and security) and temporal correctness (e.g., deadline compliance or end-to-end response time guarantees).</p> <p>To address these challenges, this special issue aims to bring together researchers and practitioners from industry and academia and provide them with a platform to report on recent developments, deployments, technology trends, research results, and initiatives related to real-time systems and their applications in a variety of industrial environments.</p> <p>Topics of interest include, but are not limited to:</p> <ul> <li>Design and Validation of Real-Time Systems</li> <li>Real-Time Scheduling</li> <li>Real-Time Programming <li>Real-Time Artificial Intelligence and Machine Learning at the edge <li>Real-Time Edge Computing and its Use Cases <li>Model Checking and Verification <li>Fault Prediction and Fault Tolerance <li>Timing and Performance Analysis <li>Design Space Exploration <li>QoS Mechanisms for Virtualization and Control <li>Energy and Power Aware Real-Time Computing <li>Fault Tolerance & Dependability Adaptive Cyber-Physical Systems <li>Cyber-Security for Real-Time Systems <li>Probabilities and Uncertainties in Real-Time Systems <li>Response-Time Analysis <li>Temporal aspects in CPS applications, including Transportation Systems, Wireless Health Care, Autonomous Driving, etc. <li>Real-Time Operating Systems and Hypervisors <li>Middleware Frameworks and Runtime Environments </ul> <p>LITES welcomes all submissions that explore the latest research and developments in real-time systems and their industrial applications. In addition, authors of selected papers from SIES 2024 (The 14th IEEE International Symposium on Industrial Embedded Systems) are invited to submit extended versions of their papers for consideration for inclusion in the special issue. </p> <br> <h5>About LITES</h5> <p>Founded in 2014, LITES is the only fully open-access, fully peer-reviewed, truly nonprofit journal on embedded systems backed by an established publisher.</p> <p> The journal is flexible in the types of articles it publishes. The range of acceptable contributions includes (but is not limited to) regular technical papers, industrial experience reports, replication studies, literature surveys, historical perspectives, position papers, tools papers, and companion papers to open-access research artifacts (such as open-source software and hardware designs, data sets, case studies, challenge problems and competitions, etc.). </p> <p> LITES welcomes all methods of scientific inquiry, including (but not limited to) systems building and empirical evaluation, mathematical modeling and rigorous proof, formal methods, deployment studies and reflections on “lessons learned” in practice, as well as statistical and empirical methods, surveys of industry practice, and user studies. <p> <p> The first 20 papers accepted for publication in 2025 will have the usual article processing charge (APC) fully waived, i.e., authors will not be charged any publication fees thanks to sponsorship by EMSIG. APC waivers will be allocated on a first-come, first-serve basis to accepted papers. Papers (co-)authored by members of the editorial board are not eligible for the APC waiver. LITES is published by EMSIG, the EDAA Special Interest Group on Embedded Systems Design, in collaboration with Schloss Dagstuhl Publishing. </p> </div> </div> </div> </div> <div class="tab-pane fade" id="author" role="tabpanel" aria-labelledby="author-tab"> <div class="row"> <div class="col-sm-2"> <h5>Author Guidelines</h5> </div> <div class="col-sm-10"> <p> Authors shall submit original work that is not submitted elsewhere while the submission and review process of LITES is going on. Authors are encouraged to submit software and data along with the article submission. This enables the replication of experiments and helps other researchers to build on the published results. </p> <p> Extensions of previously published workshop and conference papers are welcome. Extensions of conference papers and workshop papers published with a DOI require at least 30% new material to be accepted. The manuscript should include a statement explaining the novel contributions on top of the preliminary conference or workshop version of the manuscript. When in doubt whether a (planned) extension meets these requirements, please inquire with the editor-in-chief for clarification. </p> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Language</h5> </div> <div class="col-sm-10"> <p> Articles must be written in British or American English. Please be consistent – use the same form of English (i.e., British or American) throughout the text. </p> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Length</h5> </div> <div class="col-sm-10"> <p> A submitted article shall normally be no more than 25 pages (not inclduing abstract and bibliography). Longer papers might be considered but there must be a strong justification. When planning to submit a paper significantly exceeding the 25-page limit, please reach out to the editorin-chief with a justification to obtain prior approval. </p> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Submission</h5> </div> <div class="col-sm-10"> <p> Please submit manuscripts via the LITES submission system. <a href="https://ojs.dagstuhl.de/index.php/lites/login">LITES OJS Login</a> / <a href="https://ojs.dagstuhl.de/index.php/lites/user/register">LITES OJS Registration</a> </p> </div> </div> <hr /> <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 LITES style along with an example file and detailed author instructions:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>lites-v2021</b> <span class="label label-success "> v2021.2.2 </span> <aside style="display: inline-block; margin-left: 10px;"> <div class="btn-group"> <button type="button" class="btn btn-xs btn-default dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Download <span class="caret"></span> </button> <ul class="dropdown-menu"> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/lites/v2021.2.2/authors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/lites/v2021.2.2/authors/tgz"> as tar.gz-file </a> </li> </ul> </div> </aside> </div> </div> <p> For <a href="https://github.com/dagstuhl-publishing/styles/releases">older releases</a> and an <a href="https://github.com/dagstuhl-publishing/styles/issues">issue tracker</a>, see our <a href="https://github.com/dagstuhl-publishing/styles">GitHub archive</a>. </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Submission Preparation Checklist</h5> </div> <div class="col-sm-10"> <p> As part of the submission process, authors are required to check off their submission's compliance with all of the following guidelines. Submissions not adhering to these guidelines may be returned to the authors without further review. </p> <ul> <li>The submission has not been previously published, nor is it before another journal for consideration (or an explanation has been provided in Comments to the Editor).</li> <li>The submission file is in PDF format.</li> <li>Where available, URLs for the references have been provided.</li> <li>If the manuscript is an extension of a previously published workshop or conference paper, the manuscript contains a statement explaining the novel contribution relative to preliminary version already published. </li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Typesetting instructions - Summary</h5> </div> <div class="col-sm-10"> <p> <p>LITES publishes original articles on all aspects of embedded computing systems according to the principles of <a href="https://openaccess.mpg.de/Berlin-Declaration">Open Access</a>. The journal is published by the <a href="http://www.edaa.com/">European Design and Automation Association (EDAA)</a> \ <a href="http://www.emsig.net/">EMbedded Systems Special Interest Group (EMSIG)</a> and <a href="http://www.dagstuhl.de/dagpub">Schloss Dagstuhl -- Leibniz-Zentrum für Informatik GmbH, Dagstuhl Publishing</a></p> <p>LITES aims at efficient reviewing procedures to ensure that articles are published within one year of submission. LITES is continuously open for submission.</p> In order to do justice to the high scientific quality of the journal, which is ensured by the thorough review process, we believe that LITES articles must have an attractive and consistent layout matching the standard of the journal. 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 LITES. (See <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/LIPIcs', '_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="41" 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>Supplementary Material Statement</h5> </div> <div class="col-sm-10"> <p>Reproducibility is a key aspect of scientific research. Dagstuhl Publishing highly encourages that all <a href="#" data-faq-id="45" class="_faq" tabindex="0">relevant resources (e.g. research data, software, videos, ...) <i class="bi bi-question-circle-fill"></i></a> for research articles are disclosed and documented in a <b>Supplementary Material Statement</b>. This enhances reproducibility, allows the community to build on these resources, and helps readers verify or understand additional details. If resources cannot be published, authors should justify this.</p> <p>The statement could be added to the article's metadata block using the macro <a href="#" data-faq-id="21" class="_faq" tabindex="0"><code>\supplementdetails</code> <i class="bi bi-question-circle-fill"></i></a> for every supplementary resource. The publishing system supports authors in managing supplementary materials. </p> <div> Please find more information in our <a href="#" data-toggle="modal" data-target="#lites-documentation-modal">documentation</a> <div class="modal fade" id="lites-documentation-modal" tabindex="-1" role="dialog" aria-labelledby="lites-documentation-modal-label" style="z-index: 10000;"> <div class="modal-dialog" role="document" style="width: 80vw; height: 80vh; max-width: 1200px"> <div class="modal-content"> <div class="modal-header"> <h5 class="modal-title" id="lites-documentation-modal-label">Publication Workflow for Authors</h5> <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button> </div> <div class="modal-body"> <iframe loading="lazy" src="https://dagstuhl.de/api/v1/articleIframe?permalink=publication-workflow-2025" style="width: 100%; height: 65vh; border: 0; padding: 0; margin: 0"></iframe> </div> <div class="modal-footer"> <button type="button" class="btn btn-primary" data-dismiss="modal">Close</button> </div> </div> </div> </div> which covers all steps of the publication workflow. </div> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Please do not ...</h5> </div> <div class="col-sm-10"> <p class="bodytext">Generally speaking, please <b>do not override the style defaults concerning spacing, font and color settings</b>. To be more specific, a short checklist also used by Dagstuhl Publishing during the final typesetting is given below. In case of <b>non-compliance</b> with these rules, Dagstuhl Publishing will remove the corresponding parts of LaTeX code and <b>replace it with the defaults</b>. In serious cases, we may reject the LaTeX-source and expect the corresponding author to revise the relevant parts.</p> <ul> <li>Do not use a different main font. (For example, the <code class="not-allowed">times</code> package is forbidden.)</li> <li>Do not alter the spacing of the provided style file.</li> <li>Do not use <code class="not-allowed">enumitem</code> and <code class="not-allowed">paralist</code>. (The <i>enumerate</i> package is preloaded, so you can use <code>\begin{enumerate}[(a)]</code> or the like.)</li> <li>Do not use "self-made" sectioning commands (e.g., <code class="not-allowed">\noindent{\bf My Paragraph}</code>).</li> <li>Do not hide large text blocks using comments or <code class="not-allowed">\iffalse ... \fi</code> constructions. </li> <li>Do not use conditional structures to include/exclude content. Instead, please provide only the content that should be published - in one file - and nothing else.</li> <li>Do not wrap figures and tables with text. In particular, the package <code class="not-allowed">wrapfig</code> is not supported. </li> <li>Do not change the bibliography style. In particular, do not use author-year citations. (The <code class="not-allowed">natbib</code> package is not supported.) </li> </ul> <p class="bodytext">This is only a summary containing the most relevant details. Please read the complete <span class="btn btn-xs" onclick="window.open( 'https://submission.dagstuhl.de/styles/instructions/LIPIcs', '_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="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-24-Submission-author"> <a class="collapsed" href="#FAQ-24-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-24-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">affiliation</span><span class="question">What are the <b>minimum requirements</b> on an affiliation?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-24-Submission-author" role="tabpanel" aria-labelledby="FAQ-24-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-1-Submission-author"> <a class="collapsed" href="#FAQ-1-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-1-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorized user</span><span class="question">What is an <b>authorized user</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-1-Submission-author" role="tabpanel" aria-labelledby="FAQ-1-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-2-Submission-author"> <a class="collapsed" href="#FAQ-2-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-2-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">Why the <b>list of authors</b> may change during the submission process</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-2-Submission-author" role="tabpanel" aria-labelledby="FAQ-2-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-23-Submission-author"> <a class="collapsed" href="#FAQ-23-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-23-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">What if the <b>list of authors</b> is <b>incorrect</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-23-Submission-author" role="tabpanel" aria-labelledby="FAQ-23-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-22-Submission-author"> <a class="collapsed" href="#FAQ-22-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-22-Submission-author" role="tabpanel" aria-labelledby="FAQ-22-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-46-Submission-author"> <a class="collapsed" href="#FAQ-46-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-46-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">DOI metadata</span><span class="question">Why can't I find any metadata for my <b>DOI</b> at <b>CrossRef</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-46-Submission-author" role="tabpanel" aria-labelledby="FAQ-46-Submission-author"> <div class="card-body"> <p>The metadata associated with a DOI may not be available in all services, especially in the context of Crossref. The reason for this is that we use DataCite as our DOI registry and not CrossRef. CrossRef is certainly the largest registry for DOIs, but there are a few others (see <a href="https://www.doi.org/the-community/existing-registration-agencies/">https://www.doi.org/the-community/existing-registration-agencies/</a>).<p> <p>However, our data can be retrieved in a number of ways. DataCite offers several search options and APIs that are similar to those of CrossRef, see for example <a href="https://commons.datacite.org/">https://commons.datacite.org/</a>.</p> <p>Alternatively, you can of course retrieve the complete set of metada directly from us (<a href="https://drops.dagstuhl.de/metadata">https://drops.dagstuhl.de/metadata</a>) or the basic data set from dblp (<a href="https://dblp.org">https://dblp.org</a>).</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/46"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/46</a></small> </div> </div> </div> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-25-Submission-author"> <a class="collapsed" href="#FAQ-25-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-25-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">funding</span><span class="question">There are two <b>different</b> kinds of <b>funding fields</b>. Where to place what?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-25-Submission-author" role="tabpanel" aria-labelledby="FAQ-25-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-48-Submission-author"> <a class="collapsed" href="#FAQ-48-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-48-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">left-aligned equations</span><span class="question">Why are <b>equations left-aligned</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-48-Submission-author" role="tabpanel" aria-labelledby="FAQ-48-Submission-author"> <div class="card-body"> <p>The left justification of the equations is not random but part of the LIPIcs style and the other styles of Dagstuhl Publishing. We decided some years ago that we prefer text-like content (incl. equations and captions) to be left-justified and not centered. In contrast, figures and tables are centered. See also the LIPIcs Author Guidelines:<p> <p><a href="https://submission.dagstuhl.de/styles/instructions/lipics">https://submission.dagstuhl.de/styles/instructions/lipics</a></p> <p>The alignment of the equations is thus a deliberate style decision of the series. Therefore, we cannot comply with any request for centering.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/48"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/48</a></small> </div> </div> </div> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-7-Submission-author"> <a class="collapsed" href="#FAQ-7-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-7-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata</span><span class="question">How can I <b>edit the metadata</b> in the submission process?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-7-Submission-author" role="tabpanel" aria-labelledby="FAQ-7-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-47-Submission-author"> <a class="collapsed" href="#FAQ-47-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-47-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">n-dash vs. m-dash</span><span class="question">Why should I use an <b>n-dash</b> instead of an <b>m-dash</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-47-Submission-author" role="tabpanel" aria-labelledby="FAQ-47-Submission-author"> <div class="card-body"> <p>We try to harmonize dashes across the whole volume (even across the whole series). We clearly address this as one of our typesetting actions in the author guidelines - admittedly, at the very end, cf. p.1:21, Section 3.2 of our current author instructions for LIPIcs authors.</p> <p>However, seeking uniformity is always difficult if different style guides give different advice.</p> <p>The <a href="https://www.ox.ac.uk/sites/files/oxford/media_wysiwyg/University%20of%20Oxford%20Style%20Guide.pdf">University of Oxford Style Guide</a> explicitly says on p. 13:<p> <blockquote> m-dash<br/> Do not use; use an n-dash instead.<br/> <br/> n-dash<br/> Use in a pair in place of round brackets or commas, surrounded by spaces.<br/> Use singly and surrounded by spaces to link two parts of a sentence, in place of a colon.<br/> </blockquote> <p>Generally, it seems that in British English the " -- " variant is preferred over "---", whereas in American English it is just the opposite. (It seems, however, that there is no uniform opinion on this in either language area.)</p> <p>Hence our replacement ("---" -> " -- ") follows at least one of the accepted style guides.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/47"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/47</a></small> </div> </div> </div> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-4-Submission-author"> <a class="collapsed" href="#FAQ-4-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-4-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version</span><span class="question">What is a <b>related version</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-4-Submission-author" role="tabpanel" aria-labelledby="FAQ-4-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-5-Submission-author"> <a class="collapsed" href="#FAQ-5-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-5-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version url</span><span class="question">Why is a <b>URL mandatory</b> for a related version?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-5-Submission-author" role="tabpanel" aria-labelledby="FAQ-5-Submission-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-6-Submission-author"> <a class="collapsed" href="#FAQ-6-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-6-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">subject classifications</span><span class="question">How to handle <b>subject classifications </b> marked as <b>invalid</b>? </span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-6-Submission-author" role="tabpanel" aria-labelledby="FAQ-6-Submission-author"> <div class="card-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 class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-45-Submission-author"> <a class="collapsed" href="#FAQ-45-Submission-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-45-Submission-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">supplementary materials</span><span class="question">What are <b>supplementary materials</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-45-Submission-author" role="tabpanel" aria-labelledby="FAQ-45-Submission-author"> <div class="card-body"> <p>Supplementary materials are all kinds of resources related to a scholarly article such as <b>research data</b>, <b>source code</b>, <b>research software</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">zenodo</a>, <a href="https://figshare.com/">figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/45"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/45</a></small> </div> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Author Approval</h5> </div> <div class="col-sm-10"> <div class="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-30-AuthorApproval-author"> <a class="collapsed" href="#FAQ-30-AuthorApproval-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-AuthorApproval-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-30-AuthorApproval-author" role="tabpanel" aria-labelledby="FAQ-30-AuthorApproval-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-28-AuthorApproval-author"> <a class="collapsed" href="#FAQ-28-AuthorApproval-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-28-AuthorApproval-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">LaTeX-changes</span><span class="question">What happens if I ask for <b>LaTeX</b>-changes in the approval step?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-28-AuthorApproval-author" role="tabpanel" aria-labelledby="FAQ-28-AuthorApproval-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-27-AuthorApproval-author"> <a class="collapsed" href="#FAQ-27-AuthorApproval-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-27-AuthorApproval-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata changes</span><span class="question">What happens if I ask for <b>metadata changes</b> in the approval process?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-27-AuthorApproval-author" role="tabpanel" aria-labelledby="FAQ-27-AuthorApproval-author"> <div class="card-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="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-30-PublicationWorkflow-author"> <a class="collapsed" href="#FAQ-30-PublicationWorkflow-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-PublicationWorkflow-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-30-PublicationWorkflow-author" role="tabpanel" aria-labelledby="FAQ-30-PublicationWorkflow-author"> <div class="card-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="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-14-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-14-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-14-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author macro</span><span class="question">How to use the <code>\author</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-14-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-14-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-17-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-17-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-17-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorrunning macro</span><span class="question">How to use the <code>\authorrunning</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-17-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-17-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-22-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-22-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-22-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-22-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-18-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-18-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-18-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">ccsdesc macro</span><span class="question">How to use the <code>\ccsdesc</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-18-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-18-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-16-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-16-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-16-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">copyright macro</span><span class="question">How to use the <code>\Copyright</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-16-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-16-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-20-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-20-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-20-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">funding macro</span><span class="question">How to use the <code>\funding</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-20-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-20-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-15-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-15-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-15-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">keywords macro</span><span class="question">How to use the <code>\keywords</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-15-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-15-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-19-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-19-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-19-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">relatedversiondetails macro</span><span class="question">How to use the <code>\relatedversiondetails</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-19-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-19-LaTeXStyle-author"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-21-LaTeXStyle-author"> <a class="collapsed" href="#FAQ-21-LaTeXStyle-author" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-21-LaTeXStyle-author" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">supplementdetails macro</span><span class="question">How to use the <code>\supplementdetails</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-21-LaTeXStyle-author" role="tabpanel" aria-labelledby="FAQ-21-LaTeXStyle-author"> <div class="card-body"> <p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">Zenodo</a>, <a href="https://figshare.com/">Figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}, swhid={...}]{Software}{https://github.com/...} </pre> <p> <ul><li>The <b>subcategory</b> is free text, while the <b>category</b> ("Software" in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.)</li> <li>The <b>swhid</b> (Software Heritage identifier) is optional and will usually be added by the publisher.</li> </ul> <p> Please note: <ul> <li>In case of a resource that may evolve over time (e.g., source code under active development), sufficient details must be provided for readers to find the specific relevant version.</li> <li>Relevant materials can be referred to via URLs (either directly in the text or in footnotes) or via a bibliographical reference in the text. Please ensure any URLs are formatted as such, i.e., clickable in the digital version of the article to visit the relevant page.</li> <li>Relevant resources included in this statement must be well-documented or otherwise self-explanatory for readers viewing the materials.</li> <li>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use of platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</li> </ul> </p> </div> <div class="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> <div class="row"> <div class="col-sm-2"> <h5>Not found?</h5> </div> <div class="col-sm-10"> <p> Didn't find what you are looking for? Don't hesitate to leave us a message at <a href="mailto:publishing@dagstuhl.de">publishing@dagstuhl.de</a>! </p> </div> </div> </div> <div class="tab-pane fade" id="editor" role="tabpanel" aria-labelledby="editor-tab"> <div class="row"> <div class="col-sm-2"> <h5>Front Matter Template and Example Files</h5> </div> <div class="col-sm-10"> <p>Please download the current version of the LITES front matter style along with an example file:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>litesmaster-v2021</b> <span class="label label-success "> v2021.2.2 </span> <aside style="display: inline-block; margin-left: 10px;"> <div class="btn-group"> <button type="button" class="btn btn-xs btn-default dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Download <span class="caret"></span> </button> <ul class="dropdown-menu"> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/lites/v2021.2.2/editors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/lites/v2021.2.2/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>Editor Login</h5> </div> <div class="col-sm-10"> <p>Submissions via LITES Submission System: <a href="https://ojs.dagstuhl.de/index.php/lites/login">LITES OJS Login</a> / <a href="https://ojs.dagstuhl.de/index.php/lites/user/register">LITES OJS Registration</a></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="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-24-Submission-editor"> <a class="collapsed" href="#FAQ-24-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-24-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">affiliation</span><span class="question">What are the <b>minimum requirements</b> on an affiliation?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-24-Submission-editor" role="tabpanel" aria-labelledby="FAQ-24-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-1-Submission-editor"> <a class="collapsed" href="#FAQ-1-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-1-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorized user</span><span class="question">What is an <b>authorized user</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-1-Submission-editor" role="tabpanel" aria-labelledby="FAQ-1-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-2-Submission-editor"> <a class="collapsed" href="#FAQ-2-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-2-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">Why the <b>list of authors</b> may change during the submission process</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-2-Submission-editor" role="tabpanel" aria-labelledby="FAQ-2-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-23-Submission-editor"> <a class="collapsed" href="#FAQ-23-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-23-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authors</span><span class="question">What if the <b>list of authors</b> is <b>incorrect</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-23-Submission-editor" role="tabpanel" aria-labelledby="FAQ-23-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-22-Submission-editor"> <a class="collapsed" href="#FAQ-22-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-22-Submission-editor" role="tabpanel" aria-labelledby="FAQ-22-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-46-Submission-editor"> <a class="collapsed" href="#FAQ-46-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-46-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">DOI metadata</span><span class="question">Why can't I find any metadata for my <b>DOI</b> at <b>CrossRef</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-46-Submission-editor" role="tabpanel" aria-labelledby="FAQ-46-Submission-editor"> <div class="card-body"> <p>The metadata associated with a DOI may not be available in all services, especially in the context of Crossref. The reason for this is that we use DataCite as our DOI registry and not CrossRef. CrossRef is certainly the largest registry for DOIs, but there are a few others (see <a href="https://www.doi.org/the-community/existing-registration-agencies/">https://www.doi.org/the-community/existing-registration-agencies/</a>).<p> <p>However, our data can be retrieved in a number of ways. DataCite offers several search options and APIs that are similar to those of CrossRef, see for example <a href="https://commons.datacite.org/">https://commons.datacite.org/</a>.</p> <p>Alternatively, you can of course retrieve the complete set of metada directly from us (<a href="https://drops.dagstuhl.de/metadata">https://drops.dagstuhl.de/metadata</a>) or the basic data set from dblp (<a href="https://dblp.org">https://dblp.org</a>).</p> </div> <div class="card-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/46"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/46</a></small> </div> </div> </div> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-7-Submission-editor"> <a class="collapsed" href="#FAQ-7-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-7-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata</span><span class="question">How can I <b>edit the metadata</b> in the submission process?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-7-Submission-editor" role="tabpanel" aria-labelledby="FAQ-7-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-4-Submission-editor"> <a class="collapsed" href="#FAQ-4-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-4-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version</span><span class="question">What is a <b>related version</b>?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-4-Submission-editor" role="tabpanel" aria-labelledby="FAQ-4-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-5-Submission-editor"> <a class="collapsed" href="#FAQ-5-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-5-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">related version url</span><span class="question">Why is a <b>URL mandatory</b> for a related version?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-5-Submission-editor" role="tabpanel" aria-labelledby="FAQ-5-Submission-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-6-Submission-editor"> <a class="collapsed" href="#FAQ-6-Submission-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-6-Submission-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">subject classifications</span><span class="question">How to handle <b>subject classifications </b> marked as <b>invalid</b>? </span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-6-Submission-editor" role="tabpanel" aria-labelledby="FAQ-6-Submission-editor"> <div class="card-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="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-30-AuthorApproval-editor"> <a class="collapsed" href="#FAQ-30-AuthorApproval-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-AuthorApproval-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-30-AuthorApproval-editor" role="tabpanel" aria-labelledby="FAQ-30-AuthorApproval-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-28-AuthorApproval-editor"> <a class="collapsed" href="#FAQ-28-AuthorApproval-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-28-AuthorApproval-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">LaTeX-changes</span><span class="question">What happens if I ask for <b>LaTeX</b>-changes in the approval step?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-28-AuthorApproval-editor" role="tabpanel" aria-labelledby="FAQ-28-AuthorApproval-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-27-AuthorApproval-editor"> <a class="collapsed" href="#FAQ-27-AuthorApproval-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-27-AuthorApproval-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">metadata changes</span><span class="question">What happens if I ask for <b>metadata changes</b> in the approval process?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-27-AuthorApproval-editor" role="tabpanel" aria-labelledby="FAQ-27-AuthorApproval-editor"> <div class="card-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="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-30-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-30-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-30-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">author approval</span><span class="question">How does <b>author approval</b> work?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-30-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-30-PublicationWorkflow-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-31-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-31-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-31-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">editor approval</span><span class="question">How does the <b>editor approval</b> work?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-31-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-31-PublicationWorkflow-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-29-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-29-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-29-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">editor submission</span><span class="question">What are the editors' tasks between author and editor submission?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-29-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-29-PublicationWorkflow-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-8-PublicationWorkflow-editor"> <a class="collapsed" href="#FAQ-8-PublicationWorkflow-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-8-PublicationWorkflow-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">paper submission</span><span class="question">What are the <b>editor's tasks</b> during the paper submission period?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-8-PublicationWorkflow-editor" role="tabpanel" aria-labelledby="FAQ-8-PublicationWorkflow-editor"> <div class="card-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>LaTeX Style</h5> </div> <div class="col-sm-10"> <div class="card-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-17-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-17-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-17-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">authorrunning macro</span><span class="question">How to use the <code>\authorrunning</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-17-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-17-LaTeXStyle-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-22-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-22-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-22-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">bibliography</span><span class="question">In which format should the <b>bibliography</b> be submitted?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-22-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-22-LaTeXStyle-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-18-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-18-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-18-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">ccsdesc macro</span><span class="question">How to use the <code>\ccsdesc</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-18-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-18-LaTeXStyle-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-16-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-16-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-16-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">copyright macro</span><span class="question">How to use the <code>\Copyright</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-16-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-16-LaTeXStyle-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-20-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-20-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-20-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">funding macro</span><span class="question">How to use the <code>\funding</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-20-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-20-LaTeXStyle-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-15-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-15-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-15-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">keywords macro</span><span class="question">How to use the <code>\keywords</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-15-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-15-LaTeXStyle-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-19-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-19-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-19-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">relatedversiondetails macro</span><span class="question">How to use the <code>\relatedversiondetails</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-19-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-19-LaTeXStyle-editor"> <div class="card-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="card panel-default faq-list-item"> <div class="card-header" role="tab" id="heading-21-LaTeXStyle-editor"> <a class="collapsed" href="#FAQ-21-LaTeXStyle-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-21-LaTeXStyle-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">supplementdetails macro</span><span class="question">How to use the <code>\supplementdetails</code> macro?</span></span> </span></a> </div> <div class="card-collapse collapse" id="FAQ-21-LaTeXStyle-editor" role="tabpanel" aria-labelledby="FAQ-21-LaTeXStyle-editor"> <div class="card-body"> <p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">Zenodo</a>, <a href="https://figshare.com/">Figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}, swhid={...}]{Software}{https://github.com/...} </pre> <p> <ul><li>The <b>subcategory</b> is free text, while the <b>category</b> ("Software" in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.)</li> <li>The <b>swhid</b> (Software Heritage identifier) is optional and will usually be added by the publisher.</li> </ul> <p> Please note: <ul> <li>In case of a resource that may evolve over time (e.g., source code under active development), sufficient details must be provided for readers to find the specific relevant version.</li> <li>Relevant materials can be referred to via URLs (either directly in the text or in footnotes) or via a bibliographical reference in the text. Please ensure any URLs are formatted as such, i.e., clickable in the digital version of the article to visit the relevant page.</li> <li>Relevant resources included in this statement must be well-documented or otherwise self-explanatory for readers viewing the materials.</li> <li>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use of platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</li> </ul> </p> </div> <div class="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> <div class="row"> <div class="col-sm-2"> <h5>Not found?</h5> </div> <div class="col-sm-10"> <p> Didn't find what you are looking for? Don't hesitate to leave us message at <a href="mailto:publishing@dagstuhl.de">publishing@dagstuhl.de</a>! </p> </div> </div> </div> <div class="tab-pane fade" id="recently" role="tabpanel" aria-labelledby="recently-tab"> <div class="row"> <div class="col-sm-2"> <h5>Recently published volumes</h5> </div> <div class="col-sm-10"> <ul class="list-group"> <li class="list-group-item"> LITES, Vol. 9, Issue 1, <b>LITES, Volume 9, Issue 1 (2024)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-9-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> Björn B. Brandenburg </li> <li class="list-group-item"> LITES, Vol. 8, Issue 2, <b>LITES, Volume 8, Issue 2 (2022): Special Issue on Distributed Hybrid Systems</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-8-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 8, Issue 1, <b>LITES, Volume 8, Issue 1 (2022): Special Issue on Embedded Systems for Computer Vision</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-8-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 7, Issue 1, <b>LITES, Volume 7, Issue 1 (2021): Special Issue on Embedded System Security</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-7-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 6, Issue 1, <b>LITES, Volume 6, Issue 1 (2019)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-6-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 5, Issue 1, <b>LITES, Volume 5, Issue 1 (2018)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-5-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 4, Issue 2, <b>LITES, Volume 4, Issue 2 (2017)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-4-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 4, Issue 1, <b>LITES, Volume 4, Issue 1 (2017)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-4-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 3, Issue 1, <b>LITES, Volume 3, Issue 1 (2016)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-3-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 2, Issue 2, <b>LITES, Volume 2, Issue 2 (2015)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-2-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 2, Issue 1, <b>LITES, Volume 2, Issue 1 (2015)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-2-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 1, Issue 2, <b>LITES, Volume 1, Issue 2 (2014)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-1-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> LITES, Vol. 1, Issue 1, <b>LITES, Volume 1, Issue 1 (2014)</b> <div class="float-right"><a href="https://drops.dagstuhl.de/entities/issue/LITES-volume-1-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> </ul> </div> </div> </div> <div class="tab-pane fade" id="contact" role="tabpanel" aria-labelledby="contact-tab"> <div class="row"> <div class="col-sm-2"> <h5>Contact Dagstuhl Publishing</h5> </div> <div class="col-sm-10"> <div class="card"> <div class="card-body"> <h5 class="card-title">Dagstuhl Publishing Team</h5> <div class="icons"> <a href="mailto:publishing@dagstuhl.de" class="card-link"><i class="bi bi-envelope"></i> publishing@dagstuhl.de</a> </div> </div> </div> </div> </div> </div> </div> <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="41" 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>The <b>ORCID field is mandatory</b>. Include ORCID identifiers for each author. In case you don't have an ORCID yet, please request one on the <a href="https://orcid.org">ORCID website</a>. Please contact your co-authors directly for their ORCID and only use ORCIDs verified by them. </li> <li> If an author has several different affiliations, please clearly separate them with the keyword <code>\and</code>. </li> <li> E-mail and funding are optional. </li> <li> <b>Author macros cannot be shared!</b> Please use separate author macros even if two or more authors have the same affiliation! </li> </ul></span> </div> <div data-faq-stack-id="17" style="display: none;"> <span class="_title">How to use the <code>\authorrunning</code> macro?</span> <span class="_content"><p>This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:</p> <pre> \authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example} </pre> <p> Please... <ul> <li>abbreviate first names</li> <li>in case of middle initials: use <code>\,</code> as illustrated in the example</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> <li>in case of overfull \hboxes: use the name of the first author and "et al."</li> </ul> </span> </div> <div data-faq-stack-id="16" style="display: none;"> <span class="_title">How to use the <code>\Copyright</code> macro?</span> <span class="_content"><p>Using this macro, you specify the copyright holder (appearing at the bottom of the title page) which is usually the team of authors. Sample usage:</p> <pre> \Copyright{John Q. Public, Adam E. Access, and Eve Example} </pre> <p> Please... <ul> <li>use <b>full</b> first and last names</li> <li>be consistent with the <code>\author</code> macros</li> <li>in case of 2 authors: concatenate with " and "</li> <li>in case of 3 or more authors, see the sample for concatenation</li> </ul> </span> </div> <div data-faq-stack-id="18" style="display: none;"> <span class="_title">How to use the <code>\ccsdesc</code> macro?</span> <span class="_content"><p><code>\ccsdesc{...}</code> is for classification information following the ACM 2012 Computing Classification System. Sample usage:</p> <pre> \ccsdesc{Theory of computation~Proof complexity} \ccsdesc{Theory of computation~Quantum complexity theory}</pre> <p> Please feel free to use our <a class="btn btn-sm btn-default" href="https://submission.dagstuhl.de/services/acm-subject-classification" target="_blank">ACM 2012 Subject Finder</a> to search for appropriate classifications and to generate the necessary LaTeX code. </p></span> </div> <div data-faq-stack-id="15" style="display: none;"> <span class="_title">How to use the <code>\keywords</code> macro?</span> <span class="_content"><p>Sample usage:</p> <pre> \keywords{Theory of Everything, indefinite Metrics, abstract Nonsense} </pre> <p>Please note:</p> <ul> <li><b>comma</b> as delimiter</li> <li>first word and every proper noun should be capitalized</li> </ul></span> </div> <div data-faq-stack-id="19" style="display: none;"> <span class="_title">How to use the <code>\relatedversiondetails</code> macro?</span> <span class="_content"><p><code>\relatedversiondetails{...}</code> may be used to denote a related version like a <i>full version</i>, <i>extended version</i>, or also a predecessor usually published in a reliable repository like arXiv or HAL. Sample usage:</p> <pre> \relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...} </pre> <p> As all metadata should be self-contained, please add a persistent URL to the cited version (as illustrated above). This also simplifies the access for all readers. </p></span> </div> <div data-faq-stack-id="45" style="display: none;"> <span class="_title">What are <b>supplementary materials</b>?</span> <span class="_content"><p>Supplementary materials are all kinds of resources related to a scholarly article such as <b>research data</b>, <b>source code</b>, <b>research software</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">zenodo</a>, <a href="https://figshare.com/">figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</p></span> </div> <div data-faq-stack-id="21" style="display: none;"> <span class="_title">How to use the <code>\supplementdetails</code> macro?</span> <span class="_content"><p><code>\supplementdetails{...}</code> may be used to denote supplements like related <b>research data</b>, <b>source code</b>, <b>posters</b>, <b>slides</b>, ... hosted on a repository like <a href="https://zenodo.org/">Zenodo</a>, <a href="https://figshare.com/">Figshare</a>, ..., <a href="https://www.softwareheritage.org/">Software Heritage</a>.</p> <p>Sample usage:</p> <pre> \supplementdetails[subcategory={Source Code}, swhid={...}]{Software}{https://github.com/...} </pre> <p> <ul><li>The <b>subcategory</b> is free text, while the <b>category</b> ("Software" in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.)</li> <li>The <b>swhid</b> (Software Heritage identifier) is optional and will usually be added by the publisher.</li> </ul> <p> Please note: <ul> <li>In case of a resource that may evolve over time (e.g., source code under active development), sufficient details must be provided for readers to find the specific relevant version.</li> <li>Relevant materials can be referred to via URLs (either directly in the text or in footnotes) or via a bibliographical reference in the text. Please ensure any URLs are formatted as such, i.e., clickable in the digital version of the article to visit the relevant page.</li> <li>Relevant resources included in this statement must be well-documented or otherwise self-explanatory for readers viewing the materials.</li> <li>Resources should be published in such a way that enables long-term availability via persistent links; for example, use of archival platforms such as arXiv, Figshare, Zenodo, etc. is encouraged. Established platforms such as Github are also acceptable for source code and other materials. We discourage the use of platforms not intended for long-term publication, such as a personal homepage, file-sharing services (DropBox, Google Drive), etc. Company, personal and (non-archival) institutional platforms are also not suitable for archival purposes, but they can be used to host live demonstrations and services when accompanied by source code, data, and/or long-term archiving of a static snapshot.</li> </ul> </p> </span> </div> </div> <div class="_page-metadata"> <div id="_page-title"></div> <div id="_breadcrumb" data-remove="1">LITES</div> </div> </div></main><span class="__no-index-start"></span><a class="scroll-up-button -invisible" aria-label="Go to Top" href="#_top-of-page"><i class="bi bi-arrow-up-circle"></i></a><footer class="page-footer dark d-print-none"><div></div><div class="container"><div class="row expanded-menu"><div class="col-sm-2"><h5><a href="/de" class="dark link-node"><b style="color: #fff;">Das Institut</b></a></h5><ul><li><a href="/de" class="link-node">Übersicht</a></li><li><a href="/de/institute/news" class="link-node">Aktuelles</a></li><li><a href="/de/institute/organization" class="link-node">Konzept und Organisation</a></li><li><a href="/de/institute/team" class="link-node">Team</a></li><li><a href="/de/institute/committees" class="link-node">Gremien</a></li><li><a href="/de/institute/funding-and-financing" class="link-node">Förderung und Finanzierung</a></li><li><a href="/de/institute/projects" class="link-node">Projekte</a></li><li><a href="/de/institute/press" class="link-node">Presse</a></li><li><a href="/de/institute/dagstuhls-impact" class="link-node">Dagstuhl's Impact</a></li><li><a href="/de/institute/jobs" class="link-node">Stellenangebote</a></li><li><a href="/de/institute/gender-equality" class="link-node">Gleichstellungsplan</a></li><li><a href="/de/institute/ethics" class="link-node">Gute wissenschaftliche Praxis</a></li><li><a href="/de/institute/code-of-conduct" class="link-node">Code of Conduct</a></li></ul></div><div class="col-sm-2"><h5><a href="/de/seminars" class="dark link-node"><b style="color: #fff;">Seminare</b></a></h5><ul><li><a href="/de/seminars" class="link-node">Übersicht</a></li><li><a href="/de/seminars/seminar-calendar" class="link-node">Seminar-Kalender</a></li><li><a href="/de/seminars/news" class="link-node">News Seminarwesen</a></li><li><a href="/de/seminars/team" class="link-node">Mitarbeiter Seminarwesen</a></li><li><a href="/de/seminars/dagstuhl-seminars" class="link-node">Dagstuhl-Seminare</a></li><li><a href="/de/seminars/dagstuhl-perspectives" class="link-node">Dagstuhl-Perspektiven</a></li><li><a href="/de/seminars/gi-dagstuhl-seminars" class="link-node">GI-Dagstuhl-Seminare</a></li><li><a href="/de/seminars/summer-schools" class="link-node">Sommerschulen</a></li><li><a href="/de/seminars/research-meetings" class="link-node">Forschungstreffen</a></li><li><a href="/de/seminars/research-guests" class="link-node">Forschungsgäste</a></li><li><a href="/de/seminars/ethics" class="link-node">Gute wissenschaftliche Praxis</a></li></ul></div><div class="col-sm-2"><h5><a href="/de/publishing" class="dark link-node"><b style="color: #fff;">Publishing</b></a></h5><ul><li><a href="/de/publishing" class="link-node">Übersicht</a></li><li><a rel="noopener" target="_self" href="https://drops.dagstuhl.de/" class="link-external">Zu den Publikationen</a></li><li><a href="/de/publishing/news" class="link-node">Publishing News</a></li><li><a href="/de/publishing/team" class="link-node">Mitarbeiter Publishing</a></li><li><a href="/de/publishing/series" class="link-node">Die Serien im Überblick</a></li><li><a href="/de/publishing/series/details/LIPIcs" class="link-app">LIPIcs</a></li><li><a href="/de/publishing/series/details/OASIcs" class="link-app">OASIcs</a></li><li><a href="/de/publishing/series/details/LITES" class="link-app">LITES</a></li><li><a href="/de/publishing/series/details/TGDK" class="link-app">TGDK</a></li><li><a href="/de/publishing/series/details/DagRep" class="link-app">Dagstuhl Reports</a></li><li><a href="/de/publishing/open-access-policy" class="link-node">Open Access Policy</a></li><li><a href="/de/publishing/ethics" class="link-node">Publication Ethics</a></li><li><a href="/de/publishing/advisory-board" class="link-node">Publishing Beirat</a></li></ul></div><div class="col-sm-2"><h5><a href="/de/dblp" class="dark link-node"><b style="color: #fff;">dblp</b></a></h5><ul><li><a href="/de/dblp" class="link-node">Übersicht</a></li><li><a rel="noopener" target="_self" href="https://dblp.org/" class="link-external">Zur Datenbank</a></li><li><a href="/de/dblp/news" class="link-node">dblp-News</a></li><li><a href="/de/dblp/team" class="link-node">dblp-Team</a></li><li><a href="/de/dblp/advisory-board" class="link-node">dblp-Beirat</a></li><li><a href="/de/dblp/ethics" class="link-node">dblp-Ethik</a></li></ul></div><div class="col-sm-2"><h5><a href="/de/guests" class="dark link-node"><b style="color: #fff;">Gastinformation</b></a></h5><ul><li><a href="/de/guests" class="link-node">Übersicht</a></li><li><a href="/de/guests/planning-your-visit" class="link-node">Infos zum Aufenthalt</a></li><li><a href="/de/guests/how-to-get-to-schloss-dagstuhl" class="link-node">Anreise</a></li><li><a href="/de/guests/sars-cov2-prevention-measures" class="link-node">Covid-19 Vorbeugung</a></li><li><a href="/de/guests/expenses" class="link-node">Kosten</a></li><li><a href="/de/guests/childcare" class="link-node">Kinderbetreuung</a></li><li><a href="/de/guests/library" class="link-node">Bibliothek</a></li><li><a href="/de/guests/art" class="link-node">Kunst</a></li><li><a href="/de/guests/history" class="link-node">Geschichte</a></li></ul></div><div class="col-sm-2"><h5><a href="/de/contact" class="dark link-node"><b style="color: #fff;">Kontakt</b></a></h5><ul><li><a href="/de/contact" class="link-node">Übersicht</a></li></ul></div></div></div></footer><div class="copyright"><div>© 2025 Schloss Dagstuhl – Leibniz-Zentrum für Informatik GmbH</div><a href="/de/imprint" class="link-node">Impressum</a><a href="/de/contact" class="link-node">Kontakt</a><a href="/de/accessibility" class="link-node">Barrierefreiheit</a><a href="/de/privacy" class="link-node">Datenschutz</a></div><div class="-hidden leibniz-footer-logo"><a href="https://www.leibniz-gemeinschaft.de/"><img src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/images/Leibniz_Logo_DE_negativ_100px.png?bust=328a01b9" alt="Leibniz Logo" /></a></div><span class="__no-index-end"></span><script data-neos-node="/sites/site/node-j2y05jscexfna/node-u0cbnx4m2tdde/node-fp2tlltzpryut@live;language=de" src="https://www.dagstuhl.de/_Resources/Static/Packages/Neos.Neos/JavaScript/LastVisitedNode.js?bust=775acd7b" async></script><script src="https://www.dagstuhl.de/_Resources/Static/Packages/Dagstuhl.Site/Frontend/index.js?bust=259d8ca7?h=259d8ca7"></script></body></html>