December 2013 - gtld-tech - lists.icann.org

Call for Presentations for TechDay at ICANN Buenos Aires
by Dr Eberhard Lisse Jan. 28, 2014

Jan. 28, 2014

As usual we shall be organizing TechDay on Monday of the coming ICANN meeting in Buenos Aires. Please submit ideas for presentations to the list addresses where this message appears or to any of the following email addresses: el(a)lisse.na ondrej.filip(a)nic.cz This time we would like to have an Latin American focus, if possible, hence Latin American presenters are strongly encouraged to come forward. As we have no budget presenters are responsible for their own transport and room and board. As the name suggests, talks must be of a technical (or operational, perhaps even administrative) nature, and should revolve around TLDs, but otherwise we are quite open. Please forward this to gNSO and other lists as well :-)-O el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Bachbrecht, Namibia ;____/

3 6

Specification 5 - Country names... again..
by Alexander Mayrhofer Jan. 13, 2014

Jan. 13, 2014

I've started looking at the two PDFs of country names that ICANN mandates us to reserve in Section 4.2 and 4.3 of Specification 5 of the Registry Agreement. I have a couple of comments on this: a) I can only guess whether or not the PDFs that i use (http://unstats.un.org/unsd/geoinfo/ungegn/docs/ungegn-tech-ref-manual_M87_c… and http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEG…) are the correct ones, since ICANN failed to include a reference to the documents in the Agreement. b) Extracting names from those documents (particularly in scripts that i'm not familiar with) is absolutely horrible, and will likely lead to interopability problems between registries. c) The mapping of the strings required to be reserved to the actual A-Label is undefined. Therefore, could ICANN please look into creating an reservation list covering these two requirements, and publish that list as a recommended way to implement the two requirements? ICANN could use a tiny tiny fraction of the application fees to contract someone to create an authoritative list of names to be reserved - Or, maybe as a secondary option in case there should be insufficient budget, allocate resources from their "Languages Services Department" http://blog.icann.org/2013/10/introducing-the-language-services-team/ to create this list? I'm sure that many members of the community would welcome this as a useful contribution to ensure a unified approach to those requirements. thanks, Alex Mayrhofer Head of R&D nic.at

8 19

Re: [gtld-tech] Specification 5 - Country names... again..
by Alexander Mayrhofer Dec. 5, 2013

Dec. 5, 2013

John, James, I have a few more comments on the lists that we have been collecting on the Github site. Specifically: > 2. I've attached Verisign's spreadsheet for section 5.4.3 (UN Member States > and translations). There are 7 languages (including both traditional and > simplified Chinese). Spaces and hyphens are tricky. The issue is that > translation engines (here I mostly use Google's service) will often handle > spaces intelligently. For instance, "Central African Republic" translated to > Russian becomes "Центрально-Африканская Республика". That is, a > hyphen is introduced for the first space. I presume this is a standard for the > "Central" modifier. You could choose to create a variant without any > hyphens or spaces, or you could try all the permutations of hyphens and > spaces. Instead of heading down that rabbit hole, we elected to yield to the > translation wherever possible. But we'll respect the group decision and > update our implementation accordingly. On Specification 5.4.3: --------------------------- The agreement says "the list of United Nations member states in 6 official United Nations languages prepared by the Working Group on Country Names of the United Nations Conference on the Standardization of Geographical Names;" I do understand that there is an offical document from the UN that provides translations for those country names. The URL (at least the one i've been using) is: http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEG… I do understand that the above document already contains readily translated / agreed country names for the six UN languages, as required in 5.4.2. However, i do also understand that the list that's now in the Github repository was actually produced using automated translation, which potentially could yield different results compared to extracting the list of country names from the document (or the respective source file)? Therefore, could you please clarify whether the file that's now on the Github was produced by translation engines, or taken from said document? I think that's a significant impact on whether or not that file is usable to cover ICANN's requirement. On Specification 5.4.2: --------------------------- The agreement requires "the United Nations Group of Experts on Geographical Names, Technical Reference Manual for the Standardization of Geographical Names, Part III Names of Countries of the World". Looking at the respective document (http://unstats.un.org/unsd/geoinfo/ungegn/docs/pubs/UNGEGN%20tech%20ref%20m…) the actual list (starting on page 185) contains several columns: - ISO3166 code - COUNTRY- English (UN) - ISO Code; language - Short Name - Formal Name It is unclear to me which of the various columns is to be considered for the reserved names list. Candidates would be the "Country-ENGLISH" (although that is likely already covered by the UN list described in 5.4.3?), the "Short Name", and the "Formal Name". However, looking at the file that is now uploaded on the github for the respective Specification (https://github.com/centralnic/spec5-reserved-names/blob/master/S5.4.2.txt) it doesn't seem to correspond to *any* of these columns. for example, the Entry for "AF" (assumed) in the file lists "afganistán" does not exist in the PDF - in neither of the respective columns. I'm slightly worried that therefore the list that is currently uploaded does not fulfill the respective requirement (besides that i think the original requirement is highly inprecise and hence disputable).. Do i look at the wrong files? Do people interpret the requirements in a different form? Any comments appreciated... thanks, Alex

4 6

Version 1.0 of the URS technical requirements published
by Gustavo Lozano Dec. 4, 2013

Dec. 4, 2013

Colleagues, Version 1.0 of the URS technical requirements document has been published at: http://newgtlds.icann.org/en/applicants/urs The direct download link of the document is: http://newgtlds.icann.org/en/applicants/urs/tech-requirements-17oct13-en.pdf Regards, Gustavo

3 3