Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Matt Oliveri <atm...@gmail.com>
To: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Cc: awo...@cmu.edu, b.a.w.s...@gmail.com, ri...@cam.ac.uk
Subject: Re: [HoTT] Weaker forms of univalence
Date: Thu, 20 Jul 2017 18:36:51 -0700 (PDT)	[thread overview]
Message-ID: <7cf42606-2ef4-4575-ad0e-da78e2bca514@googlegroups.com> (raw)
In-Reply-To: <CAOvivQzw_dqoHYTomVyX=pwxCCoYqopykX=JcGHH0pm19t_ERw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2778 bytes --]

Why wouldn't a skeletal LCCC be a model of (1) + UIP?

On Thursday, July 20, 2017 at 1:57:37 PM UTC-4, Michael Shulman wrote:
>
> But is it known that this is definitely weaker?  E.g. are there models 
> that satisfy invariance but not the computation rule? 
>
> On Thu, Jul 20, 2017 at 4:59 AM, Steve Awodey <awo...@cmu.edu 
> <javascript:>> wrote: 
> > I think we’ve been through this before: 
> > 
> >  (1)  (A ≃ B) -> (A = B) 
> > 
> > is logically equivalent to what may be called “invariance”: 
> > 
> >         if P(X) is any type depending on a type variable X, then given 
> any equivalence e : A ≃ B , we have P(A) ≃ P(B). 
> > 
> > if we add to this a certain “computation rule”, we get something 
> logically equivalent to UA: 
> > assume p : A ≃ B → A = B; then given e : A ≃ B, we have p(e) : A = B is 
> a path in U. 
> > Since we can transport along this path in any family of types over U, 
> and transport is always an equivalence, 
> > there is a transport p(e)∗ : A ≃ B in the identity family. 
> > The required “computation rule” states that p(e)∗ = e. 
> > 
> > Steve 
> > 
> > 
> > 
> >> On Jul 20, 2017, at 8:56 AM, Bas Spitters <b.a.w...@gmail.com 
> <javascript:>> wrote: 
> >> 
> >>> It was observed previously on this list, 
> >> Maybe we should be using our wiki more? 
> >> https://ncatlab.org/homotopytypetheory/ 
> >> 
> >> 
> >> On Wed, Jul 19, 2017 at 7:19 PM, Michael Shulman <shu...@sandiego.edu 
> <javascript:>> wrote: 
> >>> It was observed previously on this list, I think, that full univalence 
> >>> (3) is equivalent to 
> >>> 
> >>> (4)  forall A, IsContr( Sigma(B:U) (A ≃ B) ). 
> >>> 
> >>> This follows from the fact that a fiberwise map is a fiberwise 
> >>> equivalence as soon as it induces an equivalence on total spaces, and 
> >>> the fact that based path spaces are contractible.  But the 
> >>> contractibility of based path spaces also gives (2) -> (4), and hence 
> >>> (2) -> (3). 
> >>> 
> >>> I am not sure about (1).  It might be an open question even in the 
> >>> case when A and B are propositions. 
> >>> 
> >>> 
> >>> On Wed, Jul 19, 2017 at 9:26 AM, Ian Orton <ri...@cam.ac.uk 
> <javascript:>> 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
>

[-- Attachment #1.2: Type: text/html, Size: 4675 bytes --]

  reply	other threads:[~2017-07-21  1:36 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 [this message]
2017-07-21  7:43           ` Peter LeFanu Lumsdaine
2017-07-19 17:21 ` Jason Gross
2017-07-19 17:28   ` Michael Shulman
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=7cf42606-2ef4-4575-ad0e-da78e2bca514@googlegroups.com \
    --to="atm..."@gmail.com \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="awo..."@cmu.edu \
    --cc="b.a.w.s..."@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).