Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Michael Shulman <shulman@sandiego.edu>
To: Thomas Streicher <streicher@mathematik.tu-darmstadt.de>
Cc: Thorsten Altenkirch <Thorsten.Altenkirch@nottingham.ac.uk>,
	 Ulrik Buchholtz <ulrikbuchholtz@gmail.com>,
	homotopytypetheory@googlegroups.com
Subject: Re: [HoTT] Re: Precategories, Categories and Univalent categories
Date: Fri, 9 Nov 2018 05:46:29 -0800	[thread overview]
Message-ID: <CAOvivQzWqb_wcEBEVZTaSf_B7X0vvEV_4ZfLPDgzhBcSm=qi0w@mail.gmail.com> (raw)
In-Reply-To: <20181109115653.GA7030@mathematik.tu-darmstadt.de>

Right, the *forward* direction requires either equality of objects or
using "essential fibers" instead of fibers.  That's what I meant by
saying a displayed category is a "refinement" of a functor: you can
make a functor from a displayed category, but the opposite direction
is harder.  That doesn't mean that you can't express composition of
functors in terms of displayed categories: it just means you can't (or
shouldn't) do it in the naive way by first making your displayed
categories into functors, composing them, and then going back to a
displayed category.  Instead you just have to "lift" functor
composition to displayed categories in the same way that we lift
function composition to Sigma-types.

Suppose D is a displayed category over C, with types of objects obD(x)
: Type and types of morphisms D(f) : D(x) -> D(y) -> Type for x:ob(C)
and f:hom_C(x,y).  Then we can form a total category Sigma(C)D whose
type of objects is Sigma(x:ob(C)) obD(x) and whose types of morphisms
are similar Sigma-types.  Now suppose we have a further displayed
category E over Sigma(C)D.  Then applying associativity of
Sigma-types, we can construct a displayed category Sigma(D)E over C,
with type of objects ob(Sigma(D)E)(x) = Sigma(y:obD(x))obE(x,y) and so
on, whose total category is equivalent (indeed, definitionally
isomorphic, if Sigma-types have definitional beta and eta) to
Sigma(Sigma(C)D)E such that its projection functor corresponds to the
composite of the two functors.
On Fri, Nov 9, 2018 at 3:56 AM Thomas Streicher
<streicher@mathematik.tu-darmstadt.de> wrote:
>
> Benedikt and Peter essentially employ an old result of Benabou saying that
> functors to BB correspond normalized lax functor from BB^op to Dist,
> the bicategory of distributors. But, obviously, the forward direction requires
> equality of objects.
> Accordingly, they can't express composition of functors in terms of
> the associated normalized lax functors.
>
> Even classically, going from fibrations to indexed categories involves
> choice. But going from functors to normalized lax functors just
> requires equality of objects.
>
> Thomas
>
> --
> 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.

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

  reply	other threads:[~2018-11-09 13:46 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ó
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 [this message]
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='CAOvivQzWqb_wcEBEVZTaSf_B7X0vvEV_4ZfLPDgzhBcSm=qi0w@mail.gmail.com' \
    --to=shulman@sandiego.edu \
    --cc=Thorsten.Altenkirch@nottingham.ac.uk \
    --cc=homotopytypetheory@googlegroups.com \
    --cc=streicher@mathematik.tu-darmstadt.de \
    --cc=ulrikbuchholtz@gmail.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).