RE: [gnso-whoissurvey-dt] RE: Survey review - through R7

[Don Blumenthal <dblumenthal@xxxxxxx>]

Firefox on a Mac

Sent from my PDA phone

-----Original Message-----
From: Berry Cobb [mail@xxxxxxxxxxxxx]
Received: Tuesday, 11 Sep 2012, 2:45pm
To: gnso-whoissurvey-dt@xxxxxxxxx [gnso-whoissurvey-dt@xxxxxxxxx]
Subject: [gnso-whoissurvey-dt] RE: Survey review - through R7


Don,

What browser are you using to access the survey?  You mentioned several
times about the formatting of the explanantions.  However, they look fine to
me in Chrome and IE.  Can you be more descriptive?

All other suggested edits below have been incorporated.

Thank you.  B

Berry Cobb
Internet Corporation for Assigned Names & Numbers (ICANN)
720.839.5735
mail@xxxxxxxxxxxxx
@berrycobb



-----Original Message-----
From: Don Blumenthal [mailto:dblumenthal@xxxxxxx]
Sent: Tuesday, September 11, 2012 06:32
To: Berry Cobb; 'Whois Survey WG'
Subject: Survey review - through R7

I have to start preparing for a 10:00 meeting. I'll send what I have now and
pick it up again later this morning.

As has been said before, excellent job. These are just inevitable last
minute tweaks.

Question index
Excellent idea but can we change the numbering to match R numbers? The first
item could go without one.

Profile
Organization Size - Spacing issue in the explanation line Residence  - Style
issue. How about "where do you reside?"
Whois access - Can we align the final line of the explanation with the
others? Also, and almost bizarre in a way, "pre-Windows" may not mean
anything to a lot of responders.

R2
Most important elements -  Of those "items"?

R3
Formal extension framework - Align all of explanation if possible. This
issue recurs so I'll stop flagging it

R5
Do  you support - extraneous period in the first word of the explanation

R6b
History - capitalize "pedigree" in the explanation Restricted to single
owner - lower case "historical"

R7
Display  - change "resultL" to "results"
Variants in responses - lower case "means" in explanation ASCII - I think it
should be US7ASCII




From: Berry Cobb <mail@xxxxxxxxxxxxx<mailto:mail@xxxxxxxxxxxxx>>
Date: Tuesday, September 11, 2012 1:24 AM
To: Whois Survey WG
<gnso-whoissurvey-dt@xxxxxxxxx<mailto:gnso-whoissurvey-dt@xxxxxxxxx>>
Subject: RE: [gnso-whoissurvey-dt] Survey Migrated

Team,

I made the changes per Susan's suggestions below.
https://limesurvey.icann.org//index.php?sid=71483&lang=en<https://limesurvey
.icann.org/index.php?sid=71483&lang=en>

I will start the communications plan tomorrow.  I will send a sample of the
communications so that the team may communicate within their organizations
as well.

Please take one last look at the survey.  Tomorrow night, I will reset the
survey.  The community should start to see the availability of the survey
Wednesday morning.

If you have any other suggested changes, please send them to the list.

Thank you.  B

Berry Cobb
Internet Corporation for Assigned Names & Numbers (ICANN)
720.839.5735
mail@xxxxxxxxxxxxx<mailto:mail@xxxxxxxxxxxxx>
@berrycobb


From:
owner-gnso-whoissurvey-dt@xxxxxxxxx<mailto:owner-gnso-whoissurvey-dt@icann.o
rg> [mailto:owner-gnso-whoissurvey-dt@xxxxxxxxx] On Behalf Of Prosser, Susan
Sent: Monday, September 10, 2012 09:59
To: Berry Cobb
Cc: Whois Survey WG
Subject: Re: [gnso-whoissurvey-dt] Survey Migrated

Great job!  I like it.  Very clean.  I like the progress bar on the top.  I
also like the Question Index on the side. Is it possible to have the
complete listing always visible?  People would then know where they were in
the process and what they have completed.

TBH, I have not made it through the whole survey yet and not sure I will
have time prior to our call in a few hours.  I did find a couple of things
to be addressed.  There were Question #'s to reference, so I shorthanded
some of them.  I hope you can follow my reference.

