Changed
In general, right adjoint profunctors correspond to profunctors into the Cauchy completion of their codomain.
to
In general, right adjoint profunctors correspond to functors into the Cauchy completion of their codomain.
I think that’s what was meant here.
]]>added pdf link to
Add reference to term “relator”.
]]>Add in the formulation in terms of spans and note the generalization to double categories.
]]>Clarify notation at composition of profunctors (if I understand previous version correctly, the - was standing for two different variables, or maybe \otimes was a fancy tensor)
]]>added pointer to:
(via user varkor, here)
Interesting: the entry used to claim that the original reference is Bénabou 1973 – only to list a couple more references from the 1960s.
I have now put the early references into chronological order.
Also I removed the claim that “the theory has mainly been developed by Bénabou”. If this needs to be said, let’s add it back in with some substantiation (e.g. saying what it is that Bénabou 1973 proves which other authors missed).
Also removed the claim that Bénabou 2000 is “excellent”. If this needs to be said, let’s add it back in with explanation of what is more excellent here than elsewhere.
]]>Turned the inline reference to Cattani’s thesis into an actual reference and added more references details (such as the title…).
]]>Moving this old discussion from out of the entry to here:
begin forwarded discussion
+–{.query} Todd: There is an inevitable debate here about whether one should use or . My own convention is to use the latter. For example, every functor yields a profunctor by composition with the Yoneda embedding on .
Mike: My convention is . I agree with your reasoning for why should be contravariant; I like to put it first because in the hom-functor the contravariant variable appears first.
Sridhar Ramesh: But surely, just as well, a functor from to yields a contravariant functor from to and thus a profunctor , by composition with the contravariant Yoneda embedding of into ? At the moment, I still do not see why there is reason to prefer in the abstract general one to the other of and , though it’s not an issue I’ve thought very much about or have strong emotions regarding. Are there further reasons beyond the above?
Mike Shulman: Well, the covariant Yoneda embedding is arguably more natural and important than the contravariant one. If a profunctor ⇸ is a functor , then we can think of it as assigning to every a presheaf on , which may or may not be representable. The profunctor “is” a functor just when all its values are representable presheaves. Of course, if instead a profunctor ⇸ were a functor , i.e. , then we could think of it as assigning to each a functor , which might or might not be (co)representable. However, for a bunch of reasons it’s often more natural to think of an object of as determined by the maps into it, rather than the maps out of it—in other words by its generalized elements, or in yet other words by the presheaf it represents. Although of course formally, there is a complete duality. =–
end forwarded discussion
Clarified the situation with Cauchy completeness, and moved the link to Mealy morphism down to related pages since I wasn’t sure what to say correctly about it or where.
]]>(In case it is not clear, Mike in #21 is replying to #18). In case it helps, Mike’s first point more directly is I think that it is not necessarily true in the non-Cauchy complete case that profunctors corresponding to functors are exactly those with a right adjoint. It would be nice with an explicit counterexample!
MIke’s second point is I think that the correct statement is that Mealy morphisms determine profunctors, and that a profunctor can be obtained in this way if and only if it is ’discrete valued’. It comes from a functor if and only if it is total and discrete valued. See these slides of Paré. Thus we have ’inclusions’
Functors -> Mealy morphisms -> Profunctors
where the difference between Functors and Mealy morphisms is totality, and the difference between Mealy morphisms and Profunctors is discrete valuedness. In the Cauchy complete case, totality and discrete valuedness must be equivalent to having a right adjoint.
It would be great to improve the nLab entries on this, and in particular as I say with explicit counterexamples to show that the inclusions are strict, etc. I am no expert, but hopefully somebody else can do it. Great that you have begun on this, Tim!
]]>I don’t quite understand what the paragraph is saying, but it doesn’t look right to me. Firstly, the profunctors having right adjoints are actually the ones that appear in the Cauchy completion; if the codomain is not Cauchy complete then they may not all be representable. Secondly, not all profunctors are Mealy morphisms either; I forget exactly what the characterization is in profunctorial terms but it’s not all of them (otherwise the term “Mealy morphism” wouldn’t have been introduced).
]]>Putting back the removed LaTeX code.
]]>[Administrative note: I have merged an old thread, comments #1-#17, into this one. There is also this old thread, but I’ll not merge that one, since it covers both anafunctors and profunctors, and could fit into either latest changes thread.]
]]>profunctors in terms of Cauchy completion and Mealy morphisms — created page for Mealy morphisms also had to remove LaTeX code for arrows to get page to save, no idea how to add it back in…
Tim H
]]>None of the existing terms for these objects — profunctor, distributor, (bi)module — is ideal. If we could (1) find a term that is completely unproblematic and (2) instantly convince all mathematicians to start using it, and retroactively edit all mathematical papers from the past to use it as well, then I think that would be a good thing. But in practice, even if we could do (1) (note that “ind-functor” is not perfect either, as it has the problem of suggesting a cocompletion under directed colimits only), what would actually happen is that instead of 3 competing terms there would be 4 competing terms, and even more confusion would be produced. As Jaap van Oosten said, “the only thing worse than bad terminology is continually changing terminology”. If a particular terminology is really bad, and nearly everyone agrees that it is bad and can be convinced to switch to the same alternative, then it is sometimes worth trying to change an established term (e.g. triple monad); but that case is extremely rare. As Todd says, this particular conflict rarely if ever leads to any actual confusion.
]]>The naming conflict with the ’pro-’ as in ’profinite’ is well-known. ’Profunctor’ is not “everyone’s favorite name”, but the problem is that the name is ancient and entrenched, and we have no plans to change it. (I’m pretty sure we discussed this in another thread.) I don’t know of any case where the conflict led to real confusion.
]]>I know that I’m rather late to the party, but the name “profunctor” seems to conflict with the choice of convention that Prof(C,D) to be a functor D^op x C -> Set.
I understand that the motivation for the convention is based on the idea of generalizing the codomain of a functor to be the colimit-completion: i.e. a functor C -> PSh(D). But from the prefix “pro” I would have expected instead generalizing to the limit-completion, and thus to the alternate convention C^op x D -> Set. The given convention might be better named “indfunctor”.
Is the given choices just that profunctor is everyone’s favorite name and the colimit completion is everyone’s favorite concept, and so the two are paired? Or is there some other motivation that I’m missing?
]]>In general, I disagree with the idea of having multiple pages about the same thing, regardless of how many names that thing might have. I think it's better to pick a particular name, explain up-front that there are others in use, and use redirects. Of course, adding any additional references to Benabou's work on the profunctor page would be a great idea.
]]>Given recent remarks on the cat list, perhaps a separate entry on distributors with references to Benabou's work would be a good thing to include, of course, with a clear link to the profunctor page.
]]>I did some reorganizing of profunctor, and also added the two ways to describe them as fibrations or cofibrations.
@Toby #10, bimodule is currently actually about profunctors. I would prefer that bimodule be more general, as you seem to be suggesting, since for many/most mathematicians it is used restricted to the one-object case; with anything there that is specifically about profunctors moved to profunctor. In any case, bimodule should not duplicate profunctor, so if we decide that bimodule should be mostly about profunctors, then I think it should instead just redirect to profunctor.
]]>Okay, that's fine. Profunctor it is, then, for this case.
]]>The term ‘bimodule’ is so general, encompassing the case that Urs describes in #7 above as well, that I would want to keep bimodule what it is, and make profunctor (or distributor, but we've already discussed that) the page that focusses on the case at hand.
]]>Profunctoris far more suggestive than distributor for outsiders, which does not even remind of functor...
]]>.. and don't forget my favorite example of bimodules, i.e. discrete differential forms :)
The key is the last paragraph of course. I'll have to try to understand that. Thanks!
]]>