Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

• Forgot your password?
• Apply for membership

1. • CommentRowNumber1.
   • CommentAuthorUrs
   • CommentTimeDec 7th 2011
   • (edited Sep 25th 2012)
   • PermaLink
   Author: Urs
   Format: MarkdownItexat [[internal hom]] the following discussion was sitting. I hereby move it from there to here *** Here\'s some discussion on notation: _[[Ronnie Brown|Ronnie]]_: I have found it convenient in a number of categories to use the convention that if say the set of morphisms is $hom(x,y)$ then the internal hom when it exists is $HOM(x,y)$. In particular we have the exponential law for categories $$Cat(x \times y,z) \cong Cat(x,CAT(y,z)).$$ Then one can get versions such as $CAT_a(y,z)$ if $y,z$ are objects over $a$. Of course to use this the name of the category needs more than one letter. Also it obviates the use of those fonts which do not have upper and lower case, so I have tended to use mathsf, which does not work here! How do people like this? Of course, panaceas do not exist. _Toby_: I see, that fits with using $\CAT$ as the $2$-category of categories but $\Cat$ as the category of categories. (But I\'m not sure if that\'s a good thing, since I never liked that convention much.) I only used 'Hom' for the external hom here since Urs had already used 'hom' for the internal hom. Most of the time, I would actually use the same symbol for both, just as I use the same symbol for both a group and its underlying set. Every closed category is a [[concrete category]] (represented by $I$), and the underlying set of the internal hom is the external hom. So I would distinguish them only when looking at the theorems that relate them, much as I would bother parenthesising an expression like $a b c$ only when stating the associative law. _Ronnie_: In the case of [[crossed complexes]] it would be possible to use $Crs_*(B,C)$ for the internal hom and then $Crs_0(B,C)$ is the actual set of morphisms, with $Crs_1(B,C)$ being the (left 1-) homotopies. But if $G$ is a groupoid does $x \in G$ mean $x$ is an arrow or an object? The group example is special because a group has only one object. If $G$ is a group I like to distinguish between the group $Aut(G)$ of automorphisms, and the crossed module $AUT(G)$, some people call it the _actor_, which is given by the inner automorphism map $G \to Aut(G)$, and this seems convenient. Similarly if $G$ is a groupoid we have a group $Aut(G)$ of automorphisms but also a group groupoid, and so crossed module, $AUT(G)$, which can be described as the maximal subgroup object of the monoid object $GPD(G,G)$ in the cartesian closed closed category of groupoids. _Toby_: 'But if $G$ is a groupoid does $x \in G$ mean $x$ is an arrow or an object?': I would take it to mean that $x$ is an object, but I also use $\mathbf{B}G$ for the pointed connected groupoid associated to a group $G$; I know that groupoid theorists descended from Brandt wouldn\'t like that. I would use $x \in \Arr(G)$, where $\Arr(G)$ is the [[arrow category]] (also a groupoid now) of $G$, if you want $x$ to be an arrow. (Actually I don\'t like to use $\in$ at all to introduce a variable, preferring the type theorist\'s colon. Then $x: G$ introduces $x$ as an object of the known groupoid $G$, $f: x \to y$ introduces $f$ as a morphism between the known objects $x$ and $y$, and $f: x \to y: G$ introduces all three variables. This generalises consistently to higher morphisms, and of course it invites a new notation for a hom-set: $x \to y$.) *** continued in next comment...

   at internal hom the following discussion was sitting. I hereby move it from there to here

   ---

   Here's some discussion on notation:

   Ronnie: I have found it convenient in a number of categories to use the convention that if say the set of morphisms is $hom(x,y)$ then the internal hom when it exists is $HOM(x,y)$. In particular we have the exponential law for categories

   $$Cat(x \times y,z) \cong Cat(x,CAT(y,z)).$$

   Then one can get versions such as $CAT_a(y,z)$ if $y,z$ are objects over $a$.

   Of course to use this the name of the category needs more than one letter. Also it obviates the use of those fonts which do not have upper and lower case, so I have tended to use mathsf, which does not work here!

   How do people like this? Of course, panaceas do not exist.

   Toby: I see, that fits with using $\CAT$ as the $2$-category of categories but $\Cat$ as the category of categories. (But I'm not sure if that's a good thing, since I never liked that convention much.) I only used ’Hom’ for the external hom here since Urs had already used ’hom’ for the internal hom.

   Most of the time, I would actually use the same symbol for both, just as I use the same symbol for both a group and its underlying set. Every closed category is a concrete category (represented by $I$), and the underlying set of the internal hom is the external hom. So I would distinguish them only when looking at the theorems that relate them, much as I would bother parenthesising an expression like $a b c$ only when stating the associative law.

   Ronnie: In the case of crossed complexes it would be possible to use $Crs_*(B,C)$ for the internal hom and then $Crs_0(B,C)$ is the actual set of morphisms, with $Crs_1(B,C)$ being the (left 1-) homotopies.

   But if $G$ is a groupoid does $x \in G$ mean $x$ is an arrow or an object? The group example is special because a group has only one object.

   If $G$ is a group I like to distinguish between the group $Aut(G)$ of automorphisms, and the crossed module $AUT(G)$, some people call it the actor, which is given by the inner automorphism map $G \to Aut(G)$, and this seems convenient. Similarly if $G$ is a groupoid we have a group $Aut(G)$ of automorphisms but also a group groupoid, and so crossed module, $AUT(G)$, which can be described as the maximal subgroup object of the monoid object $GPD(G,G)$ in the cartesian closed closed category of groupoids.

   Toby: ’But if $G$ is a groupoid does $x \in G$ mean $x$ is an arrow or an object?’: I would take it to mean that $x$ is an object, but I also use $\mathbf{B}G$ for the pointed connected groupoid associated to a group $G$; I know that groupoid theorists descended from Brandt wouldn't like that. I would use $x \in \Arr(G)$, where $\Arr(G)$ is the arrow category (also a groupoid now) of $G$, if you want $x$ to be an arrow. (Actually I don't like to use $\in$ at all to introduce a variable, preferring the type theorist's colon. Then $x: G$ introduces $x$ as an object of the known groupoid $G$, $f: x \to y$ introduces $f$ as a morphism between the known objects $x$ and $y$, and $f: x \to y: G$ introduces all three variables. This generalises consistently to higher morphisms, and of course it invites a new notation for a hom-set: $x \to y$.)

   ---

   continued in next comment…

2. • CommentRowNumber2.
   • CommentAuthorUrs
   • CommentTimeDec 7th 2011
   • PermaLink
   Author: Urs
   Format: MarkdownItex...continuation from previous comment *** _Ronnie_: I would use, and have used, $\mathbf{B}G$ for a (the) [[classifying space]] of the group, usually the realisation of the simplicial [[nerve]] of the group, and would often identify a group with its corresponding one-object groupoid. If $G$ is a [[crossed complex]] or multiple groupoid, I would want $\mathbf{B}G$ to be a space, and $Nerv(G)$ to be some combinatorial object, such as simplicial or cubical set, or multi versions of these. Actually, $Nerv(G)$ has in this case the structure of [[T-complex]], so is also a form of higher category. Of course Brandt initiated the groupoid idea, coming from the composition of quaternary quadratic forms, generalising ideas of Gauss, but other later traditions come via Reidemeister in algebraic topology and much wider from Charles Ehresmann, for fibre bundles, Lie groupoids, foliations, and other geometric applications, and these need to be considered for notational decisions. I guess the needs of geometry, algebra, analysis, logic and computer science, and even physics, will never be completely reconciled. _Toby_: We ran into the conflict with $B$ before and somewhat tentatively decided to use $\mathbf{B}G$ for the groupoid and $\mathcal{B}G$ for the space (and maybe $\mathcal{N}G$ for the nerve). You can read some of that discussion at [[category algebra]] (where it is as out of place as it is here), including reasons for distinguishing $G$ from $\mathbf{B}G$. Probably it was a mistake to use the letter $B$ again. I think that the idea was to identify all versions of a [[homotopy 1-type]] (groupoid, simplicial set satisfying certain conditions, nice topological space with no nontrivial higher homotopy groups, etc), but that is not very helpful to other fields. I would be happy to use a different letter but would want to use something. By 'groupoid theorists descended from Brandt' I really meant all those who see groupoids as generalised groups (a single set with a partial binary operation satisfying various conditions) rather than those who see them as special kinds of categories (a set of objects, a set ---or even doubly-indexed family of sets--- of isomorphisms, and so on; while it is perfectly possible to view general categories in the Brandt-like way, that seems pretty rare). [[Mike Shulman]]: I prefer to use $Cat$ for the (1- or 2-)category of small categories and $CAT$ for the (1- or 2-)category of large categories, with 1-categories in bold typeface and 2-categories in script typeface. And I always write $C(x,y)$ for the set of morphisms from $x$ to $y$, leaving $hom(x,y)$ for the internal hom if you like. Another nice option is to underline $C$ when writing $C(x,y)$ for the internal hom, although that doesn't appear to work here (although the itex2MML commands summary claims that `\underline` is accepted). By the way, it's not true that every closed category is [[concrete category|concrete]]: homming out of $I$ need not be faithful. Take simplicial sets, for instance, or even $Cat$. *** end of forwarded discussion

   …continuation from previous comment

   ---

   Ronnie: I would use, and have used, $\mathbf{B}G$ for a (the) classifying space of the group, usually the realisation of the simplicial nerve of the group, and would often identify a group with its corresponding one-object groupoid. If $G$ is a crossed complex or multiple groupoid, I would want $\mathbf{B}G$ to be a space, and $Nerv(G)$ to be some combinatorial object, such as simplicial or cubical set, or multi versions of these. Actually, $Nerv(G)$ has in this case the structure of T-complex, so is also a form of higher category.

   Of course Brandt initiated the groupoid idea, coming from the composition of quaternary quadratic forms, generalising ideas of Gauss, but other later traditions come via Reidemeister in algebraic topology and much wider from Charles Ehresmann, for fibre bundles, Lie groupoids, foliations, and other geometric applications, and these need to be considered for notational decisions.

   I guess the needs of geometry, algebra, analysis, logic and computer science, and even physics, will never be completely reconciled.

   Toby: We ran into the conflict with $B$ before and somewhat tentatively decided to use $\mathbf{B}G$ for the groupoid and $\mathcal{B}G$ for the space (and maybe $\mathcal{N}G$ for the nerve). You can read some of that discussion at category algebra (where it is as out of place as it is here), including reasons for distinguishing $G$ from $\mathbf{B}G$.

   Probably it was a mistake to use the letter $B$ again. I think that the idea was to identify all versions of a homotopy 1-type (groupoid, simplicial set satisfying certain conditions, nice topological space with no nontrivial higher homotopy groups, etc), but that is not very helpful to other fields. I would be happy to use a different letter but would want to use something.

   By ’groupoid theorists descended from Brandt’ I really meant all those who see groupoids as generalised groups (a single set with a partial binary operation satisfying various conditions) rather than those who see them as special kinds of categories (a set of objects, a set —or even doubly-indexed family of sets— of isomorphisms, and so on; while it is perfectly possible to view general categories in the Brandt-like way, that seems pretty rare).

   Mike Shulman: I prefer to use $Cat$ for the (1- or 2-)category of small categories and $CAT$ for the (1- or 2-)category of large categories, with 1-categories in bold typeface and 2-categories in script typeface. And I always write $C(x,y)$ for the set of morphisms from $x$ to $y$, leaving $hom(x,y)$ for the internal hom if you like. Another nice option is to underline $C$ when writing $C(x,y)$ for the internal hom, although that doesn’t appear to work here (although the itex2MML commands summary claims that \underline is accepted).

   By the way, it’s not true that every closed category is concrete: homming out of $I$ need not be faithful. Take simplicial sets, for instance, or even $Cat$.

   ---

   end of forwarded discussion

3. • CommentRowNumber3.
   • CommentAuthorzskoda
   • CommentTimeDec 8th 2011
   • (edited Dec 8th 2011)
   • PermaLink
   Author: zskoda
   Format: MarkdownItexThank you for nice formatted archiving version. I have left a link at the [[internal hom]] to this discussion (I think we should nearly always do that when archiving). We need also a canonical reference for this entry (maybe Kelly ??).

   Thank you for nice formatted archiving version. I have left a link at the internal hom to this discussion (I think we should nearly always do that when archiving). We need also a canonical reference for this entry (maybe Kelly ??).

4. • CommentRowNumber4.
   • CommentAuthorUrs
   • CommentTimeSep 25th 2012
   • PermaLink
   Author: Urs
   Format: MarkdownItexhave expanded at _[[internal hom]]_ the first two subsections of the _[Examples](http://ncatlab.org/nlab/show/internal+hom#Examples)_-section a little: _In a sheaf topos_ and _In smooth spaces_.

   have expanded at internal hom the first two subsections of the Examples-section a little: In a sheaf topos and In smooth spaces.

5. • CommentRowNumber5.
   • CommentAuthorUrs
   • CommentTimeSep 25th 2012
   • (edited Sep 25th 2012)
   • PermaLink
   Author: Urs
   Format: MarkdownItexafterwards I realized that Idea-section at _[[internal hom]]_ was not in good shape. I have now spent some minutes on trying to improve it. I notice this generally, and it is a bit of a pity: of all entries on the $n$Lab specifically those related to basic category are often poor... and not touched for a long while. This is because we created many of them right when the $n$Lab was very young, and didn't yet have a more "professional" perspective on writing entries. But it's still a pity. I wish somebody would give a course on basic category theory and use the occasion to boost the relevant $n$Lab entries to at least the level of decent course material.

   afterwards I realized that Idea-section at internal hom was not in good shape. I have now spent some minutes on trying to improve it.

   I notice this generally, and it is a bit of a pity: of all entries on the $n$Lab specifically those related to basic category are often poor… and not touched for a long while. This is because we created many of them right when the $n$Lab was very young, and didn’t yet have a more “professional” perspective on writing entries. But it’s still a pity. I wish somebody would give a course on basic category theory and use the occasion to boost the relevant $n$Lab entries to at least the level of decent course material.

6. • CommentRowNumber6.
   • CommentAuthorUrs
   • CommentTimeSep 26th 2012
   • PermaLink
   Author: Urs
   Format: MarkdownI kept adding some things to _[[internal hom]]_. It's not done yet, but I need to quit now.

   I kept adding some things to internal hom. It's not done yet, but I need to quit now.

7. • CommentRowNumber7.
   • CommentAuthorMike Shulman
   • CommentTimeOct 12th 2012
   • PermaLink
   Author: Mike Shulman
   Format: MarkdownItexTodd pointed out at the Cafe that two of the examples at [[internal hom]] used different notation from the rest of the page (and, arguably, poorer notation as well), so I changed them to make the page consistent. I also rewrote the section on internal-homs of super vector spaces to make sense in terms of the definition of a [[graded vector space]] as an indexed family of vector spaces, which is the category-theoretically sensible one.

   Todd pointed out at the Cafe that two of the examples at internal hom used different notation from the rest of the page (and, arguably, poorer notation as well), so I changed them to make the page consistent. I also rewrote the section on internal-homs of super vector spaces to make sense in terms of the definition of a graded vector space as an indexed family of vector spaces, which is the category-theoretically sensible one.

8. • CommentRowNumber8.
   • CommentAuthorPeter Heinig
   • CommentTimeJul 13th 2017
   • (edited Jul 13th 2017)
   • PermaLink
   Author: Peter Heinig
   Format: MarkdownItex[[internal hom]] contained a (trivial) mistake in the sentence > Formally this says that the [[functor]] $(-) \times X$ of taking the cartesian product with the set $S$ has a [[right adjoint]] given by the construction $[X,-]$. I mean, it is obvious from this sentence, at least when taken out of context like above, that the $S$ is wrong and should be $X$. It becomes sort-of-less-wrong in context, i.e. in its former version, > One way to make this precise is to mimic the basic property of a [[function set]] $[X,Y] = \{f : X \to Y\}$ of [[functions]] between two [[sets]] $X$ and $Y$: that is uniquely characterized by the fact that for any other set $S$ the functions $S \to [X,Y]$ are in [[natural bijection]] with the functions $S \times X \to Y$ out of the [[cartesian product]] of $S$ with $X$. Formally this says that the [[functor]] $(-) \times X$ of taking the cartesian product with the set $S$ has a [[right adjoint]] given by the construction $[X,-]$. in view of the "formal variable" $S$, which is presumably the cause for the slight inaccuracy. I therefore simply took out the repeating-what-the-notation-already-says phrase "taking the cartesian product [...]" from the statement of the adjunction, but somehow conserved it by giving it a place inside a verbal repetition of the adjunction, in the spirit of the known functors-are-verbs-metaphor. While I was at it, I made various _stylistic_ changes to the paragraph, all of which I think are improvements. I will not run through all of them here. I found fault with "the basic property" and "Formally this says" (I mean, wasn't the sentence before rather formal already; I changed it to a simple "That is:")

   internal hom contained a (trivial) mistake in the sentence

   Formally this says that the functor $(-) \times X$ of taking the cartesian product with the set $S$ has a right adjoint given by the construction $[X,-]$.

   I mean, it is obvious from this sentence, at least when taken out of context like above, that the $S$ is wrong and should be $X$.

   It becomes sort-of-less-wrong in context, i.e. in its former version,

   One way to make this precise is to mimic the basic property of a function set $[X,Y] = \{f : X \to Y\}$ of functions between two sets $X$ and $Y$: that is uniquely characterized by the fact that for any other set $S$ the functions $S \to [X,Y]$ are in natural bijection with the functions $S \times X \to Y$ out of the cartesian product of $S$ with $X$. Formally this says that the functor $(-) \times X$ of taking the cartesian product with the set $S$ has a right adjoint given by the construction $[X,-]$.

   in view of the “formal variable” $S$, which is presumably the cause for the slight inaccuracy. I therefore simply took out the repeating-what-the-notation-already-says phrase “taking the cartesian product […]” from the statement of the adjunction, but somehow conserved it by giving it a place inside a verbal repetition of the adjunction, in the spirit of the known functors-are-verbs-metaphor.

   While I was at it, I made various stylistic changes to the paragraph, all of which I think are improvements. I will not run through all of them here. I found fault with “the basic property” and “Formally this says” (I mean, wasn’t the sentence before rather formal already; I changed it to a simple “That is:”)

9. • CommentRowNumber9.
   • CommentAuthorUrs
   • CommentTimeJun 10th 2018
   • (edited Jun 10th 2018)
   • PermaLink
   Author: Urs
   Format: MarkdownItexI gave the entry a section _[Basic properties](https://ncatlab.org/nlab/show/internal+hom#BasicProperties)_ with statement and proof of some of the basic properties: 1. $X \otimes (-) \dashv [X,-]$ for each $X$ is sufficient to have bifunctor $[-,-]$; 1. hom adjunction internalizes as $[-,[-,-]] \simeq [-\otimes -,-]$; 1. $[-,-]$ preserves limits in second argument and sends colimits in first to limits I also did some editorial edits: 1. Made explicit that the def as stated is for _symmetric_ monoidal categories. 1. Moved the definition of evaluation map and composition map from "Properties" to "Definition". <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/56">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/56">v56</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

   I gave the entry a section Basic properties with statement and proof of some of the basic properties:

   1. $X \otimes (-) \dashv [X,-]$ for each $X$ is sufficient to have bifunctor $[-,-]$;

   2. hom adjunction internalizes as $[-,[-,-]] \simeq [-\otimes -,-]$;

   3. $[-,-]$ preserves limits in second argument and sends colimits in first to limits

   I also did some editorial edits:

   1. Made explicit that the def as stated is for symmetric monoidal categories.

   2. Moved the definition of evaluation map and composition map from “Properties” to “Definition”.

   diff, v56, current

10. • CommentRowNumber10.
    • CommentAuthorSixuan Lou
    • CommentTimeJul 4th 2018
    • (edited Jul 4th 2018)
    • PermaLink
    Author: Sixuan Lou
    Format: TextHello, I think there's a typo in the first equation of proposition 3.3, colimit notation should be changed to the limit notation. Thanks

    Hello,
    
    I think there's a typo in the first equation of proposition 3.3, colimit notation should be changed to the limit notation.
    
    Thanks
11. • CommentRowNumber11.
    • CommentAuthorUrs
    • CommentTimeJul 4th 2018
    • PermaLink
    Author: Urs
    Format: MarkdownItexThanks for catching this. Fixed now.

    Thanks for catching this. Fixed now.

12. • CommentRowNumber12.
    • CommentAuthorUrs
    • CommentTimeOct 28th 2018
    • PermaLink
    Author: Urs
    Format: MarkdownItexadded a small paragraph on and pointer to _[[stable splitting of mapping spaces]]_. <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/61">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/61">v61</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    added a small paragraph on and pointer to stable splitting of mapping spaces.

    diff, v61, current

13. • CommentRowNumber13.
    • CommentAuthorUrs
    • CommentTimeOct 28th 2018
    • PermaLink
    Author: Urs
    Format: MarkdownItexjust a reminder to myself and anyone who cares: currently _[[mapping space]]_ is still just redirecting to _[[internal hom]]_. Clearly this is not sustainable. Ought to be improved on... <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/61">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/61">v61</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    just a reminder to myself and anyone who cares:

    currently mapping space is still just redirecting to internal hom. Clearly this is not sustainable. Ought to be improved on…

    diff, v61, current

14. • CommentRowNumber14.
    • CommentAuthorTodd_Trimble
    • CommentTimeOct 28th 2018
    • PermaLink
    Author: Todd_Trimble
    Format: MarkdownItexThis is not doubting you, but what aspects of "mapping space" spill outside this redirect?

    This is not doubting you, but what aspects of “mapping space” spill outside this redirect?

15. • CommentRowNumber15.
    • CommentAuthorUrs
    • CommentTimeOct 28th 2018
    • (edited Oct 28th 2018)
    • PermaLink
    Author: Urs
    Format: MarkdownItexThe topological mapping spaces should have a dedicated article of their own, not inside the much broader entry on internal homs.

    The topological mapping spaces should have a dedicated article of their own, not inside the much broader entry on internal homs.

16. • CommentRowNumber16.
    • CommentAuthorTodd_Trimble
    • CommentTimeOct 28th 2018
    • PermaLink
    Author: Todd_Trimble
    Format: MarkdownItexPossibly I could be of assistance, if I knew what you'd want included.

    Possibly I could be of assistance, if I knew what you’d want included.

17. • CommentRowNumber17.
    • CommentAuthorUrs
    • CommentTimeOct 28th 2018
    • (edited Jan 18th 2020)
    • PermaLink
    Author: Urs
    Format: MarkdownItexI am sorry that I apparently consistently come across as being mysterious, I wish I knew what is causing it. All I am saying is that eventually the material on topological mapping spaces should be split off from the entry on internal homs to a stand-alone entry. It's a comment on formatting/entry layout. It seems completely obvious to me, which may be the cause of me not communicating it properly.

    I am sorry that I apparently consistently come across as being mysterious, I wish I knew what is causing it. All I am saying is that eventually the material on topological mapping spaces should be split off from the entry on internal homs to a stand-alone entry. It’s a comment on formatting/entry layout. It seems completely obvious to me, which may be the cause of me not communicating it properly.

18. • CommentRowNumber18.
    • CommentAuthornLab edit announcer
    • CommentTimeJan 18th 2020
    • PermaLink
    Author: nLab edit announcer
    Format: MarkdownItexClarification; 'taking ... out of' has an existing and contradictory meaning in English. linkhyrule5 <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/63">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/63">v63</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    Clarification; ’taking … out of’ has an existing and contradictory meaning in English.

    linkhyrule5

    diff, v63, current

19. • CommentRowNumber19.
    • CommentAuthorMike Shulman
    • CommentTimeJan 18th 2020
    • PermaLink
    Author: Mike Shulman
    Format: MarkdownItexWhat? The only other meaning I can think of is "taking things out of a box" but that doesn't even make any sense as an interpretation here ("the set of all functions" is not "inside" of $X$ in any sense). And "function out of $X$" is a standard mathematical usage for "function with domain $X$", more standard in my idiolect than "function on $X$".

    What? The only other meaning I can think of is “taking things out of a box” but that doesn’t even make any sense as an interpretation here (“the set of all functions” is not “inside” of $X$ in any sense). And “function out of $X$” is a standard mathematical usage for “function with domain $X$”, more standard in my idiolect than “function on $X$”.

20. • CommentRowNumber20.
    • CommentAuthorTodd_Trimble
    • CommentTimeJan 19th 2020
    • PermaLink
    Author: Todd_Trimble
    Format: MarkdownItexI think "function on" is familiar to me, but mostly when it's something like real- or complex-valued functions. It would be nice to know what "contradictory" meaning linkhyrule5 has in mind here. I think "functions out of $X$" or "functions from $X$" both work for me (both with the implication of arrows pointing away from, not toward, $X$).

    I think “function on” is familiar to me, but mostly when it’s something like real- or complex-valued functions. It would be nice to know what “contradictory” meaning linkhyrule5 has in mind here. I think “functions out of $X$” or “functions from $X$” both work for me (both with the implication of arrows pointing away from, not toward, $X$).

21. • CommentRowNumber21.
    • CommentAuthorMike Shulman
    • CommentTimeJan 21st 2020
    • PermaLink
    Author: Mike Shulman
    Format: MarkdownItexChanged to "functions with domain X", which seems maximally unambiguous. <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/64">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/64">v64</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    Changed to “functions with domain X”, which seems maximally unambiguous.

    diff, v64, current

22. • CommentRowNumber22.
    • CommentAuthoraleks
    • CommentTimeJun 3rd 2020
    • PermaLink
    Author: aleks
    Format: MarkdownItexFixed typo. <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/65">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/65">v65</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    Fixed typo.

    diff, v65, current

23. • CommentRowNumber23.
    • CommentAuthorvarkor
    • CommentTimeSep 7th 2021
    • PermaLink
    Author: varkor
    Format: MarkdownItexAdded link to [[residual]], though I'm not sure these pages ought to be distinct. <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/70">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/70">v70</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    Added link to residual, though I’m not sure these pages ought to be distinct.

    diff, v70, current

24. • CommentRowNumber24.
    • CommentAuthorrafayaashary01
    • CommentTimeJul 23rd 2022
    • (edited Jul 23rd 2022)
    • PermaLink
    Author: rafayaashary01
    Format: MarkdownItexGiven a monoidal category $(\mathcal{C},\otimes)$, the usual “provisional” definition of ‘right internal hom of $(\mathcal{C}, \otimes)$’ is a (unique in the appropriate sense, if it exists) collection indexed over objects $c$ of $\mathcal{C}$ of functors $[c, -] \colon \mathcal{C} \to \mathcal{C}$ along with adjunctions $c \otimes (-) \dashv [c, -]$. While this agrees with the ultimately desired bifunctorial notion on objects and on morphisms in the second argument, it is not a priori functorial in the first. In particular, the definition of ‘right internal hom of $(\mathcal{C},\otimes)$’ that we ultimately desire is a bifunctor $[-, -] \colon \mathcal{C}^{op} \times \mathcal{C} \to \mathcal{C}$ that satisfies $$Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1}) \simeq Hom_{\mathcal{C}}(c', [c_{0}, c_{1}])$$ naturally in all three arguments. Accordingly, [Proposition 3.1](https://ncatlab.org/nlab/revision/internal+hom/70#BasicProperties) establishes that a right internal hom in the former provisional sense can always be (uniquely, in the appropriate sense) upgraded to a right internal hom in the latter bifunctorial sense. But Yoneda’s lemma implies that the weaker condition that for all pairs of objects $c_{0}$, $c_{1}$ of $\mathcal{C}$, the functor $c' \mapsto Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1})$ is representable suffices to imply the existence of the aformentioned bifunctor. I guess my question is whether it would it be of any utility to rewrite [Definition 2.1](https://ncatlab.org/nlab/revision/internal+hom/70#definition) so that ‘a right internal hom of $(\mathcal{C}, \otimes)$’ is defined to be a bifunctor $[-, -] \colon \mathcal{C}^{op} \times \mathcal{C} \to \mathcal{C}$ equipped with a natural (in $c$, $c_{0}$, and $c_{1}$) isomorphism $$\kappa \colon Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1}) \to Hom_{\mathcal{C}}(c', [c_{0}, c_{1}])$$ and then to prove as propositions 1. That there is a unique natural transformation from any one such right internal hom to any other such internal hom that is compatible with its Currying isomorphism 1. Thus that a right internal Hom of $(\mathcal{C}, \otimes)$ is unique if it exists) 1. That the existence of such a right internal hom is equivalent to the practically weaker condition that for all pairs $(c_{0}, c_{1})$ of objects of $\mathcal{C}$, the functor $c' \mapsto Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1})$ is representable. In particular, we would be eliding adjunction from the discussion in favor of applying Yoneda’s lemma directly.

    Given a monoidal category $(\mathcal{C},\otimes)$, the usual “provisional” definition of ‘right internal hom of $(\mathcal{C}, \otimes)$’ is a (unique in the appropriate sense, if it exists) collection indexed over objects $c$ of $\mathcal{C}$ of functors $[c, -] \colon \mathcal{C} \to \mathcal{C}$ along with adjunctions $c \otimes (-) \dashv [c, -]$.

    While this agrees with the ultimately desired bifunctorial notion on objects and on morphisms in the second argument, it is not a priori functorial in the first. In particular, the definition of ‘right internal hom of $(\mathcal{C},\otimes)$’ that we ultimately desire is a bifunctor $[-, -] \colon \mathcal{C}^{op} \times \mathcal{C} \to \mathcal{C}$ that satisfies

    $$Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1}) \simeq Hom_{\mathcal{C}}(c', [c_{0}, c_{1}])$$

    naturally in all three arguments.

    Accordingly, Proposition 3.1 establishes that a right internal hom in the former provisional sense can always be (uniquely, in the appropriate sense) upgraded to a right internal hom in the latter bifunctorial sense.

    But Yoneda’s lemma implies that the weaker condition that for all pairs of objects $c_{0}$, $c_{1}$ of $\mathcal{C}$, the functor $c' \mapsto Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1})$ is representable suffices to imply the existence of the aformentioned bifunctor.

    I guess my question is whether it would it be of any utility to rewrite Definition 2.1 so that ‘a right internal hom of $(\mathcal{C}, \otimes)$’ is defined to be a bifunctor $[-, -] \colon \mathcal{C}^{op} \times \mathcal{C} \to \mathcal{C}$ equipped with a natural (in $c$, $c_{0}$, and $c_{1}$) isomorphism

    $$\kappa \colon Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1}) \to Hom_{\mathcal{C}}(c', [c_{0}, c_{1}])$$

    and then to prove as propositions

    1. That there is a unique natural transformation from any one such right internal hom to any other such internal hom that is compatible with its Currying isomorphism

    2. Thus that a right internal Hom of $(\mathcal{C}, \otimes)$ is unique if it exists)

    3. That the existence of such a right internal hom is equivalent to the practically weaker condition that for all pairs $(c_{0}, c_{1})$ of objects of $\mathcal{C}$, the functor $c' \mapsto Hom_{\mathcal{C}}(c_{0} \otimes c', c_{1})$ is representable.

    In particular, we would be eliding adjunction from the discussion in favor of applying Yoneda’s lemma directly.

25. • CommentRowNumber25.
    • CommentAuthorHurkyl
    • CommentTimeJul 23rd 2022
    • (edited Jul 23rd 2022)
    • PermaLink
    Author: Hurkyl
    Format: MarkdownItexI suspect the motivation for that framing is that it's often interesting to talk about [[exponentiable objects]] even when not every object is exponentiable, which leads to one talking about the situation where _every_ object is exponentiable. I would actually suggest rewriting this definition in the opposite way: define the internal hom pointwise -- i.e. for each pair $c_0, c_1$, define an internal hom to be a representing object* for $\hom(c_0 \otimes -, c_1)$ if one exists -- and then invoke yoneda to prove that it's uniquely functoral on the full subcategory where they exist for any global choice of internal homs for each pair. That way it's more general; you can talk about internal homs even when they don't exist for every pair. I suppose taking the functor as part of the definition sweeps the "once you make a choice" under the rug, for better or for worse. *: For the sake of precision, by "representing object" I mean to include both the object $[c_0, c_1]$ and the natural isomorphism $\hom(-, [c_0, c_1]) \cong \hom(c_0 \otimes -, c_1)$ is part of the data.

    I suspect the motivation for that framing is that it’s often interesting to talk about exponentiable objects even when not every object is exponentiable, which leads to one talking about the situation where every object is exponentiable.

    I would actually suggest rewriting this definition in the opposite way: define the internal hom pointwise – i.e. for each pair $c_0, c_1$, define an internal hom to be a representing object* for $\hom(c_0 \otimes -, c_1)$ if one exists – and then invoke yoneda to prove that it’s uniquely functoral on the full subcategory where they exist for any global choice of internal homs for each pair. That way it’s more general; you can talk about internal homs even when they don’t exist for every pair. I suppose taking the functor as part of the definition sweeps the “once you make a choice” under the rug, for better or for worse.

    *: For the sake of precision, by “representing object” I mean to include both the object $[c_0, c_1]$ and the natural isomorphism $\hom(-, [c_0, c_1]) \cong \hom(c_0 \otimes -, c_1)$ is part of the data.