In general there are inconsistencies in capitalization of Registries and
Registrars.  There is also inconsistency with Whois vs WHOIS.  I know there
is debate / belief on which is appropriate in specific situations.  But, it
is inconsistent in use throughout the questionnaire.

Background section:
Q. How do you access the Whois information?
-- there is a qualifier description for Website interfaces that moved down
to the following question.
-- if any Microsoft lawyer were to read this they may take offense to the
non-cap'd Windows reference (windows DOS).

R1. Provision of a publicly accessible....
Q. The WHOIS Requirement Inventory identifies the ..... ... Registry, RIR
and Registrar WHOIS Servers.
-- should RIR term be qualified (Regional Internet Registry, "RIR") be
identified or believe recipients will know who/what RIR is?
Q. The inventory of requirements suggests.....
-- the descriptor has a trailing double quote (") after Discovery"

R2. Definition standard query...
Q. Assuming you can identify IDN....
-- The qualifier statement has a typo:  Internetdomain needs a space between
the words

R3.  Definition standard data...
Q. Typo: Do you support a formal extension framework/mechanismin -->need a
space between the words Q.  Should the data structure allow...
-- The qualifier statement has a typo: .... characters (ie cyrillic )other
--> closing parenthesis needs to be next to cyrillic with space prior to
'other'  (should cyrillic be cap'd?)

R4 Standardized error handling
The leading paragraph includes the qualifier answers used in the questions.
I do not believe that is necessary.
Q. Do you support the use of standard error messages....
-- missing the qualifier descriptor (in leading paragraph)

R5 Submitting WHOIS queries
Leading paragraph has a typo:  ....to submit otherrelated registration data
Q. This question seems to be missing words.  "Is there a ?? to search
WHOIS..."   "Please choose one of the following" is repeated, can remove one
of them.
Q. Typo:  Please rate 1-6 below on importance -- needs to be 1-7 according
to options.

R6a  Adoption of structured data model
Leading paragraph... not sure I understand that last sentence "Properties
the ability of the Whois .... data structures."
Q. In order to improve WHOIS capabilities...
--- qualifier needs a ending period.
Q. Work on such a model should include IETF radio button typo:  Question
does not matteR (R required)
-- qualifier IETF.org should be a hyperlink (IMO)

R7. IDN Requirements
Q. Should WHOIS clients (both port 43...)
-- qualifier has typo:  Ascii is all cap'd elsewhere ASCII Q.  Should WHOIS
responses include....
-- qualifier http://idn.icann.org/IDN_basics should by hyperlink (IMO) Q.
Should WHOIS service return....  IDN domains queried? (missing ending
question mark)
-- qualifier has IDN hyperlink only ??
Q. Should WHOIS services return both .. nameservers names..
-- qualifier http://en.wikipedia.org/wiki/Domain_Name_System hyperlink
missing

Please let me know if there are any questions about these reference.
-Susan



On Thu, Sep 6, 2012 at 8:45 PM, Berry Cobb
<mail@xxxxxxxxxxxxx<mailto:mail@xxxxxxxxxxxxx>> wrote:
WSWG Team,

Thank you to Wilson for migrating the WHOIS Tech Survey over to the ICANN
hosted solution.  The survey can be accessed here:
https://limesurvey.icann.org//index.php?sid=71483&lang=en<https://limesurvey
.icann.org/index.php?sid=71483&lang=en>

We will review the survey at our meeting next Monday.  In the meantime,
please feel free to review and test what we have completed so far.  If you
see any issues, please post your comments to the list.

I've confirmed that all approved changes as a result of the public comment
review were loaded into this final version.  I made other typo corrections
and small consistency or cosmetic changes.  A few of these I will confirm
with the WG next week, as well as the skillset language we have talked
about.

There is one technical issue that I discovered on the ICANN hosted instance.
The Resume Later function did not appear to work and produced a PHP error.
I will work with Wilson and our IT group to get it resolved.  The other
issue is the center justification for the descriptions of each section.  It
looks to be a template issue.


Thank you.  B

Berry Cobb
Internet Corporation for Assigned Names & Numbers (ICANN)
720.839.5735<tel:720.839.5735> mail@xxxxxxxxxxxxx<mailto:mail@xxxxxxxxxxxxx>
@berrycobb