You're reading the public-facing archive of the Category Theory Zulip server.
To join the server you need an invite. Anybody can get an invite by contacting Matteo Capucci at name dot surname at gmail dot com.
For all things related to this archive refer to the same person.
i'm looking at this page https://ncatlab.org/nlab/show/big+and+little+toposes
and it seems kinda confusingly worded, but let me see if i follow...
the "big topos" pov seems straightforward enough, i think
as for "small topos"—is this correct: the idea is that we can regard a topos not so much as itself being a generalized space, but as encoding the data of a generalized space, by thinking about a hypothetical base space which it is the topos of sheaves over?
Topos theorists like to identify a topological space X (maybe with some extra adjectives) with its category of sheaves Shv(X)--that's why they consider morphisms to go in (unpopular opinion) the "wrong" direction.
hmm.
Maybe "identify" is not the perfect word, but the idea is that a topos is a generalization of a space.
this seems uncomfortably close in concept space to sheaves themselves being generalized spaces :thinking:
and/or feels uncomfortably close in concept space to the yoneda embedding
what am i smelling?
oh, and slice categories come in here somewhere too >:/
I like to think of as a souped up version of sending to the ring of continuous functions on . Now they are Set-valued functions, and they can be evaluated on points of (producing stalks), but there's some extra "stuff" (no longer a property, like continuity) saying how the stalks relate.
Beware that I have not tested this analogy in any serious way, I just like the way it sounds.
i think i have heard that you can redefine things like sheaves as functors between ∞-groupoids or something
like the 0-cells of your ∞-groupoid are the points, you send them to stalks; 1-cells are paths, you send them to isos between stalks; 2-cells are homotopies of paths, you send them to coherences or something? idk
I've been told that some of this is somehow related to locales vs. frames, in ways that I don't understand enough to say. Like, you should distinguish between a topos and a category of sheaves like you distinguish between a locale and its frame of opens (and they are related by ).
wait, srsly?
that's cute
Maybe someone else can explain that to you. :)
no i think i get it hahaha
(And re-explain it to me.)
The trouble is that because left adjoints, well, have right adjoints, it's so tempting to just call the right adjoint the "morphism"
it sounds to me like they're saying that "topos" has been defined the wrong way, with the arrows going the wrong way
and that we should think of the objects we currently refer to as "topoi" as formal duals of the things that really deserve to be named after the greak word for "place"
Yeah, probably.
I think Joyal calls this a "logos".
(not to mention that a frame is a (0, 1)-grothendieck topos, so what's a (1, 1)-locale...?)
Well, probably the locale should be the topos, and the (0,1)-grothendieck topos should be called something else?
The logos?
no i mean at level (0, 1) we have frames and locales
the corresponding terms at level (1, 1) are "grothendieck topos" and... nothing, we don't talk about the formal duals of those
Oh, yeah, sorry. The (1,1)-frame is the logos.
I think the table is
frame locale logos topos ring affine scheme
However in the last line we have the handy notation Spec for the antiequivalence between the two columns, while in the second line (and the first I guess) people don't write anything.
hmm, im going out on a real limb by saying "we don't talk about the formal duals of those"
as if i know what topos theorists talk about
using "we" as if im part of that group
lmao
So where in algebraic geometry we have for an affine scheme
we should write in topos theory
where "Spec" just denotes passing to the opposite category; and now it's okay to identify the topos on the left with the (sober) topological space on the right.
But instead people just regard Sh(X) as living in the opposite category, and don't write Spec.
https://ncatlab.org/nlab/show/logos
u know i think this topic has made a couple things click for me 🤯
like....... i swear to god i think i see that a sheaf is a categorification of an open subset @__@
i think it should be more standard to recommend poring over the correspondences between (0, 0) and (0, 1) and (1, 1), it's helped me a ton
nPOV for n > (1, 1) gets too much focus!!! more representation for nPOV with n < (1, 1) nowww
Reid Barton said:
I think Joyal calls this a "logos".
I knew logos as Heyting categories, but this usage makes much much more sense!!
to the original question, the way i think of as "petit" and "gros" is say you have a space and want to think of the category of sheaves over that space, then its still sort of "stuff regarding that space" and you have a petit topos. Now, suppose you have a "nice category of spaces" and show that it itself is a topos, then that is a "gros" topos. There is a lot of rather mystifying to me stuff about how one can relate the two notions, and give this intuition some formal weight or talk about how you might have a "gros" topos where the objects themselves can be thought of as "petit" toposes (which I would think could be fleshed-out in stacky/2-categorical approaches), but that's the general sense at least.
its too late ive already become convinced that i was right with my initial analysis :upside_down:
(but i guess it's not really very different from what you said anyway)
Reid Barton said:
Topos theorists like to identify a topological space X (maybe with some extra adjectives) with its category of sheaves Shv(X)--that's why they consider morphisms to go in (unpopular opinion) the "wrong" direction.
They are called geometric morphisms...
sarahzrf said:
using "we" as if im part of that group
Come join us :heart_kiss:
Reid Barton said:
Topos theorists like to identify a topological space X (maybe with some extra adjectives) with its category of sheaves Shv(X)--that's why they consider morphisms to go in (unpopular opinion) the "wrong" direction.
It would be more accurate to say that we identify locales with their toposes of sheaves. Which we can do because the 2-category of locales (internal to Set) is equivalent to the 2-category of localic toposes over Set :innocent: We can recover a locale from a localic topos from its subterminal objects.
Gershom said:
to the original question, the way i think of as "petit" and "gros" is say you have a space and want to think of the category of sheaves over that space, then its still sort of "stuff regarding that space" and you have a petit topos. Now, suppose you have a "nice category of spaces" and show that it itself is a topos, then that is a "gros" topos. There is a lot of rather mystifying to me stuff about how one can relate the two notions, and give this intuition some formal weight or talk about how you might have a "gros" topos where the objects themselves can be thought of as "petit" toposes (which I would think could be fleshed-out in stacky/2-categorical approaches), but that's the general sense at least.
In the same vein, to get the petit topos corresponding to a space (object) in a gros topos, one simply takes the slice over that object.
For intuition about this, suppose I have a nice category C of spaces which isn't too big (eg has a set of objects). Then I have a natural Grothendieck topology J on it that identifies covering collections of morphisms, so (C,J) is a site for the Grothendieck topos Sh(C,J), which is the gros topos for those spaces. Alternatively, I can try to build a topos by other means to act as this gros topos. Lawvere, Johnstone and company have put a lot of effort into finding such toposes, or at least identifying the properties they should have in order to be able to bring geometric techniques to bear on them.
Taking the slice at a representable object X, I get the petit topos for that space which in particular contains all of the spaces which lay over X in my original category. But I can think of any object of Sh(C,J) as a space built (via suitable colimits) from those in my original category, and can take slices over them to get the corresponding petit toposes which embody the properties of these "imaginary spaces".
Yes, it's quite appreciated that there is this reminder "geometric" that the morphism goes the wrong way :upside_down:
and the real issue is not with the direction of the morphisms between topoi, but with the identification "a topos is a category with blah blah properties".
But "a topos is not a category" is probably an even more unpopular opinion.
Care to explain what you mean?
Because I would really like there to be a clearer distinction between "unpopular opinion" and "nonsense" :rolling_on_the_floor_laughing:
A logos/category of sheaves/Grothendieck topos (as a category) is like a ring. (Small) colimits play the role of addition, finite limits play the role of multiplication. A morphism is a functor which preserves small colimits and finite limits, namely the left adjoint part of a geometric morphism.
It should be apparent a priori that "right adjoint whose left adjoint preserves finite limits" isn't a great definition.
Nobody would say a morphism in the category of rings from A to B is a ring homomorphism from B to A. But because left adjoints happen to have right adjoints which go in the opposite direction, it is possible to do this in the context of topoi.
In general there are many places in category theory where it's clear that, when considering categories which are built out of Set or otherwise resemble Set, it's better to regard an adjunction between such categories as a morphism in the direction of the left adjoint. The most basic example being presheaves on a category A as the free cocompletion of A.
Also it's the equivalent of saying, "a locale is not a completely distributive lattice." Or, "a set is not a complete atomic boolean algebra."
But for the reasons Reid mentioned, people associated the name with the wrong thing historically.
@Reid Barton Are things not backwards for the gros topos case? I.E. should one think of 'a generalized category of sets' as being a logos?
Or do the morphisms of toposes not really matter as much in that scenario?
Reid Barton said:
It should be apparent a priori that "right adjoint whose left adjoint preserves finite limits" isn't a great definition.
But a geometric morphism isn't the right adjoint functor, it's the whole adjunction! We just choose the direction to match the direction of the things that actually generate geometric morphisms (originally continuous maps, but also functors between small categories for presheaf toposes).
Dan Doel said:
Also it's the equivalent of saying, "a locale is not a completely distributive lattice." Or, "a set is not a complete atomic boolean algebra."
Okay, we often give the objects of a dual category different names for concision/clarity, but saying that an object in the dual category is fundamentally other is a stretch, isn't it?
I'm happy to concede that the "logos" naming convention is a good idea, but that won't stop me from talking about objects of a topos in the same way that I talk about open sets of a topological space.
I think there's a lot of value to objectively false but "morally true" statements
I don't know. do you actually think of a set as being the same thing as a CABA? That's saying that a set is the same thing as its lattice of subsets. That doesn't seem to be the way people think about them at all.
I certainly take for granted the presence of subsets and their behaviour, and make arguments about sets that employ those, so I suppose I implicitly do, yes!
So, you don't think a set is a collection of points.
I smell a false dichotomy here. You're saying I'm only allowed to think of a set either in terms of its elements or in terms of its subsets? Clearly it's both!
I choose my morphisms of sets to go in the direction described by mappings of points because there's less data to specify, though, and that direction was simply inherited by topology and then topos theory
Of course, for toposes with enough points, the same reasoning about the direction also works. Otherwise one has to look at points valued in a topos with enough models of a theory classified by your "domain" topos, but since many mathematicians care more about internal models of things than the toposes themselves (I can justify this if someone wants to pick me up on it), I think this is a good argument for the choice of direction too.
Morgan Rogers said:
I'm happy to concede that the "logos" naming convention is a good idea, but that won't stop me from talking about objects of a topos in the same way that I talk about open sets of a topological space.
okay, but how about "elements of a frame"?
would you say "elements of a locale" to mean the same thing?
suppose i said "cantor space forms a locale. let's pick an element of it..."—what would you assume i mean?
if you say "well, i would say a point of cantor space" then you are dodging the question :-)
here's a better argument, btw:
what is the product of two locales? what is the product of two frames?
As I said above, we use different names for the objects in the dual of a category for concision/clarity about which way around the morphisms go; in your last example the universal property of the product is obviously dependent on which way the morphisms go and the names tell me which it is. That typically extends to the data too: an element of a frame is an open of a locale; a completely prime filter of a frame is a point of a locale etc. But using different names doesn't impose a concrete separation between a category and its opposite. If I perform a construction in a set or in a locale, I choose one of the two terminological perspectives for consistency, but I can always express that argument from the other perspective if someone forces me to.
sarahzrf said:
suppose i said "cantor space forms a locale. let's pick an element of it..."—what would you assume i mean?
I would assume you're talking about a point, because Cantor space is a pretty classical space from before people thought so hard about open sets as frames. It's easy to take for granted how modern the locale/frame perspective is! But I would recommend that you refer to an element as a point if you insist on calling the space a locale :stuck_out_tongue_wink: