From: peasthope@shaw.ca
To: categories@mta.ca
Cc: peasthope@shaw.ca
Subject: Re: Explanations
Date: Fri, 29 Apr 2011 11:56:48 -0800 [thread overview]
Message-ID: <E1QGFn2-0006ah-FD@mlist.mta.ca> (raw)
In-Reply-To: <BANLkTi=XhOM=FKajXUA6pyOq575fm_N=PQ@mail.gmail.com>
Charles & everyone,
Earlier peasthope wrote,
"...changing a few words of a sentence can make a concept obvious rather
than nebulous". Revise that to "obvious rather than difficult".
From: Charles Wells <charles@abstractmath.org>
Date: Fri, 22 Apr 2011 09:37:44 -0500
> Can you give specific examples? I suspect that in most cases the change
> introduces a useful metaphor that was hidden before.
Here is a small example from the _Conceptual Mathematics_ of
Lawvere and Schanuel. No offense to the authors or the book.
It's an indispensible and invaluable resource.
L&S page 292, "Definition ... equalizer ... and for each x:T-->X ... there is
exactly one e:T-->E ... ." "For all T" is implicit.
http://en.wikipedia.org/wiki/Equalizer_(Mathematics) , "In category theory
... defined by a universal property, ... object E and morphism eq ... such that,
given any other object O and morphism m ... ."
For me, the reference to "any other object O" helps. The definition in the
Wikipedia seems to reveal the "universality" of the equalizer better. The
diagram also helps.
A trivial issue for most readers but a small detail can make a difference for
a student.
Regards, ... Peter E.
--
Telephone 1 360 450 2132. bcc: peasthope at shaw.ca
Shop pages http://carnot.yi.org/ accessible as long as the old drives survive.
Personal pages http://members.shaw.ca/peasthope/ .
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next parent reply other threads:[~2011-04-29 19:56 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 ` peasthope [this message]
2011-04-30 19:58 ` Explanations Charles Wells
2011-05-02 17:01 ` Explanations Clemson Steve
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=E1QGFn2-0006ah-FD@mlist.mta.ca \
--to=peasthope@shaw.ca \
--cc=categories@mta.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).