categories - Category Theory list
 help / color / mirror / Atom feed
From: Richard Garner <rhgg2@hermes.cam.ac.uk>
To: Michael Shulman <shulman@uchicago.edu>, categories@mta.ca
Subject: Re: abstraction of notation from sets.
Date: Fri, 26 Feb 2010 18:53:21 +0000 (GMT)	[thread overview]
Message-ID: <E1NlSzO-0004nQ-A6@mailserv.mta.ca> (raw)
In-Reply-To: <E1Nl4KC-0001ih-Fm@mailserv.mta.ca>


> One cannot write "a \in C" to mean that a is an object of
> the category C, at least as long as \in is restricted to
> its precise set-theoretic meaning.  However, in my
> experience it is fairly common to write "a \in C" with this
> meaning, although perhaps not so common in formal
> mathematical writing.

> One can refer to this sort of thing perjoratively as an "abuse of
> notation," but one can also regard it as a perfectly legitimate part of
> informal mathematical language which is not captured by the
> set-theoretic encoding.  One could also formalize it by regarding the
> symbol "\in" as "overloaded" in a precise sense analogous to programming
> languages.

I think it is more perspicuous to treat this, not as an
overloading of \in, but as an "implicit conversion"
associated to the notion of category; that is, we allow the
forgetful functor Cat->Set to be applied silently in contexts
which otherwise would not type-check. In fact the vast
majority of "abuses of notation" are of this character, when
applied to, for example, any forgetful functor from an
Eilenberg-Moore category; the discrete category functor
Set->Cat; the Yoneda embedding C -> [C^op, Set]; the
forgetful functor from universal cones to their vertex, etc,
etc. In principle this becomes problematic as soon as the
category generated by all such implicit conversions has
non-identity idempotents; in practice, this category is free
on a graph and we hope to identify a shortest path between
two vertices!

Richard


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


  reply	other threads:[~2010-02-26 18:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  0:43 peasthope
2010-02-24 14:39 ` Johannes Huebschmann
2010-02-24 15:59 ` Mikael Vejdemo-Johansson
2010-02-24 16:46 ` Aleks Kissinger
2010-02-25  7:17 ` Partha Pratim Ghosh
2010-02-25 18:26   ` Michael Shulman
2010-02-26 18:53     ` Richard Garner [this message]
2010-02-27 23:20       ` Paul Levy
2010-02-28 21:30 ` Vaughan Pratt
2010-02-24 16:30 peasthope
2010-02-25 19:23 ` Toby Bartels

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=E1NlSzO-0004nQ-A6@mailserv.mta.ca \
    --to=rhgg2@hermes.cam.ac.uk \
    --cc=categories@mta.ca \
    --cc=shulman@uchicago.edu \
    /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).