Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Michael Shulman <shu...@sandiego.edu>
To: Thorsten Altenkirch <Thorsten....@nottingham.ac.uk>
Cc: "Martín Hötzel Escardó" <"escardo..."@gmail.com>,
	"Homotopy Type Theory" <"homotopyt..."@googlegroups.com>
Subject: Re: [HoTT] Bishop's work on type theory
Date: Sat, 5 May 2018 14:27:48 -0700	[thread overview]
Message-ID: <CAOvivQzpNrDQdqUh58w5HgnWQdqGC+dgobqmd=7W3Bs=gJ7fcA@mail.gmail.com> (raw)
In-Reply-To: <CAOvivQzXXrBsMXNFTK0LXZ=NFbz7b6a7X4sW+p2e9bCZ4zmKQA@mail.gmail.com>

On 5/5/18, Michael Shulman <shu...@sandiego.edu> wrote:
> I think the problem is that it's not consistent about what a
> "proposition" is.  If a "proposition" is a setoid in which all
> elements are equal, then to be consistent, the equality relations of
> other setoids should also be valued in "propositions" of *this* sort,
> not the original collection of "propositions" you started with.
> Otherwise, I think you won't necessarily be able to take the quotient
> of a setoid by a "proposition"-valued equivalence relation, which is
> the whole point of introducing setoids in the first place.  But down
> this route lies infinity.

I take that back: this doesn't lead to an infinite sequence, instead
it stops after one iteration, at a result that coincides with (1):

> 1. Use propositions as types, as in MLTT Type-valued setoids and the
> ex/lex completion.

After all, "a proposition is a setoid in which any two elements are
equal" is essentially the same as "a proposition is a type".  This is
of course a perfectly good way to get a category of setoids (although
from a semantic point of view it is too limiting, restricting you to
categories that arise as ex/lex completions), and I believe it's how a
lot of people have interpreted Bishop's mathematics inside MLTT (for
instance).  But unless I'm confused, it's not what Bishop is trying to
do in this manuscript; he definitely seems to want the equality
relations of his setoids to be proof-irrelevant predicates.

  parent reply	other threads:[~2018-05-05 21:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 21:01 Martín Hötzel Escardó
2018-05-04 21:19 ` [HoTT] " Michael Shulman
2018-05-04 21:56 ` Bas Spitters
2018-05-04 22:04   ` Martín Hötzel Escardó
2018-05-04 22:12     ` Bas Spitters
2018-05-04 22:16       ` Martín Hötzel Escardó
2018-05-04 22:23         ` Michael Shulman
2018-05-05  4:27           ` Michael Shulman
2018-05-05 11:35             ` Thorsten Altenkirch
2018-05-05 15:13               ` Michael Shulman
2018-05-05 15:21                 ` Michael Shulman
2018-05-05 21:27                 ` Michael Shulman [this message]
2018-05-09 22:27             ` Martín Hötzel Escardó
2018-05-10  6:35               ` Andrej Bauer
2018-05-09  9:04 ` Matt Oliveri
2018-05-09 16:15   ` [HoTT] " Michael Shulman

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='CAOvivQzpNrDQdqUh58w5HgnWQdqGC+dgobqmd=7W3Bs=gJ7fcA@mail.gmail.com' \
    --to="shu..."@sandiego.edu \
    --cc="Thorsten...."@nottingham.ac.uk \
    --cc="escardo..."@gmail.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).