26. • CommentRowNumber26.
    • CommentAuthorvarkor
    • CommentTimeJul 23rd 2022
    • PermaLink
    Author: varkor
    Format: MarkdownItexRe. #24. Just to point out that the structure you are describing is a [[two-variable adjunction]]. The internal hom can be phrased in both ways, but I agree with Hurkyl that in practice one is often interested in the setting in which the hom exists only for some objects.

    Re. #24. Just to point out that the structure you are describing is a two-variable adjunction. The internal hom can be phrased in both ways, but I agree with Hurkyl that in practice one is often interested in the setting in which the hom exists only for some objects.

27. • CommentRowNumber27.
    • CommentAuthornLab edit announcer
    • CommentTimeJun 30th 2023
    • PermaLink
    Author: nLab edit announcer
    Format: MarkdownItexremoving the previous edit Jg <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/74">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/74">v74</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    removing the previous edit

    Jg

    diff, v74, current

28. • CommentRowNumber28.
    • CommentAuthorRodMcGuire
    • CommentTimeJun 30th 2023
    • PermaLink
    Author: RodMcGuire
    Format: MarkdownItex27 > removing the previous edit No you didn't. You still removed the parenthesis which are needed to understand the composite morphism, which I have restored. $$ [Y, Z] \times [X , Y] \times X \stackrel{(id_{[Y,Z]}, eval_{X,Y})}{\to} [Y,Z] \times Y \stackrel{eval_{Y,Z}}{\to} Z \,. $$ $$ [Y, Z] \times ([X , Y] \times X) \stackrel{(id_{[Y,Z]}, eval_{X,Y})}{\to} [Y,Z] \times Y \stackrel{eval_{Y,Z}}{\to} Z \,. $$ <a href="https://ncatlab.org/nlab/revision/diff/internal+hom/75">diff</a>, <a href="https://ncatlab.org/nlab/revision/internal+hom/75">v75</a>, <a href="https://ncatlab.org/nlab/show/internal+hom">current</a>

    27

    removing the previous edit

    No you didn’t. You still removed the parenthesis which are needed to understand the composite morphism, which I have restored.

    $$[Y, Z] \times [X , Y] \times X \stackrel{(id_{[Y,Z]}, eval_{X,Y})}{\to} [Y,Z] \times Y \stackrel{eval_{Y,Z}}{\to} Z \,.$$ $$[Y, Z] \times ([X , Y] \times X) \stackrel{(id_{[Y,Z]}, eval_{X,Y})}{\to} [Y,Z] \times Y \stackrel{eval_{Y,Z}}{\to} Z \,.$$

    diff, v75, current