From: Eduardo Dubuc <edubuc@dm.uba.ar>
To: categories@mta.ca
Subject: Re: locally cartesian closed categories
Date: Tue, 9 Oct 2007 11:18:18 -0300 (ART) [thread overview]
Message-ID: <E1IfPpA-0001FN-1c@mailserv.mta.ca> (raw)
hi,
yet another point in favor that terminal object and products should not
be mandatory in locally cartesian closed categories:
terminal (or products) implies connection, fiber products don't.
compare with the notion of cofilter category (axiom similar to existence
of products), is connected, while pseudofiltered (axiom similar to
existence of fiber products), is not connected.
this is essentially the difference between filterness and cofilterness,
with all what it means
same thing, fiber products and not products are in the essence of the
notion of locally cartesian closedness
ps: congratulations to Bob R., I fully agree with all the good things that
were said recently about his handling of this list (not an easy job !).
eduardo dubuc
next reply other threads:[~2007-10-09 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 14:18 Eduardo Dubuc [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-09 7:34 Lutz Schroeder
2007-10-08 15:28 Paul Taylor
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=E1IfPpA-0001FN-1c@mailserv.mta.ca \
--to=edubuc@dm.uba.ar \
--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).