[Ctn-crosscom] Soft confusing similarity

Mon Mar 30 09:13:36 UTC 2015

I completely agree. Still, as I remember it, ICANN Board decided that there was no contention. We´ll see how it ends. Take a look here and search for hotel.

https://gtldresult.icann.org/application-result/applicationstatus/viewstatus

Annebeth B. Lange
Fagansvarlig jus og myndighetskontakt
UNINETT Norid AS
C. J. Hambros plass 2 C
NO-0164 OSLO
annebeth.lange at uninett.no<mailto:annebeth.lange at uninett.no>
Mobil: + 47 95911559

From: "Daniel Kalchev .bg" <daniel at digsys.bg<mailto:daniel at digsys.bg>>
Date: Monday 30 March 2015 09:25
To: "ctn-crosscom at icann.org<mailto:ctn-crosscom at icann.org>" <ctn-crosscom at icann.org<mailto:ctn-crosscom at icann.org>>
Subject: Re: [Ctn-crosscom] Soft confusing similarity

Dear All,

I would like to share Mirjana's opinion. These two strings should be
considered confusingly similar.

Perhaps a "solution" would be to threat them as "variants", even if they
are not, according to the current opinion what a variant is at ICANN.

Daniel Kalchev

On 29.03.15 14:56, Mirjana Tasic wrote:
Dear all,
I was very astonished when I read this in the mail sent by Joke Braeken:
"New gTLDs: Soft confusing similarity check. E.g.: Hotels and hotel are
not deemed to be confusingly similar;”

I have looked a little bit around about “Soft confusing similarity
check” on ICANN site and there is an explanation that the SWORD
algorithm is used in the first step in string similarity evaluation
process. String has to pass additional check in step 7a Quality Review
for Strings That Pass the Initial Evaluation

*https://newgtlds.icann.org/en/program-status/evaluation-panels/geo-names-similarity-process-07jun13-en.pdf*

>From my point of view there is no chance that “Hotels” and “hotel” could
be registered as TLD, for me these two strings are the same.
Mirjana Tasic
On 16.3.2015 10:01, Joke Braeken wrote:

Dear all,

Just a small “no objection” from my side in the attached documents, to
the suggestion to have .eu included as an example (page 3 – comment
number 8 – clean version).    Moreover, I took the opportunity to add
in this context that an unchallengeable policy in terms of confusing
similarity throughout the TLD space would be highly desirable.

Currently:

·         When requesting a new ccTLD corresponding to an ISO-code,
there is no confusing similarity assessment made at present. If the
code is available, it is delegated;

·         New gTLDs: Soft confusing similarity check. E.g.: Hotels and
hotel are not deemed to be confusingly similar;

·         IDN ccTLDs: Strict confusing similarity check against ISO
codes and even gTLDs or applied for gTLDs.

Best regards,

Joke Braeken (Ms)

/External Relations Deputy Manager/

*EUR/id/*

Woluwelaan 150

1831 Diegem - Belgium

TEL.: +32 (0) 2 401 27 50

DIRECT: +32 (0) 2 401 30 14

MOB.:+32 (0) 473 779 559

joke.braeken at eurid.eu<mailto:joke.braeken at eurid.eu> <mailto:joke.braeken at eurid.eu>

http://www.eurid.eu <http://www.eurid.eu/>
facebook_icon_email
<https://www.facebook.com/EUregistry>twitter_icon_email
<https://twitter.com/Euregistry>

email_sign_bootjetipleftcrop

*From:*ctn-crosscom-bounces at icann.org<mailto:*ctn-crosscom-bounces at icann.org>
[mailto:ctn-crosscom-bounces at icann.org] *On Behalf Of *Lars Hoffmann
*Sent:* maandag 16 maart 2015 8:15
*To:* ctn-crosscom at icann.org<mailto:ctn-crosscom at icann.org>
*Subject:* [Ctn-crosscom] today's meeting

Dear all,

In preparation for our meeting, please find attached the latest
version of the Options paper – one clean version (with comments only)
and one redline version with comments received since our last call. We
will aim to finalise the background section and start discussing
substantial options for 2-letter codes.

Many thanks and best wishes,

Lars

*Proposed agenda, CWG on Country and Territory Names, Monday 16 March
20 UTC, *http://tinyurl.com/mxjcvcm

1. Welcome

2. Confirm agreement on Section 1

3. Substantial Discussion on two-letter strings (Section 2 of Options
Paper)

4. Confirmation of Next Meeting

5. AOB

*Disclaimer:*
/This email and any attachment hereto is intended solely for the
person to which it is addressed and may contain confidential and/or
privileged information. If you are not the intended recipient or if
you have received this email in error, please delete it and
immediately contact the sender by telephone or email, and destroy any
copies of this information. You should not use or copy it, nor
disclose its content to any other person or rely upon this
information. Please note that any views presented in the email and any
attachment hereto are solely those of the author and do not
necessarily represent those of EURid. While all care has been taken to
avoid any known viruses, the recipient is advised to check this email
and any attachment for presence of viruses./
Other languages:
English <http://www.eurid.eu/en/legal-disclaimer> Estonian
<http://www.eurid.eu/et/legal-disclaimer> Italian
<http://www.eurid.eu/it/legal-disclaimer> Maltese
<http://www.eurid.eu/mt/legal-disclaimer> Romanian
<http://www.eurid.eu/ro/legal-disclaimer> Swedish
<http://www.eurid.eu/sv/legal-disclaimer>
Czech <http://www.eurid.eu/cs/legal-disclaimer> Spanish
<http://www.eurid.eu/es/legal-disclaimer> Latvian
<http://www.eurid.eu/lv/legal-disclaimer> Dutch
<http://www.eurid.eu/nl/legal-disclaimer> Slovak
<http://www.eurid.eu/sk/legal-disclaimer> Greek
<http://www.eurid.eu/el/legal-disclaimer>
Danish <http://www.eurid.eu/da/legal-disclaimer> French
<http://www.eurid.eu/fr/legal-disclaimer> Lithuanian
<http://www.eurid.eu/lt/legal-disclaimer> Polish
<http://www.eurid.eu/pl/legal-disclaimer> Slovenian
<http://www.eurid.eu/sl/legal-disclaimer> Bulgarian
<http://www.eurid.eu/bg/legal-disclaimer>
German <http://www.eurid.eu/de/legal-disclaimer> Gaelic
<http://www.eurid.eu/ga/legal-disclaimer> Hungarian
<http://www.eurid.eu/hu/legal-disclaimer> Portuguese
<http://www.eurid.eu/pt/legal-disclaimer> Finnish
<http://www.eurid.eu/fi/legal-disclaimer> Croatian
<http://www.eurid.eu/hr/legal-disclaimer>

_______________________________________________
Ctn-crosscom mailing list
Ctn-crosscom at icann.org<mailto:Ctn-crosscom at icann.org>
https://mm.icann.org/mailman/listinfo/ctn-crosscom
_______________________________________________
Ctn-crosscom mailing list
Ctn-crosscom at icann.org<mailto:Ctn-crosscom at icann.org>
https://mm.icann.org/mailman/listinfo/ctn-crosscom
_______________________________________________
Ctn-crosscom mailing list
Ctn-crosscom at icann.org<mailto:Ctn-crosscom at icann.org>
https://mm.icann.org/mailman/listinfo/ctn-crosscom

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20150330/2e2761c6/attachment-0001.html>