ICANN ICANN Email List Archives

[gnso-whoissurvey-dt]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-whoissurvey-dt] Last few questions

  • To: Berry Cobb <mail@xxxxxxxxxxxxx>
  • Subject: Re: [gnso-whoissurvey-dt] Last few questions
  • From: "Prosser, Susan" <susan@xxxxxxxxxxxxxxx>
  • Date: Tue, 11 Sep 2012 09:42:30 -0700

I just completed the survey as well.  Below are my notes, some of which Don
already referenced in his review.  Please let me know if any of my notes
beg explanation.
thanks
-Susan


R8.1 Defining authentication framework
-- typo:  Leading paragraph 'Elevated'
Q. If access rights to WHOIS were....
-- needs ending period
Q. Describe your preferred....
-- needs ending period
-- typo: authenticated/verifiedwhile - needs space
-- typo: yourelevated - needs space

R8.2 Implementing authorization framework
-- typo:  ...contact elements ( such as law... - remove space
Should RDDS be defined?  It is referenced earlier in survey (R3).  I
overlooked it there.  Could be helpful.

R8.3 Defining a framework
Q. What elements of WHOIS acces....
-- typo: RequestEr IP address in question vs RequestOr in qualifier, select
one variant to use
Q. Does the collection or use....
-- form error:  Upon selecting "yes" comment box is not required although
implied in question

R10 New TLDs operating a thick WHOIS
Should this be referenced as R9 not R10 ?

R10 Definition of a standard WHOWAS
typo: ...period of time.A WHOWASservice - need space after period and after
WHOWAS

R11 Registrar & Registries (abuse contact)
Q. Several different methods...
Form logic error: question implies to indicate preference.  Users can
select all options in same level of preference.



On Tue, Sep 11, 2012 at 9:08 AM, Don Blumenthal <dblumenthal@xxxxxxx> wrote:

>
> Based on an experience that I just had when returning to the
> questionnaire, we should have language asking people to click Resume Later
> if they take a break. I timed out. Also stress to use the Previous button
> instead of the back page.
>
> Another general note. i.e. And e.g. should be italicized throughout.
>
> I went back to look at Requirement descriptions and recheck one question
> Descriptions
> R3 – space between query and (question) at the end of the italicized
> section.
>
> R6a – To evolve from rather than to be evolved from
>
> R7 – US7ASCII issue that I raised before
>
> Recheck
> R5 – is it necessary to force an answer to the data element ranking?
>
> Onward
> R8.1
> Description - Elavated should be elevated in italicized section
> Is there a problem with saying that the rate limiting is necessary in the
> description but then asking a question about it at the end of the section?
> Capitalize first words in explanations
> Preferred approach – space between verified and while
> Also, "by which WHOIS users identify"
>
> R8.2
> Extraneous space at the start of the second parenthetical in the
> description?
>
> R8.3
> Auditable metrics – is there an extraneous space between ( and For?
>
> I don't see an R9
>
> R10 – thick WHOIS
> Start of description. All new TLDs should… Doesn't that beg a question in
> the section?
>
> R10 - WHOWAS
> Explanation - Can we split the first sentence? It got hard to follow. At
> the least, put a comma between name and which.
> Also, insert a space after time. and before A and between WHOWAS and
> service.
>
> R11
> Explanation - "alternately" should start a new sentence.
> How would POC be valuable – is there an extraneous empty line at the top
> of the question?
>
>
>
>
>


<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy