From: <streicher@mathematik.tu-darmstadt.de>
To: Uwe Egbert Wolter <Uwe.Wolter@uib.no>
Cc: <categories@mta.ca>
Subject: Re: Discrete fibrations vs. functors into Set
Date: Thu, 3 Dec 2020 09:53:23 +0100 [thread overview]
Message-ID: <E1kl1C6-00039o-Sp@rr.mta.ca> (raw)
In-Reply-To: <E1kkeRg-0000Mp-6S@rr.mta.ca>
See pp.16-17 of my notes on fibered cats available from the arxiv.
There is an obvious functor Set^(_) : cat^op -> Cat to which one can apply
the Grothendieck construction.
Moreover, a cartesian functor is a fibered equivalence iff all its fibers
are ordinary equivalences. All this is folklore and just documented in my
notes.
Thomas
> We consider two categories. The first category with objects given by a
> small category B and a functor F:B->Set and morphisms
> (H,alpha):(B,F)->(C,G) given by a functor H:B->C and a natural
> transformation alpha:F=>H;G. The second category has as objects discrete
> fibrations p:E->B and morphisms (H,phi):(E,p)->(D,q:D->C) are given by
> functors H:B->C and phi:E->D such that phi;q=p;H.
>
> 1. Are there any "standard" terms and notations for these categories?
> 2. For both categories we do have projection functors into Cat! Are
> these functors kind of (op)fibrations?
> 3. We know that the Grothendieck construction establishes equivalences
> between corresponding fibers of the two projection functors into Cat. Do
> these fiber-wise equivalences extend to an equivalence between the two
> categories?
>
> Thanks
>
> Uwe
>
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2020-12-03 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 13:53 Uwe Egbert Wolter
2020-12-03 8:53 ` streicher [this message]
2020-12-03 11:10 ` Andrée Ehresmann
[not found] ` <e55e765ce4a17b3a2879f311425c3eb2@unice.fr>
2020-12-04 8:46 ` Clemens Berger
2020-12-04 15:42 Walter P Tholen
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=E1kl1C6-00039o-Sp@rr.mta.ca \
--to=streicher@mathematik.tu-darmstadt.de \
--cc=Uwe.Wolter@uib.no \
--cc=categories@mta.ca \
/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).