categories - Category Theory list
 help / color / mirror / Atom feed
From: David Roberts <droberts@maths.adelaide.edu.au>
To: David Leduc <david.leduc6@googlemail.com>
Cc: categories <categories@mta.ca>
Subject: Re: Evil in bicategories
Date: Sun, 12 Sep 2010 10:58:01 +0930	[thread overview]
Message-ID: <E1OusPy-0001oF-2N@mlist.mta.ca> (raw)
In-Reply-To: <E1OuQsT-0003hL-P6@mlist.mta.ca>

Hi David,

We had a discussion about this at some point in the n-group
(n-category cafe, nLab etc), and it isn't evil to assume that source
and target must be equal, as this is a _typing_ issue, rather than an
equality predicate. A morphism f in a 1-category C is an element of
the set C(a,b) with a = s(f) and b=t(f). In this set it is not evil to
test for equality (unless one has gone so far as to negate equality on
hom-sets, but then I can't help you!). Composition is _defined_ as a
map

C(a,b) x C(b,c) ----> C(a,c)

and so even in a 1-category without an equality predicate on the
collection of objects, it isn't evil to say, for example that a square
commutes (i.e. the two composites of two different pairs of morphisms
are equal).

It is no different in a bicategory B: it may be evil to assert that
two arbitrary 1-arrows are equal, but the hom-categories are indexed
by the objects (I don't know if this requires an extension of
dependent type theory, or if one can have types depending on types,
themselves dependent on something else - I'm no expert on DTT). Thus
for two objects of a hom-category B(a,b) you may not assert two are
equal, but you do know that they have the same source a and target b.

David Roberts

On 11 September 2010 11:35, David Leduc <david.leduc6@googlemail.com> wrote:
> In a bicategory, composition of 1-cells is associative up to
> isomorphism. Because it would be evil to insist that h o (g o f) is
> equal to (h o g) o f. However the source and target objects of those
> compositions must be equal. Isn't it evil? Why not weaken this
> requirement by saying that the sources (respectively, targets) of h o
> (g o f) and (h o g) o f must only be isomorphic?
>


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


  parent reply	other threads:[~2010-09-12  1:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-11  2:05 David Leduc
2010-09-11 23:23 ` Toby Bartels
2010-09-12  1:28 ` David Roberts [this message]
2010-09-12  6:03 ` Jocelyn Paine
     [not found] ` <20100911232358.GA32145@ugcs.caltech.edu>
2010-09-12  6:27   ` David Leduc
     [not found]   ` <AANLkTimbfG0tkjSNZgjL2yADBHnKAXQiHYsAkioEnxJY@mail.gmail.com>
2010-09-12  7:31     ` Toby Bartels
     [not found] ` <20100912073136.GA9115@ugcs.caltech.edu>
2010-09-12 10:22   ` David Leduc
     [not found]   ` <AANLkTi=ZLdVcbvaHPaCfaZhzyDYCdwLNUQTj-5fNZ4p4@mail.gmail.com>
2010-09-12 17:13     ` Toby Bartels
2010-09-12 12:38 ` JeanBenabou
2010-09-13  0:16   ` David Roberts
2010-09-13 22:28     ` Toby Bartels
2010-09-14 22:32     ` Richard Garner
2010-09-14 15:09   ` Miles Gould
2010-09-12 16:52 ` Peter LeFanu Lumsdaine
2010-09-14  6:28 Michael Shulman
2010-09-15  1:12 Vaughan Pratt

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=E1OusPy-0001oF-2N@mlist.mta.ca \
    --to=droberts@maths.adelaide.edu.au \
    --cc=categories@mta.ca \
    --cc=david.leduc6@googlemail.com \
    /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).