From: Crystal Chang Din <Crystal.Din@uib.no>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] FTfJP 2025 - Second Call for Papers
Date: Wed, 9 Apr 2025 10:22:41 +0000 [thread overview]
Message-ID: <DB9PR01MB9392CA2470E8160C1CE3108A84B52@DB9PR01MB9392.eurprd01.prod.exchangelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4904 bytes --]
FTfJP 2025
27th International Workshop on Formal Techniques for Judicious Programming, 03 July 2025, Bergen, Norway
Conference website:
https://2025.ecoop.org/home/FTfJP-2025
Submission link:
https://easychair.org/conferences?conf=ftfjp2025
=== Important dates ===
- Paper submission: 15 April 2025 (AoE)
- Paper notification: 21 May 2025 (AoE)
- Workshop date: 03 July 2025 (co-located with ECOOP 2025)
Deadlines expire at 23:59 anywhere on earth on the dates displayed above.
=== Objectives and scope ===
Formal techniques can help analyse programs, precisely describe program behaviour, and verify program properties. Modern programming languages (such as C#, Java, Kotlin, Rust, or Scala) are interesting targets for formal techniques due to their ubiquity and wide user base, stable and well-defined interfaces and platforms, and powerful (but also complex) libraries. New languages and applications in this space are continually arising, resulting in new programming languages research challenges.
Work on formal techniques and tools and on the formal underpinnings of programming languages themselves naturally complement each other.
The Formal Techniques for Judicious Programming (FTfJP) workshop is an established workshop which has run annually since 1999 alongside ECOOP, with the goal of bringing together people working in both fields. Webpages for previous workshops in this series are available at https://ftfjp.github.io/.
Example topics of interest include:
- Language design and semantics
- Type systems
- Concurrency and new application domains
- Specification and verification of program properties
- Program analysis (static or dynamic)
- Program synthesis
- Security
- Pearls (programs or proofs)
FTfJP welcomes submissions on technical contributions, case studies, experience reports, challenge proposals, tools, and position papers.
=== Paper Categories ===
We solicit two categories of papers:
- Full Papers (12 pages, excluding references) present a technical contribution, case study, or detailed experience report. We welcome both complete and incomplete technical results; ongoing work is particularly welcome, provided it is substantial enough to stimulate interesting discussions.
- Short Papers (6 pages, excluding references) should advocate a promising research direction, or otherwise present a position likely to stimulate discussion at the workshop. We encourage e.g. established researchers to set out a personal vision, and beginning researchers to present a planned path to a PhD.
Both types of contributions will benefit from feedback received at the workshop. Submissions will be peer reviewed and will be evaluated based on their clarity and their potential to generate interesting discussions. Reviewing will be single blind, i.e, submissions need not be anonymized.
The format of the workshop encourages interaction. FTfJP is a forum in which a wide range of people share their expertise, from experienced researchers to beginning PhD students.
=== Submission guidelines ===
Papers must be formatted according to the guidelines for Springer LNCS papers.
Submissions should be made via EasyChair: https://easychair.org/conferences?conf=ftfjp2025.
There is no need to indicate the paper category (long/short).
The accepted papers will be published as post-proceedings in JOT (Journal of Object Technology), though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must register to the workshop by the early registration date and attend the workshop to present the work and participate in the discussions.
=== Steering Committee ===
- Rosemary Monahan, National University of Ireland, Ireland (SC chair)
- Radu Grigore, Facebook, United Kingdom
- Gary T. Leavens, University of Central Florida, United States
- Werner Dietl, University of Waterloo, Canada
- Alexander J. Summers, University of British Columbia, Canada
=== Program Committee ===
- Crystal Chang Din, University of Bergen, Norway (PC Chair)
- Richard Bubel, Technische Universität Darmstadt, Germany
- Syed Ali Asadullah Bukhari, Maynooth University, Ireland
- Claire Dross, AdaCore, France
- Erik Ernst, Google Inc., Denmark
- Marie Farrell, The University of Manchester, United Kingdom
- Carlo A. Furia, Università della Svizzera italiana (USI), Switzerland
- Atsushi Igarashi, Kyoto University, Japan
- Marie-Christine Jakobs, LMU Munich, Germany
- Taylor T Johnson, Vanderbilt University, United States
- Matthew Lutze, Aarhus University, Denmark
- Wojciech Mostowski, Halmstad University, Sweden
- Wytse Oortwijn, TNO-ESI, Netherlands
- Violet Ka I Pun, Western Norway University of Applied Sciences, Norway
- Anton Wijs, Eindhoven University of Technology, Netherlands
- Elena Zucca, University of Genoa, Italy
[-- Attachment #2: Type: text/html, Size: 25775 bytes --]
reply other threads:[~2025-04-09 10:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly 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=DB9PR01MB9392CA2470E8160C1CE3108A84B52@DB9PR01MB9392.eurprd01.prod.exchangelabs.com \
--to=crystal.din@uib.no \
--cc=caml-list@inria.fr \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox