From: Vaughan Pratt <pratt@CS.Stanford.EDU>
To: <categories@mta.ca>
Subject: Re: Questions on dinatural transformations.
Date: Thu, 01 Jul 2004 10:01:28 -0700 [thread overview]
Message-ID: <200407011701.i61H1SRH005609@coraki.Stanford.EDU> (raw)
>From: noson@sci.brooklyn.cuny.edu
>I was hoping that the category of small categories, functors and
>dinat transformations...
There's a category problem already at this point. Dinats don't go between
functors F,G:C->D, they go between sesquifunctors F:C^op x C->D and differ
from n.t.'s of that type by only being defined on the diagonal of C^op x C.
The off-diagonal and non-identity-morphism entries in F,G only participate
in the dinaturality condition, not in the transformation itself.
>a) It is well known that there is no vertical
>composition of dinatural transformations.
>How about horizontal composition?
Before you can compose dinats horizontally you have to be able to compose
the sesquifunctors they bridge. I don't know how others do this, but if I
had to compose G:D^op x D -> E with F:C^op x C -> D, my inclination would
be to restrict the evident composite G(F(a,b),F(c,d)) to a=d, b=c (i.e.
where the variances match up). That is, GoF:C^op x C -> E is defined by
G(F(c,c'),F(c',c)) on object pairs (c',c) of C^op x C, with the expected
extension to morphism pairs (f',f) where f':c'->d' in C^op (i.e.
f':d'->c' in C) and f:c->d in C, namely
G(F(f,f'),F(f',f)): G(F(c,c'),F(c',c)) -> G(F(d,d'),F(d',d)).
With that (or some) choice of sesquifunctor composition one can then ask
about horizontal composition tos where s:F->F', t:G->G'. How would you
whisker a dinatural on the left, i.e. apply the whisker G:D^op x D->E
on the left to the dinat s:F->F' on the right where F,F':C^op x C->D?
For natural transformations, G is just a functor G:D->E, so this is just a
matter of applying G pointwise to each s_c. For dinaturals however, G is
a sesquifunctor. What do you want a sesquifunctor to do to a morphism s_c?
Maybe there's some span-like thing one can do here but I don't see it.
For dinaturals, vertical composition may turn out to be easier than
horizontal, in that it at least makes sense provided one solves the
shape-matching problem somehow. In doing so one also solves another
problem, that dinaturality is too weak a condition, typically admitting
transformations on the internal hom that aren't Church numerals (Pare & Roman,
JPAA 128 33-92 for Set, Pratt, TCS 294:3, bottom of p461, for Chu(Set,K) and
chu(Set,K) which awkwardly seem to need different treatments). Mike Barr
has a notion of strong dinatural (unpublished?), and the notion of binary
(more generally n-ary) logical transformation also works well here when
definable on the category of interest.
Vaughan Pratt
next reply other threads:[~2004-07-01 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 17:01 Vaughan Pratt [this message]
2004-07-03 0:20 ` Claudio Hermida
-- strict thread matches above, loose matches on Subject: below --
2004-06-29 17:19 Noson Yanofsky
2004-07-01 1:15 ` Phil Scott
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=200407011701.i61H1SRH005609@coraki.Stanford.EDU \
--to=pratt@cs.stanford.edu \
--cc=categories@mta.ca \
/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).