From: Michael Barr <barr@math.mcgill.ca>
To: Categories list <categories@mta.ca>
Subject: On defining *-autonomous categories
Date: Sun, 16 Dec 2007 21:45:53 -0500 (EST) [thread overview]
Message-ID: <E1J4IS7-00041o-21@mailserv.mta.ca> (raw)
I got a note from a student named Benjamin Jackson saying that someone had
told him that to define a *-autonomous category, you need only a symmetric
monoidal category and a contravariant involution * such that Hom(A @ B,C*)
= Hom(A,(B @ C)*). Here "=" means natural equivalence and @ is the tensor
product. Not only is this apparently true but that equivalence is needed
only for A = I, the tensor unit. Of course, what is going on is that all
the coherence is built-in to the structure of a symmetric monoidal
category.
First define A --o B = (A @ B*)*. Then the isomorphism above implies that
Hom(A,B) = Hom(I @ A,B) = Hom(I,(A @ B*)*) = Hom(I,A --o B)
Next we see that
(A @ B) --o C = (A @ B @ C*)* = A --o (B @ C*)* = A --o (B --o C)
and, applying Hom(I,-), that
Hom(A @ B,C) = Hom(A,B --o C)
Also we have that
A --o I* = (A @ I)* = A* and A --o B = (A @ B*)* = (B* @ A)* = B* --o A*
which gives the structure of a *-autonomous category with dualizing
object I*.
The trouble with this is that generally speaking it is the --o which is
obvious and the tensor is derived from it. The coherences involving
internal hom alone are much less well-known, although they are included
in the original Eilenberg-Kelly paper in the La Jolla Proceedings.
Still I am surprised that I never noticed this before.
next reply other threads:[~2007-12-17 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 2:45 Michael Barr [this message]
2007-12-17 18:29 Peter Selinger
2007-12-18 13:08 Robin Houston
2007-12-18 14:27 Robin Houston
2007-12-19 12:04 Prof. Peter Johnstone
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=E1J4IS7-00041o-21@mailserv.mta.ca \
--to=barr@math.mcgill.ca \
--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).