From: Aleks Kissinger <aleks0@gmail.com>
To: categories <categories@mta.ca>
Subject: Re: Functors and limits
Date: Tue, 26 Apr 2011 22:12:36 +0100 [thread overview]
Message-ID: <E1QEs3H-0006jm-Me@mlist.mta.ca> (raw)
In-Reply-To: <BANLkTi=j=2CWOQqb_=bPMWVkp6U8EtPHEQ@mail.gmail.com>
Correction:
1. reflects limits if F*(k) contains only limiting cones
On 26 April 2011 16:15, Aleks Kissinger <aleks0@gmail.com> wrote:
> Dear categorists,
>
> The "standard" definitions for functors doing nice things with limits
> have always seemed a bit clumsy to me. Here's what I think is quite a
> natural way to unroll the quantifiers:
>
> For a functor F : C --> D and a cone k, let F*(k) be the class of all
> cones k' in C s.t. F(k') = k.
>
> For all limiting cones k in D, F....
> 1. reflects limits if F*(k) != {} implies F*(k) contains a limiting cone
> 2. lifts limits if F*(k) contains a limiting cone
> 3. lifts limits uniquely if F*(k) contains exactly 1 limiting cone,
> but possibly other cones
> 4. creates limits if F*(k) = {k'}, for k' a limiting cone
>
> This seems to read much more cleanly than the usual, quantifier-laden
> version that seems to be in most standard texts. Of course, they're
> all still there in the def, but there is no ambiguity in how they
> nest. For example, the difference in 3 in 4 ranges from subtle to
> all-but-invisible in most of the places I've seen them defined. Does
> this definition, or some close relative exist somewhere? If not, is it
> problematic somehow? For example, do you get into trouble when F*(k)
> is a proper class?
>
> Thanks!
> Aleks
>
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next parent reply other threads:[~2011-04-26 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTi=j=2CWOQqb_=bPMWVkp6U8EtPHEQ@mail.gmail.com>
2011-04-26 21:12 ` Aleks Kissinger [this message]
2011-04-26 15:15 Aleks Kissinger
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=E1QEs3H-0006jm-Me@mlist.mta.ca \
--to=aleks0@gmail.com \
--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).