On the one hand, we can regard the topos itself as a generalized space. This tends to be a useful point of view when the site is the category of open subsets of a topological space (or some manifold or the like), or some other site which we regard as containing data from only “one space.” In this case, we refer to as a little topos, or (if we fail to translate the original French) a petit topos.
On the other hand, we can view a topos as a well-behaved category whose objects are generalized spaces. This tends to be a useful point of view when the site is a category of all test spaces in some sense, such as Top, Diff, or CartSp. In this case, we refer to as a big topos, or (in French) a gros topos.
These distinctions carry over in a straightforward way to higher topoi such as (∞,1)-topoi.
Objects in a big topos may be thought of as spaces modeled on , in the sense described at motivation for sheaves, cohomology and higher stacks and at space.
On the other hand, the objects of a petit topos, such as , can also be regarded as a kind of generalized spaces, but generalized spaces over on which the rigid structure of morphisms in (only inclusions of subsets, no more general maps) induces a correspondingly rigid structure so that they are not all that general. In fact, is equivalent to the category of etale spaces over —i.e. spaces “modeled on ” in a certain sense. More generally, for any topos , the objects of can be identified with local homeomorphisms of toposes into .
From the “little topos” perspective, it can be helpful to think of a “big topos” as a “fat point,” which is not “spread out” very much spatially itself, but contains within that point lots of different types of “local data,” so that even spaces which are “rigidly” modeled on that point can have a lot of interesting cohesion and local structure. (One should not be misled by this into thinking that a big topos has only one point, although it is usually a local topos and hence has an initial point.)
If is a topological space, then the canonical little topos associated to is the sheaf topos . On the other hand, if is a site of probes enabling us to regard as an object of a big topos , then we can also consider the topos as a representative of . These two toposes are often called the little topos of (or petit topos of ) and the big topos of (or gros topos of ) respectively.
There might be some debate about whether is, itself, “a little topos” or “a big topos.” While it certainly contains information about the space specifically, its objects are not “spaces locally modeled on ” but rather spaces locally modeled on the big site which happen to have a map to . The standard phrase “the big topos of ” is the most descriptive.
Note that if is actually an object of the site , then can be identified with the topos of sheaves on the slice site (and otherwise, it can be identified with the topos of sheaves on the category of elements of ). This site is often referred to as the big site of , as compared to the little site, which is (or appropriate replacement). The topos can thus be viewed as spaces modelled on , but parameterised by the representable sheaf .
Note that when with its local-homeomorphism topology, there is a canonical functor which preserves finite limits and both preserves and reflects? covering families. Therefore, it induces both a geometric morphism and one , of which the latter is the left adjoint of the former in Topos. In other words, the geometric morphism is local, and in particular a homotopy equivalence of toposes. This fact relating the big and little toposes of also holds in other cases.
If a site is given by a Grothendieck pretopology, then one can define an associated notion of a little site associated to any object of , and hence both a little topos and a big topos, which are related as above.
One proposed axiomatization of the notion of big topos is that of a cohesive topos.
For a topological space, the little topos that it defines is the category of sheaves on the category of open subsets of . A general object in this topos can be regarded as an etale space over . The space itself is incarnated as the terminal object .
On the other hand, a big topos in which is incarnated is a category of sheaves on a site of test spaces with which may be probed. For instance for Top, or Diff or CartSp with their standard coverages, is such a big topos.
In good cases, the intrinsic properties of do not depend on whether one regards it as a little topos or as an object of a gros topos. For instance at cohomology in the section Nonabelian sheaf cohomology with constant coefficients it is discussed how the nonabelian cohomology of a paracompact manifold with constant coefficients gives the same answer in each case.
The notion of a gros topos of a topological space is due to Jean Giraud. Some early results from the Grothendieck school appear in
In this context see also
In the context of a discussion of the big Zariski topos Lawvere calls the gros-petit distinction ‘a surprising twist of logic that is not yet fully clarified’ on p.110 of his contribution to the Eilenberg-Festschrift:
The suggestion that a general notion of gros topos is needed goes back to some remarks in Pursuing Stacks. A precise axiom system capturing the notion is first proposed in
The axioms 0 and 1 for toposes of generalized spaces given there later became called the axioms for a cohesive topos
Further discussion of this axiomatics for gros toposes is in
where a proposal for a general axiomatization of homotopy/homology-like “extensive quantities” and cohomology-like “intensive quantities”) as covariant and contravariant functors out of a distributive category are considered.
The left and right adjoint to the global section functor as a means to identify discrete and codiscrete spaces respectively is also mentioned in
on page 14.
Under the term categories of cohesion these axioms are discussed in
Another definition of gros vs petit toposes and remarks on applications in Galois theory is in
There is also something relevant in this article:
A discussion and comparison of big vs little approaches to -topos theory began at these blog entries: