============================================================ The 34th Edition of ECOOP Call for Papers 13th-17th July 2020 Berlin, Germany https://2020.ecoop.org/ ============================================================ ECOOP is a conference about programming. Originally its primary focus was on object orientation, but now it looks at a much broader range of programming topics. Areas of interest include, at least, the design, implementation, optimization, analysis, and theory of programs, programming languages, and programming environments. It solicits both innovative and creative solutions to real problems as well as evaluations of existing solutions—evaluations that provide new insights. It also encourages the submission of reproduction studies. ECOOP 2020 solicits high-quality submissions describing original, unpublished results. The program committee will evaluate the technical contribution of each submission as well as its general relevance and accessibility to the ECOOP audience according to the following criteria: - Originality. Papers must present new ideas and place them appropriately within the context established by previous research in the field. - Significance. The results in the paper must have the potential to add significantly to the state of the art or practice. - Evidence. The paper must present evidence supporting its claims. Examples of evidence include implemented systems, experimental results, statistical analyses, case studies, formalizations, and proofs. - Clarity. The paper must present its contributions and results clearly. On submission, authors will be asked to identify their paper with one of the following categories: - Research Paper. This is the most traditional category and solicits high quality research papers that demonstrate advances in the field. (As an alternative to being published in the conference proceedings, authors may wish to submit research papers to be considered for publication in ACM TOPLAS or Science of Computer Programming.) - Tool Insights Paper. These submissions focus on the practical details of the design and implementation of PL tools—details that are often omitted from regular research papers, despite being fascinating and worthy of communication. A strong Tool Insights Paper should communicate engineering experience and insights that are likely to be useful to other members of the PL community, who may face similar problems in future. Examples of issues that Tool Insights Papers might focus on include, but are not limited to: performance, reliability, portability, inter-tool integration, infrastructure re-use, evaluation issues, theory/practice gaps, precision/efficiency, and soundness/efficiency trade-offs. - Reproduction Study. A Reproduction Study is an empirical evaluation. It reconstructs an already published experiment but in a different context (for example, using a different virtual machine or platform, or in a different class of applications) in order to validate or refute important results of earlier work. A good Reproduction Study includes thorough empirical evaluation as well as a detailed comparison with the previous results, providing reasons for possible disagreements. (A thoroughly-conducted Reproduction Study that perfectly replicates an existing experiment and reaches the same conclusions will be regarded as significant, so long as said experiment is significant enough to be worthy of reproduction.) - Experience Report. Such reports focus on noteworthy applications of known PL techniques, tools, and ideas in interesting domains and by other communities. Examples include, but are not limited to, applications of PL techniques in industry, open source, education, and other academic disciplines. We welcome reports on successful applications of PL ideas and reports that shed light on limitations and problems that may provide inspiration for future research. - Pearl. This category solicits articles that explain a known idea in a new and elegant way, to the benefit of the PL community. A Pearl may well be shorter than a regular research paper, but there is no hard requirement on this. - Brave New Idea. The Brave New Idea category solicits forward-looking articles on ideas in the field of PL that may take some time to substantiate, but for which early communication to the community is likely to be of benefit. For this category we welcome papers that are particularly conceptually novel or unconventional and that as a result may be harder to back up by traditional evaluation methods. A Brave New Idea paper may well be shorter than a regular research paper, but there is no requirement for it to be so. Paper Submission ================ Only papers that have not been published and are not under review for publication elsewhere may be submitted. Double submissions will be rejected without review. If major parts of an ECOOP submission have appeared elsewhere in any form, authors are required to notify the ECOOP program chair and explain the overlap and relationship. Authors are also required to inform the program chair about closely related work submitted to another conference while the ECOOP submission is under review. Papers must be no longer than 25 pages, excluding references. See below for information about appendices. Authors will not be penalized for papers that are shorter than the page limit. Submissions will be carried out electronically via the conference website [1]. ECOOP Proceedings are published by Dagstuhl LIPIcs. Papers must be written in English and follow the Dagstuhl LIPIcs LaTeX-style template [2]. Authors retain ownership of their content. Note: Submitted papers do not need to include the ACM classification or keywords. Also, please DO NOT put your name in either the \author or \Copyright macro, in order to maintain anonymity for double-blind reviewing (see below). Anonymity ========= ECOOP will use light double-blind reviewing: authors’ identities are withheld until a reviewer submits his or her review (as usual, reviews are anonymous). To facilitate this, submitted papers must adhere to two rules: - Author names and institutions must be omitted. - References to authors’ own other work should be in the third person (for example, not “We build on our previous work…” but rather “We build on the work of…”). When in doubt, contact the Program Chair. Additional Material =================== Clearly marked additional appendices containing analyses, statistics, supporting proofs, etc. of possible value to reviewers but not published in the final publication, may be included beyond the page limit. The submission system provides an option to submit supplementary material; for example, a technical report including proofs, or web pages and repositories that cannot easily be anonymized. This supplementary material will be made available to reviewers after the initial reviews have been completed, when author names are revealed. Reviewers are under no obligation to examine such appendices and supplementary material. Therefore, the paper must be a stand-alone document - the appendices and supplementary material are a way of providing useful information that cannot fit in the page limit; they are not a means to extend the page limit. Authors of papers that have been submitted but not accepted by previous conferences may optionally submit a Note to Reviewers. The Note to Reviewers should provide the following information: - the identity of the previous venue(s) (for example, ESOP 2020, ‹Programming› 2020, POPL 2020, OOPSLA 2019) - a list the major issues identified by the reviews at those venues - a description of the changes made to the paper in response to those reviews These notes will be made available to reviewers after their initial reviews have been completed and author names have been revealed. Response Period =============== Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no formal length limit, but concision is likely to be effective. Artifact Evaluation =================== To reward the creation of artifacts and support replication of experiments, authors of accepted research papers may submit artifacts (such as tools, data, models, or videos) to be evaluated by an Artifact Evaluation Committee. Artifacts that pass muster will be recognized officially. Important Dates =============== - Paper submission: 10 January 2020 (Fri) - Author response: 16–18 March 2020 (Mon-Wed) - Author notification: 8 April 2020 (Wed) Journal First ============= We have Journal First arrangements with ACM Transactions on Programming Languages and Systems and Elsevier Science of Computer Programming. Common to both routes --------------------- Only new research papers are eligible for the Journal First routes to ECOOP 2020. That is, it is not acceptable to submit an extension of a previous conference paper, even if the associated journal solicits extended papers via its standard submission route. Authors of all accepted Journal First papers will be invited to submit a short abstract for their paper to appear in the ECOOP 2020 conference proceedings. Journal First papers will be included along with research papers submitted directly to the conference when a Distinguished Paper is selected. Science of Computer Programming route ------------------------------------- See this dedicated web page [3] for full details of how to submit to the ECOOP 2020 Science of Computer Programming (SCP) special issue. Submission deadline: December 2, 2019 (Mon) ACM Transactions on Programming Languages and Systems route ----------------------------------------------------------- See this announcement [4] for details of the TOPLAS scheme whereby papers submitted to TOPLAS can be presented at selected conferences. Authors interested in this route should submit their paper to TOPLAS via its usual submission system and mark it as an ECOOP 2020 submission. The ECOOP Program Chair will then be informed of this submission and will have some input into the review process. Submission deadline: October 10, 2019 (Thu) More Information ================ For additional information, please contact the ECOOP Program Chair, Robert Hirschfeld [5]. [1] https://2020.ecoop.org/track/ecoop-2020-papers [2] https://www.dagstuhl.de/en/publications/lipics/instructions-for-authors/ [3] https://www.journals.elsevier.com/science-of-computer-programming/call-for-p... [4] https://toplas.acm.org/announcements.cfm#submit-a-paper-for-pldi-2016 [5] https://www.hpi.uni-potsdam.de/hirschfeld/people/hirschfeld/