<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [gnso-osc-ccc] CCT Report II
- To: Scott Pinzon <scott.pinzon@xxxxxxxxx>, Mason Cole <masonc@xxxxxxxxxxxxx>, "gnso-osc-ccc@xxxxxxxxx" <gnso-osc-ccc@xxxxxxxxx>
- Subject: Re: [gnso-osc-ccc] CCT Report II
- From: Scott Pinzon <scott.pinzon@xxxxxxxxx>
- Date: Thu, 25 Feb 2010 13:30:29 -0800
Ken, after today’s call, I suggest this language to append at the end of 4.5:
For GNSO participants who author documents, we recommend using the “Readability
Statistics” feature found in Microsoft Word. [Ken, it’s up to you whether this
next bit is a footnote, or parenthetic: (Readability Statistics is an option
attached to Word’s Spelling and Grammar Checker. To enable it in Microsoft
Word, from the Word menu, select Preferences, then Spelling and Grammar. Enable
the checkbox for “Show readability statistics.” Click OK. The statistic will
then display after each time you run the Spelling and Grammar checker on a
document.) Where possible, we recommend that documents rating a Flesch-Kincaid
Grade Level higher than 12 should be edited to reduce complexity. For documents
that are targeted for non-native English speakers, we recommend striving toward
the goal of an average sentence length of 15 words and a Flesch-Kincaid Grade
Level rating of 4. This will not always be achievable, and it is not our intent
to mandate a given readability level. However, in the view of the
Communications Team this approach represents a quantifiable way for each author
to gauge his or her personal progress toward writing more understandable
English. We encourage GNSO authors to develop the habit of monitoring their own
Readability Statistics and trying to lower them.
Ken, the instructions I’ve written above work on a Mac, but I don’t have a
Windows machine to try them on. Can you verify whether they are accurate for
Windows?
Thanks,
Scott
On 2/25/10 8:33 AM, "Scott Pinzon" <scott.pinzon@xxxxxxxxx> wrote:
Upon re-reading the document, I see multiple recommendations for the GNSO to
use “clear English” and plain English. I agree with that (certainly!) but I
wonder if we could also introduce an objective standard. The document
essentially encourages the GNSO to do better, which is quite vague. An
objective standard of some sort would provide a means to measure what the
definition of “better” is.
I think Word is nearly ubiquitous in the GNSO, and the Word Spelling/Grammar
checker has an option you can enable that checks the document and returns
readability statistics. (Found here: Tools ==> Spelling and Grammar ==> Options
==> Show readability statistics)
Would the group be in favor of language that recommended each document should
be checked for readability by its author, and should be edited to return a
Flesch-Kincaid readability level at a certain grade or lower? (This CCT
document comes in at a 12th grade reading level. In case “grade” does not have
the same meaning internationally, it is saying the reader needs the
understanding of an 18-year-old native English speaker to understand the
document.)
Just a suggestion, which perhaps you will discuss on the call today.
Best Regards,
Scott Pinzon
Director, Policy Communications
ICANN
On 2/20/10 5:22 PM, "Mason Cole" <masonc@xxxxxxxxxxxxx> wrote:
CCT Members:
As promised in my earlier communication, this email transmits the latest
version of Report II-Communications & Coordination. As you will see, there are
many remaining edits and comments that we need to discuss.
I have asked our GNSO Secretariat to find a date/time next week that will work
on the GNSO calendar and, hopefully, with your schedules. A Doodle poll
announcement will be mailed to the CCT list, so please be on the lookout for it
and respond as soon as you are able.
Once we have completed our work on Report II, this team’s activities should be
completed. I ask for your commitment and participation a few more weeks as we
put the finishing touches on this final portion of our recommendations.
I am hoping that Liz Gasster from the Policy Staff will be able to attend our
next session since she made some excellent contributions to this latest version.
If you have any questions, please let me know; otherwise, I look forward to
working with you again next week.
Regards,
Mason Cole
-- sp
. . . . . . . . . . . .
Scott Pinzon, CISSP
Director, Policy Communications
ICANN
+1 (310) 279 2655
-- sp
. . . . . . . . . . . .
Scott Pinzon, CISSP
Director, Policy Communications
ICANN
+1 (310) 279 2655
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|