From: Todd Trimble <trimble1@optonline.net>
To: "Joyal, André" <joyal.andre@uqam.ca>
Cc: Categories list <categories@mta.ca>
Subject: Re: potential names
Date: Fri, 01 Oct 2010 10:40:24 -0400 [thread overview]
Message-ID: <E1P21u3-0006zp-2j@mlist.mta.ca> (raw)
In-Reply-To: <E1P0kdv-00045H-OQ@mlist.mta.ca>
Of the choices offered here, I like "precarious", "unstable", or
"fragile". I just thought of "risky" myself. Good, experienced
mathematicians will know when it's okay to take "risks" (and
will be aware of what the risks are).
"Unstable" seems like a very sober choice, not too likely to
ruffle feathers.
I encourage anyone who cares about this issue to take a look
at the current discussion at the nForum:
http://www.math.ntnu.no/~stacey/Mathforge/nForum/comments.php?DiscussionID=1886
You will see that opinions are divided even among workers in
the nLab.
Todd
----- Original Message -----
From: "Joyal, André" <joyal.andre@uqam.ca>
To: "Juergen Koslowski" <koslowj@iti.cs.tu-bs.de>
Sent: Tuesday, September 28, 2010 9:57 AM
Subject: categories: potential names
Dear Juergen,
You wrote:
>Let me start by proposing "equi-unstable" and "precarious" as possible
>replacements for "evil".
I agree that we should explore various options.
Strickly speaking, there is no need for a new terminology
since "non-invariant" has been used in the past
and it is working pretty well.
Let me draw a list of potential names.
I have added a few:
non-invariant
equi-unstable
precarious
unstable
fragile
private
I invite everyone to contribute to the list.
Best,
AJ
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2010-10-01 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 9:15 EVIL terminology Juergen Koslowski
[not found] ` <E1P0kdv-00045H-OQ@mlist.mta.ca>
2010-09-29 4:45 ` potential names Martin Escardo
2010-10-01 14:40 ` Todd Trimble [this message]
2010-10-02 17:43 ` Paul Taylor
2010-10-04 7:20 ` Vaughan Pratt
2010-10-03 14:27 ` Todd Trimble
2010-10-05 22:18 Fred E.J. Linton
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=E1P21u3-0006zp-2j@mlist.mta.ca \
--to=trimble1@optonline.net \
--cc=categories@mta.ca \
--cc=joyal.andre@uqam.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).