Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: "Martín Hötzel Escardó" <escardo.martin@gmail.com>
To: Homotopy Type Theory <HomotopyTypeTheory@googlegroups.com>
Subject: Re: [HoTT] Re: Precategories, Categories and Univalent categories
Date: Thu, 8 Nov 2018 13:37:20 -0800 (PST)	[thread overview]
Message-ID: <5645fcc6-2520-498f-8e82-0b335d4eb3f1@googlegroups.com> (raw)
In-Reply-To: <CAOvivQyG1q9=3YoS8hX3bRQK0yi+mpBnJu+rqb3oon0uPLpZ4A@mail.gmail.com>


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

We have two separate issues here:

(1) What is the appropriate notion of category for univalent
mathematics.

(2) What is the right terminology for it.

There is also a separate, orthogonal question,

(3) Whether there is a foundation-independent (dubbed "agnostic")
notion of category, which gives the right notion for each
foundation, *and* can be formulated in MLTT (without K or
univalence).

Regarding (3), even if this is possible (assuming the question
makes sense), it is not given by any of the proposed notions, and
this should not be regarded as surprising or shocking.

(This raises the question of whether there is a categorical
definition of category, for people who would like to see category
theory itself as a foundation.)

Regarding (1), I think the arguments by Ulrik, Paolo, Mike and
Eric (Finster) are pretty convincing: "univalent category" is the
right notion of category for univalent mathematics.

However, it *is* common and useful in mathematics to formulate
and prove theorems with minimal hypotheses, and then what is
called a pre-category, and what Thorsten called a wild category,
often arise naturally and unavoidably as part of the building
blocks of mathematics.

Regarding (2), I would say, in view of (the answer to) (3), that
it is probably better to avoid the naked terminology "category"
in HoTT/UF, as it would give the wrong impression of *capturing*
a universal, pre-existing, foundation-independent notion of
category (in particular compatible with the ZFC view of what a
category is, which has evilness as a built-in feature):

     * Then "univalent category" could mean, ambiguously but
       consistently, both

            (a) a pre-category that satisfies a certain technical
                condition analogous to the univalence axiom for
                types, or

            (b) "the appropriate notion of category for univalent
                 mathematics".

            (c) In both cases, (a) and (b), the
                adjective "univalent" makes sense. In (b), it
                would be not in opposition to "category", but
                instead in opposition to e.g. "ZFC category".

Martin


