categories - Category Theory list
 help / color / mirror / Atom feed
From: Vaughan Pratt <pratt@cs.stanford.edu>
To: categories list <categories@mta.ca>
Subject: Re: "Kantor dust"
Date: Mon, 02 Feb 2009 15:43:16 -0800	[thread overview]
Message-ID: <E1LUM8p-0003RT-Dy@mailserv.mta.ca> (raw)



Prof. Peter Johnstone wrote:
> A topos with a Cantor set object (i.e. a final coalgebra for FX = X+X)
> necessarily has a natural number object. Observe that the Cantor set K
> necessarily has a point (since 1 has an F-coalgebra structure), so the
> isomorphism K+K \cong K yields a monomorphism K \to K and a point
> disjoint from its image. From there on, use Corollary D5.1.3 in the
> Elephant.

Oh, of course: pick a point out of one half and recurse on the other.
Very plausible that that would work in any topos, but it's great to be
able to stare at an actual proof.  Thank you!

How about the converse: does N entail K?  In any topos with NNO N the
underlying object of the final coalgebra of FX = X+X is presumably 2^N.
  Does the Elephant prove that 2^N can be made a final coalgebra of X+X?

And if so, what other coalgebras are brought into existence by N?  For
example can N^N be made a doubly inductive (inductive-coinductive)
coalgebra encoding the lexicographic order that gives N^N the order type
of the nonnegative reals?  That would give a pretty direct construction
of the usual topology of the real line in any topos with NNO.  (This is
the one-dimensional conception of the continuum, as opposed to the
zero-dimensional conception preferred by descriptive set theorists, who
take the continuum to be N^N with the ordinary product topology.)

Does \Omega^N as the final coalgebra for FX = \Omega x X ever arise in
practical situations where \Omega is more than just a pointed version of
1+1 as in Set, e.g. graph theory?

Vaughan Pratt




             reply	other threads:[~2009-02-02 23:43 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 23:43 Vaughan Pratt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-13  5:40 Vaughan Pratt
2009-02-12  9:05 Bas Spitters
2009-02-12  9:00 Prof. Peter Johnstone
2009-02-12  4:25 Toby Bartels
2009-02-12  4:10 Toby Bartels
2009-02-12  4:05 Toby Bartels
2009-02-11 23:51 Vaughan Pratt
2009-02-11 22:16 Bhupinder Singh Anand
2009-02-11 19:56 Greg Meredith
2009-02-11 17:53 Vaughan Pratt
2009-02-11 17:33 Prof. Peter Johnstone
2009-02-11 16:11 Michael Shulman
2009-02-11 15:55 Toby Kenney
2009-02-11  9:01 Vaughan Pratt
2009-02-11  9:01 Vaughan Pratt
2009-02-11  5:49 Vaughan Pratt
2009-02-11  0:13 Toby Bartels
2009-02-10 22:18 Prof. Peter Johnstone
2009-02-10 21:05 Greg Meredith
2009-02-10 19:04 Steve Stevenson
2009-02-10  9:54 Vaughan Pratt
2009-02-09 22:47 Prof. Peter Johnstone
2009-02-09 22:18 Dusko Pavlovic
2009-02-09  1:30 Toby Bartels
2009-02-09  0:31 Toby Bartels
2009-02-08 20:36 Steve Stevenson
2009-02-08 15:03 Paul Taylor
2009-02-08 14:51 Prof. Peter Johnstone
2009-02-08 11:56 gcuri
2009-02-07 22:58 Toby Bartels
2009-02-07 17:18 Prof. Peter Johnstone
2009-02-07  0:37 Vaughan Pratt
2009-02-05 21:44 Toby Bartels
2009-02-04 20:24 Vaughan Pratt
2009-02-03 17:59 Prof. Peter Johnstone
2009-02-01 18:53 Prof. Peter Johnstone
2009-02-01  0:06 Vaughan Pratt
2009-01-31 10:25 spitters
2009-01-31  4:35 Galchin, Vasili
2009-01-30 22:40 Galchin, Vasili
2009-01-30 21:52 Bas Spitters
2009-01-30  7:18 Galchin, Vasili
2009-01-30  7:18 Galchin, Vasili

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=E1LUM8p-0003RT-Dy@mailserv.mta.ca \
    --to=pratt@cs.stanford.edu \
    --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).