caml-list - the Caml user's mailing list
 help / Atom feed
From: Louis Mandel <>
Subject: [Caml-list] [REBLS 2019] 2nd CfP (deadline extension)
Date: Fri, 2 Aug 2019 10:07:24 -0400
Message-ID: <> (raw)


6th Workshop on Reactive and Event-based Languages and Systems (REBLS 2019)
co-located with the SPLASH Conference
Athens, Greece, Sun 20 - Fri 25 October 2019


Submission Deadline: 16 Aug 2019 (extended)
Author Notification:  7 Sep 2019


Reactive programming and event-based programming are two closely related
programming styles that are becoming ever more important with the advent of
advanced HPC technology and the ever increasing requirement for our
applications to run on the web or on collaborating mobile devices. A number
of publications on middleware and language design -- so-called reactive and
event-based languages and systems (REBLS) -- have already seen the light,
but the field still raises several questions. For example, the interaction
with mainstream language concepts is poorly understood, implementation
technology is in its infancy and modularity mechanisms are almost totally
lacking. Moreover, large applications are still to be developed and
patterns and tools for developing reactive applications is an area that is
vastly unexplored. This workshop will gather researchers in reactive and
event-based languages and systems. The goal of the workshop is to exchange
new technical research results and to define better the field by coming up
with taxonomies and overviews of the existing work.

We welcome all submissions on reactive programming, aspect- and event-
oriented systems, including but not limited to:

* Language design, implementation, runtime systems, program analysis,
  software metrics, patterns and benchmarks.

* Study of the paradigm: interaction of reactive and event-based
  programming with existing language features such as object-oriented
  programming, mutable state, concurrency.

* Advanced event systems, event quantification, event composition,
  aspect-oriented programming for reactive applications.

* Functional-reactive programming, self-adjusting computation and
  incremental computing.

* Synchronous languages, modeling real-time systems, safety-critical
  reactive and embedded systems.

* Applications, case studies that show the efficacy of reactive

* Empirical studies that motivate further research in the field.

* Patterns and best-practices.

* Related fields, such as complex event processing, reactive data
  structures, view maintenance, constraint-based languages, and their
  integration with reactive programming. IDEs, Tools.

* Implementation technology, language runtimes, virtual machine support,

* Modularity and abstraction mechanisms in large systems.

* Formal models for reactive and event-based programming.

The format of the workshop is that of a mini-conference. Participants can
present their work in slots of 30 mins with Q&A included. Because of the
declarative nature of reactive programs, it is often hard to understand
their semantics just by looking at the code. We therefore also encourage
authors to use their slots for presenting their work based on live demos.


REBLS encourages submissions of two types of papers:

* Research results: complete works that will be published in the ACM
  digital library.

* In progress papers: papers that have the potential of triggering an
  interesting discussion at the workshop or present new ideas that require
  further systematic investigation. These papers will not be published in
  the ACM digital library.


* Submissions should be formatted according to the instructions for the
  authors below.

* Full papers can be up to 10 pages in length including references.

* In progress papers can be up to 6 pages.

* Authors are required to explicitly specify the type of paper in the

Instructions for the Authors:

Submission link: 

For fairness reasons, all submitted papers should conform to the formatting
instructions. Submissions that violate these instructions may be rejected
without review.

Papers must describe unpublished work that is not currently submitted for
publication elsewhere as described by SIGPLAN’s Republication Policy.
Submitters should also be aware of ACM’s Policy and Procedures on

Submissions should use the ACM SIGPLAN Conference acmart Format with
sigplan Subformat, 10 point font, using Biolinum as sans-serif font and
Libertine as serif font. All submissions should be in PDF format. If you
LaTeX or Word, please use the ACM SIGPLAN acmart Templates.


Tomoyuki Aotani, Tokyo Institute of Technology, Japan
Patrick Bahr, IT University of Copenhagen, Denmark
Engineer Bainomugisha, Makerere University, Uganda
Guillaume Baudart, IBM Research, United States
Aggelos Biboudis, EPFL, Switzerland
Tim Felgentreff, Oracle Labs, Potsdam, Germany
Tetsuo Kamina, Oita University, Japan *co-chair*
Louis Mandel, IBM Research, United States
Hidehiko Masuhara, Tokyo Institute of Technology, Japan *co-chair*
Yoshiki Ohshima, HARC / Y Combinator Research, Japan
Ivan Perez, NIA / NASA Formal Methods, United States
Noemi Rodriguez, PUC-Rio, Brazil
Steven Smyth, Kiel University, Germany
Mirko Viroli, University of Bologna, Italy
Harumi Watanabe, Tokai University, Japan
Takuo Watanabe, Tokyo Institute of Technology, Japan
YungYu Zhuang, National Central University, Taiwan
Ana Lúcia de Moura, PUC-Rio, Brazil


Guido Salvaneschi, TU Darmstadt, Germany
Wolfgang De Meuter, Vrije Universiteit Brussel, Belgium
Patrick Eugster, Universita della Svizzera Italiana, Switzerland
Francisco Sant'Anna, Rio de Janeiro State University, Brazil
Lukasz Ziarek, SUNY Buffalo, United States

                 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:

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

  git send-email \ \ \ \

* 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

AGPL code for this site: git clone public-inbox