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 have been polishing and expanding the entry weak factorization system:
gave it an Idea-section;
gave the definitions numbered environments and full details;
spelled out the proof of the closure properties in full detail.
Regarding notation: I decided to use as generic name for a weak factorization system:
not , as used to be used in the entry (for that’s already my preferred generic choice for pairs of adjoint functors on the Lab, and for discussion of Quillen adjunctions the notation conventions would clash);
not or the like, since that gives no hint as to what is meant (running into an “” in the middle of some discussion, the reader is always at risk of having to browse back to figure out which class is meant);
but… , for that is nicely indicating what is meant.
Does anyone else use that terminology/notation?
Given a single class of morphisms, it’s standard to write and for the corresponding left and right lifting classes. Accordingly, it’s standard to say things like “ happens to be a weak factorization system” or happens to be a weak factorization system”.
I much prefer . I generally use for a generic pair of adjoint functors, but maybe you could do to disambiguate?
Let’s maybe wait with changing notation back until edits stabilize.
Because, for instance that statement about the closure property is all about the lifting axioms and independent of the factorization, so its proof might better be copied over to the entry on lifting problems. There notation such as wouldn’t work, while and would be preferred there.
In my opinion, notation such as and would never be preferred.
Why?
For one thing, I think it’s general mathematical practice that variables have single-character names. Multi-character identifiers are becoming more common than they used to be, but in all cases I can think of they are used to denote specific, defined objects rather than variables being quantified over. We talk about “the category ” but we say “for any category ”. I think violating a convention like this would be very confusing.
My experience is the opposite, frequently when looking up things in a longer text I need to waste time with browsing to figure out what the authors means by their letters. Notation that comes with indication of its meaning is less confusing and more efficient for communication. And specifically things like “fib, cof, proj, inj” are standard.
But let’s leave it at that. I have replaced the in the entry now with .
fib, cof, proj, inj are standard as operations that are specific and defined, and that are applied to variables, e.g. or .
not sure why we really need to debate this. I find myself now interrupting doing useful work and instead collecting references just to argue about notation; I shouldn’t do that. But before I could stop myself, the first hit was this here: pdf.
But let’s really leave it at that. I have changed the notation on the nLab to your preference, so all is good.
1 to 13 of 13