A sieve is a way to encode a morphism of presheaves that behaves like a cover. It is used to say which presheaves are actually sheaves with respect to a given coverage or Grothendieck topology.
Sieves are an equivalent way to encode subobjects of representable functors in a presheaf category in terms of the total sets of elements of such a subfunctor.
The notion of sieve is usually used when certain such subobjects are singled out as covers of a (sifted) coverage: the singled out subobjects then correspond to covering sieves.
Urs, I changed ‘coverage’ back to ‘Grothendieck topology’ above, since it's specifically Grothendieck topologies that deal with covering sieves; coverages deal with arbitrary covering families (generally not sieves and generally not all of them), which is part of why coverages both can be more useful and are less canonical.
Urs: hm, okay. My impression was that the point of coverages is that we don’t impose the four axioms of Grothendieck topology on the covering things, while we do keep the notion of sieves itself. Because “sieve” is really just another way to say “subfunctor of a representable” so the question really is: which collections of subfunctors of representables do we want to use as coverages. For me the 1-line definition of “coverage” would be: choice of subcollection of all monois in a given 1-topos. That then makes sense also in non-presheaf topoi. For presheaf topoi it happens to have a reformulation in terms of sieves.
So, in conclusion, I am thinking that the point of using more general coverages over Grothendieck topologies is not primarily to relax the closure under composition that makes a sieve a sieve. That’s kind of a trivial thing. The point is that we don’t need to impose the four axioms of a Grothendieck topology on the collection of all such.
But maybe not. This is just so you know what I am thinking. :-)
Toby: Ah, now I see what you're saying!
The problem is that the difference between a Grothendieck topology and a coverage is twofold: first, each individual covering family that appears in a Grothendieck topology is saturated (and so becomes a sieve); second, subject to the restriction that only sieves may appear, the class of covering families is saturated. (I should write something about this at coverage.) You are thinking of dropping the second without changing the first.
I know just the term for that: ‘sifted coverage’ (which may be found in the Elephant).
A choice of collections of morphism into an object for each reminds one of the representable functor presheaf which assigns to each the set of all morphisms from to . Every choice of covers of is therefore for each a subset of the value of this functor evaluated at . This begins to look like an monic natural transformation into this functor. Indeed, it turns out that one can assume without restriction of generality that the assignment of covers of can always be extended to such a monic natural transformation, and hence one formalizes the notion of “collection of covers” of as a subobject of the functor represented by : a sieve at .
A dual notion is a cosieve.
Let be a small category.
A sieve (Fr. crible) on an object is a subset of the set of objects of the over category over which is closed under precomposition: it has the property that with for every morphism also the composite is in .
Sometimes the condition of a sieve being closed under the operation of precomposing with an arbitrary morphism is called a “saturation condition”. Given any collection of morphisms targeted at , one can always close it up or saturate it, to obtain a sieve on .
This is probably called a sieve because it “sifts out” the ‘special’ maps into from the set of all maps into . (Note that ‘sieve’ is the noun, while ‘sift’ is the verb.)
There is a canonical way to create subfunctors from sieves and sieves from subfunctors.
A subfunctor is a subobject in a functor category. Here, specifically, one is interested in subobjects in a presheaf category of representable functors. It’s these subfunctors of representable functors that are in bijection with sieves.
Given a sieve on , the subfunctor defined by the sieve is the presheaf
that assigns to each object the set ;
that assigns to each morphism the function induced on elements by precomposition with .
Given a subfunctor , the sieve defined by the subfunctor is given by
or equivalently
Bruce: Hey, if you are being extra careful here you should be saying that the sieve obtained from the subfunctor is really the image of (as you say below), i.e. if we write for the explicit inclusion map, then for each , .
Right now, this makes me prefer the notion of ‘sieve’ to the notion of ‘subfunctor of a representable’. The reason is that the elements of the sieve are actually morphisms in the category, whereas the subfunctor can be composed of ‘abstract elements’. Why are you pushing the viewpoint of ‘subfunctor of a representable’? Is it for later -category purposes? If so, you should say that at the top of the article, so the reader understands why you are introducing extraneous ‘abstract nonsense’ elements into the conversation… :-)
Urs: thanks for the comment, Bruce! Here I would find it helpful if you could put in directly what you would find helpful. Because I am not sure. At the moment it says right at the beginning that sieves are a way to encode subfunctors of representables. This is the reason why we care about them.
The point is really, as described in some detail at sheaf, that we want to characterize certain morphisms of presheaves, called local isomorphisms. And it turns out that a lot is already gained once we understand all local isomorphisms that are monomorphisms (called then dense monomorphisms). And it turns out that among them in turn it suffices to look at those with representable codomain. These, finally, are seen to have a more pedestrian description in terms of sieves. That’s why one cares about sieves.
Should we say this here again? Maybe. But It is already described in some detail at sheaf.
But of course you are right to “prefer” sieves in a way: they are the explicit hand-on realization of some abstract nonsense. That’s why one useses them. As a tool. But their raison d’etre is the abstract nonsense that they are a manifestation of.
Todd: I much prefer “subfunctor of a representable” on grounds of snappiness and immediate comprehension, but it may help (as I do myself) to think of ‘subfunctor’ here not in terms the general abstract notion of ‘subobject’, but in terms of ‘subset’ of naive set theory.
The situation seems to be this: ‘subobject’ refers to an isomorphism class of monomorphisms. But probably most people think of isomorphism classes (or equivalence classes generally) as another layer of abstraction they would prefer to do without when they can; they would rather deal with concrete elements, picking out a distinguished representative of the class and working directly with that (for example, think of how we multiply in or something). So, instead of “isomorphism class of injective functions”, they go straight to the actual subset inclusion in the class – the ‘image’ as Bruce said – as the distinguished element they want to get their hands on, formulated in the good old-fashioned language of naive sets and elements we grew up with, not this newfangled subobject nonsense.
Since presheaves and sheaves are based on sets to begin with, we have that! So here there is no harm whatsoever in defining subfunctor in this concrete way, as an arrow whose components are literal subset inclusions. That’s how I always picture these things myself, and it gives the notion of sieve straightaway, in a tight conceptual package.
Toby: Funny I don't think of a subobject as a class of monomorphisms; I think of it as an individual monomorphism. And yet, I don't pick a distinguished representative either! Instead, I just remember that sometimes two subobjects are equal.
It's really no different in principle from thinking about objects. I don't work with isomorphism classes of objects, and I don't work in skeleta either. I just work with objects, and sometimes two objects are isomorphic.
These two definitions establish a bijection between sieves on and subobjects of .
For every sieve we have
and for every subfunctor we have
The construction of makes sense for every morphism of presheaves . The sieve is sensitive precisely to the image of this map,
In the presence of a Grothendieck topology a morphism is sometimes called a local epimorphism if the sieve is a covering sieve. If is actually a subfunctor, then it is called a dense monomorphism.
The pullback of a subfunctor along any morphism is again a subfunctor of , hence sieves are closed under pulling back. Concretely,
A sieve on , for a subfunctor, may be described as a function which assigns to each object a collection of morphisms into . Naturality of the inclusion means that whenever belongs to the sieve and is any morphism, then also belongs to the sieve.
The subfunctor corresponding to a sieve is the coimage of the morphism out of the disjoint union of all objects (regarded as representable presheaves) in the sieve:
in that
If the sieve is generated by (is the saturation of) a collection of morphisms then the same statement remains true with being the coproduct over just these .
As described at limits and colimits by example, the colimit of presheaves may be computed objectwise in . Doing so and using the Yoneda lemma tells us that for each object we have
where all objects appearing (at least in the first lines) are implicitly regarded as presheaves under the Yoneda embedding.
But this colimit now manifestly computes the set
where the equivalence relation is
So the set is just the set of maps from to that factor through one of the , which is precisely the set assigned by the subfunctor corresponding to the sieve.
For a topological space let be the category of open subsets of and consider presheaves on . For any open subset let be a cover of by open subsets in the ordinary sense (i.e. each is an open subset of and their joint union is , ), then (with the Yoneda embedding) is a local epimorphism of presheaves on and its image – or equivalently its coimage – is the subfunctor that sends each to the set of maps that factor through one of the . The collection of all such maps for all choice of is the corresponding covering sieve .
The situation for more general sites other than is literally the same as above, with etc. objects of .
The following is a pedagogical step-by-step description of the crucial aspects of sieves as covers.
To start with the simplest example that already contains in it all the relevant aspects, consider a topological space with an open subset that is covered by two open subsets in that the union in coincides with :
This is the coproduct in the category of open subsets of , but that behaves very differently from the disjoint coproducts that we are used to from categories like Set. On the other hand, when one comes to a category of presheaves or sheaves (a Grothendieck topos), this topos does have disjoint coproducts.
Another way to think of this is obtained by first forming the fiber product of with over in , which is the intersection sitting in the pullback diagram
in .
The union is again obtained from this by removing in the above diagram the bottom right corner and then forming the pushout over the resulting diagram: this is again , i.e. the diagram
is not only a pullback also a pushout diagram.
The important point about (covering) sieves is that they show up when the above situation is sent via the Yoneda embedding from to presheaves on . The crucial aspect here that gives rise to the peculiarities of sieves is that
As a result, the above discussion goes through equivalently for the presheaves represented by our open subsets all the way up to the last pushout. In that last pushout reproduced the open subset . In it instead reproduces the sieve on generated by and .
Let’s go through this in detail. First of all notice that in all limits and colimits do exist (see limits and colimits by example for more on that); in particular the coproduct
exists. Here denotes the Yoneda embedding which we here indicate explicitly, even though often and elsewhere, notably elsewhere in this entry here, it is notationally suppressed.
For the following it is helpful to say explicitly what the presheaf is like. Since, as described at limits and colimits by example, colimits of presheaves are computed objectwise, we know that this presheaf evaluated on any open set yields the set
where the coproducts on the right are just those in Set which are just ordinary disjoint unions of sets.
So this says that is the presheaf that assigns to any open set the disjoint union of the collections of maps from to and those from to in . (Since is a poset there is either none or one such map in each case, but it is helpful to speak generally of “sets of all maps”, since that is the general intuition useful for presheaf categories. just happens to be a particularly simple example.)
Notice that in particular a given map which factors both through as well as through will appear as two distinct elements in the set . This we’ll come back to in a minute.
But first consider the fiber product from before, now after having applied the Yoneda embedding. Since we know from general nonsense that this preserves fiber products, we know that the pullback presheaf in
is the same as .
But this is also easily checked explicitly. We go through this because this kind of reasoning for computing limits and colimits of presheaves will be needed throughout here: since for any the covariant hom-functor preserves limits (by the very definition of limit!) we have for every a pullback diagram of sets
Again by the Yoneda lemma this is simply
This being a pullback diagram now says in words:
The set is the set of those pairs of maps and that coincide as maps and to .
Clearly, this set is the same as the set of maps into the intersection , so indeed
So far so long-winded. Now let’s see what happens when we now form the pushout over
that will go, for a moment, by its canonical but lenghty name
Again, we can figure out what this presheaf is by computing objectwise what it does to any open subset : since colimits of presheaves are computed objectwise, the diagram
must be a colimit in Set. Again, this is easily read out in words:
The set is the quotient of the disjoint union of the collection of maps from into and those from into , by the equivalence relation which identifies two such maps and if they both factor through a map , i.e. if they both land in the intersection and coincide there.
But this just means that contrary to the plain coproduct , two maps and that coincide as maps are no longer regarded as different elements of our set given by the pushout presheaf, but are regarded as being the same.
So this means we find that
But this is by definition the assignment of the subfunctor coresponding to the sieve on generated by and .
So we find that
Given that we made it to this point, we should go one small step further that will be very useful.
In the present simple example we worked with a cover given by just two objects and . Of course in general the cover will consist of more than just two objects. Then the above kind of notation becomes a bit cumbersome. But there is a simple reformulation that makes everything look nice again.
Namely, let’s come back to the observation that the coproduct does exist. Let’s just call this presheaf . (not in general a representable!).
Then it is easy to see by the same kind of objectwise reasoning that the colimiting presheaf that we are after is equivalently the colimit over the pair of parallel morphisms
in that
This description now has an evident direct generalization to the case where instead of just and we have an arbitrary collection of open sets covering . One finds again with
that
is the presheaf that to every assigns the set of all maps that factor through any one of the .
It is in this way that sieves and their associated subfunctors encode the notion of cover of an object : they tell us which of all the maps into do factor through the cover.
And, to end this pedagocial piece with an outlook to indicate the gain in understanding this achieves:
once we start forming there is no stopping. We can keep forming higher and higher such fiber products
When one passes from just presheaves to (∞,1)-presheaves, then covering presheaves will be given by the right kind of colimit over these simplicial diagrams (namely the homotopy colimit). More on that is at descent.
We now show that the subfunctor associated with a sieve coming from a cover is the right kind of morphism to require a sheaf to be a local object for, by demonstrating that using it the usual sheaf condition on a presheaf with respect to the cover is reproduced:
From the above detailed discuss recall that is precisely the coequalizer of the obvious pair of morphisms
with denoting the presheaf represented under the Yoneda embedding by , as usual.
Here the domain of this parallel pair is the pullback of the evident map
along itself, and the two parallel arrows are the projection maps out of this pullback:
Thus for any presheaf, maps are precisely the same as maps which coequalize the parallel pair. Applying to the colimit diagram
yields the limit diagram
which using Yoneda is the equalizer diagram
and hence identifies indeed as the set of descent data for the sheaf condition on .
This description contains in it the seed of its generalization from the context of sheaves to that of descent for ∞-stacks.
See also the discussion at Čech cover.
For a cover, there is a simplicial presheaf – the Čech nerve of the cover – that in degree is the -fold fiber product .
This may be regarded as an ∞-groupoid valued presheaf.
More algebraically, with the free strict omega-groupoid on the standard filtered -simplex, is the nerve of the groupoid
The sieve associated with the cover is the presheaf obtained by starting with the -prestack represented by and decategorifying, i.e. passing to equivalence classes.
Equivalently, for a presheaf regarded as a constant simplicial presheaf using the inclusion Set SSet we have
simply because all the higher morphism of have to map to identity morphisms in .