categories - Category Theory list
 help / color / mirror / Atom feed
From: Toby Bartels <toby+categories@ugcs.caltech.edu>
To: categories <categories@mta.ca>
Subject: Re: bilax monoidal functors
Date: Mon, 10 May 2010 09:12:58 -0700	[thread overview]
Message-ID: <E1OBdE1-0002OI-E4@mailserv.mta.ca> (raw)
In-Reply-To: <E1OBEDT-0000fS-HG@mailserv.mta.ca>

Michael Batanin wrote:

>Dear John and Andre,

>I am using a mixture of your terminologies:
>  monoidal = 1-braided
>  braided = 2-braided
>  sylleptic = 3-braided
>......

I think that this terminology is dangerous.

While there is a debate to be had over which is better:
John's "k-tuply monoidal" or André's "k-braided monoidal",
the good thing about either of them is that you can understand them
without having to be told precisely how the numbering works,
as long as you follow the rule that "1-foo" = "foo".
So while I also prefer John's numbering to André's,
I'm happy to use either and have had occasion to use both.
But mixing John's numbering with André's terminology would confuse me.

Sometimes the "1-foo" = "foo" rule is violated.
I was very confused when I first saw "n-connected space";
I'd have understood "n-simply connected space" right away.
I tend to think that a lot of established names are badly numbered,
including "n-category" which may be the most basic on a categories list,
but it doesn't really cause any problems as long as "1-foo" = "foo".


--Toby


[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


  reply	other threads:[~2010-05-10 16:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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
  -- 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-11  1:04 bilax_monoidal_functors Fred E.J. Linton
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-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=E1OBdE1-0002OI-E4@mailserv.mta.ca \
    --to=toby+categories@ugcs.caltech.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).