Added a reference for creation of limits in comma categories.
]]>added pointer to:
I have formatted that as a usual reference and added pointer to Borceux (here)
]]>Mention original reference for comma categories.
]]>re #22:
Just noticed that the nlab page “lax pullback” redirects to “comma object”, which is a bit of a disaster from a terminological perspective.
There is a brief remark (here) meant to clarify this point at comma category – but clearly it would be good if somebody found the time and energy to do justice to this issue.
The authors of 2-pullback were working in this direction, but the comma/lax issue still has no good dedicated discussion on the $n$Lab, it seems.
]]>briefly made explicit the notion of “iso-comma category” (now here) and added the redirects
]]>Just noticed that the nlab page “lax pullback” redirects to “comma object”, which is a bit of a disaster from a terminological perspective.
]]>Hi Théo, thank you very much indeed for this! I’ll think some more about it!
]]>[deleted]
]]>Hmm, taking $A = 1$, one obtains $\mathsf{Cat}$ and not $\mathsf{Set}$ I think. Perhaps one gets something like the category of presheaves of categories in general, i.e. the $\mathsf{Cat}$-enriched free co-completion.
]]>I have been mulling over what I think would be called the ’lax comma category’ $\mathsf{Cat} // A$ for some small category $A$. This is the same as the usual over-category of diagrams $\mathsf{Cat} \rightarrow A$, except that an arrow between $D_1 \rightarrow A$ and $D_2 \rightarrow A$ consists of an arrow $D_1 \rightarrow D_2$ and a natural transformation from one side of the evident triangle to the other (in the ordinary over-category, one would require that this triangle commutes). One obtains an actual (1-)category in this way.
My first question is: $\mathsf{Cat} // A$ co-complete? I think it is; I think one can use a kind of ’double mapping cylinder’ construction to exhibit what a colimit is, but I think one could also use some argument involving sketches to prove that the category is locally presentable.
My second question is: how far is $\mathsf{Cat} // A$ from being the free co-completion of $A$ (up to equivalence of categories)? Note first that there is a natural ’Yoneda embedding’ $y : A \rightarrow Cat // A$. This is where we use the laxness of $Cat // A$; with the ordinary under-category there are no interesting arrows. If my answer to my first question is correct, then we have co-completeness. So the question boils down to: is every object of $\mathsf{Cat} // A$ (canonically) a colimit of objects in the essential image of $y$? It is not immediately obvious to me that this is false, though I haven’t tried to write down a careful argument.
]]>I think the conditions for completeness of the comma category were stated incorrectly. Please correct me if I’m wrong.
]]>Added information about completeness and cocompleteness of comma categories. The results in Borceux are not as strong as they should be.
]]>Noted that that example is a special case of the universal property of a comma object.
]]>added hyperlinks to that anonymously-added paragraph .
]]>A small inclusion in the examples section to illustrate the correspondence between natural transformations between two functors and nice functors from the domain category to the comma category of those two functors.
T
]]>I made a few wording changes, and removed the 2-limit discussion under “Properties” since it is now in the “Definition” section. I also changed my mind about briefly warning the reader against “lax pullback” on this page.
]]>I would even more strongly be inclined to remove all uses of the word “pullback” to refer to comma objects, even informally.
Tried to do this. Left “pullback” in the section on the 1-categorical pullback. Also left it in in the one sentence on the homotopy pullback.
Changed the label of the section on the 2-limit view, so as not to use “pullback” there.
Harmonised the “foreshadowing” list under “Definition”.
Added “(pb)” in the 1-categorical pullback, which seems to contrast nicely with the explicitly denoted 2-cell in the other diagrams.
In one of the diagrams, an “H_D” is still missing. For lack of time, will add this later, when more care can be applied.
]]>It’s true that in general, even the most experience of us shy away from deleting material written by others, instead trying to incorporate it into new text. I think I support this particular change, however. In fact I would even more strongly be inclined to remove all uses of the word “pullback” to refer to comma objects, even informally.
]]>but just as a general precept, I get nervous when people who are still learning a subject take it upon themselves to erase material introduced by relatively more experienced people
Okay. Will try to calibrate even more towards conserving as much as possible. And indeed, perhaps everyone except the most experienced should try to be as undestructive as possible.
In this particular case, what made me eventually eliminate “lax” from comma object is the paragraph
Note that lax pullbacks are not the same as comma objects. In general comma objects are much more useful, but there are 2-categories that admit all lax limits but do not admit comma objects, so using “lax pullback” to mean “comma object” can be misleading.
in 2-limit. The article comma category, in a sense, did not heed that warning, and had opted for “using “lax pullback” “.
On a technical note, I recognize that strictly speaking I did not carry out what Mike Shulman had been suggesting, namely to perhaps add a proof of
This is still not in comma category, which currently only states that the definitions are equivalent.
Reason was that, partly for lack of time, I thought I make some trivial rearranging changes first (of which the discussion of the “projections” to me clearly seemed to add structure), and make the suggested routine but non-trivial edits perhaps later.
]]>(I’ll let Mike answer to the changes announced in #7, but just as a general precept, I get nervous when people who are still learning a subject take it upon themselves to erase material introduced by relatively more experienced people. Usually there are other ways of combatting potential confusions aside from simple erasure.)
]]>Thanks for the answer. In comma category I made what I though were easy and improving changes.
Thinking about it, I found the former presenation a bit sawtooth-like. It seems clearer and more linear now.
Notably,
The former version simultaneously mentioned the “lax” usage and warned readers against it. This seems potentially confusing and seems better be confined to the article 2-limit.
]]>They are not just isomorphic but equal. However, a more explicit description of how comma categories acquire the universal property of comma objects would not be amiss, either at comma category or comma object.
]]>This is a type of question that often occurs to me, and that most of the time I do not dare to ask, a type characterized by
one does not really need the answer for the structures one is currently trying to construct,
one would nevertheless like to know the answer, out of curiosity and “architectual” interest in the theory,
a modicum of thought and unpacking of definition would probably yield an answer but this would slow one down.
Here, I think it may result in a valuable addition to an article, so I risk asking it, although I suspect that the answer is obvious and can be given conceptually.
So here goes (the details given should be more than sufficient in this forum; if not, I will gladly draw a diagram):
Arguably, given the data defining a comma category, there are two “canonical” functors from the comma category to the source-categories of the defining cospan:
the evident forgetful projections $P_i$ (for which there apparently is no usual name),
the so-called projections $H_i$ which are shipped with the comma object point of view.
It seems natural to ask:
It seems not usual to mention this question; I have never seen it in the literature.
It seems useful to discuss
Like I mentioned above, this should be straightforward to answer, and I did not stop to think about it; my apologies if this is totally obvious and with good reason never discussed.
]]>