Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Martin Escardo <escardo...@googlemail.com>
To: Homotopy Type Theory List <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Re: Joyal's version of the notion of equivalence
Date: Wed, 12 Oct 2016 23:45:55 +0100	[thread overview]
Message-ID: <a23ccd7f-1211-65ac-09a6-2154e28741e0@googlemail.com> (raw)
In-Reply-To: <878ttt3dq1.fsf_-_@uwo.ca>



On 12/10/16 14:21, Dan Christensen wrote:
> On Oct 12, 2016, Peter LeFanu Lumsdaine <p.l.lu...@gmail.com> wrote:
>
>> And for Joyal-equivalences, I don’t know anywhere they’re explicitly
>> discussed at all, before HoTT.  Like Martín, I’d be really interested if
>> anyone does know any earlier sources for them!
>
> I'm not sure if this is what you are looking for, but Exercise 11 in
> Chapter 0 of Hatcher's "Algebraic Topology" says:
>
>   Show that f : X -> Y is a homotopy equivalence if there exist maps
>   g, h : Y -> X such that fg ≃ 1 and hf ≃ 1.  More generally, show that
>   f is a homotopy equivalence if fg and hf are homotopy equivalences.

Nice for the historical record as asked by Peter L.

But let me try dissect this from the point of view of univalent type
theory, and relate it to my question.

    Joyal-equivalence(f:X->Y) := f has a section * f has a retraction.
    f has a section    := Sigma(g:Y->X), fg ≃ 1.
    f has a retraction := Sigma(h:Y->X), hf ≃ 1.

Remark 1. "Sigma" is not the same thing as "exists".

Remark 2. The type "f has a section" is not an hproposition. This
means that having a section is structure rather than property.
Similarly for "f has a retraction".

Remark 3. Existence is truncated structure. So there is no problem *at
all* in seeing that

       f is an equivalence := ||f has a section|| *
                              ||f has a retraction||.

(Which is what the above exercise says a priori.)

But my question was why, although each of

     f has a section

and

     f has a retraction

individually are structure on f, they become property of f when put
together.

I know why, as I said, because I am in possession of a proof. But I
don't feel I am in possession of a conceptual explanation.

Best,
Martin

  reply	other threads:[~2016-10-12 22:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <963893a3-bfdf-d9bd-8961-19bab69e0f7c@googlemail.com>
2016-10-07 23:51 ` Martin Escardo
2016-10-08  0:21   ` [HoTT] " Martin Escardo
2016-10-08 17:34     ` Joyal, André
2016-10-09 18:31       ` Martin Escardo
2016-10-09 18:56         ` Joyal, André
2016-10-11 22:54           ` Martin Escardo
2016-10-12  9:45             ` Peter LeFanu Lumsdaine
2016-10-12 13:21               ` Dan Christensen
2016-10-12 22:45                 ` Martin Escardo [this message]
2016-10-12 22:17               ` [HoTT] " Vladimir Voevodsky
2016-10-12 23:55                 ` Martin Escardo
2016-10-13 10:14                   ` Thomas Streicher
2016-10-13  7:14                 ` Joyal, André
2016-10-13 12:48                   ` Egbert Rijke

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=a23ccd7f-1211-65ac-09a6-2154e28741e0@googlemail.com \
    --to="escardo..."@googlemail.com \
    --cc="HomotopyT..."@googlegroups.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).