Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Jamie Vicary <jamie...@gmail.com>
To: Homotopy Type Theory <HomotopyT...@googlegroups.com>,
Subject: Second CfP: Applied Category Theory Conference (ACT2020)
Date: Sun, 3 May 2020 17:18:19 +0100	[thread overview]
Message-ID: <CANr23v1AGdrGY_ckhT8yPJH_sdpxK6sFJ=+fmT+wK5LhRe7F0Q@mail.gmail.com> (raw)
In-Reply-To: <CACcOXSEgh8j5QB7-UEcdABd=zMLLJ5y6aCEYQe36fzt3wXqi4Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4932 bytes --]


3rd Annual International Conference on
Applied Category Theory (ACT2020)

July 6 – 10, 2020


           * * *

Applied category theory is a topic of interest for a growing community of
researchers interested in studying many different kinds of systems using
category-theoretic tools. These systems are found across computer science,
mathematics, and physics, as well as in social science, linguistics,
cognition, and neuroscience. The background and experience of our members
is as varied as the systems being studied. The goal of the Applied Category
Theory conference is to provide a platform for researchers in the area to
discuss recent progress.

We seek submissions of both original research papers and extended abstracts
of work that's been submitted, accepted, or published elsewhere. Original
research papers we accept will be invited for publication in a proceedings
volume. Some contributions will be invited to become keynote addresses, and
best paper award(s) may also be given.

ACT2020 will be held entirely online, with all the attendant advantages: no
registration fee, no need to travel, etc. It will consist of three 2-hour
sessions per day, spaced the clock to accommodate the different time zones
of our speakers. All the talks will be both live streamed and recorded on
YouTube. Our goal is a conference that provides high quality, interactive
talk sessions; generative, high bitrate discussions; and serendipitous
interactions with new people.

The conference will include a business showcase, and it will be preceded by
a tutorial day.

This event follows ACT2018 in Leiden, and ACT2019 in Oxford.

** IMPORTANT DATES (all in 2020)**

Submission of contributed papers: Sunday May 10
Success notification: Sunday June 7
Tutorial day: July 5
Main conference: July 6 – 10


Two types of submissions are accepted, both of which will be reviewed using
the same standards:

  - Proceedings Track. Original contributions of high-quality work
consisting of a 5 – 12 page extended abstract that provides evidence of
results of genuine interest, and with enough detail to allow the program
committee to assess the merits of the work. Submission of a
work-in-progress is encouraged, but it must be more substantial than a
research proposal.

  - Non-Proceedings Track. Descriptions of high-quality work submitted or
published elsewhere will also be considered, provided the work is recent
and relevant to the conference. The work may be of any length, but the
program committee members may only look at the first 3 pages of the
submission, so you should ensure that these pages contain sufficient
evidence of the quality and rigor of your work.

Submissions should be prepared using LaTeX, and must be submitted in PDF
format. The submission link is available on the ACT2020 web page.


Mathieu Anel, Carnegie Mellon University
Miriam Backens, University of Birmingham
John Baez, Centre for Quantum Technologies
Richard Blute, University of Ottawa
Tai-Danae Bradley, City University of New York
Andrea Censi, ETH Zurich
Corina Cirstea, ETC Zurich
Bob Coecke, University of Oxford
Valeria de Paiva, Samsung Research America and University of Birmingham
Ross Duncan, University of Strathclyde
Eric Finster, University of Birmingham
Brendan Fong, Massachusetts Institute of Technology
Tobias Fritz, Perimeter Institute for Theoretical Physics
Richard Garner, Macquarie University
Fabrizio Romano Genovese, Statebox
Jeremy Gibbons, University of Oxford
Amar Hadzihasanovic, IRIF, Université de Paris
Helle Hvid Hansen, Delft University of Technology
Jules Hedges, Max Planck Institute for Mathematics in the Sciences
Kathryn Hess Bellwald, Ecole Polytechnique Fédérale de Lausanne
Chris Heunen, The University of Edinburgh
Alex Hoffnung, Bridgewater
Joachim Kock, Universitat Autònoma de Barcelona
Alexander Kurz, Chapman University
Tom Leinster, The University of Edinburgh
Martha Lewis, University of Amsterdam
Daniel R. Licata, Wesleyan University
David Jaz Myers, Johns Hopkins University
Paolo Perrone, Massachusetts Institute of Technology
Daniela Petrisan, University of Paris, IRIF
Vaughan Pratt, Stanford University
Peter Selinger, Dalhousie University
Michael Shulman, University of San Diego
David I. Spivak, Massachusetts Institute of Technology (co-chair)
John Terilla, Tunnel Technologies
Walter Tholen, York University
Todd Trimble, Western Connecticut State University
Christina Vasilakopoulou, University of Patras
Jamie Vicary, University of Birmingham (co-chair)
Maaike Zwart, University of Oxford


John Baez (University of California Riverside)
Bob Coecke (University of Oxford)
David Spivak (MIT)
Christina Vasilakopoulou (University of Patras)

[-- Attachment #2: Type: text/html, Size: 5306 bytes --]

           reply	other threads:[~2020-05-03 16:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CACcOXSEgh8j5QB7-UEcdABd=zMLLJ5y6aCEYQe36fzt3wXqi4Q@mail.gmail.com>]

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:

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

  git send-email \
    --in-reply-to='CANr23v1AGdrGY_ckhT8yPJH_sdpxK6sFJ=+fmT+wK5LhRe7F0Q@mail.gmail.com' \
    --to="jamie..."@gmail.com \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="types-a..."@lists.seas.upenn.edu \


* 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;
as well as URLs for NNTP newsgroup(s).