categories - Category Theory list
 help / color / mirror / Atom feed
From: street@mpce.mq.edu.au (Ross Street)
To: categories@mta.ca
Subject: re: co-
Date: Tue, 7 Jul 1998 10:49:43 +1000	[thread overview]
Message-ID: <199807070048.KAA19559@macadam.mpce.mq.edu.au> (raw)

While our insecurities about "co-" are being aired, I thought I should
admit to even more worries in the case of 2-categories (or bicategories)!
In these terminological matters, I have given up on linguistic correctness
and have also almost given up worrying about mathematical consistency.

Here is the difficulty. Motivation for 2-category theory comes from (at
least) two different directions which often lead to the same basic concepts
yet with different suggestions for terminology for the three other dual
concepts. Each concept has a co-, op-, and coop-version but the good choice
of op or co is not clear at all.

First motivation: We can take the view that our 2-category is foremost a
category with the 2-cells as extra structure (like homotopies in Top).
Then, for example, as pointed out by John Gray in the La Jolla 1965 volume,
Grothendieck was wrong in using "cofibration" for the *2-cell*-reversing
dual of fibration. Compare the situation in  Top  where cofibrations are
the *arrow*-reversing dual of fibrations.  So this leads to "opfibration"
for the *2-cell*-reversing dual of "fibration" (this is unnecessary in  Top
since homotopies are invertible).  However, Grothendieck's terminology has
stuck in some literature.  Using this first motivation, we define products
and coproducts of objects in a 2-category as we would in a category plus an
extra 2-cell condition.

Second motivation: We think of our 2-category  K  as a place to develop
category theory so that arrows f : U --> A  into an object  A  of  K  are
thought of as generalised objects of  A,  and 2-cells into  A  are
generalised arrows of  A.  Take a notion such as monad on  A.  From this
motivation, reversing *2-cells* in  K,  we should get the notion of
"comonad".  This terminology is in conflict with the doctrine developed on
the basis of the first motivation. Of course, "monad" is invariant under
*arrow*-reversal, but there are other concepts which are not.

--Ross






             reply	other threads:[~1998-07-07  0:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-07  0:49 Ross Street [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-15 13:50 co- Robert Dawson
1998-07-08 19:39 co- Fred E J Linton
1998-07-09  4:04 ` co- Vaughan Pratt
1998-07-08 11:10 co- Koslowski
1998-07-06 18:15 co- Paul Taylor
1998-07-04 17:40 co- Dr. P.T. Johnstone
1998-07-06 16:02 ` co- Michael Barr
1998-07-04 17:30 co- Dr. P.T. Johnstone
1998-07-04 15:36 co- John R Isbell
1998-07-03 11:39 co- Paul Taylor
1998-07-03 17:09 ` co- James Stasheff
1998-07-03 19:40   ` co- Graham White
1998-07-03 19:28 ` co- Michael Barr
1998-07-04 14:09   ` co- James Stasheff
1998-07-03 19:37 ` co- John R Isbell
1998-07-04 14:07   ` co- James Stasheff
1998-07-04 15:02 ` co- Peter Selinger
1998-07-05 11:52   ` co- James Stasheff
1998-07-05 18:10     ` co- Peter Selinger
1998-07-05 21:24     ` co- John Duskin
1998-07-04 17:33 ` co- John R Isbell

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=199807070048.KAA19559@macadam.mpce.mq.edu.au \
    --to=street@mpce.mq.edu.au \
    --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).