categories - Category Theory list
 help / color / mirror / Atom feed
From: JS Lemay <js.lemay@mq.edu.au>
To: Categories mailing list <categories@mq.edu.au>
Subject: Re: Defining composition via colimit
Date: Fri, 3 Nov 2023 10:29:05 +0000	[thread overview]
Message-ID: <ME2PR01MB31229E56D7A2AC04E426C8CFCDA5A@ME2PR01MB3122.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <a31ae7ae-b5f5-4f86-9b4f-0b36adab1ea7-0@mqoutlook.onmicrosoft.com>

[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]

[[The following message is sent on behalf of streicher@mathematik.tu-darmstadt.d -- for whatever reason it did not seem to have been sent/approved properly to the mailing list, apologies if you receive multiple copies]]


Composition of distributors or profunctors would be an example. But
composition is only defined up to isomorphism and so one gets a
bicategory. This was done in the second half of the sixties by Benabou.

But the situation can be rectified when redefining distributors from A to B
as cocontinuous functors from Psh(A) to Psh(B).

Thomas

PS I take the opportunity to thank Bob for organising and moderating the
categories list for such a long time.
And thanks to the people who have taken over! I missed it for quite some
time already!

> In a current project we have the following situation. For a category
> we are attempting to define, we know what the objects are, and also
> the morphisms. Unfortunately we do not have an obvious composition
> operation. What we do have is a "colimit" operation, which operates on
> a directed graph labelled by our objects and morphisms, and returns a
> putative colimit object equipped with a family of morphisms in the
> usual way (or fails.)
>
> We then define the composite of morphisms A->B, B->C to be the
> colimit of the diagram A->B->C. We then check that this composition
> operation satisfies the axioms of a category, and that our earlier
> colimit construction is indeed an actual colimit with respect to the
> compositional structure. It seems that everything works fine, and we
> are happy.
>
> My question is whether this has any precedent in the literature. The
> situation as I have described it is a bit simplified, in reality there
> is some higher categorical stuff going on. Personally I'm sure I've
> read similar things in the literature in the past but I can't track
> them down now that I actually need them. The nLab article on
> "composition" has some stuff about this with regard to transfinite
> composition, but we're not trying to do anything transfinite here.
>
> Best wishes,
> Jamie
>
>
>
> ----------
>
> You're receiving this message because you're a member of the Categories
> mailing list group from Macquarie University.
>
> Leave group:
> https://outlook.office365.com/owa/categories@mq.edu.au/groupsubscription.ashx?source=EscalatedMessage&action=leave&GuestId=4d7e0354-0b41-4b99-be68-d7eebf3df1ae<https://outlook.office365.com/owa/categories@mq.edu.au/groupsubscription.ashx?source=EscalatedMessage&action=leave&GuestId=4d7e0354-0b41-4b99-be68-d7eebf3df1ae>
>


[-- Attachment #2: Type: text/html, Size: 3722 bytes --]

       reply	other threads:[~2023-11-03 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f93fc7025b48c018f4d644ae95d2f11e.squirrel@webmail.mathematik.tu-darmstadt.de>
     [not found] ` <a31ae7ae-b5f5-4f86-9b4f-0b36adab1ea7-0@mqoutlook.onmicrosoft.com>
2023-11-03 10:29   ` JS Lemay [this message]
2023-10-26 14:14 Signing off Bob Rosebrugh
2023-11-02 18:55 ` Defining composition via colimit Jamie Vicary
2023-11-02 23:23   ` Richard Garner

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=ME2PR01MB31229E56D7A2AC04E426C8CFCDA5A@ME2PR01MB3122.ausprd01.prod.outlook.com \
    --to=js.lemay@mq.edu.au \
    --cc=categories@mq.edu.au \
    /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).