categories - Category Theory list
 help / color / mirror / Atom feed
From: Vaughan Pratt <pratt@cs.stanford.edu>
To: categories list <categories@mta.ca>
Subject: The division lattice as a category:  is 0 prime?
Date: Wed, 26 Sep 2007 15:01:05 -0700	[thread overview]
Message-ID: <46FAD6A1.8090408@cs.stanford.edu> (raw)

Has the division lattice been organized as a category somewhere in the
literature in a way that accounts somehow for 0?

A simplistic construction is [FinSet^N] denoting the finitary
finite-set-valued functors from the discrete category N.  ("Finitary" in
the sense of being zero almost everywhere.)

Interpreting N as indexing the primes and coproduct as numeric
multiplication, product becomes gcd and the pushout of (a,b) over its
gcd is its lcm.

It is simplistic by virtue of omitting (numeric) 0, which is standardly
placed at the top of the division lattice.  Unlike the rest of the
lattice 0 is not generated from the primes by finite coproducts,
suggesting it needs to feature in some sort of basis for the complete
lattice.

The natural thing would be to remove all but the primes and 0 from the
division lattice and then try to put them back finitarily.  This makes
the starting point the inverted flat CPO N^* where N consists of the
primes and "bottom" * is now at the top, denoting 0.  (That convention
makes N_* the usual flat CPO of natural numbers.)

If I'm not mistaken the completion of N^* under finite coproducts has as
objects two copies of the natural numbers.  Below * is [FinSet^N]
understood as previously.  Above * is FinSet, which was created from *
by completion under coproducts.  This amounts to FinSet + [FinSet^N]
joined at the hip with a shared initial object (numeric 1) and a shared
final object (numeric 0, or *).

 From the Yoneda standpoint the objects are functors from N_* (the usual
CPO) to FinSet.  The ones below are the functors that are 0 at * and
cofinitely many elements of N.  The ones above are 0 at N, with *
unconstrained.

Yoneda's hands are a bit tied here because we are only taking
coproducts.  Closing under finite colimits presumably frees up Yoneda to
produce FinSet x [FinSet^N]  = [FinSet^{N_*}].  This might come in handy
when one wants a system of pairs of numbers (m,n) for which
(m,n)+(m',n') = (m+m',nxn').

Is there some abstract nonsense reason why coproducts produced the sum
(actually pushout over the initial and final objects) while colimits
produced the product?

I arrived at all this after Steve Vickers mentioned on the univalg
mailing list that ring theorists define 0 to be a prime number because
then they could define n to be prime just when the ring Z/nZ extends to
a field.  This got me to wondering how this could be reflected in the
division lattice, which has 0 at the top without however being
considered a prime.  I personally am too old to believe that 0 is a
prime, but I can see where a younger generation could be hoodwinked.
Even with the above understanding however I don't see how 0 can be
understood as just another ordinary prime, any more than bottom is just
another ordinary number in N_*.

Vaughan Pratt




             reply	other threads:[~2007-09-26 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 22:01 Vaughan Pratt [this message]
2007-09-27 17:40 Vaughan Pratt
2007-09-27 21:59 Jeff Egger
2007-09-27 23:36 Vaughan Pratt
2007-09-29 14:49 Bill Lawvere

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=46FAD6A1.8090408@cs.stanford.edu \
    --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).