categories - Category Theory list
 help / color / mirror / Atom feed
From: "Joyal, André" <joyal.andre@uqam.ca>
To: Michael Shulman <shulman@sandiego.edu>, David Yetter <dyetter@ksu.edu>
Cc: "categories@mta.ca" <categories@mta.ca>
Subject: Re: Grothendieck toposes
Date: Sun, 30 Oct 2016 19:39:10 +0000	[thread overview]
Message-ID: <E1c1I98-0007Rj-60@mlist.mta.ca> (raw)
In-Reply-To: <E1c0vQq-0004Eq-5b@mlist.mta.ca>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

Dear All,

The difference between a Grothendieck topos and an elementary topos
is like the difference between a "frame"(= a locale) and a Heyting algebra.

A Grothendieck topos should be called a "topos",
whereas an elementary topos could be called a "logical topos".

Best regards,
André

________________________________________
From: Michael Shulman [shulman@sandiego.edu]
Sent: Saturday, October 29, 2016 11:06 PM
To: David Yetter
Cc: categories@mta.ca
Subject: categories: Re: Grothendieck toposes

I would tend to assume that a "Grothendieck topos" is one bounded over
"Set", whatever the current meaning of "Set" is, and in particular
whether or not "Set" is classical.  Thus, when working in the internal
language of an arbitrary topos S, I would say "Grothendieck topos" to
mean what *externally* to S would be called a bounded S-topos.

On Fri, Oct 28, 2016 at 12:08 PM, David Yetter <dyetter@ksu.edu> wrote:
> I, for one, would assume the same meaning for the phrase "Grothendieck topos" as is used in the Elephant.
>
> David Yetter
>
>

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


  reply	other threads:[~2016-10-30 19:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 19:08 David Yetter
2016-10-30  3:06 ` Michael Shulman
2016-10-30 19:39   ` Joyal, André [this message]
     [not found] <a98ed351-1df6-4f7d-1977-7d82d5a9900b@cs.bham.ac.uk>
2016-11-09 15:01 ` Thomas Streicher
     [not found] <8641_1478651661_58226F0D_8641_41_1_E1c4Goq-0004eP-Dd@mlist.mta.ca>
2016-11-09  2:35 ` Marta Bunge
2016-11-09 15:53   ` Patrik Eklund
  -- strict thread matches above, loose matches on Subject: below --
2016-11-08 13:32 wlawvere
2016-11-09 10:48 ` Thomas Streicher
2016-11-06 15:41 wlawvere
     [not found] <YQBPR01MB061141EA2F53A36490E14F0ADFA50@YQBPR01MB0611.CANPRD01.PROD.OUTLOOK.COM>
2016-11-05 15:04 ` Joyal, André
2016-11-03 14:03 Townsend, Christopher
     [not found] <YQBPR01MB0611BC0F9930A55EC2DFE2C8DFAF0@YQBPR01MB0611.CANPRD01.PROD.OUTLOOK.COM>
2016-10-31 11:27 ` Steve Vickers
2016-11-01 10:10   ` Clemens.BERGER
2016-11-01 10:30   ` Thomas Streicher
     [not found] ` <30618_1477941855_58179A5F_30618_291_1_E1c1IA3-0007Te-Te@mlist.mta.ca>
2016-10-31 22:40   ` Marta Bunge
     [not found]   ` <YQBPR01MB0611528D9E09F09BEB7C14B8DFAE0@YQBPR01MB0611.CANPRD01.PROD.OUTLOOK.COM>
2016-11-01 15:33     ` Marta Bunge
2016-11-02  0:20       ` Michael Barr
     [not found]     ` <004501d23520$bce007f0$36a017d0$@oliviacaramello.com>
2016-11-02 18:34       ` Marta Bunge
2016-10-30 20:17 Marta Bunge
2016-11-01 15:16 ` Joyal, André
     [not found]   ` <23129f7a064fe24cddfc1414403dfe85@cs.umu.se>
2016-11-02 11:18     ` Marta Bunge
2016-11-02 15:09       ` Townsend, Christopher
2016-11-03  4:45       ` Eduardo Julio Dubuc
2016-11-03 19:36         ` Joyal, André
     [not found] ` <YQBPR01MB0611FD1B0099E7F4D36C84D9DFA00@YQBPR01MB0611.CANPRD01.PROD.OUTLOOK.COM>
2016-11-02 17:50   ` majordomo
2016-11-02 19:15     ` Marta Bunge
     [not found]     ` <YQBPR01MB0611A198AF9A5F51AD5562E8DFA00@YQBPR01MB0611.CANPRD01.PROD.OUTLOOK.COM>
     [not found]       ` <313cc907380f63841975a95b12cb1856@cs.umu.se>
2016-11-03 10:17         ` Steve Vickers
     [not found] ` <581B0EB3.4030304@cs.bham.ac.uk>
2016-11-03 11:13   ` Patrik Eklund
2016-10-27 11:07 Steve Vickers

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=E1c1I98-0007Rj-60@mlist.mta.ca \
    --to=joyal.andre@uqam.ca \
    --cc=categories@mta.ca \
    --cc=dyetter@ksu.edu \
    --cc=shulman@sandiego.edu \
    /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).