From: Paul Levy <P.B.Levy@cs.bham.ac.uk>
To: robin@ucalgary.ca, categories@mta.ca
Subject: Re: Conditions for adjoints -- another variant
Date: Sun, 25 Oct 2009 10:05:48 +0000 [thread overview]
Message-ID: <E1N24XR-0004P4-M6@mailserv.mta.ca> (raw)
Hi Robin,
In my thesis
http://www.cs.bham.ac.uk/~pbl/papers/thesisqmwphd.pdf
Def. 109 - 110, pages 220-222
I listed six (equivalent) definitions of adjunction, one of which (Def.
110(4)) resembles yours, and two of which (Def. 110(4)-(5)) don't mention
any functors.
(Some of these definitions - though not the one that resembles yours - use
the notion of "representing object", which itself can be defined in either
element style or naturality style.)
The list also appears in my "Call-by-push-value" book, Def. 9.33 (page 235)
and Def. 11.17 (pages 278-280).
Also see the discussion in Sect. 1.2 of my TAC paper "Adjunction models for
call-by-push-value with stacks"
http://www.tac.mta.ca/tac/volumes/14/5/14-05abs.html
regards,
Paul
On Sat, 24 Oct 2009 17:11:26 -0600 (MDT), robin@ucalgary.ca wrote:
> BTW. Here are some even cleaner conditions ....
>
> There is an adjoint between two categories iff
> there are two object functions F and G (not required to be functors) and
> For each X \in \X and Y \in \Y there are two functions:
>
> #: \X(X,G(Y)) -> \Y(F(X),Y) ---- sharp
> @: \Y(F(X),Y) -> \X(X,G(Y)) ---- flat
>
> (i)' @ and # are inverse @(#(f)) = f and #(@(g)) = g
> (ii)' @(h k) = @(h) @(#(1) k) and dually #(xy) = #(x @(1)) #(y)
>
> Still hoping to find where these all are recorded!!
>
> -robin
>
>
>
>
>
>
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next reply other threads:[~2009-10-25 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 10:05 Paul Levy [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-09 23:50 Ellis D. Cooper
2009-11-01 2:20 Ellis D. Cooper
2009-10-25 1:03 Dusko Pavlovic
2009-10-24 23:11 robin
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=E1N24XR-0004P4-M6@mailserv.mta.ca \
--to=p.b.levy@cs.bham.ac.uk \
--cc=categories@mta.ca \
--cc=robin@ucalgary.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).