categories - Category Theory list
 help / color / mirror / Atom feed
From: Jeff Egger <jeffegger@yahoo.ca>
To: categories@mta.ca
Subject: Re: Teaching Category Theory
Date: Tue, 4 Sep 2007 12:30:00 -0400 (EDT)	[thread overview]
Message-ID: <E1ISiuA-00053K-HH@mailserv.mta.ca> (raw)

--- Michael Shulman <shulman@math.uchicago.edu> wrote:

> My guess would be that it's because for non-category theorists, many
> (perhaps most) categories which arise in practice are enriched (over
> something more exotic than Set), while few are internal (to something
> more exotic than Set). 

I'm not sure I agree with that: internal groupoids, at the very least,
show up in a variety of situations which non-category theorists can be,
and are, interested in.  Perhaps one of the reasons why some people try
to deal with groupoids as if they weren't a special case of categories
is because they never thought of categories in any other way than as a 
mass of hom-sets.

> Even when working over Set, I think it's fair
> to say that the vast majority of categories arising in mathematical
> practice are locally small.

Now I do think there is a good reason for this, which is the fact 
that in functorial semantics (by which I don't just mean the original, 
universal-algebraic, case), the domain category is typically small.
Raising to a small power does not destroy local smallness.

> Since in general, neither enriched nor internal category theory is a
> special case of the other, it doesn't seem justified to me to consider
> either one as "more primitive". 

I agree with this entirely, of course.  It follows that, in a first 
course on category theory, one should present both styles of definition 
as soon as possible.  This, in turn, suggests (but does not prove) that 
one should not sweep size distinctions under the carpet.  

> Actually, currently my favorite level of generality is something I
> call a "monoidal fibration".  Roughly, the idea is that you have two
> different "base" categories, S and V, such that the object-of-objects
> comes from S while the object-of-morphisms comes from V.  When S and V
> are the same, you get internal categories, and when S=Set, you get
> classical enriched categories.  This could be regarded as "explaining"
> the coincidence of internal and enriched categories for V=Set.  I
> wrote a bit about this at the end of "Framed Bicategories and Monoidal
> Fibrations" (arXiv:0706.1286), but I intend to say more in a
> forthcoming paper.

I look forward to it!

Cheers,
Jeff.




             reply	other threads:[~2007-09-04 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 16:30 Jeff Egger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-09 11:40 Ronnie Brown
2007-09-05 22:36 Michal Przybylek
2007-09-05 13:09 Michal Przybylek
2007-09-01 23:36 Michael Shulman
2007-08-31 13:37 Jeff Egger
     [not found] <200708311017.17603.spitters@cs.ru.nl>
2007-08-31 13:34 ` Jeff Egger
2007-08-31  9:55 Steve Vickers
2007-08-30 17:50 Jeff Egger
2007-08-28  1:04 Vaughan Pratt
2007-08-27  1:58 Tom Leinster

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=E1ISiuA-00053K-HH@mailserv.mta.ca \
    --to=jeffegger@yahoo.ca \
    --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).