Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Martin Escardo <escardo...@googlemail.com>
To: Michael Shulman <shu...@sandiego.edu>
Cc: "HomotopyT...@googlegroups.com" <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Conjecture
Date: Fri, 7 Apr 2017 19:10:03 +0100	[thread overview]
Message-ID: <2c2fac47-505a-07d9-31e2-5e1a32f360a1@googlemail.com> (raw)
In-Reply-To: <CAOvivQwpFWMz7tqf-y4=ZZV_tQLr=MQK5HYvQUU1KDmu-=NsCw@mail.gmail.com>

On 07/04/17 18:11, Michael Shulman wrote:
> On Fri, Apr 7, 2017 at 2:49 AM, 'Martin Escardo' via Homotopy Type
> Theory <HomotopyT...@googlegroups.com> wrote:
>> (1) Indeed, I do like to think of the fragment of univalent type
>> theory consisting of function extensionality + proposition
>> extensionality + propositional truncation as essentially the same
>> thing as topos logic, provided we have propositional resizing. (But,
>> as discussed, much can be done without propositional resizing (but not
>> all), and one way of looking at HIT's is as a mechanism to avoid
>> resizing.)
> 
> I would say that to really be talking about (elementary) topos logic,
> one should also do without universes other than hProp.  Of course,
> elementary 1-toposes also validate UIP.

Agreed. (But you can consider elementary toposes with a universe object,
and a number of people have worked on that independently of any
connection with dependent type theory.)

> If we also omit hProp and propositional resizing, but include
> nonrecursive HITs as well as ordinary inductive types, then it ought
> to be basically Pi-W-pretopos logic; right?

I'd let the experts on these details to answer this.

I noticed the following mistake immediately after I send my message this
morning, and this is a good opportunity to rectify it:

>> In topos logic, you define (for the dominance of all propositions)
>>
>>   Lift(X) = { A:X->Omega | (exists(x:X), A x) &
>>                            forall(x,y:X), A x -> A y -> x = y }
>>

  Lift(X) = { A:X->Omega | forall(x,y:X), A x -> A y -> x = y }

If anybody noticed, they probably knew I meant that, and, if they didn't
notice, they probably understood that. There are other possibilities, of
course. :-)

Martin


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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 21:57 Conjecture Martin Escardo
2017-03-29 21:08 ` [HoTT] Conjecture Nicolai Kraus
2017-03-29 22:05   ` Martin Escardo
2017-03-30 10:59     ` Michael Shulman
2017-03-30 19:22       ` Egbert Rijke
2017-03-30 23:02         ` Nicolai Kraus
2017-03-30 22:49     ` Nicolai Kraus
2017-03-31 16:09       ` Martin Escardo
2017-04-05 19:37         ` Martin Escardo
2017-04-06  0:23           ` Jon Sterling
2017-04-06  5:55             ` Martin Escardo
2017-04-06 12:40               ` Vladimir Voevodsky
2017-04-06 13:50                 ` Martin Escardo
     [not found]                   ` <81c0782f-9287-4111-a4f1-01cb9c87c7e8@cs.bham.ac.uk>
2017-04-06 16:09                     ` Martin Escardo
2017-04-06 11:52             ` Thomas Streicher
2017-04-07  9:49               ` Martin Escardo
2017-04-07 17:11                 ` Michael Shulman
2017-04-07 18:10                   ` Martin Escardo [this message]
2017-04-03  0:35 ` Conjecture Daniel R. Grayson
2017-04-03  2:20   ` [HoTT] Conjecture Favonia
2017-04-03  9:56   ` Nicolai Kraus
2017-04-03 11:50     ` Daniel R. Grayson

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=2c2fac47-505a-07d9-31e2-5e1a32f360a1@googlemail.com \
    --to="escardo..."@googlemail.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).