Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Michael Shulman <shu...@sandiego.edu>
To: Matt Oliveri <atm...@gmail.com>
Cc: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Re: Canonical forms for initiality
Date: Thu, 19 Oct 2017 12:07:32 -0700	[thread overview]
Message-ID: <CAOvivQzx5sqNqaw=AWx8V83hooeQ8LN5e-9wv2SpTcUaq8otag@mail.gmail.com> (raw)
In-Reply-To: <d420c124-4461-437b-80b3-6e010544e7dd@googlegroups.com>

On Tue, Oct 17, 2017 at 9:00 AM, Matt Oliveri <atm...@gmail.com> wrote:
> Could you explain why you want to use normal forms and hereditary
> substitution--rather than more typical typing rules--if you expect to need
> an infinite tower of coherences anyway? Needing the coherence tower seems
> like it will make the definition dramatically more complicated, so wouldn't
> it be best to base it on the most simple and familiar typing rules?

The advantage of canonical forms and hereditary substitution is that
the object-language judgmental equality automatically coincides with
the metatheoretic equality, and the inductive-inductive syntax should
simultaneously automatically form a set.  If we instead build a
coherence tower of judgmental equalities and higher judgmental
equalities, then we not only need to decide what that coherence
structure should be (whereas I think the coherence structure for
hereditary substitution should be fairly straightforward in
principle), but prove that it is "coherent" in some sense, in order to
enable the interpretation of raw syntax into inductive-inductive
syntax.

The rules of canonical-form type theory are the simple and familiar
ones, they're just annotated with "directionality" or "atomicity"
information.

  reply	other threads:[~2017-10-19 19:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 17:01 Michael Shulman
2017-10-17  7:33 ` [HoTT] " Andrea Vezzosi
2017-10-19 19:03   ` Michael Shulman
2017-10-17 16:00 ` Matt Oliveri
2017-10-19 19:07   ` Michael Shulman [this message]
2017-10-20 10:57     ` [HoTT] " Neel Krishnaswami
2017-10-20 11:16       ` Michael Shulman
2017-10-30  9:52         ` Andrea Vezzosi

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='CAOvivQzx5sqNqaw=AWx8V83hooeQ8LN5e-9wv2SpTcUaq8otag@mail.gmail.com' \
    --to="shu..."@sandiego.edu \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="atm..."@gmail.com \
    /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).