categories - Category Theory list
 help / color / mirror / Atom feed
From: Sam Staton <sam.staton@cl.cam.ac.uk>
To: Andrej Bauer <andrej.bauer@andrej.com>, <categories@mta.ca>
Subject: Re: Sheaf toposes and chain-complete posets
Date: Tue, 28 Jul 2009 09:35:55 +0100	[thread overview]
Message-ID: <E1MVqBC-0000qO-Vp@mailserv.mta.ca> (raw)

Dear Andrej, when you say "complete" but not "chain-complete", do you
mean "directed complete"?

Here is (I think) an example that is also natural and relevant.

Do you know Andy Pitts' work (with others) on Nominal Sets? The
category of nominal sets is a sheaf topos (the "Schanuel topos", it
is actually Boolean). Andy has done some domain theory in nominal
sets to model a language with dynamic allocation of fresh names,
FreshML.

Fixing an infinite set of "atoms" A, then the category of nominal
sets is a subcategory of the category of actions of the symmetric
group on A (see reference for full definition). The set of atoms has
itself a natural group action. The finite powerset of the nominal set
of atoms, ordered by inclusion, is chain complete, but not directed
complete. Any chain of finite sets can only have finite support, and
is thus necessarily finite. But the full finite powerset is itself
directed, without an upper bound.

I hope that is of some help. Best regards, Sam.

Reference: Section 3 of On a Monadic Semantics for Freshness, M. R.
Shinwell and A. M. Pitts, Theoretical Computer Science 342, 2005.
Available from Andy Pitts' web page. NB "nominal sets" are there
called "FM-sets".

The example I mention appears in Mark Shinwell's PhD thesis, The
Fresh Approach: functional programming with names and binders. http://
www.cl.cam.ac.uk/techreports/UCAM-CL-TR-618.html.


On 27 Jul 2009, at 13:45, Andrej Bauer wrote:

> Dear categorists,
>
> I am trying to wrap my mind around the concept of an (internal)
> chain-complete poset in a sheaf topos. I am failing to come up with an
> example of a poset that is chain-complete but is not complete. The
> precise definitions of "chain-complete" in the internal language are
> as follows.
>
> Suppose (P, <=) is a poset in a topos. For C in Omega^P, let chain(C)
> be the statement
>
>   forall x, y : P, (x in C and y in C) ==> (x <= y or y <= x)
>
> Then P is chain-complete if
>
>   forall C : Omega^P, chain(C) ==> exists x : P, x is the supremum
> of C
>
> where "x is the supremum of C" means the usual thing.
>
> So what does a chain-complete poset which isn't complete look like?
>
> Since I am used to arguing intuitionistically, it would help a lot if
> there were some (possibly infinitary) logical principle or schema that
> is typical of sheaf toposes -- something expressing the local nature
> of validity. Such a principle ought to be invalid in realizability
> toposes, so perhaps it should express or imply cocompleteness (with
> respect to Set). But would that be of any help for arguing in the
> internal language?
>
> With kind regards,
>
> Andrej Bauer
>

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


             reply	other threads:[~2009-07-28  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28  8:35 Sam Staton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-28  5:44 Andrej Bauer
2009-07-28  4:06 Fred E.J. Linton
2009-07-27 12:45 Andrej Bauer

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=E1MVqBC-0000qO-Vp@mailserv.mta.ca \
    --to=sam.staton@cl.cam.ac.uk \
    --cc=andrej.bauer@andrej.com \
    --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).