From: "Reinhard Boerger" <Reinhard.Boerger@FernUni-Hagen.de>
To: "'Michael Shulman'" <mshulman@ucsd.edu>
Cc: <categories@mta.ca>
Subject: Re: source, sinks, and ?
Date: Tue, 4 Jan 2011 11:44:01 +0100 [thread overview]
Message-ID: <E1Pa7b4-0006BJ-Rk@mlist.mta.ca> (raw)
Hello,
I am used to a slightly different terminology, which seems appropriate.
> A family of morphisms { x_i --> y }_{i \in I} in some category, all
> with the same codomain, is called a "sink" or a "cocone".
For a sink, as I know it, the codomain should also be specified, i.e. a sink
is given by an object y and a family of morphisms x_i --> y. If I is not
empty, this does not matter, but for empty I at least y should be given. A
cocone is given by an object y and a natural transformation from some
functor to the constant functor with value y; her y is also specified. So a
sink is essentially a discrete cocone.
A family {
> x --> y_j }_{j \in J} all with the same domain is called a "source" or
> a "cone".
These are the dual notions.
> Is there a name for a family of the form { x_i --> y_j }_{i
> \in I, j \in J} ? A cylinder? Or a frustrum (since I \neq J)?
I do not know. Where does it occur? Probably the domain and codomain should
also be specified, possibly even an arrow. If a non-empty collection of
arrows behave similarly (e.g. is mapped to the same arrow by a given functor
F), this means the same a saying that they all behave in the same way as a
given arrow 8e.g are mapped to some special morphism by F). A collection of
two objects x,y (prescribed domain and codomain) is something different; it
does not give an arrow Fx -->Fy.
Greetings
Reinhard
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next reply other threads:[~2011-01-04 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 10:44 Reinhard Boerger [this message]
2011-01-04 18:31 ` Michael Shulman
2011-01-05 4:30 ` JeanBenabou
-- strict thread matches above, loose matches on Subject: below --
2011-01-03 0:40 Fred E.J. Linton
2011-01-02 23:26 Michael Shulman
2011-01-03 22:40 ` burroni
2011-02-04 18:48 ` Tom Prince
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Pa7b4-0006BJ-Rk@mlist.mta.ca \
--to=reinhard.boerger@fernuni-hagen.de \
--cc=categories@mta.ca \
--cc=mshulman@ucsd.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).