Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
I do not understand why this is a separate entry from Grothendieck topology.
Should this entry be merged into Grothendieck topology?
Yes I think so, and the discussion can be archived at the nForum. I can then delete this page in the database afterwards, since there is only one revision, so no history to preserve.
Removed the discussion to nForum:
The following discussion is about this terminological issue:
So what's stopping us from going with Johnstone? —Toby (And how about ’Lawvere–Tierney operator’?)
Well, I was hesitant to make such a change without getting some support from other people. “Lawvere-Tierney operator” would work. At the nCafe, Todd suggested “local modal operator” and I countersuggested the shorter “local modality.” -Mike
Toby says: I like eponyms, because they're less likely to be overloaded. Of course, it's important that a Lawvere–Tierney operator is a locality modality (speaking of cute names …), but there may be others. In a similar vein, I don't really like using ’coverage’ for a basis for a Grothendieck coverage. (What is such a basis, by the way? Is it anything like a Grothendieck pretopology?, which we may call ’Grothendeick precoverage’ of course.)
Mike: Does “local” have an existing meaning in modal logic? If not, I would be inclined to essentially take Lawvere-Tierney operators as a definition of a “local modality.”
I am not as fond of eponyms because they are not descriptive unless you already know what they mean. Saying something is a “Grothendieck foo” or “Lawvere-Tierney foo” conveys no information to the reader beyond “foo,” unless they are already aware that there are different types of foo and know what each eponym refers to.
A coverage in Johnstone’s sense is even weaker than a Grothendieck pretopology: it’s a set of covering families satisfying only stability under pullback (which can be defined even without required the underlying category to have pullbacks). Perhaps I was mistook and there is no classical notion of “basis,” or else this is not it? Johnstone makes the point that this is really the essential aspect of a coverage that makes sheaves behave the way we are used to; all the other conditions Grothendieck imposed are just “closure” conditions that are there because they might as well be. Do you have any objection to “coverage” other than its lack of eponymity?
Toby: Isn't stability under pullback also a closure condition? I dislike using basic terms for anything between an arbitrary collection and a collection closed under everything.
As long as you think that ’local’ doesn't have any other meaning in modal logic (in particular, if it's the same as the one here), then ’local modality’ or ’local operator’ is OK; one can always restore ’Lawvere—Tierney’ afterwards if necessary.
Mike: Stability under pullback is a closure condition in the formal sense, but unlike the others, it makes a difference to the notion of sheaf whether or not we impose it. If I have a class of covering families satisfying pullback-stability, I can close it up under the other properties without changing the notion of “sheaf,” but that is not true for pullback-stability. There is an example somewhere in the Elephant of a collection of “covering families” that is not pullback-stable and whose category of “sheaves” is not a topos.
Section 7.6 of the paper you link to is all about “geometric modalities” with reference to local operators on a topos, which implies that there is no other modal-logic notion of “local.”
Toby: OK, I see that Johnstone's notion of ’coverage’ is good because you can write down a simple (the usual) definition of ’sheaf’, whereas the definition would be more complicated if you started with an arbitrary collection.
I remembered that paper as having a couple of different kinds of local modalities, but now I see that really it had a couple of different kinds of ’geometric logic’ instead, so that's all right.
Mike: Another thing worth mentioning … moved to predicativism.
In the other conversation we seem to be having simultaneously, now I think I might actually prefer geometric modality over “local modality.” It’s not really the modality that’s local, so “locality modality” would be more correct, if it didn’t have an unfortunate rhyme. But “geometric modality” doesn’t have that problem and also suggests that they induce geometric morphisms.
Toby: Ah, but now you run into conflicts with other meanings of ’geometric logic’ in modal logic! It's wrong to favour ’locality modality’ for the cute rhyme, but we shouldn't reject it if it's really correct.
Mike: What are the other meanings of “geometric”? I didn’t notice any in the paper you linked to but maybe I didn’t look hard enough.
Toby: See Sections 3.2 and 4.5. I think that you can argue that the former should really be called ’topological’, while the latter seems to refer (it's not clear to me) to an outdated understand of ’geometry’ as meaning Euclid's axioms; but they do show that ’geometric modality’ could be misconstrued by at least some people. Thus I would still prefer ’Lawvere–Tierney modality’, at least when inventing a new term.
Mike: Actually, I think the one in section 3.2 is actually a special case of what we’re doing here–I think there’s a coverage on the poset of all subsets of a topological space whose covers are the families with topologically-dense image. As for the one in 4.5, I don’t think that a single speculative sentence in a paper in 1957, if it was never pursued or made precise, prevents us from using “geometric modality” to mean something different that it is evidently well-suited for.
Toby: OK, fair enough; I prefer the eponym only on general grounds of safety.
David Roberts: A coverage in Johnstone’s sense is even weaker than requiring pullbacks of covers to exist, just that there exists some cover which fills the role of pullback, but doesn’t have to be universal.
Mike: Yes, that’s what I intended by “stability under pullback (which can be defined even without required the underlying category to have pullbacks).” But what you said is more correct.
Zoran “relationship between a category and its topology is quite different from the relationship between a set and its topology. In particular, when we construct a site from a topological space, the objects of the category are the open sets, not the points, of the space.”
I do not understand guys what is the complaint here. Classically topology is a FAMILY of open sets, not family of points. Who cares what kind of data determine open sets, this can always be generalized. But in any case, any proper generalization of topology of a top space is a collection of local windows into the space, which you call open sets. If they are determined by more than just points that means you have to give some orientation about where they lie. That is why you put the morphisms into the game. In noncommutative geometry there are other generalizations and nobody complains against word topology. For example the lattice of hereditary torsion theories. Over there one does not have stability axiom, pullback of cover will not be necessarily a cover. Van Oystaeyen has axiomatized this situation. There are oter approaches like Q-categories, where sheaf theory looks more like in Lawvere-Tierney approach.
Toby: I agree with your approach to topology (the field of mathematics), but the complaint is more about the grammar of the word ’topology’. That is, traditionally one talks of ’a toplogy on’ a set of points; now one talks of ’a topology on’ a category of objects and morphisms, but the elements of this set and category don't correspond. In noncommutative geometry, does one ever put ’a topology on’ something that consists of local windows in some sense?
Zoran Topology is in any case on a space of some kind. The fact that in differential geometry space is given by local coordinate charts, in set-theoretic topology by a set with the topology itself, in noncommutative geometry on a hypothetical object locally behaving like dual to a ring etc. does not change anything. Topology is on a ’space’, not on points; whether a concrete example is defined by collection of sets, and sets are made of points does not matter. At least the second view is very faint in my memory. Poincare had worked with manifolds which had much more rich struture than just topological space, the fact that the extension of open sets is determined by the points is accidental. Open subschemes of a scheme for example are not deteremined by underlying reduced scheme, infinitesimal neighborhoods of different order have the same underlying set, and both are open windows of a sort. Topology is a structured collection of open windows on a space this or that way in my view.
Mike: All I can say is to essentially repeat what Toby said. A site is, certainly, a type of space (or, at least, the topos of sheaves on it is a space). But to me “a topology” is a structure that one puts onto a set of points to make it into a space. I never call, for instance, the real line “a topology;” I call it “a topological space,” meaning a set equipped with a topology. Grothendieck decided that “a topology” should also mean a different structure that one puts onto a category to make it into a space. The problem is that these two meanings are in conflict.
Zoran Skoda: My point was that the topology as a subject existed BEFORE Hausdorff, and was dealing mainly with some examples, which were manifolds embedded in Eucledean space, polyhedra and so on. When Hausdorff defined a topology on a set, it was just an abstraction of situation where he was considering what part is essential from topological point of view and made axioms for “topology” on a set. So space he started looking at was already there, and only in his particular abstraction he said well, I can STILL call it space, though I have neglected fine structure of the metric and just left this assembly out of it…topology. On the other hand, I do not consider “site” a “space”; for many reasons not the least being that Grothendieck considered topos more invariant than a site. From the point of view of algebraic geometer, the site of interest is the category of affine schemes with some subcanonical Grothendieck (pre)topology, and an algebraic kind of SPACE is NOT that site, but rather any sheaf in that topology. Thus such sheaf is a space, site is not (any ’affine’ site is just a toolbox having pieces and scissors for assemblying such a space out of “pieces’ via descent). The objects are of course representable sheaves, hence representable spaces.
Mike: I view that as reaching pretty far back. Hausdorff was writing in 1914, nearly a century ago. In modern mathematics, “topology” is always used is Hausdorff’s sense, until Grothendieck decided it should also mean something different.
I did remark that probably the topos of sheaves should be considered the space rather than the site. Certainly a topos is not always considered a “space,” but sometimes it is. Anyway I don’t think the question of what is, or isn’t, a “space” is really relevant.
Harry: I feel like grothendieck topology is fine, since the condition of continuity is actually a condition about the function’s behavior with respect to the contravariant open set functor. It’s in this sense that a Grothendieck topology generalizes a classical topology.
Removed the content to Grothendieck topology.
It is done now, the article can be removed.
Deleted now. For the record, the content of the single revision (now at Grothendieck topology or in this thread, as Dmitri mentioned), was added by Zoran.
1 to 6 of 6