From: Michael Shulman <shu...@sandiego.edu>
To: "Martín Hötzel Escardó" <"escardo..."@gmail.com>
Cc: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Re: Where is the problem with initiality?
Date: Thu, 31 May 2018 04:09:39 -0700 [thread overview]
Message-ID: <CAOvivQy4ma1siR=DZcEquCJaAWG+=r7vZ98Q8tt7mfzouG+s_Q@mail.gmail.com> (raw)
In-Reply-To: <433eba9a-1d5b-43ce-a266-64d2f6b10047@googlegroups.com>
On Thu, May 31, 2018 at 3:48 AM, Martín Hötzel Escardó
<escardo...@gmail.com> wrote:
> Is the
> study of type theories mature enough to admit a general definition of a type
> theory, of which the ones we are looking at are a particular case?
Well, we won't know whether it is unless we try. Various of the
people working on the initiality theorem are approaching it by way of
formulating such definitions, either syntactically (collections of
rules) or semantically (structure on a CwF). And I spoke about
another class of general definitions-in-progress in my own HoTTEST
talk (jww Dan Licata and Mitchell Riley).
prev parent reply other threads:[~2018-05-31 11:10 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 5:46 Michael Shulman
2018-05-22 16:47 ` Ambrus Kaposi
2018-05-23 16:26 ` [HoTT] " Thorsten Altenkirch
2018-05-24 5:52 ` Michael Shulman
2018-05-24 8:11 ` Thorsten Altenkirch
2018-05-24 9:53 ` Ambrus Kaposi
2018-05-24 17:26 ` Michael Shulman
2018-05-26 9:21 ` Thomas Streicher
2018-05-26 11:47 ` Michael Shulman
2018-05-26 16:47 ` stre...
2018-05-27 5:14 ` Bas Spitters
2018-05-28 22:39 ` Michael Shulman
2018-05-29 9:15 ` [HoTT] " Thorsten Altenkirch
2018-05-29 15:15 ` Michael Shulman
2018-05-30 9:33 ` Thomas Streicher
2018-05-30 9:37 ` Thorsten Altenkirch
2018-05-30 10:10 ` Thomas Streicher
2018-05-30 12:08 ` Thorsten Altenkirch
2018-05-30 13:40 ` Thomas Streicher
2018-05-30 14:38 ` Thorsten Altenkirch
2018-05-30 10:53 ` Alexander Kurz
2018-05-30 12:05 ` Thorsten Altenkirch
2018-05-30 19:07 ` Michael Shulman
2018-05-31 10:06 ` Thorsten Altenkirch
2018-05-31 11:05 ` Michael Shulman
2018-05-31 19:02 ` Alexander Kurz
2018-06-01 9:55 ` Martin Escardo
2018-06-01 17:07 ` Martín Hötzel Escardó
2018-06-01 17:43 ` Eric Finster
2018-06-01 19:55 ` Martín Hötzel Escardó
2018-06-01 20:59 ` András Kovács
2018-06-01 21:06 ` Martín Hötzel Escardó
2018-06-01 21:23 ` Michael Shulman
2018-06-01 21:53 ` Eric Finster
2018-06-01 22:09 ` Michael Shulman
2018-06-02 15:06 ` Eric Finster
2018-06-05 20:04 ` Michael Shulman
2018-06-02 5:13 ` Thomas Streicher
2018-06-01 21:52 ` Jasper Hugunin
2018-06-01 22:00 ` Eric Finster
2018-06-01 21:27 ` Matt Oliveri
2018-06-02 5:21 ` Ambrus Kaposi
2018-06-02 6:01 ` Thomas Streicher
2018-06-02 14:35 ` Thorsten Altenkirch
2018-05-30 13:30 ` Jon Sterling
2018-06-05 7:52 ` Andrej Bauer
2018-06-05 8:37 ` David Roberts
2018-06-05 9:46 ` Gabriel Scherer
2018-06-05 22:19 ` Martín Hötzel Escardó
2018-06-05 22:54 ` Martín Hötzel Escardó
2018-06-05 22:12 ` Richard Williamson
2018-06-06 15:05 ` Thorsten Altenkirch
2018-06-06 19:25 ` Richard Williamson
2018-05-29 14:00 ` Jon Sterling
2018-05-30 22:35 ` Michael Shulman
2018-05-31 10:48 ` Martín Hötzel Escardó
2018-05-31 11:09 ` Michael Shulman [this message]
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='CAOvivQy4ma1siR=DZcEquCJaAWG+=r7vZ98Q8tt7mfzouG+s_Q@mail.gmail.com' \
--to="shu..."@sandiego.edu \
--cc="HomotopyT..."@googlegroups.com \
--cc="escardo..."@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).