On Wednesday, 7 November 2018 15:55:45 UTC, Michael Shulman wrote:
>
> I strongly agree with Ulrik.  Perhaps the point that's not getting 
> across is that we are not talking about terminology for MLTT in 
> general, but specifically for HoTT (with univalence).  The terminology 
> to be decided on doesn't have to make sense or come out to anything 
> meaningful in type theory with UIP, and we shouldn't expect it to. 
> The terminology in MLTT+UIP should be different from that for MLTT+UA, 
> because they are different theories and relate to "traditional" 
> mathematics in different *incompatible* ways.  I doubt there is *any* 
> choice of terminology for plain MLTT without UA *or* UIP that is 
> sensible in that it can be specialized to the right terminology upon 
> the addition of either of these two inconsistent axioms. 
> On Wed, Nov 7, 2018 at 6:27 AM Peter LeFanu Lumsdaine 
> <p.l.lu...@gmail.com <javascript:>> wrote: 
> > 
> > On Wed, Nov 7, 2018 at 3:14 PM Ulrik Buchholtz <ulrikbu...@gmail.com 
> <javascript:>> wrote: 
> >> 
> >> On Wednesday, November 7, 2018 at 2:58:28 PM UTC+1, Thorsten Altenkirch 
> wrote: 
> >>> 
> >>> As I tried to say, I find that precategory is the novel concept, and 
> that both strict category and univalent category should be familiar to 
> category theorists. (They have a mental model for when one notion is called 
> for or the other, but we can make the distinction formal.) 
> >>> 
> >>> 
> >>> This is too clever! 
> >>> 
> >>> 
> >>> 
> >>> If you just transcribe the traditional definition of a category in 
> type theory you end up with what in the HoTT book is called precategory. 
> This is confusing for the non-expert even though you can justify why it 
> should be so. 
> >> 
> >> 
> >> No, you get the notion of a strict category, which in some sense is all 
> that you directly have in set theory. 
> > 
> > 
> > No in turn: you can arguably get either strict categories, or 
> precategories, or what Thorsten dubbed “wild categories” above, since “set” 
> in set theory is the (naïve) interpretation of both “set” and “type”. 
>  (Just as when you transcribe classical definitions in a constructive 
> setting, you sometimes want to read “predicate” just as “predicate” and 
> other times as “decidable predicate” — all predicates are decidable 
> classically, but that doesn’t mean that their constructive transcription 
> should include “decidable” by default.) 
> > 
> > –p. 
> > 
> > -- 
> > 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 HomotopyTypeTheory+unsubscribe@googlegroups.com <javascript:>. 
>
> > 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 HomotopyTypeTheory+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2018-11-08 21:37 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 10:03 [HoTT] " Ali Caglayan
2018-11-07 10:31 ` [HoTT] " Paolo Capriotti
2018-11-07 10:35 ` Ulrik Buchholtz
2018-11-07 10:37   ` Ulrik Buchholtz
2018-11-07 11:09   ` Peter LeFanu Lumsdaine
2018-11-07 11:43     ` Ulrik Buchholtz
2018-11-07 11:50       ` Erik Palmgren
2018-11-07 11:51       ` Ulrik Buchholtz
2018-11-07 12:03         ` Erik Palmgren
2018-11-07 12:21           ` Martín Hötzel Escardó
2018-11-07 13:00             ` Erik Palmgren
2018-11-07 13:02             ` Bas Spitters
2018-11-07 13:47               ` Ali Caglayan
2018-11-07 13:53               ` Thomas Streicher
2018-11-07 14:05                 ` Thorsten Altenkirch
2018-11-07 13:58       ` Thorsten Altenkirch
2018-11-07 14:14         ` Ulrik Buchholtz
2018-11-07 14:27           ` Peter LeFanu Lumsdaine
     [not found]             ` <CAOvivQyG1q9=3YoS8hX3bRQK0yi+mpBnJu+rqb3oon0uPLpZ4A@mail.gmail.com>
2018-11-07 20:01               ` Michael Shulman
2018-11-08 21:37               ` Martín Hötzel Escardó [this message]
2018-11-08 21:43                 ` Michael Shulman
2018-11-09  4:43                   ` Andrew Polonsky
2018-11-09 10:18                     ` Ulrik Buchholtz
2018-11-09 10:57                       ` Paolo Capriotti
2018-11-07 14:31           ` Thorsten Altenkirch
2018-11-07 14:05       ` Peter LeFanu Lumsdaine
2018-11-07 14:28         ` Ulrik Buchholtz
2018-11-07 15:35           ` Thomas Streicher
2018-11-07 16:54             ` Thorsten Altenkirch
2018-11-07 16:56               ` Thorsten Altenkirch
2018-11-07 17:31                 ` Eric Finster
2018-11-08 11:58               ` Thomas Streicher
2018-11-08 12:23                 ` [HoTT] " Emily Riehl
2018-11-08 12:28                   ` Emily Riehl
2018-11-08 14:01                     ` Thomas Streicher
2018-11-08 16:10                   ` Thomas Streicher
2018-11-08 14:38                 ` [HoTT] " Michael Shulman
2018-11-08 21:08                   ` Thomas Streicher
2018-11-08 21:30                     ` Michael Shulman
2018-11-09 11:56                       ` Thomas Streicher
2018-11-09 13:46                         ` Michael Shulman
2018-11-09 15:06                           ` Thomas Streicher
2018-11-08 16:01                 ` Thorsten Altenkirch
2018-11-08 19:39                   ` Thorsten Altenkirch
2018-11-07 20:00         ` Michael Shulman
2018-11-08 21:35 ` Martín Hötzel Escardó

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=5645fcc6-2520-498f-8e82-0b335d4eb3f1@googlegroups.com \
    --to=escardo.martin@gmail.com \
    --cc=HomotopyTypeTheory@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).