categories - Category Theory list
 help / color / mirror / Atom feed
From: Clemson Steve <steve@clemson.edu>
To: Charles Wells <charles@abstractmath.org>
Cc: peasthope@shaw.ca, catbb <categories@mta.ca>
Subject: Re: Explanations
Date: Mon, 02 May 2011 13:01:10 -0400	[thread overview]
Message-ID: <E1QH3r2-0006Ol-7R@mlist.mta.ca> (raw)
In-Reply-To: <E1QGrp9-00044X-Qt@mlist.mta.ca>

I think this is a perfect example of when something is or is not an
explanation. It's both in this case: to the cogniscenti, it is perfectly
clear; the novice is going to head off on the wrong track.

On 4/30/11 15:58, Charles Wells wrote:
> In the expression "any x:T->X" the T depends on x.  If you use the
> arrow notation you seem bound to name the domain of the morphism.  You
> could say "for any x with codomain X there is an e:dom x ->  X ..." but
> in the rest of the sentence you will have to mention the domain again.
>
> My impression is that notation "any x:T->X" where T depends on x
> without that fact being mentioned is common in category theory
> writing.  There is nothing wrong with this if a reader understands the
> intent.
<snip>

-- 
Dr. D. E. Stevenson
Associate Professor
Director, Insitute for Modeling and Simulation Applications
School of Computing, Clemson University


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


  reply	other threads:[~2011-05-02 17:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTi=XhOM=FKajXUA6pyOq575fm_N=PQ@mail.gmail.com>
2011-04-29 19:56 ` Explanations peasthope
2011-04-30 19:58   ` Explanations Charles Wells
2011-05-02 17:01     ` Clemson Steve [this message]
2011-05-01 12:50   ` Explanations F. William Lawvere
     [not found] <654PeBPnq2496S01.1304350816@web01.cms.usa.net>
2011-05-02 18:22 ` Explanations peasthope
2011-05-01 21:27 Explanations peasthope
     [not found] <609PDdViw1024S04.1304197762@web04.cms.usa.net>
2011-05-01 21:00 ` Explanations peasthope
  -- strict thread matches above, loose matches on Subject: below --
2011-04-30 21:09 Explanations Fred E.J. Linton
2011-04-28 13:12 Explanations Ellis D. Cooper
2011-04-27  8:16 Explanations Mattias Wikström
2011-04-22 13:55 Explanations Graham White
2011-04-23 20:27 ` Explanations David Yetter
2011-04-23 21:29 ` Explanations Ronnie Brown
2011-04-25 13:51   ` Explanations Joyal, André
2011-04-26  0:52     ` Explanations jim stasheff
2011-04-26 13:45     ` Explanations William Messing
     [not found]     ` <4DB6CC7D.40407@math.umn.edu>
2011-04-26 22:05       ` Explanations Ronnie Brown
2011-04-23 21:52 ` Explanations Dusko Pavlovic
2011-04-25 13:17   ` Explanations ClemsonSteve
2011-04-26  5:55     ` Explanations Timothy Porter
2011-04-27  7:53       ` Explanations Uli Fahrenberg
     [not found] ` <17617_1303861705_4DB759C9_17617_39_1_E1QEryD-0006dq-7k@mlist.mta.ca>
2011-04-27 13:20   ` Explanations Marta Bunge
2011-04-20 17:22 Explanations Fred E.J. Linton
2011-04-21 19:09 ` Explanations peasthope
2011-04-19 23:37 Explanations Jean-Pierre Marquis

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=E1QH3r2-0006Ol-7R@mlist.mta.ca \
    --to=steve@clemson.edu \
    --cc=categories@mta.ca \
    --cc=charles@abstractmath.org \
    --cc=peasthope@shaw.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).