caml-list - the Caml user's mailing list
 help / Atom feed
From: Keisuke Nakano <ksk@riec.tohoku.ac.jp>
Cc: Keisuke Nakano <ksk@riec.tohoku.ac.jp>
Subject: [Caml-list] FLOPS 2020: DEADLINE EXTENSION (abstract 22 Nov, full paper 29 Nov)
Date: Fri, 15 Nov 2019 19:37:15 +0900
Message-ID: <7033425A-9DF6-4FF3-86B8-890BED387560@riec.tohoku.ac.jp> (raw)

FINAL Call For Papers (*** DEADLINE EXTENSION ***)

FLOPS 2020: 15th International Symposium on Functional and Logic Programming

In-Cooperation with ACM SIGPLAN
===============================

23-25 April, 2020, Akita, Japan

https://www.ipl.riec.tohoku.ac.jp/FLOPS2020/

Writing down detailed computational steps is not the only way of
programming. An alternative, being used increasingly in practice, is
to start by writing down the desired properties of the result. The
computational steps are then (semi-)automatically derived from these
higher-level specifications. Examples of this declarative style of
programming include functional and logic programming, program
transformation and rewriting, and extracting programs from proofs of
their correctness.

FLOPS aims to bring together practitioners, researchers and
implementors of the declarative programming paradigm, to discuss
mutually interesting results and common problems: theoretical
advances, their implementations in language systems and tools, and
applications of these systems in practice. The scope includes all
aspects of the design, semantics, theory, applications,
implementations, and teaching of declarative programming.  FLOPS
specifically aims to promote cross-fertilization between theory and
practice and among different styles of declarative programming.


*** Scope ***

FLOPS solicits original papers in all areas of the declarative
programming:

* functional, logic, functional-logic programming, rewriting systems,
  formal methods and model checking, program transformations and
  program refinements, developing programs with the help of theorem
  provers or SAT/SMT solvers, verifying properties of programs using
  declarative programming techniques;

* foundations, language design, implementation issues (compilation
  techniques, memory management, run-time systems, etc.), applications
  and case studies.

FLOPS promotes cross-fertilization among different styles of
declarative programming. Therefore, research papers must be written to
be understandable by the wide audience of declarative programmers and
researchers. In particular, each submission should explain its
contributions in both general and technical terms, clearly identifying
what has been accomplished, explaining why it is significant for its
area, and comparing it with previous work.  Submission of system
descriptions and declarative pearls are especially encouraged.

*** Submission ***

Submissions should fall into one of the following categories:

* Regular research papers: they should describe new results and will
  be judged on originality, correctness, and significance.

* System descriptions: they should describe a working system and will
  be judged on originality, usefulness, and design.

* Declarative pearls: new and excellent declarative programs or
  theories with illustrative applications.

System descriptions and declarative pearls must be explicitly marked
as such in the title.

Submissions must be unpublished and not submitted for publication
elsewhere. Work that already appeared in unpublished or informally
published workshops proceedings may be submitted. See also ACM SIGPLAN
Republication Policy, as explained on the web at
http://www.sigplan.org/Resources/Policies/Republication.

Submissions must be written in English and can be up to 15 pages
excluding references, though system descriptions and pearls are
typically shorter. The formatting has to conform to Springer's
guidelines. Regular research papers should be supported by proofs
and/or experimental results. In case of lack of space, this supporting
information should be made accessible otherwise (e.g., a link to
an anonymized Web page or an appendix, which does not count towards
the page limit). However, it is the responsibility of the authors to
guarantee that their paper can be understood and appreciated without
referring to this supporting information; reviewers may simply choose
not to look at it when writing their review.

FLOPS 2020 will employ a double-blind reviewing process.
To facilitate this, submitted papers must adhere to two rules:

 1. author names and institutions must be omitted, and
 
 2. references to authors' own related work should be in the third
    person (e.g., not "We build on our previous work..." but rather
    "We build on the work of...").

The purpose of this process is to help the reviewers come to a
judgement about the paper without bias, not to make it impossible
for them to discover the authors if they were to try.
Nothing should be done in the name of anonymity that weakens the
submission or makes the job of reviewing the paper more difficult
(e.g., important background references should not be omitted or
anonymized). In addition, authors should feel free to disseminate
their ideas or draft versions of their paper as they normally
would. For instance, authors may post drafts of their papers on the
web or give talks on their research ideas.

Papers should be submitted electronically at
https://easychair.org/conferences/?conf=flops2020

Springer Guidelines
https://www.springer.com/gp/computer-science/lncs/conference-proceedings-guidelines


*** Proceedings ***

The proceedings will be published by Springer International Publishing
in the Lecture Notes in Computer Science (LNCS) series 
(www.springer.com/lncs).


*** Important Dates ***

[Extended] 22 November 2019 (AoE): Abstract submission
[Extended] 29 November 2019 (AoE): Submission deadline
[Extended] 31 January 2020: Author notification
[Extended] 20 February 2020: Camera ready due
23-25 April 2020: FLOPS Symposium


*** Programming Comittee ***
Elvira Albert	Universidad Complutense de Madrid
María Alpuente	Universitat Politècnica de València
Edwin Brady	University of St Andrews
Michael Hanus	CAU Kiel
Nao Hirokawa	JAIST
Zhenjiang Hu	Peking University
John Hughes	Chalmers University of Technology
Kazuhiro Inaba	Google
Shin-Ya Katsumata	National Institute of Informatics
Ekaterina Komendantskaya  	Heriot-Watt University
Leonidas Lampropoulos	University of Pennsylvania
Akimasa Morihata	The University of Tokyo
Shin-Cheng Mu	Academia Sinica
Keisuke Nakano	Tohoku University (co-chair)
Koji Nakazawa	Nagoya University
Enrico Pontelli	New Mexico State University
Didier Remy	INRIA
Ricardo Rocha	University of Porto
Konstantinos Sagonas	Uppsala University (co-chair)
Ilya Sergey	Yale-NUS College
Kohei Suenaga	Kyoto University
Tachio Terauchi	Waseda University
Kazushige Terui	Kyoto University
Simon Thompson	University of Kent
Philip Wadler, University of Edinburgh

*** Organizers ***

Keisuke Nakano	Tohoku University, Japan (PC Co-Chair, General Chair)
Kostis Sagonas	Uppsala University, Sweden (PC Co-Chair)
Kazuyuki Asada	Tohoku University, Japan (Local Co-Chair)
Ryoma Sin'ya	Akita University, Japan (Local Co-Chair)
Katsuhiro Ueno	Tohoku University, Japan (Local Co-Chair)


*** Contact Address ***

flops2020 _AT_ easychair.org

-------------------------------------------------------------------------------

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7033425A-9DF6-4FF3-86B8-890BED387560@riec.tohoku.ac.jp \
    --to=ksk@riec.tohoku.ac.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list

AGPL code for this site: git clone https://public-inbox.org/ public-inbox