caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Protzenko <jonathan.protzenko@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] Second and Final Call for Submissions: Programming Languages and the Law (ProLaLa)
Date: Tue, 5 Oct 2021 13:54:04 -0700	[thread overview]
Message-ID: <d049c17d-01d8-6f01-e372-f2a7eeb05a5d@gmail.com> (raw)

-----------------------------------------------------------------------

    ProLaLa 2022 -- 1st Workshop on Programming Languages and the Law

                        Sunday Jan 16th, 2022
                          Philadelphia, PA
                      co-located with POPL 2022

-----------------------------------------------------------------------

                     (please forward to anyone who might be interested!)


We are pleased to announce ProLaLa'22, a new workshop concerned with the 
intersection of PL (Programming Languages) techniques and the law. We 
are particularly concerned with the following topics:

- language design for legal matters;
- static analysis of legal texts;
- program synthesis and repair for legal software components;
- formal modeling of legal semantics;
- non-standard logics in support of legal reasoning;
- program verification for legal expert systems.

If you have explored any of these areas, we encourage you to submit a 
short abstract. We are hoping to solidify around this workshop what we 
believe is a nascent community. As such, the workshop will be informal, 
and we strongly encourage you to submit ongoing or already-published 
work in the form of a brief 3-page submission for a long talk, or a 
1-page submission for a short talk.

Full details: 
https://popl22.sigplan.org/home/prolala-2022#Call-for-submissions

### Venue

ProLaLa will be colocated with POPL'22. If POPL'22 goes virtual, we will 
be virtual too. If POPL'22 happens in-person, we will support hybrid 
(in-person and remote) participation.

### Submission details

We accept two kinds of submissions.
- Long talks: 3 pages excluding references
- Short talks: 1 page excluding references

No formatting requirements. We recommend using SIGPLAN's two-column 
LaTeX format if possible.

Submission site: https://prolala22.hotcrp.com/

### Important dates

- Thu 28 Oct 2021: Submission deadline
- Thu 11 Nov 2021: Notification of acceptance
- Sun 16 Jan 2022: Workshop

## Program committee

- Timos Antonopoulos, Yale University
- Joaquin Arias, Universidad Politécnica de Madrid and IMDEA Software 
Institute, Spain
- Shrutarshi Basu, Cornell University, USA
- Nate Foster, Cornell University, USA
- James Grimmelmann, Cornell University, USA
- Sarah Lawsky (Co-Chair), Northwestern University, USA
- Denis Merigoux, INRIA, France
- Ruzica Piskac, Yale University, USA
- Jonathan Protzenko (Co-Chair), Microsoft Research, USA
- Giovanni Sartor, University of Bologna, Italy
- Ken Satoh, National Institute of Informatics, Japan
- Kanae Tsushima, National Institute of Informatics, Japan
- Meng Weng Wong, Singapore Management University, Singapore






                 reply	other threads:[~2021-10-05 20:54 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=d049c17d-01d8-6f01-e372-f2a7eeb05a5d@gmail.com \
    --to=jonathan.protzenko@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).