PDA

View Full Version : ICANN may let new TLD applicants modify their applications


555
19th June 2012, 11:52 PM
ICANN is considering allowing applicants for new top level domains to make changes to their applications, the organization confirmed to Domain Name Wire today.
The group is working on a process that could allow applicants to fix errors in their final applications. Officially:

ICANN has received requests for changes to submitted applications. We take these requests very seriously and are working on developing guidelines for these changes.
The ICANN community spent a lot of time coming up with applicant guidelines, but one it didn’t think to include was a mechanism for fixing errors in applications.

We might also see VeriSign ask to alter some of the IDNs it submitted. More on that later.

http://domainnamewire.com/2012/06/19/icann-may-let-new-tld-applicants-modify-their-applications/

Drewbert
19th June 2012, 11:56 PM
Woot!

alpha
20th June 2012, 06:17 AM
We might also see VeriSign ask to alter some of the IDNs it submitted. More on that later.

http://domainnamewire.com/2012/06/19/icann-may-let-new-tld-applicants-modify-their-applications/

before anyone gets their hopes up..

this is not domainnamewire reporting that they have heard verisign want to modify their applications

this is domainnamewire reporting that there are those of us who think verisign should modify their applications

gammascalper
20th June 2012, 07:09 AM
Well, if Kerry is allowed to correct their spelling mistake (don't know) then Verisign should be allowed to make edits too.

Drewbert
20th June 2012, 07:11 AM
Let's also remember that Verisign has ICANN over a barrel with the .com contract so I think they'll certainly get the ability to correct their Hebrew cock-up if they so desire.

alpha
20th June 2012, 07:16 AM
Well, if Kerry is allowed to correct their spelling mistake (don't know) then Verisign should be allowed to make edits too.

I've no doubt that the typos will be allowed to be fixed, so Hebrew should be fine, but I can't see that be extended to completely swapping out strings (which is what we'd want for the Chinese fails)

bumblebee man
20th June 2012, 10:09 AM
Didn't Moshe contact Verisign? Any response?

555
20th June 2012, 12:56 PM
I will update if i hear anything.

jose
20th June 2012, 01:04 PM
So there's hope after all!

alpha
20th June 2012, 01:11 PM
Funny, no one cared when I posted this yesterday, lol.

http://www.idnforums.com/forums/31732-icann-may-let-new-tld-applicants-modify-their-applications.html

Jose you posted it a couple of hours after this thread with the same topic was raised and had replies already, so it was put in the dumpster as a dup thread.

Jay
20th June 2012, 01:48 PM
I've no doubt that the typos will be allowed to be fixed, so Hebrew should be fine, but I can't see that be extended to completely swapping out strings (which is what we'd want for the Chinese fails)

Well hopefully they can slip the Urdu/Persian/Farsi variants into the Arabic application - that would be good.

jose
20th June 2012, 01:48 PM
Sorry, my bad then.

blastfromthepast
20th June 2012, 01:59 PM
Jose you posted it a couple of hours after this thread with the same topic was raised and had replies already, so it was put in the dumpster as a dup thread.

Back in the day, José used to complain when people posted threads that were of a similar topic to something he thought about.

chrisofmel
20th June 2012, 02:04 PM
I've no doubt that the typos will be allowed to be fixed, so Hebrew should be fine, but I can't see that be extended to completely swapping out strings (which is what we'd want for the Chinese fails)

i agree this will be a typo only modification

alpha
20th June 2012, 02:16 PM
Well hopefully they can slip the Urdu/Persian/Farsi variants into the Arabic application - that would be good.

I thought the latest thinking on this (courtesy of fka200 in that thread) was that urdu/farsi shouldn't be a variant as it is not visibly similar.

if thats true... and if you take Giants comments as gospel about the chinese com being the best translit, then actually verisign ony f*cked up the Hebrew, as apposed to a catalog of errors.

Jay
20th June 2012, 02:34 PM
I thought the latest thinking on this (courtesy of fka200 in that thread) was that urdu/farsi shouldn't be a variant as it is not visibly similar.

It depends on how visually dissimilar it has to be. You be the judge:

کام vs كوم

Now compare that to the Chinese variants that were applied for:

點看 vs 点看 vs 奌看

I'd say there is more chance of confusion with the Arabic variants than the Chinese ones.

DomainNameWire
20th June 2012, 02:36 PM
Hey guys,

Andrew with DNW here.

I'm not sure if VeriSign has contacted ICANN about changing its applications. All the group would confirm to me is that some people had contacted it about fixing applications.

My guess is applications could be changed in a very limited set of circumstances.

Also, I know some in this community have collated a list of VeriSign's interesting selections (Hebrew) and omissions. I plan to publish this on DNW, but somehow the UTF8 got messed up on my blog recently. It appears there's a plugin to covert the database, but I may not get around to doing this until early next week.

Thanks

IdnHost
20th June 2012, 02:46 PM
Hey guys,

Andrew with DNW here.

I'm not sure if VeriSign has contacted ICANN about changing its applications. All the group would confirm to me is that some people had contacted it about fixing applications.

My guess is applications could be changed in a very limited set of circumstances.

Also, I know some in this community have collated a list of VeriSign's interesting selections (Hebrew) and omissions. I plan to publish this on DNW, but somehow the UTF8 got messed up on my blog recently. It appears there's a plugin to covert the database, but I may not get around to doing this until early next week.

Thanks

Thanks for the update Andrew.

blastfromthepast
20th June 2012, 02:52 PM
I don't see where Giant said it was the best version in Chinese. He's simply trying to make the best rationalization of a bad situation.

squirrel
20th June 2012, 02:54 PM
Hey guys,

Andrew with DNW here.

I'm not sure if VeriSign has contacted ICANN about changing its applications. All the group would confirm to me is that some people had contacted it about fixing applications.

My guess is applications could be changed in a very limited set of circumstances.

Also, I know some in this community have collated a list of VeriSign's interesting selections (Hebrew) and omissions. I plan to publish this on DNW, but somehow the UTF8 got messed up on my blog recently. It appears there's a plugin to covert the database, but I may not get around to doing this until early next week.

Thanks

Alternatively you can probably just change the encoding (http://en.wikipedia.org/wiki/Character_encodings_in_HTML) of the article's page and use html entities (http://centricle.com/tools/html-entities/) for TLDs.

Ryu
20th June 2012, 02:57 PM
if thats true... and if you take Giants comments as gospel about the chinese com being the best translit, then actually verisign ony f*cked up the Hebrew, as apposed to a catalog of errors.

I have no reason to disagree .点看 is the best traslit for Chinese .com under the current circumstances (no 1 char tld allowed), but I still think it's a certain lose.

I studied Chinese for 2 years, and honestly, it looks horrible. The presence of 点 there kills everything imo. dotdotwhatever doesn't work. My guess is, not even 1% of current ChineseIDN.com end users would ever migrate to .点看.

yanni
20th June 2012, 03:04 PM
Also, I know some in this community have collated a list of VeriSign's interesting selections (Hebrew) and omissions. I plan to publish this on DNW, but somehow the UTF8 got messed up on my blog recently. It appears there's a plugin to covert the database, but I may not get around to doing this until early next week.

Thanks

http://wordpress.org/extend/plugins/utf-8-database-converter/

http://wordpress.org/extend/plugins/utf-8-db-converter/

blastfromthepast
20th June 2012, 03:23 PM
If you use HTML entities, there might be no need to change the encoding, it should all be converted in the end by the browser.

TrafficDomainer
20th June 2012, 04:01 PM
I don't see where Giant said it was the best version in Chinese. He's simply trying to make the best rationalization of a bad situation.

I thought the same and had asked Giant to clarify here:

http://www.idnforums.com/forums/31695-is-there-a-better-choice-for-com-and-net-in-chinese-6.html

Hopefully, we will hear from him soon.

Drewbert
21st June 2012, 07:46 AM
Alternatively you can probably just change the encoding (http://en.wikipedia.org/wiki/Character_encodings_in_HTML) of the article's page and use html entities (http://centricle.com/tools/html-entities/) for TLDs.

Gaaaaaaaaaa. Steer clear of HTML entities.

Set your blog and DB up so they're both running UTF-8 then you won't have anymore problems, now or in the future.

squirrel
21st June 2012, 02:51 PM
Yeah a DB convert would be a permanent fix

DomainNameWire
25th June 2012, 07:01 PM
Hey guys,

You might get a kick out of this comment submitted to one of VeriSign's IDN applications. I think the commentor misses the point :)

https://gtldcomment.icann.org/comments-feedback/applicationcomment/commentdetails/169

bwhhisc
25th June 2012, 07:15 PM
Hey guys,
You might get a kick out of this comment submitted to one of VeriSign's IDN applications. I think the commentor misses the point :)
https://gtldcomment.icann.org/comments-feedback/applicationcomment/commentdetails/169

Thanks...he obviously doesn't know they will both be "mirrored" together.

Rubber Duck
25th June 2012, 07:24 PM
Thanks...he obviously doesn't know they will both be "mirrored" together.

That is because Versign never said that in their application.

DomainNameWire
25th June 2012, 07:47 PM
And, to be fair, Verisign plans to charge to "mirror" the .IDN. So I guess if you don't pay for it, the person wouldn't be able to find your web site (although they wouldn't go to the wrong web site).

Rubber Duck
25th June 2012, 07:59 PM
And, to be fair, Verisign plans to charge to "mirror" the .IDN. So I guess if you don't pay for it, the person wouldn't be able to find your web site (although they wouldn't go to the wrong web site).

Yes, I think ICANn is making a big mistake allowing them to do this.

However, Verisign is making a much bigger mistake even wanting to!

They will see the light ,eventually.

DktoInc
26th June 2012, 02:43 AM
OFFTOP:

this one is my favorite comment so far by far

https://gtldcomment.icann.org/comments-feedback/applicationcomment/commentdetails/64


String: INDIANS
Application ID: 1-1308-78414
Panel/Objection Ground: Geographic Names Evaluation Panel
Subject: Indians - top level domain
Comment Submission Date:18 Jun 2012 at 09:08:45 UTC
Comment:
Indians are people who live in a country named india. Reliance industries a private firm has no right to claim ownership of this TLD.

Mulligans!!!

DomainNameWire
27th June 2012, 05:36 PM
Just published the story on Domain Name Wire. Thanks for the suggestions on fixing my database for UTF8.

http://domainnamewire.com/2012/06/27/idn-community-reacts-to-verisigns-com-transliteration-selections/

IdnHost
27th June 2012, 05:43 PM
Just published the story on Domain Name Wire. Thanks for the suggestions on fixing my database for UTF8.

http://domainnamewire.com/2012/06/27/idn-community-reacts-to-verisigns-com-transliteration-selections/

Perfect, straight to the point. Maybe now people will start waking up from deep sleep. Great article!

Drewbert
28th June 2012, 12:32 AM
[QUOTE=DomainNameWire;200171]Thanks for the suggestions on fixing my database for UTF8.

Congrats Andrew!

Now if I post ၑၑ.com there in the comments, it will show up correctly :)

Rubber Duck
28th June 2012, 06:23 AM
Perfect, straight to the point. Maybe now people will start waking up from deep sleep. Great article!

Not so easy when you are on an intravenous morphine drip.

IdnHost
28th June 2012, 07:02 AM
Not so easy when you are on an intravenous morphine drip.

lol. the idn space doesnt consist of only namepros members and Rick Schwartz fan boy cheerleaders R.D. There are people, im sure, out there that are ready to learn about IDNS and jump on the opportunity, although arriving late to the party. Im sure these people will be waking up by the thousands very shortly.. But yes, most will still be counting sheep when idn.idn is in the root no doubt.

alpha
28th June 2012, 07:09 AM
Im sure these people will be waking up by the thousands very shortly.

news snippets, PR releases and blog posts like this have been going out for years, if you set your expectations dial to low, you won't be disappointed.

IdnHost
28th June 2012, 07:34 AM
news snippets, PR releases and blog posts like this have been going out for years, if you set your expectations dial to low, you won't be disappointed.

Agreed, but what is there really to be disapointed about in the first place? Those that didnt get the memo will soon enough and those that are to blind to see the opportunity pass them by will most likely be kicking themselves later. If anything those people are actually the ones that should be setting their dial tones to low cause they won't be getting any phone calls with offers for IDNS.

Rubber Duck
28th June 2012, 07:45 AM
I think you are harking back to the Good Old Days when the main American import from Columbia was Coffee.

IdnHost
28th June 2012, 07:51 AM
I think you are harking back to the Good Old Days when the main American import from Columbia was Coffee.

yeah, maybe.