[TYPES/announce] Call for Affiliated Workshops at QONFEST 2020, in Vienna, TU Wien

2019-11-26 Thread Ana Sokolova
[ The Types Forum (announcements only),
 http://lists.seas.upenn.edu/mailman/listinfo/types-announce ]

* *QONFEST 2020* *

August 31-September 5, 2020, Vienna, Austria

(http://qonfest2020.conf.tuwien.ac.at/ <
http://qonfest2020.conf.tuwien.ac.at/)


QONFEST is the umbrella conference comprising the joint international

2020 meetings CONCUR (31st International Conference on Concurrency

Theory), QEST (17th International Conference on Quantitative

Evaluation of SysTems), FORMATS (18th International Conference on

Formal Modeling and Analysis of Timed Systems) and FMICS (25th

International Conference on Formal Methods for Industrial Critical

Systems). QONFEST 2020 will be hosted at TU Wien, Vienna, Austria,

with the conferences taking place in the main building at Karlsplatz

13, 1040 Wien, and the workshops in the computer science building at

Favoritenstr. 9–11, 1040 Wien.



CALL FOR AFFILIATED WORKSHOPS


Researchers and practitioners are invited to submit proposals for

workshops to be affiliated to QONFEST 2020. Example topics include:

concurrency theory and its applications, timed systems, semantics,

logics, verification techniques, cross-fertilization between industry

and academia and opportunities for young and prospective researchers.

Past QONFEST conferences have been accompanied by successful workshops

on a variety of topics. You can have an idea of the past workshops by

browsing the pages of the previous editions of CONCUR, QEST, FORMATS

and FMICS.




The purpose of the workshops is to provide participants with a

friendly, interactive atmosphere for presenting novel ideas and

discussing their application.




The workshops take place on Monday August 31, 2020 and Saturday

September 5, 2020.




Proposals should include:




 * The name and the preferred date of the proposed workshop (August

31 or September 5, 2020)

 * A short description of the workshop (500 words max)

 * If applicable, a description of past versions of the workshop,

including dates, organizers, submission and acceptance counts, and

attendance

 * The expected number of participants

 * The name and a link to the website(s) of the organizer(s)

 * The publication plan (only invited speakers, no published

proceedings, pre-/post-proceedings published with EPTCS/ENTCS/...).




The QONFEST organization offers:


* a link from the QONFEST web site;

* setup of meeting space, and related equipment,

* coffee-breaks and lunch for the participants on the day of the workshop,

* on-line and on-site registration to the workshop,

* free workshop registration for an organizer and in case of more than

15 participants a second free workshop registration




The main responsibility for organizing the workshop goes to the

workshop organizer(s), including:


* workshop publicity (possibly including call for papers, submission

and review process)

* scheduling of workshop activities in collaboration with the QONFEST

workshop chair.




IMPORTANT DATES


Submission of workshop proposals: January 15, 2020 (but we greatly

appreciate if you announce your proposal to us as soon as possible).


Notification: January 31, 2020




SUBMISSION TO: Florian Zuleger (zuleger at forsyte dot at)


[TYPES/announce] [TFP'20] draft paper deadline open (January 10 2020) Trends in Functional Programming 2020, 13-14 February, Krakow, Poland

2019-11-26 Thread Peter Achten

[ The Types Forum (announcements only),
http://lists.seas.upenn.edu/mailman/listinfo/types-announce ]

-
 Third call for papers
    21st Symposium on Trends in Functional Programming
  tfp2020.org
-

Did you miss the deadline to submit a paper to Trends in Functional 
Programming

http://cse.chalmers.se/~rjmh/tfp/? No worries -- it's not too late!
Submission is open until January 10th 2020, for a presentation slot at 
the event

and post-symposium reviewing.

The symposium on Trends in Functional Programming (TFP) is an international
forum for researchers with interests in all aspects of functional 
programming,
taking a broad view of current and future trends in the area. It aspires 
to be

a lively environment for presenting the latest research results, and other
contributions.

* TFP is moving to new winter dates, to provide an FP forum in between the
  annual ICFP events.

* TFP offers a supportive reviewing process designed to help less 
experienced

  authors succeed, with two rounds of review, both before and after the
  symposium itself. Authors have an opportunity to address reviewers' 
concerns

  before final decisions on publication in the proceedings.

* TFP offers two "best paper" awards, the John McCarthy award for best 
paper,

  and the David Turner award for best student paper.

* This year we are particularly excited to co-locate with Lambda Days in
  beautiful Krakow. Lambda Days is a vibrant developer conference with 
hundreds
  of attendees and a lively programme of talks on functional 
programming in
  practice. TFP will be held in the same venue, and participants will 
be able

  to session-hop between the two events.


Important Dates
---

Submission deadline for pre-symposium review:   15th November, 2019  -- 
passed --

Submission deadline for draft papers:   10th January, 2020
Symposium dates:    13-14th February, 2020

Visit tfp2020.org for more information.


[TYPES/announce] FLOPS 2020: Final Call For Papers (Due on 29 Nov, 2019)

2019-11-26 Thread Keisuke Nakano
[ The Types Forum (announcements only),
 http://lists.seas.upenn.edu/mailman/listinfo/types-announce ]

FINAL Call For Papers (*** STILL AVAILABLE ***)

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