ICANN ICANN Email List Archives

[ssac-gnso-irdwg]


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

[ssac-gnso-irdwg] ACTIONS/DISCUSSION POINTS: Meeting 07 December 2009

  • To: "ssac-gnso-irdwg@xxxxxxxxx" <ssac-gnso-irdwg@xxxxxxxxx>
  • Subject: [ssac-gnso-irdwg] ACTIONS/DISCUSSION POINTS: Meeting 07 December 2009
  • From: Julie Hedlund <julie.hedlund@xxxxxxxxx>
  • Date: Mon, 7 Dec 2009 13:23:35 -0800

Dear IRD-WG members,

Below are the action items and main discussion points from the 07 December 
meeting of the IRD-WG.  These also are on the wiki at: 
https://st.icann.org/int-reg-data-wg/index.cgi?internationalized_registration_data_working_group.
   Please let me know if you have any changes or questions.  Our next meeting 
is tentatively scheduled for Monday, 21 December at 1400 UTC, 06:00 PST, 09:00 
EST, 14:00 London, 15:00 CET. Also, we are pleased to announce that the WG has 
approved Jeremy Hitchcock as the co-chair from the SSAC.  He joins Edmon Chung 
as co-chair from the GSNO.

Best regards,

Julie

Julie Hedlund, Director, SSAC Support

1. Action Items: WG members should consider on the list possible requirements 
that could form part of a check list to decide what is, or is not, in the scope 
of the work of the WG.

2. Main Discussion Points: The Charter calls for co-chairs from the GNSO and 
SSAC.  The WG  approved Jeremy Hitchcock as co-chair from SSAC.  Edmon Chung 
suggested that to help further define the scope/mission/goals the WG could 
begin by looking at requirements for registration data.  Dave Piscitello noted 
that based on the survey he conducted  one possible requirement could be that 
in addition to collecting and displaying data in ASCII/roman script, if it was 
beneficial data also could be displayed in local script.  Bob Hutchinson asked 
whether there was any sense of the degree of difficulty for adding data display 
in local script.  He wondered whether it would be helpful to formulate a set of 
specific questions that could form a larger survey of ccTLDs.    Edmon noted 
that a survey could be a good idea, particularly in understanding how 
registries currently receive and display data, although he noted that the goals 
of the ccTLDs would likely be different from those of the gTLDs.  Dave 
suggested that one requirement could be to tag each piece of data and Mark 
Kosters asked whether such a requirement would be in the scope of the WG.  Dave 
noted that the requirement would not have to change what data is collected 
today.  He also noted that ICANN staff are studying Whois service requirements 
at the request of the GNSO Council  (the "May 7 request of the GNSO Council") 
and this study considers a data schema for registration data in the context of 
a broad set of service requirements including IRD.  Edmon suggested that it 
might be useful to prepare a checklist of possible requirements for receiving 
and displaying internationalized registration data and use the list to decide 
what is, or is not, in the scope of the WG.  Bob questioned whether there was a 
consensus on a recommendation for structure data and didn't know if displaying 
in a local language would require a significant amount of work.  Steve Sheng, 
Edmon, and Yao Jiankang all noted that there could be challenges for 
translation of an address into Chinese.  Edmon suggesting using the summary 
provided by Dave of the survey of 16 ccTLDs as a basis to produce an initial 
checklist of requirements to decide what is in scope.  Dave noted that the WG 
would not have to recommend a specific format, but could use the United Postal 
Union (UPU) standard as an analog for how data could be represented using Roman 
characters and additionally represented for a recipient or viewer of the data. 
In the UPU example, the recipient is both the addressee and the postal workers 
in the destination country; in the Whois case, the recipient/viewer could be an 
application (that already assumes USASCII7) or a viewer who may or may not 
understand roman characters but does understand characters of his local 
language.


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

Privacy Policy | Terms of Service | Cookies Policy