From: "Fred E.J. Linton" <fejlinton@usa.net>
To: categories <categories@mta.ca>
Subject: Re: bilax_monoidal_functors
Date: Mon, 10 May 2010 21:04:53 -0400 [thread overview]
Message-ID: <E1OBzdr-0007S4-8r@mailserv.mta.ca> (raw)
Jeff Egger <jeffegger@yahoo.ca> wrote, in part,
> My objection to the phrase "autonomous category" (which
> Dusko brought up) has less to do with defending Fred
> Linton's original usage of that phrase than the fact
> that "autonomous category" is a special case (and, from
> one point of view, a rather uninteresting special case)
> of "star-autonomous category", whereas it sounds like
> "star-autonomous category" should mean an "autonomous
> category" with some extra structure. (And, of course,
> this once was the case, w.r.t. the older terminology.)
> This is confusing; hence one term or the other should
> be changed. I am, in fact, open to all suggestions,
> though I cannot help but prefer that "star-autonomous"
> be kept and "autonomous" changed.
Without seeking to prolong the use of "autonomous" today,
let me just say in my defense that, at the time I brought
that term into use, I was thinking it was the sort of
place-holder name that would, eventually, be replaced (as
it has been) by something more appropriate. This was, as I
recall, also the original motivation for the term "exact";
fortunately for its coiners, "exact" worked so well that
it never did need to get replaced. "Autonomous," on the
other hand, was not nearly as felicitous a choice, and has
long since been superceded -- I have no qualms about that,
nor any regrets (all the fewer because, as I recall, I was
at that time thinking only of symmetric closed monoidal
categories V for which the Set-valued Hom functor V(E, -)
(E the monoidal unit object) was faithful :-) ).
Cheers, -- Fred
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next reply other threads:[~2010-05-11 1:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 1:04 Fred E.J. Linton [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-15 16:23 bilax_monoidal_functors Jeff Egger
2010-05-11 8:28 bilax_monoidal_functors?= Michael Batanin
2010-05-15 16:54 ` bilax_monoidal_functors Jeff Egger
2010-05-09 16:26 bilax_monoidal_functors?= Andre Joyal
2010-05-10 19:28 ` bilax_monoidal_functors Jeff Egger
2010-05-13 17:17 ` bilax_monoidal_functors Michael Shulman
2010-05-15 1:05 ` bilax_monoidal_functors Andre Joyal
2010-05-08 3:27 RE : bilax monoidal functors John Baez
2010-05-10 10:28 ` Urs Schreiber
2010-05-11 3:17 ` bilax_monoidal_functors Andre Joyal
2010-05-14 14:34 ` bilax_monoidal_functors Michael Shulman
2010-05-08 1:05 bilax monoidal functors David Yetter
2010-05-07 18:03 John Baez
2010-05-08 2:23 ` Andre Joyal
2010-05-08 23:11 ` Michael Batanin
2010-05-10 16:12 ` Toby Bartels
[not found] ` <4BE5EF9C.1060907@ics.mq.edu.au>
2010-05-08 23:34 ` John Baez
2010-05-08 9:38 ` Steve Lack
[not found] ` <C80B6E26.B13C%s.lack@uws.edu.au>
2010-05-08 23:19 ` John Baez
2010-05-06 23:02 Q. about " Steve Lack
2010-05-07 14:59 ` bilax " Joyal, André
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=E1OBzdr-0007S4-8r@mailserv.mta.ca \
--to=fejlinton@usa.net \
--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).