From: Colin McLarty <colin.mclarty@case.edu>
To: Categories list <categories@mta.ca>
Cc: "Eduardo J. Dubuc" <edubuc@dm.uba.ar>
Subject: Re: isomorphisms
Date: Sun, 30 May 2010 11:11:45 -0400 [thread overview]
Message-ID: <E1OIsMT-0005X7-8L@mailserv.mta.ca> (raw)
In-Reply-To: <E1OIjRj-0006J0-RS@mailserv.mta.ca>
2010/5/29 Eduardo J. Dubuc <edubuc@dm.uba.ar>
Expresses my main point when I quoted Grothendieck on equivalence and
isomorphism.
> isomorphisms appear not only in examples but are essential also in the
> theory.
> For example Grothendieck defines limits and colimits of categories (as
> universal pseudocones) in SGA4 by means of an isomorphism of categories.
> Same for toposes.
When AG says "none of the equivalences we meet in practice are
isomorphisms" he has in mind lots of examples that I will not even try
to survey. (For a really simple one, the category of sheaves defined
as espaces etales on on a topological space versus the category of
sheaves defined as suitable functors on the site of open subsets.)
But when he defines functor categories, or derived categories, and a
lot of other things like that, he defines them up to unique
isomorphism over the data. A topos E will often be defined only up to
equivalence. But, given E, its derived category is defined up to
unique isomorphism and one constantly uses the fact that various
induced functors are isomorphisms.
AG's practice constantly distinguishes isomorphisms from equivalences,
and thus distinguishes identity of objects from isomorphism of them.
best, Colin
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2010-05-30 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 21:18 isomorphisms Eduardo J. Dubuc
2010-05-30 15:11 ` Colin McLarty [this message]
2010-05-31 2:51 ` isomorphisms Michael Shulman
2010-06-01 3:26 ` Equality and fibration Joyal, André
2010-06-02 9:34 ` Prof. Peter Johnstone
2010-06-01 12:57 ` Peter LeFanu Lumsdaine
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=E1OIsMT-0005X7-8L@mailserv.mta.ca \
--to=colin.mclarty@case.edu \
--cc=categories@mta.ca \
--cc=edubuc@dm.uba.ar \
/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).