DSub

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta name="google" content="notranslate"> <meta http-equiv="Content-Language" content="en"> <meta name="viewport" content="width=device-width, initial-scale=1" /> <meta name="csrf-token" content="XF9E7BNzM1xoWEcB9IsJMM61FcqNnOkPECBRKihW" /> <title>DSub</title> <link rel="icon" href="https://submission.dagstuhl.de/images/favicon.ico" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/fonts.css" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/bootstrap.css" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/app.css?2024-10-31" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/jquery-ui.css" /> <link rel="stylesheet" href="https://submission.dagstuhl.de/css/jquery.qtip.min.css" /> </head> <body> <div id="app" data-release="2024-10-31"> <nav class="navbar navbar-static-top"> <div class="container"> <div class="navbar-header">  <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#app-navbar-collapse" aria-expanded="false"> <span class="sr-only">Toggle Navigation</span> <span class="glyphicon glyphicon-menu-hamburger"></span> </button>  <a class="navbar-brand" href="https://submission.dagstuhl.de" > D<sub>Sub</sub> </a> </div> <div class="collapse navbar-collapse" id="app-navbar-collapse">  <ul class="nav navbar-nav"> </ul>  <ul class="nav navbar-nav navbar-right">  <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"><span class="glyphicon glyphicon-book"></span>  Series <span class="caret"></span></a> <ul class="dropdown-menu"> <li><a href="https://submission.dagstuhl.de/series/details/LIPIcs">LIPIcs | Leibniz International Proceedings in Informatics</a></li> <li><a href="https://submission.dagstuhl.de/series/details/OASIcs">OASIcs | Open Access Series in Informatics</a></li> <li><a href="https://submission.dagstuhl.de/series/details/LITES">LITES | Leibniz Transactions on Embedded Systems</a></li> <li><a href="https://submission.dagstuhl.de/series/details/TGDK">TGDK | Transactions on Graph Data and Knowledge</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DARTS">DARTS | Dagstuhl Artifacts Series</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DagRep">DagRep | Dagstuhl Reports</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DagMan">DagMan | Dagstuhl Manifestos</a></li> <li><a href="https://submission.dagstuhl.de/series/details/DFU">DFU | Dagstuhl Follow-Ups</a></li> </ul> </li> <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"><span class="glyphicon glyphicon-question-sign"></span>  Docs/Services <span class="caret"></span></a> <ul class="dropdown-menu"> <li><a href="https://submission.dagstuhl.de/documentation/authors">Instructions for Authors</a></li> <li><a href="https://submission.dagstuhl.de/documentation/editors">Instructions for Editors</a></li> <li role="separator" class="divider"></li> <li><a href="https://submission.dagstuhl.de/services/acm-subject-classification">ACM 2012 Subject Classification</a></li> <li><a href="https://submission.dagstuhl.de/services/capitalization">Title Capitalization Tool</a></li> <li role="separator" class="divider"></li> <li><a href="https://drops.dagstuhl.de/metadata">Metadata Export</a></li> </ul> </li> <li> <a href="https://www.dagstuhl.de/en/publishing/news" target="_blank"> <span class="glyphicon glyphicon-bullhorn"></span>  News </a> </li> <li> <a href="https://submission.dagstuhl.de/login"> <span class="glyphicon glyphicon-log-in"></span>  Login </a> </li> <li> <a href="https://submission.dagstuhl.de/register"> <span class="glyphicon glyphicon-link"></span> Register </a> </li> </ul> </div> </div> </nav> <ol class="breadcrumb"> <li><a href="/home">Home</a></li> <li>Series</li> <li>Dagstuhl Reports</li> </ol> <h1> Dagstuhl Reports (DagRep) <img class="publishing-logo" src="/images/04dagstuhl-reports.png" height="24px" alt="Dagstuhl Publishing" style="max-height: 3rem;" /> </h1> <div class="subtitle"> <br/> </div> <div class="documentation"> <main class="col-12 col-md-12 py-md-3 pl-md-5 bd-content" role="main"> <div class="centered-content"> <ul class="nav nav-tabs" id="documentation" role="tablist"> <li class="nav-item active" role="presentation"> <a class="nav-link active" id="general-tab" data-toggle="tab" href="#general" role="tab" aria-controls="general" aria-selected="true"> General </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="editorialboard-tab" data-toggle="tab" href="#editorialboard" role="tab" aria-controls="editorialboard" aria-selected="false"> Editorial Board </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="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="faq-tab" data-toggle="tab" href="#faq" role="tab" aria-controls="faq" aria-selected="false"> FAQ </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="recently-tab" data-toggle="tab" href="#recently" role="tab" aria-controls="recently" aria-selected="false"> Recently published </a> </li> <li class="nav-item" role="presentation"> <a class="nav-link" id="contact-tab" data-toggle="tab" href="#contact" role="tab" aria-controls="contact" aria-selected="false"> Contact </a> </li> </ul> <div class="tab-content" id="tab-contents"> <br /> <div class="tab-pane fade in active" id="general" role="tabpanel" aria-labelledby="general-tab"> <div class="row"> <div class="col-sm-2"> </div> <div class="col-sm-10"> <p>Since 2011, the periodical <em>Dagstuhl Reports</em> serves as publication medium to document Dagstuhl Seminars and Dagstuhl Perspectives Workshops in a journal-like manner to allow for a high visibility and timely communication of the seminars' outcome. <p>The periodical <em>Dagstuhl Reports</em> is published in one volume with 12 issues per year. Each issue documents the Dagstuhl Seminars and Dagstuhl Perspectives Workshops of one month.</p> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>Publications</h5> </div> <div class="col-sm-10"> All documents published in this journal are available open access on <a href="https://drops.dagstuhl.de">DROPS</a>: <a href="https://drops.dagstuhl.de/entities/journal/DagRep" style="margin-left: 10px;"> <span class="btn btn-sm" style="text-align: center"> <span style="line-height: 2em">Browse DagRep on DROPS</span><br> <img class="publishing-logo" src="/images/04dagstuhl-reports.png" height="24px" alt="DagRep Logo" style="max-height: 3rem;" />   </span> </a> <br><br> Moreover, all papers are indexed in dblp: <a href="https://dblp.org/db/journals/dagstuhl-reports">DagRep @ dblp</a> </div> </div> <hr> <div class="row"> <div class="col-sm-2"> <h5>Aims and Scope</h5> </div> <div class="col-sm-10"> <p>The periodical <em>Dagstuhl Reports</em> documents the program and the results of Dagstuhl Seminars and Dagstuhl Perspectives Workshops.</p> <p>In principle, for each Dagstuhl Seminar or Dagstuhl Perspectives Workshop a report is published that contains the following:</p> <ul> <li>an executive summary of the seminar program and the fundamental results,</li> <li>an overview of the talks given during the seminar (summarized as talk abstracts), and</li> <li>summaries from working groups (if applicable).</li> </ul> <p>This basic framework can be extended by suitable contributions that are related to the program of the seminar, e.g. summaries from panel discussions or open problem sessions.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Open Access Policy</h5> </div> <div class="col-sm-10"> The periodical Dagstuhl Reports is published as an open access journal, i.e., the content is accessible 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"> Dagstuhl Reports are 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"> For the series Dagstuhl Reports, no fee is charged. </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>ISSN</h5> </div> <div class="col-sm-10"> <span>2192-5283</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"> The digital archiving of each issue is done in cooperation with the Deutsche Nationalbibliothek/German National Library (<a href="http://www.dnb.de/" title="Link zu http://www.dnb.de/" target="_blank">http://www.dnb.de</a>). </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Publication Ethics</h5> </div> <div class="col-sm-10"> Dagstuhl Publishing as a division of Schloss Dagstuhl – Leibniz-Zentrum für Informatik GmbH (LZI, or Schloss Dagstuhl for short) and its series and journals adhere to <a target="_blank" href="https://publicationethics.org/core-practices">CORE practices guidance</a> laid by <a target="_blank" href="https://publicationethics.org/">COPE (Committee on Publication Ethics)</a> and are committed to the rules of good scientific practice in accordance with the <a target="_blank" href="https://www.leibniz-gemeinschaft.de/en/about-us/leibniz-integrity/good-scientific-practice-and-ombuds-services">guidelines of the Leibniz Association</a> and the <a target="_blank" href="https://wissenschaftliche-integritaet.de/en/">German Research Foundation (DFG)</a>. We expect all parties (so authors, editors, and reviewers) involved in the publication and review process of contributions to be published in the series to follow these core practises and the guidelines. Allegations of misconduct will be investigated in accordance with the COPE Best Practice Guidelines as far as is practicable. If notified of a potential breach of publication ethics, we encourage editors and authors to inform Dagstuhl Publishing contact as soon as possible. Detailed information can be found on the <a target="_blank" href="https://www.dagstuhl.de/en/publishing/ethics">Publication Ethics website</a>. </div> </div> </div> <div class="tab-pane fade" id="editorialboard" role="tabpanel" aria-labelledby="editorialboard-tab"> <div class="row"> <div class="col-sm-2"> <h5>Editorial Board</h5> </div> <div class="col-sm-10"> <ul> <li> Elisabeth André <a href="https://www.uni-augsburg.de/de/fakultaet/fai/informatik/prof/hcm/team/andre/">Universität Augsburg, DE</a> </li> <li> Franz Baader <a href="http://lat.inf.tu-dresden.de/~baader/">TU Dresden, DE</a> </li> <li> Goetz Graefe Google - Madison, US </li> <li> Reiner Hähnle <a href="http://www.informatik.tu-darmstadt.de/se/gruppenmitglieder/groupmembers_detailseite_30784.de.jsp">TU Darmstadt, DE</a> </li> <li> Barbara Hammer <a href="http://www.techfak.uni-bielefeld.de/~bhammer/">Universität Bielefeld, DE</a> </li> <li> Lynda Hardman <a href="http://www.cwi.nl/~lynda/">CWI - Amsterdam, NL</a> and <a href="https://www.uu.nl/staff/LHardman">University of Utrecht, NL</a> </li> <li> Holger Hermanns <a href="http://depend.cs.uni-saarland.de/hermanns">Universität des Saarlandes - Saarbrücken, DE</a> </li> <li> Steve Kremer <a href="http://www.loria.fr/~skremer/">INRIA Nancy - Grand Est, FR</a> </li> <li> Rupak Majumdar <a href="http://www.mpi-sws.org/~rupak">Max-Planck-Institut für Softwaresysteme – Kaiserslautern, DE</a> </li> <li> Heiko Mantel <a href="http://www.mais.informatik.tu-darmstadt.de/Heiko_Mantel.html">TU Darmstadt, DE</a> </li> <li> Lennart Martens <a href="https://ai.ugent.be/people/LennartMartens.en.html">Ghent University, BE</a> </li> <li> Albrecht Schmidt <a href="http://www.um.informatik.uni-muenchen.de/personen/professoren/schmidt/index.html">LMU München, DE</a> </li> <li> Wolfgang Schröder-Preikschat <a href="http://www4.cs.fau.de/~wosch/">Universität Erlangen-Nürnberg, DE</a> </li> <li> Raimund Seidel <a href="http://www-tcs.cs.uni-saarland.de/">Universität des Saarlandes - Saarbrücken, DE</a> - <span>Scientific Director</span> </li> <li> Heike Wehrheim <a href="https://uol.de/informatik/formale-methoden/team/heike-wehrheim">Universität Oldenburg, DE</a> </li> <li> Verena Wolf <a href="http://mosi.cs.uni-saarland.de/?page_id=53">Universität des Saarlandes - Saarbrücken, DE</a> </li> <li> Martina Zitterbart <a href="http://telematics.tm.kit.edu/staff_zitterbart.php">KIT - Karlsruher Institut für Technologie, DE</a> </li> </ul> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Constitution</h5> </div> <div class="col-sm-10"> <p>The <a href="https://www.dagstuhl.de/en/about-dagstuhl/bodies-and-boards/scientific-directorate/">Scientific Directorate of Schloss Dagstuhl</a> acts as editorial board. The task of the Scientific Directorate is to implement the Center's designated purpose in a scientific and subject-matter capacity. It convenes twice a year to establish the research and event program, ensure the quality of the Center's offerings, and monitor how the program is put into practice.</p> <p>Members of the Scientific Directorate are the Scientific Director and as many scientific experts as necessary and appropriate for the competent evaluation of important computer science fields.</p> <p>Members of the Scientific Directorate are appointed by the Supervisory Board following a joint proposal by the Scientific Director and the Scientific Advisory Board. Proposals are collated by the Scientific Director in collaboration with the Scientific Advisory Board based on proposals from the shareholders, the Scientific Directorate, and the Scientific Advisory Board.</p> </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>Info for Authors</h5> </div> <div class="col-sm-10"> <p>As part of our quality assurance towards our funding partners, Schloss Dagstuhl likes to keep records of all Dagstuhl Seminars and Dagstuhl Perspectives Workshops. Furthermore, such a documentation provides a reference for the seminar participants as well as for researchers who were unable to attend.</p> <p>We hereby ask you to prepare a documentation entry with regard to your talk (in case you have given one during the seminar). Additionally, results from working groups should also be documented. For given talks, the documentation mainly consists of a brief abstract along with a list of co-authors and a bibliograpic reference (if available).</p> <p>Your documentation entry will be published as part of the seminar's issue in the periodical series <em>Dagstuhl Reports</em>.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>General procedure</h5> </div> <div class="col-sm-10"> <p>Each seminar designates a collector (see #editor) who is in charge of supporting the seminar organizers to prepare the report for the seminar.</p> <p>Maybe already during, but at the latest shortly after the seminar, the collector will send a <em>Call-for-Abstracts</em> to the seminar participants asking them to submit an abstract of their talk. If the seminar has organized working groups, some participants may also be in charge of submitting a report with regard to the disucssions and results of the working group.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Deadline</h5> </div> <div class="col-sm-10"> <p>The collector will announce a deadline in the <em>Call-for-Abstracts</em> by which your abstract should be submitted. This deadline is strict and there will be no extensions.</p> <p>Typically, the deadline is about two months after the seminar.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Upload of your documentation entry</h5> </div> <div class="col-sm-10"> <p>To submit your documentation entry, please visit<blockquote><em>http://drs.dagstuhl.de/<sem-nr></em></blockquote> whereby <em><sem-nr></em> is the five-digit number of your seminar, e.g. 10501. To access the Dagstuhl Reports submission interface, you need the door key which was communicated with the travel informations as well as with the collector's call-for-abstracts.</p> <p>The submission works as follows: <ol> <li>Select <em>"Add abstract"</em> (or click the edit button for an already existing entry).</li> <li>Fill out the form by providing title, authors, abstract, and - if applicable - a bibliographic reference together with its digital location.</li> <li>IMPORTANT: To approve your entry for publication, please select <em>"Complete abstract"</em> in the <em>"Completed"</em> section of the abstract editor. No more changes can be made after saving a completed entry. You may modify or amend your entry as long as it is not marked as completed.</li> <li>Select <em>"Save abstract"</em> to save your data (or select <em>"Cancel"</em> if you wish to abort the submission).</li> <li>Select either <em>"save all"</em> or <em>"cancel"</em> brings you back to the list of your documentation entries.</li> </ol> Please note that you have to complete your submission before the deadline announced by the collector.</p> <p>By submitting your documentation entry timely, you support the seminar organizers to comply with the funding guidelines of Schloss Dagstuhl. This is highly appreciated.</p> <p>In case of questions, please contact the seminar's collector or the <a href="mailto:reports@dagstuhl.de">editorial office</a> at Schloss Dagstuhl.</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>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> Info for Organizers</h5> </div> <div class="col-sm-10"> <p>The funding scheme of Dagstuhl Seminars and Dagstuhl Perspectives Workshops requires quality assurance and documentation. We rely on your input and support for assuring our obligations. Hence, we appreciate your efforts for preparing a comprehensive report of your seminar that fulfills not only the task of documentation, but may also serve as a reference in the future or for researchers who couldn't attend the seminar.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Content</h5> </div> <div class="col-sm-10"> <p>The content of the report should include:</p> <ul> <li>an executive summary of the seminar program and the fundamental results,</li> <li>an overview of the talks given during the seminar (summarized as talk abstracts), and</li> <li>summaries from working groups (if applicable).</li> </ul> <p>This basic framework can be extended by suitable contributions that are related to the program of the seminar, e.g. summaries from panel discussions or open problem sessions.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Organization</h5> </div> <div class="col-sm-10"> <p>The organizers are asked to designate a <em>collector</em> (see paragraph below), typically a junior researcher, who coordinates the preparation of the report in close cooperation with the organizers and the editorial office at Schloss Dagstuhl. The collector should have basic knowledge of LaTeX due to being in charge of typesetting issues.</p> <p>The collector collects the abstracts of the talks given during the seminar (by sending out an appropriate <em>Call-for-Abstracts</em>) as well the results from working groups. Finally, the executive summary, written by the seminar organizers, and additional summaries (from panel discussions or open problem sessions) must be integrated into the report.</p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Collector</h5> </div> <div class="col-sm-10"> <p>The collector acts as editorial coordinator supporting the seminar organizers in preparing the report for the Dagstuhl Seminar or Dagstuhl Perspectives Workshop in close cooperation with the editorial office at Schloss Dagstuhl.</p> <p>During the seminar, the collector should observe the seminar program, especially with respect to given talks and working groups. Furthermore, records should be kept on open problem sessions or panel discussions.</p> <p>After the seminar, the collector is in charge of sending out a <em>Call for Abstracts</em> to the seminar participants. Technical interfaces are provided by Schloss Dagstuhl and corresponding URLs are communicated in due time to the collector. Via the technical webinterface, participants are able to upload the abstract of their talk along with comprehensive metadata. The collector can make use of our semi-automated scripts that provide a single LaTeX-file capturing all submitted abstracts.</p> <p>The seminar report is typeset using LaTeX, hence the collector should have basic knowledge with LaTeX. The collector has to prepare the LaTeX document containing the executive summary (written by the seminar organizers), the abstracts submitted by the seminar participants, and--if applicable--reports from working groups, panel discussions, or open problem sessions.</p> <p>If contentwise the report is final (which should be approved by the seminar organizers), the collector sends the LaTeX sources to the editorial office at Schloss Dagstuhl (<a href="mailto:reports@dagstuhl.de">reports@dagstuhl.de</a>).</p> <p>The report is the finalized by Dagstuhl's editorial office (adaption of page numbers and further bibliographic issues, minor corrections, ...). Before official publication, the report is sent to the seminar organizers and the collector for approval.</p> <p>The collector receives a fair compensation for her/his efforts after the report is published. Details are available on <a href="mailto:reports@dagstuhl.de">request</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 DagRep style along with an example file:</p> <div class="alert alert-info alert-inline"> <div class="latex-style"> <b>dagrep-v2021</b> <span class="label label-success "> v2021.1.3 </span> <aside style="display: inline-block; margin-left: 10px;"> <div class="btn-group"> <button type="button" class="btn btn-xs btn-default dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Download <span class="caret"></span> </button> <ul class="dropdown-menu"> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/dagrep/v2021.1.3/authors/zip"> as zip-file </a> </li> <li> <a class="dropdown-item" href="https://submission.dagstuhl.de/styles/download-tag/dagrep/v2021.1.3/authors/tgz"> as tar.gz-file </a> </li> </ul> </div> </aside> </div> </div> <p> For <a href="https://github.com/dagstuhl-publishing/styles/releases">older releases</a> and an <a href="https://github.com/dagstuhl-publishing/styles/issues">issue tracker</a>, see our <a href="https://github.com/dagstuhl-publishing/styles">GitHub archive</a>. </p> </div> </div> <hr /> <div class="row"> <div class="col-sm-2"> <h5>Editorship / Authorship</h5> </div> <div class="col-sm-10"> <p>The organizers of the Dagstuhl Seminar or Dagstuhl Perspectives Workshop are going to act as editors of the seminar report. The authorship of the talk abstracts is mentioned adequately within the report.</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>General</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-36-General-editor"> <a class="collapsed" href="#FAQ-36-General-editor" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-36-General-editor" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">collector</span><span class="question">Can the <b> collector</b> also be listed as an editor of the Dagstuhl Report?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-36-General-editor" role="tabpanel" aria-labelledby="FAQ-36-General-editor"> <div class="panel-body"> <p>The list of editors is restricted to the organisers of the seminar. The collector is mentioned as editorial assistant directly on the front page of the report (i.e., "Edited in cooperation with ..."). Furthermore, the collector receives a fair compensation for his efforts after the report is published.</p> <p>Dagstuhl Publishing and the scientific director of Schloss Dagstuhl decided several years ago to unify the format of the seminar documentation and to publish these documentations as so called Dagstuhl Reports. It was decided that only the official organizers of the seminar are listed as editors of the respective report. </p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/36"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/36</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="faq" role="tabpanel" aria-labelledby="faq-tab"> <div class="row"> <div class="col-sm-2"> <h5>FAQ</h5> </div> </div> <div class="row"> <div class="col-sm-2"> <h5>General</h5> </div> <div class="col-sm-10"> <div class="panel-group" id="faq-accordion" role="tablist" aria-multiselectable="true"> <div class="panel panel-default faq-list-item"> <div class="panel-heading" role="tab" id="heading-37-General-"> <a class="collapsed" href="#FAQ-37-General-" data-toggle="collapse" aria-expanded="false" aria-controls="FAQ-37-General-" data-parent="#faq-accordion" class="_faq"><span><span class="label label-info">Report and Manifesto</span><span class="question">Do perspectives workshops need to provide both a manifesto and a report?</span></span> </span></a> </div> <div class="panel-collapse collapse" id="FAQ-37-General-" role="tabpanel" aria-labelledby="FAQ-37-General-"> <div class="panel-body"> <p>Yes, we expect our Perspective Workshops to prepare a Dagstuhl Report <b>and</b> a Dagstuhl Manifesto.</p> <p>The <i>Dagstuhl Reports</i> series aims at documenting a seminar/workshop; the report is not reviewed. See <a href="http://www.dagstuhl.de/dagrep">http://www.dagstuhl.de/dagrep</a>.<br /> (We expect the submission of the report 3 months after the workshop/seminar.)</p> <p>A <i>Dagstuhl Manifesto</i> aims at describing the state of the art of the field and proposing visions and perspectives. The manifesto is reviewed by the scientific directorate of Dagstuhl. The manifesto targets both the scientific community and "political" stakeholders (such as funding agencies, EU departments, ...). See <a href="http://www.dagstuhl.de/dagman">http://www.dagstuhl.de/dagman</a>.<br /> (We expect the submission of the manifesto ~6 months after the seminar.)</p> </div> <div class="panel-footer"> <small><a href="https://submission.dagstuhl.de/documentation/faq/37"><span class="glyphicon glyphicon-new-window"></span> https://submission.dagstuhl.de/documentation/faq/37</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"> DagRep, Vol. 14, Issue 4, <b>DagRep, Volume 14, Issue 4</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-14-issue-4"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 14, Issue 3, <b>DagRep, Volume 14, Issue 3</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-14-issue-3"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 14, Issue 2, <b>DagRep, Volume 14, Issue 2</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-14-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 14, Issue 1, <b>DagRep, Volume 14, Issue 1</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-14-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 12, <b>DagRep, Volume 13, Issue 12</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-12"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 11, <b>DagRep, Volume 13, Issue 11</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-11"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 10, <b>DagRep, Volume 13, Issue 10</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-10"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 9, <b>DagRep, Volume 13, Issue 9</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-9"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 8, <b>DagRep, Volume 13, Issue 8</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-8"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 7, <b>DagRep, Volume 13, Issue 7</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-7"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 6, <b>DagRep, Volume 13, Issue 6</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-6"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 5, <b>DagRep, Volume 13, Issue 5</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-5"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 4, <b>DagRep, Volume 13, Issue 4</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-4"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 3, <b>DagRep, Volume 13, Issue 3</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-3"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 2, <b>DagRep, Volume 13, Issue 2</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-2"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 13, Issue 1, <b>DagRep, Volume 13, Issue 1</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-13-issue-1"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 12, Issue 12, <b>DagRep, Volume 12, Issue 12</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-12-issue-12"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 12, Issue 11, <b>DagRep, Volume 12, Issue 11</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-12-issue-11"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 12, Issue 10, <b>DagRep, Volume 12, Issue 10</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-12-issue-10"><button type="button" class="btn btn-default btn-xs">To the portal ...</button></a></div> <br /> </li> <li class="list-group-item"> DagRep, Vol. 12, Issue 9, <b>DagRep, Volume 12, Issue 9</b> <div class="pull-right"><a href="https://drops.dagstuhl.de/entities/issue/DagRep-volume-12-issue-9"><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> <hr/> </div> </main> </div> </div> <div class="footer"> <a href="https://www.dagstuhl.de/en/publications/"> <img class="publishing-logo" src="/images/dagpub-wortmarke-grey-160x34.png" height="24px" alt="Dagstuhl Publishing"/> </a> <div> <span class="copyright">© 2019-2024 <a href="https://www.dagstuhl.de">Schloss Dagstuhl - LZI GmbH</a></span> <div> <span class="imprint"><a href="https://submission.dagstuhl.de/imprint" >Imprint</a></span> <span class="privacy"><a href="https://submission.dagstuhl.de/privacy" >Privacy</a></span> </div> </div> </div> <div class="loader-overlay -hidden"> <div class="centered-loader"> <div class="loader"></div> </div> </div> <script src="https://submission.dagstuhl.de/js/app.js?2024-10-31"></script> <script type="text/javascript"> $(document).ready(function() { const innerAnchors = [ 'resource-articles', 'cfp-si-resources', 'cfp-si-autonomous-systems-and-knowledge-graphs' ]; let anchors = []; $('a[role="tab"]').each(function() { anchors.push($(this).attr('aria-controls')); }); innerAnchors.forEach(function(anchor) { if ($('#'+anchor).length > 0) { anchors.push(anchor); } }); let selectedAnchor = window.location.hash.substring(1); if (anchors.indexOf(selectedAnchor) === -1) { selectedAnchor = 'general' } const innerAnchorIndex = innerAnchors.indexOf(selectedAnchor); // anchor sits inside tab -> open the tab first, then scroll to anchor if (innerAnchorIndex > -1) { const $tab = $('#'+selectedAnchor).closest('.tab-pane'); $('a.nav-link[aria-controls="'+$tab.attr('id')+'"]').click(); setTimeout(function() { $('#'+selectedAnchor)[0].scrollIntoView(); window.scrollBy(0, -100); }, 400); } // anchor references tab else { $('a.nav-link[aria-controls="'+selectedAnchor+'"]').click(); $(window).scrollTop(0); } $('a.nav-link').on('click', function() { $('#faq').find('[aria-describedby]').click(); }); }); </script> <script type="text/javascript"> $(document).ready(function() { $('[data-scroll-link]').on('click', function(e) { e.preventDefault(); const $target = $(e.currentTarget); const href = $target.attr('href'); console.log(href); $(href)[0].scrollIntoView(); window.scrollBy(0,-200); }); $('[data-tab-link]').on('click', function(e) { const $target = $(e.currentTarget); let href = $target.attr('href'); let scrollLink = null; if (href === '#cfp-si-list') { scrollLink = href; href = '#cfp'; } $(href+'-tab').click(); if (scrollLink !== null) { setTimeout(function() { $(scrollLink)[0].scrollIntoView(); window.scrollBy(0,-200); }, 200); } else { window.scrollTo(0,0); } }); }); </script> <script type="text/javascript"> $('document').ready(function() { var _faq = { initSingleFaq: function($this) { var id = $this.attr('data-faq-id'); if (id === undefined) { id = $this.attr('id').replace('_multi-faq-', ''); } $this.popover({ html: true, trigger: 'focus', placement: 'auto', container: 'body', title: function() { return $('[data-faq-stack-id="'+id+'"]').first().find('._title').html(); }, content: function() { return $('[data-faq-stack-id="'+id+'"]').first().find('._content').html(); } }); }, initialize: function() { // initialize single faqs $('[data-faq-id]').each(function() { _faq.initSingleFaq($(this)); }).on('click', function(e) { e.preventDefault(); // close multi faqs when clicking a single one // $('._multi-faq-close').click(); }); /* // initialize multiple faqs $('[data-multi-faq-id]').each(function() { var $this = $(this); var id = $this.attr('data-multi-faq-id'); var $stack = $('[data-multi-faq-stack-id="'+id+'"]').first(); $this.popover({ html: true, trigger: 'manual', placement: 'auto', container: 'body', title: function() { return $stack.find('._title').html(); }, content: function() { return $stack.find('._content').html(); } }); }).on('click', function(e) { e.stopPropagation(); $(e.currentTarget).popover('toggle'); $('.popover').find('a').on('click', function (e) { e.stopPropagation(); }); $('[id^=_multi-faq]').each(function () { _faq.initSingleFaq($(this)); }); $('._faq-close').off().on('click', function (e) { var id = $(e.currentTarget).parent().parent().attr('id'); $('[aria-describedby="' + id + '"]').popover('hide'); }); }); // finally close multiple $('body').on('click', function(e) { $('[data-multi-faq-id]').popover('hide'); }).on('mousedown', '.popover', function(e) { var id = $(e.currentTarget).attr('id'); var $anchor = $('[aria-describedby="' + id + '"]'); if (!$anchor.is('[data-multi-faq-id]')) { e.preventDefault(); return true; } }); */ } }; _faq.initialize(); window._faq = _faq; }); </script> </body> </html>

CINXE.COM

DSub