[gtld-tech] Specification 5 - Country names... again..

[Luis Muñoz]

On Nov 25, 2013, at 11:18 AM, Alexander Mayrhofer wrote:

> 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_combined.pdf and http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEGN%20WG%20Country%20Names%20Document%202011.pdf) 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.


++

I went to the trouble of interacting with the primary sources and obtaining workable references because what is published is quite hard to coerce into the format we all need it. In the process I received rather amusing responses from various organizations that should know better. I'm attaching a list that should be easier to work with.

Rather than simply sending them to this mailing list, wouldn't it be better to setup a github repo or similar device so that updates can be made to the data, and we all have access to the latest version of the common work? In the meanwhile, comments and additions are welcome.

Best regards

-lem

-------------- next part --------------
A non-text attachment was scrubbed...
Name: restricted.list
Type: application/octet-stream
Size: 195125 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gtld-tech/attachments/20131125/bb06d943/restricted-0001.list>