Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Ulrik Buchholtz <ulrikbuchholtz@gmail.com>
To: Homotopy Type Theory <HomotopyTypeTheory@googlegroups.com>
Subject: Re: [HoTT] Re: Precategories, Categories and Univalent categories
Date: Wed, 7 Nov 2018 03:43:32 -0800 (PST)	[thread overview]
Message-ID: <1a3288ec-ca0e-48ce-80ad-9cad01f56845@googlegroups.com> (raw)
In-Reply-To: <CAAkwb-k8aKxP6N8yjOtwMCbXm8iExr5SGgeWbuobbhOKCEXb5Q@mail.gmail.com>


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

I'm a bit confused by your message, Peter: HoTT doesn't have a naive set 
interpretation and is inconsistent with UIP, so I'm not sure how that 
should guide us. (Maybe if we're working in good old (agnostic?) MLTT?)

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.)

On Wednesday, November 7, 2018 at 12:10:10 PM UTC+1, Peter LeFanu Lumsdaine 
wrote:
>
> Ulrik’s email nicely lays out the three key notions (pre-category, strict 
> category, univalent category), and the argument for the 
> Ahrens–Kapulkin–Shulman / HoTT book terminology, with “category” meaning 
> “univalent category” by default.
>
> For my part I lean the other way: I think it’s too radical to use 
> “category” for a definition which doesn’t come out equivalent to the 
> traditional definition under the naïve set interpretation (or under the 
> addition of UIP to the type theory).  Choosing terminology that actively 
> clashes with traditional terminology makes it much harder to compare 
> statements in HoTT with their classical analogues, and see what difference 
> HoTT really makes to the development of topics.
>
> Based on that criterion, I strongly prefer taking category to mean 
> “precategory”.  A big payoff from this is that if you formalise something 
> using “category ” to mean “precategory” in type theory without assuming UA, 
> then you can read the result either as valid in HoTT, or (under the 
> set-interpretation) as ordinary arguments in classical category theory, 
> with all the terms meaning just what they traditionally would.
>
> Univalence of categories is an important and powerful property, but not an 
> innocuous one; it changes the character of the resulting “category theory” 
> in interesting ways.  Making the restriction to univalent categories tacit 
> is misleading to readers who aren’t fully “insiders”, and obscures 
> understanding its effects.
>
> –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.
For more options, visit https://groups.google.com/d/optout.

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

  reply	other threads:[~2018-11-07 11:43 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 [this message]
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ó
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=1a3288ec-ca0e-48ce-80ad-9cad01f56845@googlegroups.com \
    --to=ulrikbuchholtz@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).