From: Michael Shulman <shu...@sandiego.edu>
To: Martin Escardo <escardo...@googlemail.com>
Cc: "HomotopyT...@googlegroups.com" <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Does MLTT have "or"?
Date: Sat, 13 May 2017 14:46:41 -0700 [thread overview]
Message-ID: <CAOvivQzHVGmPk16Xz=9mj2Y8Lm9pQYtUYgCPyAij9-=uhXO5wQ@mail.gmail.com> (raw)
In-Reply-To: <1cef3819-ed3f-c684-d070-f49576045a19@googlemail.com>
On Fri, May 12, 2017 at 11:10 AM, Martin Escardo
<escardo...@googlemail.com> wrote:
> The above argument relies on having a universe (first, to formulate
> excluded middle and funext, and, second, to formulate and prove the
> universality of eta).
>
> *** What is the interaction (if any) of excluded middle with regularity,
> in your thought above? It seems to me that adding a universe is playing
> a role. It is different to say externally that all morphisms have
> images, than to say this internally using a universe (or am I wrong?).
Three replies:
1. I don't think the argument technically relies on having a universe.
LEM, funext, and the universality of eta are usually stated internally
by quantifying over a universe, but they can also be stated as rules
with type judgments as premises, and I believe the proof of
universality goes through as a derivation of one rule from others.
2. In general, saying something internally is different from saying it
externally, but I think that for images (and more generally for
universal properties that are stable under pullback and descent) there
is no difference. In such cases saying it internally with a universe
is the same as saying it externally for the "universal case", which
implies its external truth in all other cases. (You can also say it
"internally" without a universe using stack semantics.)
3. A Boolean coherent category automatically has a subobject
classifier, namely 1+1. Thus, if it is also cartesian closed, it is
automatically a topos.
> A second side-remark is this, which I realized just now while writing
> this, although I have known the above for several years:
>
> We know that the addition of propositional truncations as a rule, with
> certain stipulated definitional equalities, as in the HoTT book, gives
> function extensionality.
>
> A number of us (including Nicolai and me), asked whether hypothetical
> propositional truncations (which cannot come with stipulated
> definitional equalities) also give funext.
>
> The above argument shows that hypothetical propositional truncations
> definitely cannot give function extensionality. For, if this were the
> case, excluded middle would also imply function extensionality. But we
> know that this is not the case.
>
> Best,
> Martin
next prev parent reply other threads:[~2017-05-13 21:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 9:09 Martin Escardo
2017-05-02 19:04 ` [HoTT] " Michael Shulman
2017-05-03 6:47 ` Martin Escardo
2017-05-12 18:10 ` Martin Escardo
2017-05-12 18:41 ` Martin Escardo
2017-05-13 21:46 ` Michael Shulman [this message]
2017-05-14 9:54 ` stre...
2017-05-16 6:20 ` Michael Shulman
2017-05-03 10:55 ` Thomas Streicher
2017-05-03 14:25 ` Martin Escardo
2017-05-03 14:48 ` Thomas Streicher
2017-05-03 15:04 ` Martin Escardo
2017-05-03 12:17 ` Andrew Polonsky
2017-05-03 12:24 ` [HoTT] " Martin Escardo
2017-05-03 12:24 ` Michael Shulman
2017-05-06 13:51 ` Andrew Swan
2017-05-07 13:49 ` [HoTT] " Martin Escardo
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='CAOvivQzHVGmPk16Xz=9mj2Y8Lm9pQYtUYgCPyAij9-=uhXO5wQ@mail.gmail.com' \
--to="shu..."@sandiego.edu \
--cc="HomotopyT..."@googlegroups.com \
--cc="escardo..."@googlemail.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).