Sure.
My only concerns are to keep the definitions short and to avoid
overly abstract definitions like: An item is a discrete unit of
information...
Good catch on affordance, I've changed it to mechanism. But feel free
to improve on that.
Thanks,
Mimi
On Aug 25, 2007, at 3:16 PM, Philippe Bossut wrote:
Hi,
Mimi Yin wrote:
It includes a brief glossary at the top and more descriptive
titles for the movies as promised.
Are there terms missing from the glossary? (This abbreviated
glossary should probably link to Pieter's more complete glossary
in the Get Started Guide.)
The idea of a glossary is to translate jargon in plain English.
Jargon is good as it allows to manipulate one complex new concept
using one single convenient word. However, explaining jargon with
more jargon is a put off for readers. In a glossary, we should:
- use only Webster certified words. Avoid things like "affordance"
which is UI expert jargon, not an English word that a lay person
would understand.
- when defining something the first sentence must be a direct
statement with the thing to define as the subject, e.g.: "A <XYZ>
is a <plain English>". Explaining "item" for instance by saying
that Chandler offers 4 different kind of them doesn't really help
the reader.
I can make a short rewrite if its ok with you.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
