From: Robert Dawson <dawson@cs.smu.ca>
To: "categories@mta.ca" <categories@mta.ca>
Subject: Re: Comments on a wikipedia article on a Timeline of Category theory
Date: Fri, 08 Jul 2011 09:57:30 -0300 [thread overview]
Message-ID: <E1QfLGp-0006mq-Me@mlist.mta.ca> (raw)
In-Reply-To: <E1Qf9mJ-0003rJ-4x@mlist.mta.ca>
This is the sort of article that Wikipedia necessarily does badly at -
as anybody who thinks about it for a few minutes must realize would be
the case.
An ad hoc committee not in regular communication can often do a very
good job of putting together a collection of facts. Connections between
facts are harder because they are often not explicitly in the literature
- and Wikipedia [correctly - there are other fora for that] discourages
"original research" and "opinion". Similarly, balanced emphasis in long
articles is difficult because (as intended) no one person writes all of
it, and if the person writing about non-normal whiffle theorists has
more spare time and enthusiasm than the person writing on quasinormal
whiffle theorists, the non-normal group end up with disproportionate
coverage. (For obvious reasons, the less-prolific writer would not be
popular if [s]he ripped out an inexpert selection of several hours of
the other writer's work to correct this!) And omissions are
problematic. In a good single-author article, we could conclude that if
there was nothing about X's contributions to the field, they were
probably quite minor. A Wikipedia article does not permit this deduction.
Can't we just accept that Wikipedia has its weaknesses as well as its
strengths? For instance, in a paper encyclopedia you would be lucky to
find an article on category theory at all; Wikipedia does not have to
keep within (say) 15,000 pages for all topics.
This article is probably fairly reliable on who _was_ working on what
when; it should not be trusted for who was _not_ working on something,
or whose work was most important, and may be dubious on priority. To
damn it for this is like damning a thesaurus for not being an
etymological dictionary - a sign that somebody is contemplating using a
specialized tool for the wrong purpose.
Robert Dawson
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2011-07-08 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 13:14 Ronnie Brown
2011-07-08 1:35 ` Joyal, André
2011-07-08 7:33 ` Andree Ehresmann
2011-07-08 11:53 ` Sergei SOLOVIEV
2011-07-08 12:57 ` Robert Dawson [this message]
2011-07-08 13:43 ` Valeria de Paiva
2011-07-09 2:52 ` Peter Selinger
2011-07-09 14:37 ` Toby Bartels
2011-07-09 19:48 ` Eduardo J. Dubuc
2011-07-08 0:07 Fred E.J. Linton
2011-07-08 22:46 ` Messing
2011-07-10 17:03 Timelines for category theory: a response to comments Ronnie Brown
2011-07-11 15:58 ` jim stasheff
2011-07-11 18:11 ` Robert Dawson
2011-07-11 18:14 ` Sergei SOLOVIEV
2011-07-11 21:18 ` David Roberts
2011-07-12 16:13 ` Graham White
2011-07-13 0:33 ` Comments on a wikipedia article on a Timeline of Category theory peasthope
2011-07-13 7:43 ` Re: Timelines for category theory: a response to comments Patrik Eklund
2011-07-12 14:10 ` Jeremy Gibbons
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=E1QfLGp-0006mq-Me@mlist.mta.ca \
--to=dawson@cs.smu.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).