From: Chris Heunen <heunen@comlab.ox.ac.uk>
To: categories@mta.ca
Subject: Re: "compact", "rigid", or "autonomous"?
Date: Fri, 14 May 2010 16:34:41 +0100 [thread overview]
Message-ID: <E1ODKrz-000692-T6@mailserv.mta.ca> (raw)
In-Reply-To: <E1OCuLU-0002QV-Qd@mailserv.mta.ca>
> I don't know if this is what people were thinking when they first
> applied "compact" to categories
As far as I'm aware, the terminology "compact" for categories came about
via representation theory: the finite-dimensional unitary
representations of a group form a category with certain properties, and
the group can be reconstructed from that category when the group is
compact. It seems the name transferred from groups to such categories.
But I wouldn't claim historical correctness; perhaps someone has the
definitive word about the origin of this terminology?
Best,
Chris
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
prev parent reply other threads:[~2010-05-14 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 17:37 John Baez
2010-05-14 15:34 ` Chris Heunen [this message]
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=E1ODKrz-000692-T6@mailserv.mta.ca \
--to=heunen@comlab.ox.ac.uk \
--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).