Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Michael Shulman <shu...@sandiego.edu>
To: Jason Gross <jason...@gmail.com>
Cc: Ian Orton <ri...@cam.ac.uk>,
	 "HomotopyT...@googlegroups.com" <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Weaker forms of univalence
Date: Wed, 19 Jul 2017 10:28:27 -0700	[thread overview]
Message-ID: <CAOvivQwWRZmxFdK+UOnOLg9qssYdApZ+k7ZuLAKoC-+q2hNADA@mail.gmail.com> (raw)
In-Reply-To: <CAKObCargfD7gf2Gr7a1E88Tere+QkFcxgvbFMErEPP7c89oy0Q@mail.gmail.com>

I don't think you need function extensionality for contractibility and
Sigma to respect equivalence.  We need funext for Pi to respect
equivalence, but there are no Pis here.

On Wed, Jul 19, 2017 at 10:21 AM, Jason Gross <jason...@gmail.com> wrote:
> Certainly (2) => (3), at least if you assume function extensionality; it
> suffices to show that (\Sigma B, A ≃ B) is contractable, and since
> contractibility and sigma respect equivalence, we can transfer the proof
> that (\Sigma B, A = B) is contractable. I think the same is not true of (1),
> though I'm not sure.
>
> On Wed, Jul 19, 2017, 7:26 PM Ian Orton <ri...@cam.ac.uk> wrote:
>>
>> Consider the following three statements, for all types A and B:
>>
>>    (1)  (A ≃ B) -> (A = B)
>>    (2)  (A ≃ B) ≃ (A = B)
>>    (3)  isEquiv idtoeqv
>>
>> (3) is the full univalence axiom and we have implications (3) -> (2) ->
>> (1), but can we say anything about the other directions? Do we have (1)
>> -> (2) or (2) -> (3)? Can we construct models separating any/all of
>> these three statements?
>>
>> Thanks,
>> Ian
>>
>> --
>> 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.
>
> --
> 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.

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 16:26 Ian Orton
2017-07-19 17:19 ` [HoTT] " Michael Shulman
2017-07-19 18:04   ` Nicolai Kraus
2017-07-20  6:56   ` Bas Spitters
2017-07-20 11:59     ` Steve Awodey
2017-07-20 17:57       ` Michael Shulman
2017-07-21  1:36         ` Matt Oliveri
2017-07-21  7:43           ` Peter LeFanu Lumsdaine
2017-07-19 17:21 ` Jason Gross
2017-07-19 17:28   ` Michael Shulman [this message]
2017-07-19 18:02     ` Jason Gross

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=CAOvivQwWRZmxFdK+UOnOLg9qssYdApZ+k7ZuLAKoC-+q2hNADA@mail.gmail.com \
    --to="shu..."@sandiego.edu \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="jason..."@gmail.com \
    --cc="ri..."@cam.ac.uk \
    /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).