categories - Category Theory list
 help / color / mirror / Atom feed
From: Vaughan Pratt <pratt@cs.stanford.edu>
To: categories@mta.ca
Subject: Re: The Idea of Structure as Data and Conditions
Date: Tue, 29 May 2012 23:26:17 -0700	[thread overview]
Message-ID: <E1SZfNz-0005OG-QH@mlist.mta.ca> (raw)
In-Reply-To: <E1SZ8q4-0004H2-2Y@mlist.mta.ca>

On 5/27/2012 11:00 PM, FEJ Linton wrote:
> Virtually no one ever wants to restrict attention to functions that respect
> (preserve or reflect) membership (other than "preserve" between ordinals).

Wouldn't that depend on the context in which membership arises?
Certainly group homomorphisms aren't expected to respect membership of
group elements in groups, but neither are they expected to respect the
composition of group homomorphisms equipping the category Grp.

The latter kind of respect is accorded categories by functors between
them.  By the same token the former kind is accorded elementary models
of set theory by elementary homomorphisms between them, the appropriate
counterpart of functors in that context.  Elementary homomorphisms
preserve elementary structure, which in the case of models of set theory
has membership as a basic part.  ZFC structure is very different (at the
bottom few layers) from the algebraic-in-Grph structure of the category
Set, which has function composition as a basic part.

For those who prefer algebra to logic, Joyal, Moerdijk and Awodey offer
Algebraic Set Theory, AST, as a middle ground here.  This replaces
membership by (set-sized) unions and singleton a |--> {a}.
Homomorphisms then have their usual algebraic meaning, which is arguably
less fiddly than for elementary maps.  Union allows the subset relation
to be defined as X <= Y  iff  X U Y = Y, from which one can then define
membership X e Y as {X} <= Y.  Both relations are preserved by the
homomorphisms of AST.  For a crash course see Awodey's

http://www.andrew.cmu.edu/user/awodey/preprints/astIntroFinal.pdf

ZFC, Set, and AST differ only at the bottom few layers, above which
foundational variations are tied to more fundamental issues involving
Choice vs. Determinacy etc.  One might compare the differences at the
bottom with the wave-particle dichotomy in quantum mechanics or the
event-state and time-information dichotomies in concurrency that I spoke
on at Physics & Computation 1992 and 1994, see

http://boole.stanford.edu/pub/ph94.pdf
and the earlier (1992)
http://boole.stanford.edu/pub/ql.pdf

Or at least that's how it all looks to this outsider.  Happy to be
corrected on details I've got wrong.

Vaughan Pratt


[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


  parent reply	other threads:[~2012-05-30  6:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 22:09 Ellis D. Cooper
2012-05-26 23:48 ` Michael Barr
2012-05-27 18:16   ` Eduardo J. Dubuc
2012-05-28  6:00   ` FEJ Linton
2012-05-29 13:28     ` Staffan Angere
2012-05-30  6:26     ` Vaughan Pratt [this message]
2012-05-27 13:02 ` Charles Wells
     [not found] ` <CABZOOqZ54NtG1n3K4f8o6mMRSgZ_2yVjE6S+-UWkQSO_PXi1tQ@mail.gmail.com>
2012-05-27 13:06   ` Charles Wells
2012-05-27 23:25 ` Vaughan Pratt
2012-05-29  3:15 Fred E.J. Linton
2012-05-29 13:28 ` Colin McLarty

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=E1SZfNz-0005OG-QH@mlist.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).