categories - Category Theory list
 help / color / mirror / Atom feed
From: Steve Vickers <s.j.vickers@cs.bham.ac.uk>
To: "Jean Bénabou" <jean.benabou@wanadoo.fr>
Cc: Categories <categories@mta.ca>
Subject: Re: Composition of Fibrations
Date: Mon, 21 Jul 2014 21:06:29 +0100	[thread overview]
Message-ID: <E1X9euz-00030B-S7@mlist.mta.ca> (raw)
In-Reply-To: <32AB43B0-58DA-4375-A4FD-6C84F4E527EA@wanadoo.fr>

Dear Jean,

Street's result is as follows. The arrow p: E -> B is a 0-fibration over B if and only if the arrow
   p~ : ΦE -> p/B
corresponding to the 2-cell

ΦE  --pd1--> B
|                      ||
d0                   ||
|         pλ  =>   ||
v                     ||
E   --p------> B

has a left adjoint with unit an isomorphism.

Here ΦE = E/E and p/B are comma objects, d0 and d1 are projections, and λ is the canonical 2-cell in a comma square (in this case for ΦE). 0-fibration is opfibration.

Regards,

Steve.

> On 21 Jul 2014, at 19:02, Jean Bénabou <jean.benabou@wanadoo.fr> wrote:
> 
> Dear Steve,
> 
> Thank you for your prompt  answer. 
> 
> Let me first clarify a possible ambiguity. 
> The Street fibrations I was referring to are defined in his paper: 
> Fibrations in bicategories.  Cahiers Top. Geom. Diff. 21 (1980)
> When the bicategory is Cat, they do not coincide with the usual fibrations. In particular every equivalence is a Street fibration.
> 
> There might be another ambiguity about what you call the Chevalley criterium. Could you please tell me with precision what it is (I assume p: B -> A is a map in a 2-category C with comma objects and 2-pullbacks)
> 
> I shall come back to mathematical questions as soon as these two ambiguities are solved.
> 
> Best wishes,
> 
> Jean
> 

[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


  parent reply	other threads:[~2014-07-21 20:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20 16:18 Jean Bénabou
2014-07-21 12:30 ` Steve Vickers
     [not found] ` <3E52EFB7-7955-47B1-9B00-9F6F6152BBC1@cs.bham.ac.uk>
2014-07-21 18:02   ` Jean Bénabou
     [not found]   ` <32AB43B0-58DA-4375-A4FD-6C84F4E527EA@wanadoo.fr>
2014-07-21 20:06     ` Steve Vickers [this message]
     [not found]     ` <6EFFC44F-E933-412B-89F2-C33B598D78B0@cs.bham.ac.uk>
2014-07-22  4:24       ` Jean Bénabou
     [not found]       ` <9747FDFD-FF71-4ACE-8DD3-538462A1B283@wanadoo.fr>
2014-07-22 14:55         ` Steve Vickers
     [not found]         ` <C1C93FE1-09FF-43C4-A6DA-D0883440A2FC@cs.bham.ac.uk>
2014-07-22 21:52           ` Ross Street
2014-07-22 23:25 ` Eduardo J. Dubuc
2014-07-30 15:06 ` cleavages and choice Thomas Streicher
     [not found] ` <20140730150643.GC19613@mathematik.tu-darmstadt.de>
2014-07-30 17:56   ` Jean Bénabou
2014-08-01 16:47     ` Eduardo J. Dubuc
2014-08-02 10:58       ` Marco Grandis
2014-08-03 15:17         ` Paul Levy
2014-08-03 16:30         ` Toby Bartels
2014-08-04 14:47           ` Marco Grandis
     [not found]       ` <82157841-9DE2-4D99-8533-57AAB99CD236@dima.unige.it>
2014-08-02 15:24         ` Eduardo J. Dubuc
     [not found]     ` <53DBC493.5060700@dm.uba.ar>
2014-08-01 17:52       ` Jean Bénabou
2014-08-03  9:22     ` Thomas Streicher
2014-08-03 20:41       ` Eduardo J. Dubuc

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=E1X9euz-00030B-S7@mlist.mta.ca \
    --to=s.j.vickers@cs.bham.ac.uk \
    --cc=categories@mta.ca \
    --cc=jean.benabou@wanadoo.fr \
    /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).