categories - Category Theory list
 help / color / mirror / Atom feed
From: Scott Morrison <scott@tqft.net>
To: Steve Vickers <s.j.vickers@cs.bham.ac.uk>
Cc: John Baez <baez@math.ucr.edu>, categories <categories@mta.ca>
Subject: Re: only_marketing_?
Date: Wed, 21 Aug 2019 13:30:22 +1000	[thread overview]
Message-ID: <E1i0NLM-0003EY-1n@mlist.mta.ca> (raw)
In-Reply-To: <E1i08K9-0003z6-FP@mlist.mta.ca>

(On the subject of "letting go of the strict domain-codomain discipline"...)

In my work with Kevin Walker (e.g. https://arxiv.org/abs/1009.5025,
particularly the disklike n-categories of \S 6) we talk about
n-categories for which notions of input and output are solely "in the
eye of the beholder", and argue that this is a convenient and natural
language for the role of categories in TFT.

As an application of this, in a very recent paper with Kevin and Paul
Wedrich, https://arxiv.org/abs/1907.12194, we give what is arguably
the "first interesting example" of a 4-category, built out of Khovanov
homology. Formalising this gadget as a disklike 4-category, we can say
enough to produce invariants of oriented 4-manifolds. Attempting
instead to formalise this gadget as a "conventional" "domain-codomain"
4-category, we were much less satisfied --- we can check the axioms
for a braided monoidal 2-category, but after that it's not
particularly clear which duality properties one would need to check
(in Lurie's language, perhaps this is working out what an SO(4)-fixed
point structure actually is?) in order to continue on to building
4-manifold invariants.

best regards,
Scott

On Wed, Aug 21, 2019 at 3:56 AM Steve Vickers <s.j.vickers@cs.bham.ac.uk> wrote:
>
> Dear John,
>
> Those are rather pertinent examples, as the dagger closed and hypergraph categories show up a weakness in my question.
>
> I asked about seeking objects, morphisms, identities and associative composition, which seems very natural because it's the basic definition of category. Everything has a domain and a codomain, an input and an output, and composition is malformed unless it's domain with codomain. This leads many of our category theoretic intuitions to be based on thinking of objects and morphisms as being, at some level of abstraction, like sets and functions.
>
> Once you have set up the structure of what is input and what is output, it takes some effort to forget it. Dagger closed and the associated string diagrams provide a mechanism for doing that.
>
> A good example is Rel. A morphism from X1 x ... x Xm to Y1 x ... x Yn is just a subset of X1 x ... x Xm x Y1 x ... x Yn, in the light of which it is  perhaps perverse to impose domain and codomain structure - unless, perhaps  you want to carry on to say which relations are functional.
>
> As you propose, this certainly looks like a good way to analyse networks,  and open systems where there is an interface between internal structure and external behaviour, an interface along which we must compose components.
>
> I've heard Jamie Vicary and others use the word "compositionality" as something not quite the same as category theory. Is this what they mean, letting go of the strict domain-codomain discipline?
>
> All the best,
>
> Steve.
>
>

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


  reply	other threads:[~2019-08-21  3:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 14:37 only_marketing_? Eduardo J. Dubuc
2019-08-08  7:01 ` only_marketing_? Patrik Eklund
2019-08-12  0:03   ` only_marketing_? Vaughan Pratt
2019-08-16 10:40     ` only_marketing_? Steve Vickers
2019-08-16 16:30       ` only_marketing_? Alexander Kurz
2019-08-17  3:44       ` only_marketing_? John Baez
2019-08-20  8:55         ` only_marketing_? Steve Vickers
2019-08-21  3:30           ` Scott Morrison [this message]
2019-08-12  8:32   ` only_marketing_? John Baez
2019-08-20 23:32   ` only_marketing_? Bob Coecke
2019-08-08  5:34 only_marketing_? Ellerman, David
2019-08-12  3:54 ` only_marketing_? John Baez
2019-08-13  6:16   ` only_marketing_? David Espinosa
2019-08-13 19:53     ` only_marketing_? Vaughan Pratt
2019-08-16 10:44       ` only_marketing_? Patrik Eklund

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=E1i0NLM-0003EY-1n@mlist.mta.ca \
    --to=scott@tqft.net \
    --cc=baez@math.ucr.edu \
    --cc=categories@mta.ca \
    --cc=s.j.vickers@cs.bham.ac.uk \
    /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).