WST 2022 - Call for Papers
18th International Workshop on Termination
August 11-12, 2022, Haifa, Israel
Co-located with IJCAR-11 at FLoC 2022
The Workshop on Termination (WST) traditionally brings together, in an
informal setting, researchers interested in all aspects of
termination, whether this interest be practical or theoretical,
primary or derived. The workshop also provides a ground for
cross-fertilization of ideas from the different communities interested
in termination (e.g., working on computational mechanisms, programming
languages, software engineering, constraint solving, etc.). The
friendly atmosphere enables fruitful exchanges leading to joint
research and subsequent publications.
* submission deadline: May 3, 2022
* notification: June 8, 2022
* final version due: June 22, 2022
* workshop: August 11-12, 2022
The 18th International Workshop on Termination welcomes contributions
on all aspects of termination. In particular, papers investigating
applications of termination (for example in complexity analysis,
program analysis and transformation, theorem proving, program
correctness, modeling computational systems, etc.) are very welcome.
Topics of interest include (but are not limited to):
* abstraction methods in termination analysis
* certification of termination and complexity proofs
* challenging termination problems
* comparison and classification of termination methods
* complexity analysis in any domain
* implementation of termination analysis methods
* non-termination analysis and loop detection
* normalization and infinitary normalization
* operational termination of logic-based systems
* ordinal notation and subrecursive hierarchies
* SAT, SMT, and constraint solving for (non-)termination analysis
* scalability and modularity of termination methods
* termination analysis in any domain (lambda calculus, declarative
programming, rewriting, transition systems, probabilistic
* well-founded relations and well-quasi-orders
Submissions are short papers/extended abstracts which should not
exceed 5 pages. There will be no formal reviewing. In particular, we
welcome short versions of recently published articles and papers
submitted elsewhere. The program committee checks relevance and
provides additional feedback for each submission. The accepted papers
will be made available electronically before the workshop.
Papers should be submitted electronically via the submission page:
Please, use LaTeX and the LIPIcs style file
to prepare your submission.
* Jose Divasón - U. de La Rioja
* Florian Frohn - AbsInt GmbH
* Jera Hensel - RWTH Aachen
* Dieter Hofbauer - ASW Saarland
* Sebastiaan Joosten - Dartmouth College
* Cynthia Kop (chair) - Radboud U. Nijmegen
* Akihisa Yamada - AIST, Japan
* Hans Zantema - Eindhoven U. of Technology
(Apologies for multiple copies of this announcement. Please circulate.)
Call for Location for FSCD 2024
The FSCD conference covers all aspects of Formal Structures for
Computation and Deduction from theoretical foundations to
applications. The annual FSCD conference comprises the main
conference and a considerable number of affiliated workshops
(expectedly, more than ten).
We invite proposals for locations to host the 9th FSCD International
Conference to be held during the summer of 2024. Previous (and
upcoming) FSCD meetings include:
FSCD 2016 in Porto (Portugal);
FSCD 2017 in Oxford (UK) co-located with ICFP 2017;
FSCD 2018 in Oxford (UK) as part of FLoC 2018;
FSCD 2019 in Dortmund (Germany);
FSCD 2020 in Paris (France) co-located with IJCAR 2020;
FSCD 2021 in Buenos Aires (Argentina);
FSCD 2022 in Haifa (Israel) as part of FLOC2022;
FSCD 2023 in Rome (Italy).
The deadline for proposals is *** 27th June 2022 ***. Proposals should
be sent to the FSCD Steering Committee Chair (see contact information
below). We encourage proposers to register their intention informally
as soon as possible.
Selected proposals are to be presented at the business meeting of FSCD
2022 taking place at Haifa in August 2022. The final decision about
hosting and organising of FSCD 2024 will be taken by the SC after an
advisory vote of the members of the community in attendance at the
Proposals should address the following points:
* FSCD Conference Chair (complete name and current position), host
institution, FSCD Local Committee (complete names and current
positions), availability of student-volunteers.
* National, regional, and local government and industry support, both
organizational and financial.
* Accessibility to the location (i.e., transportation) and
attractiveness of the proposed site. Accessibility can include both
information about local transportation and travel information to the
location (flight and/or train connections), as well as estimated
* Appropriateness of the proposed dates (including consideration of
holidays/other events during the period), hotel prices, and access
to dormitory facilities for students.
* Estimated costs on registration for the conference and workshops,
both for regular and student participants.
* Conference and exhibit facilities for the anticipated number of
registrants (typically around 200). For example:
= number, capacity and audiovisual equipment of meeting rooms;
= a large plenary session room that can hold all the registrants;
= enough rooms for parallel session workshops/tutorials in the two
days before and the two days after the main conference;
= internet connectivity and workstations for demos/competitions;
= catering services;
= presence of professional staff.
* Support for hybrid attendance to the conference.
* Residence accommodations and food services in a range of price
categories and close to the conference venue, for example, number
and cost range of hotels, and availability and cost of dormitory
rooms (e.g., at local universities) and kind of services they offer.
* Other relevant information, which can include information about
leisure activities and attractiveness of the location (e.g.,
cultural and historical aspects, touristic activities, etc...).
FSCD SC Chair
while ago, SC discussed on how to fix TPDB benchmarks. We should
maintain consistency with past competition results, so we agree on the
If changes should be made on benchmarks that has been used in a past
competition, please follow the procedure:
- Rename the benchmark following the rule: file.ext -> file_REV2.ext ->
file_REV3.ext -> ...
- Make sure the old file is removed.
- Then make pull request.