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.
I like to denote mathematical objects in consistent ways, like any diligent mathematician. For example, all my categories are \mathbf
, all my double categories are \mathbb
, functors are uppercase Latin whereas morphisms are smallcase Latin, and so on.
Now the trouble starts when you have something that started as an object of some kind, like a double category , but then is turned into an object of another kind, like its (single!) category of morphisms /.
In your opinion, is it better to preserve the original 'kind' despite the modifier or to switch to the notation of the new kind?
I would prefer you don't switch the font.
An alternative that would be as intuitive (for me) is to have be in the data that defines .
I agree with the alternative. Something like “Let be a double category” seems nicest to me. But I guess this doesn’t work if you want to write something like for the bicategory of loose morphisms for example
Ralph Sarkis said:
An alternative that would be as intuitive (for me) is to have be in the data that defines .
Yeah that's what I meant. But one might want to write ?
I'm really on the line
My personal opinion is that font is a terrible place to encode critical information. I really think you should just say what you mean. Of course, I've consistently gotten tons of pushback when I bring this up to any coauthor. I use mathsf for any specifically named category-like gizmo: Set, Cat, Prof, Fib, etc. and mathcal for generics like C, D etc. If I'm talking both about the 1-category of categories and the 2-category of categories at the same time, I'd say "Consider the 2-category of categories, functors, and natural transformations", use Cat_1 for it's truncation, and Cat_h for it's homotopy 1-category.
I like using fonts to encode these distinctions but I think it's always good to also say what you mean in words, repeatedly, not expecting readers to memorize your conventions.
Redundancy is very helpful for clearly conveying information. Some mathematicians ignore this and write as if the only goal was to make it theoretically possible to figure out what they mean, like cracking a code.
I had the problem Matteo describes in my latest paper on double categories.. . and I forget how we resolved it!
It was a real dilemma.
In general I think a good approach is for operations that "change the kind" in this way to be denoted more obviously as functions rather than with a notation like subscripts that tends to disappear visually. For instance, if double categories are in \mathbb
and bicategories are in \mathcal
, then I would notate the bicategory of loose morphisms of a double category by . That way it is clear that the object itself is a bicategory, and it is constructed from a double category.
I definitely don't think that the category of morphisms of a double category could be denoted by . I would regard that not just as poorly-chosen notation but bordering on incorrect.
Mike will be happy that Christina and Kenny and I wound up agreeing with him:
Conventions
In this paper, we use a sans-serif font like for categories, boldface like for bicategories or 2-categories, and blackboard bold like for double categories. For double categories with names having more than one letter, like , only the first letter is in blackboard bold. In this paper, 'double category' means 'pseudo double category'. A double category has a category of objects and a category of arrows, and we call these and despite the fact that they are categories.
To clarify, I'm okay with "let ," just not with changing the font and still thinking of the "C" in as referring to the same object .
Hmm, I was not talking about thinking, purely notation. Our dilemma was: if we denote double categories by things like , how should we denote the two categories they're made of: and (since that's our font for categories) or and (since they are entities derived from via systematic processes).
We wanted a systematic rule so we could say stuff like
Let be another double category... then [or ] is cartesian if...
without having to remind the reader, every time, of how we're getting (or ) from the double category .
Yes, I'm talking about notation too. I think I'm not being very clear. Let me try again.
If I have a function , and I consider the value of that function at some input , then any notation for that value should include so that the reader can tell what the function is being applied to. This is obviously the case for the usual function-application notation . It's also the case for other notations such as or or . It would be wrong to write the value of the function on the input with a notation like , because is not the object that the function is being applied to; is.
Similarly, if is the function that takes a double category to its category of arrows, it would be wrong to write the value of on an input with a notation like , because is not the object that the function is being applied to; is. In all of my experience of the way that notation is used in mathematics, there is no a priori connection in meaning between variable names that are "the same letter" written in different fonts. The variable is as different from the variable as it is from the variable or ; if I want to I can use to denote a topological space and to denote a regular cardinal. Similarly, , , , and are just different variable names, and some object that is denoted by cannot suddenly switch to being denoted by just because some function is being applied to it whose outputs belong to a type whose elements we conventionally denote with sans-serif letters.
Okay, so we agree: we shouldn't use font change to indicate application of a function or functor to some variable. We decided that principle overrode our desire to use different fonts for different types.
Yes, we agree. I was just clarifying that I didn't object to Dylan's suggestion above.
Mike Shulman said:
In general I think a good approach is for operations that "change the kind" in this way to be denoted more obviously as functions rather than with a notation like subscripts that tends to disappear visually. For instance, if double categories are in
\mathbb
and bicategories are in\mathcal
, then I would notate the bicategory of loose morphisms of a double category by . That way it is clear that the object itself is a bicategory, and it is constructed from a double category.
Uhm this feels like the most convincing take here... in a sense both options I proposed have flaws: using a subscript or decoration to denote a functor is confusing, and so is using a change in font.
Yeah, that avoid both problems. We just didn't think of that. We might still have decided this notation was too "bulky", since we were talking about things like and over and over again, a lot. But luckily our paper is published so we don't have to think about this anymore!
I think denoting a functor by a subscript or decoration can be okay sometimes, just as ordinary functions are sometimes denoted that way. One has to be careful with it, and when you are trying to match fonts to types consistently it does step out of such a system, but it doesn't rub me as wrong the way "denoting a functor with a change of font" does.
John Baez said:
Yeah, that avoid both problems. We just didn't think of that. We might still have decided this notation was too "bulky", since we were talking about things like and over and over again, a lot. But luckily our paper is published so we don't have to think about this anymore!
I wouldn't say your choice was bad, actually that's the way I've been denoting them myself all this time. I'm nitpicking to astronomical levels in this thread!
Yes, a stream on a category theory server specially devoted to terminology and notation is a nitpicker's idea of heaven! :innocent: