From: "Stephen Lack" <S.Lack@uws.edu.au>
To: "categories list" <categories@mta.ca>
Subject: Re: What is the right abstract definition of "connected"?
Date: Fri, 12 Oct 2007 09:05:14 +1000 [thread overview]
Message-ID: <E1Ig9Br-00021q-9h@mailserv.mta.ca> (raw)
Dear Vaughan,
Lawvere and Janelidze have each argued for many years (in somewhat
different contexts) that notions of connectedness and cohesion should
be understood as relative. This impacts on both your questions: how
should connectedness be defined, and what sort of answers should be
allowed
to the question ``how many connected components does X have?'' --- the
second question becomes ``what is the codomain of the pi_0 functor?''
Steve Vickers mentioned the example Set^2. He said that the terminal
object
(1,1) is obviously connected. But it is equally obviously not connected:
(1,1)=(1,0)+(0,1). The latter point of view comes from thinking of Set^2
as a Set-topos, where the connected components functor becomes the
functor
Set^2-->Set given by homming out of (1,1). The former point of view
comes
from thinking of Set^2 as defined over itself; then, as Steve says,
(1,1)
becomes almost tautologically connected, since pi_0 is just the identity
functor Set^2-->Set^2.
If crng is the category of finitely presentable commutative rings with
no
non-trivial nilpotents, then there is a lovely pi_0:crng^op-->set_f. For
in this case every ring R splits as R_1 x R_2 x ... x R_n, where the R_i
have no non-trivial idempotents. It is these R_i which are your
connected
components. For a larger category of commutative rings, you have to
expand
your notion of connected component to something like Stone spaces.
For a locally connected topos E, defined over S, the inverse image
functor
e^*:S-->E has not just a right adjoint e_* but also a left adjoint e_!,
which
serves as pi_0. But one can describe just in terms of e_! -| e^* (i.e.
without
mention of e_*, and without all of the topos structure) the sorts of
abstract
properties needed for a good pi_0. This is the starting point for
Janelidze's Galois theory.
If E is infinitarily extensive (small coproducts, which are stable under
pullback
and disjoint), then a good notion of connectedness of an object X is
that
the hom-functor E(X,-):E-->Set preserves coproducts. This includes the
locally
connected topos case, which in turn includes your case of directed
graphs.
The case of crng is a finitary version.
Regards,
Steve Lack.
next reply other threads:[~2007-10-11 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 23:05 Stephen Lack [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 18:48 Marta Bunge
2007-10-10 22:08 Vaughan Pratt
2007-10-10 20:43 Vaughan Pratt
2007-10-10 12:00 Marta Bunge
2007-10-09 14:43 Jonathon Funk
2007-10-09 9:31 Steve Vickers
2007-10-08 20:18 Vaughan Pratt
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=E1Ig9Br-00021q-9h@mailserv.mta.ca \
--to=s.lack@uws.edu.au \
--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).