categories - Category Theory list
 help / color / mirror / Atom feed
From: Steve Vickers <s.j.vickers@cs.bham.ac.uk>
To: streicher@mathematik.tu-darmstadt.de
Cc: Paul Blain Levy <P.B.Levy@cs.bham.ac.uk>,
	categories list <categories@mta.ca>
Subject: Re: V-included categories
Date: Thu, 4 Jan 2018 20:47:18 +0000	[thread overview]
Message-ID: <E1eXUfH-0006fV-3a@mlist.mta.ca> (raw)
In-Reply-To: <20180104110046.GA24344@mathematik.tu-darmstadt.de>

Dear Thomas,

What I'm curious to understand is how inevitable is a certain practical behaviour of universes. In many situations we know they are foundationally necessary, but we still seek ways to disregard them in everyday mathematics.

If we try to use generalized spaces as our prime notion of collection, instead of sets, it begins to look different. We still have universes of a kind. For example the object classifier is a universe whose elements are sets (discrete spaces). But one would not make the mistake of thinking it is a set itself, as it has a non-discrete topology - it even has non-identity specialization morphisms in functions between sets. There are various other universes  for various other kinds of spaces, such as the Boolean algebra classifier for Stone spaces. The different universes represent qualitative distinctions,  not just one of "size".

As you know, I'm trying to do something along those lines but based on arithmetic universes instead of Grothendieck toposes. 

All the best,

Steve.

> On 4 Jan 2018, at 11:00, streicher@mathematik.tu-darmstadt.de wrote:
> 
> Dear Steve at al.
> 
> I think in one or the other form universes are inevitable be they type
> or set theoretical. Of course, you can do category over fairly general
> bases like finite limit categories (as Benabou developed some time ago).
> But then you are bound to work externally since one can speak about a
> fibration in the internal language of its base in an only very
> restricted way.
> 
> Thomas



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


  parent reply	other threads:[~2018-01-04 20:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01 13:10 Paul Blain Levy
2018-01-01 18:28 ` Paul Blain Levy
2018-01-01 21:14 ` Eduardo Julio Dubuc
     [not found] ` <e962e844-fa2d-5a56-e3e7-be308a483c12@dm.uba.ar>
2018-01-01 22:46   ` Paul Blain Levy
2018-01-02 18:40 ` rosicky
2018-01-02 19:15 ` Michael Shulman
     [not found] ` <03876a66-f7ee-a161-091c-32944a0d8556@dm.uba.ar>
2018-01-03  6:44   ` Paul Blain Levy
     [not found] ` <E1eWtjA-0006aj-48@mlist.mta.ca>
     [not found]   ` <918B0A9E-DFD0-4033-AB7A-1A8A364DB8A9@cs.bham.ac.uk>
     [not found]     ` <20180104110046.GA24344@mathematik.tu-darmstadt.de>
2018-01-04 20:47       ` Steve Vickers [this message]
     [not found] ` <5c1ec079-335b-5609-9cb7-ae4e519f6716@dm.uba.ar>
2018-01-04 21:20   ` Thomas Streicher
     [not found] ` <C16D1DBE-89F3-42EC-86A0-B69B5DBF5713@cs.bham.ac.uk>
2018-01-04 21:30   ` Thomas Streicher
     [not found] ` <E1eWtkf-0006d1-O1@mlist.mta.ca>
2018-01-04 23:28   ` Richard Williamson

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=E1eXUfH-0006fV-3a@mlist.mta.ca \
    --to=s.j.vickers@cs.bham.ac.uk \
    --cc=P.B.Levy@cs.bham.ac.uk \
    --cc=categories@mta.ca \
    --cc=streicher@mathematik.tu-darmstadt.de \
    /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).