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.
Hi folks,
I asked this question on Twitter, let me echo it here: https://twitter.com/mattecapu/status/1562816006204321793?s=20&t=HAdCYkJQzKBCT_ukhej4ag
can anyone motivate why lifting properties are stated for squares instead of cospans? i.e. why i and f are there in this def? https://twitter.com/mattecapu/status/1562816006204321793/photo/1
- Matteo Capucci (@mattecapu)To clarify, I'm asking why lifting properties are not stated as 'for every and of (some nice class of morphisms) there is a lift such that (bunch of properties)'
I'd like to know that as well! The only "motivation" I know of is that it subsumes lifting and extension properties.
This was already basically answered on Twitter, but the simplest example from topology would be that we have a map , and we want to lift a path in to a path in that starts at a specified lift of the initial point of . Diagrammatically, that is a condition involving a square with and as its two sides.
Note that the condition is about and , and quantifies over all and . If is the initial object, so that the diagram reduces to the one you drew, it would still be a condition about that quantifies over all , not a condition about all and .
On the other hand, lifting in a square is the same as lifting in a cospan in a coslice category...
Might be worth observing that with different quantification on the cospan you can instead define [[projective object]] s.
Oh, I completely misunderstood your question on Twitter, Matteo. I thought you were wanting to do something really weird.
In fact, the kind of lifting property you're talking about is very commonly used and important. For example it shows up in the definition of [[projective module]].
However as Barton pointed out, in topology (and elsewhere) we also often want to look at a combination of lifting and extension. His example is the fundamental one: we are trying to lift a path in to a path in , but we have already chosen how to lift the starting point of that path, so we are extending that lift to a lift of the whole path.
This example should remind you of the concept of Grothendieck (op)fibration.
Thanks everyone for the replies :) I now see the point behind a square, as a lift with an extension condition (or an extension with a lifting condition)
Yesterday I was playing with actions and spans and I wondered what the action of a monad in span(C) on another endomorphism looks like
Monads in span(C) are categories, so this almost recovers actions of categories, but there's an extra condition. Indeed what you get is the 'action of a category on a graph', i.e. you get a composition operation that takes an arrow of a graph (internal to C) and extends it with an arrow of the acting category: image.png
(It is crucial that both the graph and the category share the same set of vertices/objects)
Call the acting category . The thing above is an action of on a graph
If we swap the legs of we get . Now a (right) action of on is an operation such as
and we can read as 'the lift of along '
The laws of action tell us that and , which seem reasonable conditions for a lifting operation
Dually, a left action of gives an extension operation:
with similar properties
Now I wonder if 'lifting properties' expressed as squares can be expressed in this way... I tried figuring out what a bimodule is but it falls short of being the right thing
A bimodule (endo- or not) between monads M, N in is a [[profunctor]] . A bimodule in is an [[internal profunctor]] in . A one-sided module is the same as a bimodule with a trivial monad on one side.
Aaah sure :O that's cool