From: Andrea Vezzosi <sanz...@gmail.com>
To: Michael Shulman <shu...@sandiego.edu>
Cc: "HomotopyT...@googlegroups.com" <homotopyt...@googlegroups.com>
Subject: Re: [HoTT] Canonical forms for initiality
Date: Tue, 17 Oct 2017 09:33:21 +0200 [thread overview]
Message-ID: <CAOSJkmyMphPH3peVqVPH6RVR3X+NrbTb-wmRq_cg1pwiFEp14g@mail.gmail.com> (raw)
In-Reply-To: <CAOvivQxX4crPBKj7ANMsTk-d3=oqkL6k_iK0KxAu64Y_fTe1vA@mail.gmail.com>
On Mon, Oct 16, 2017 at 7:01 PM, Michael Shulman <shu...@sandiego.edu> wrote:
> [...]
> However, when doing this intrinsically (which is the direct way to get
> a useful induction principle) and without h-level restriction, I found
> that there seems to be a new problem: you end up needing to substitute
> hereditarily not just one term but a whole context morphism, and then
> in defining the clauses for the graph of that hereditary substitution
> you need to know already that it is associative. So you add another
> judgment for the graph of its associativity, but in defining its
> clauses you need to know that the associativity is coherent, and so
> on.
This is interesting but I can't quite see it, what would be the type
of the "graph of associativity" judgment?
And how would you use it in the term/type judgments?
> The result is an inductive-inductive definition with infinite
> dependency, which we don't know how to make sense of internally. But
> if we can make sense of it (or make it finite by capping the h-level
> somewhere), then this tower of dependent inductive-inductive types
> ought to present the entire (semi)simplicial nerve of the syntactic
> category of the type theory (probably in the form of something like a
> "comprehension quasicategory").
>
> The induction principle of this inductive-inductive definition should
> then let us interpret it into an arbitrary sufficiently structured
> quasicategory, or even an internally defined "complete Segal space" if
> we do it in a homotopy type theory, such as the canonical universe,
> thereby solving the autophagy problem. On the other hand, since it
> has no path-constructors, an encode-decode argument should prove that
> it actually consists of h-sets, which should then allow us to
> interpret untyped syntax into it.
>
> Of course this is a VERY rough sketch and there are a lot of ways it
> could go wrong, plenty of which I expect people will point out. (-:
>
> Mike
>
> --
> You received this message because you are subscribed to the Google Groups "Homotopy Type Theory" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to HomotopyTypeThe...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-10-17 7:33 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 ` Andrea Vezzosi [this message]
2017-10-19 19:03 ` [HoTT] " Michael Shulman
2017-10-17 16:00 ` Matt Oliveri
2017-10-19 19:07 ` [HoTT] " Michael Shulman
2017-10-20 10:57 ` 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=CAOSJkmyMphPH3peVqVPH6RVR3X+NrbTb-wmRq_cg1pwiFEp14g@mail.gmail.com \
--to="sanz..."@gmail.com \
--cc="homotopyt..."@googlegroups.com \
--cc="shu..."@sandiego.edu \
/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).