an interesting ICANN development on similar domain names

[JFC Morfin]

Erci, Vint,
I currently work on a table of 27,000 linguistic entities that are 
supported by all the different scripts and mostly supported by 
phonetic characters. All of them are attached to human relational 
spaces which have the same legitimacy to have a TLD as did ".cat" or 
the currently broadly used five (or more ?) Chinese Names TLDs.  WTO 
agreements imply that each of these TLDs should be supported in the 
other 27,000-1 entities. This means 738.923.000 TLD to start with. 
There will obviously be many g/sTLD in these communities. We can 
therefore guesstimate that there is a need for as many TLDs as Credit 
Card Numbers for example (something we daily live with). Each of my 
credit card transaction is perfectly designated in my banking 
statements with a reference.

This "transaction_reference.my_credit_card_number" is a good domain 
name to access the information my bank has on the transaction. Any 
ISO 11179 compatible system will be able to start from there to dig 
many information. This is the real world.

I would be surprised if anyone tried to decide much all these 
references were confusing, and confusing to who (machines, writers, 
speakers, young, old people, etc.) and at which degree (high-, 
medium+, medium-, low_0, etc.) along criteria. What is very confusing 
to me is this constant effort I observe to unilaterally rule the most 
multilaterai system ever created by billions of people: their common 
digital ecosystem. This just because the legacy Internet model is 
IANA centralised and does not uses classes.

I understood this WG was about to make IDNA2003 work better without 
caring about real world expectations nor ICANN last fancies. Please 
let stick to it or this work will never be ended.
jfc


At 02:44 10/08/2008, Eric Brunner-Williams wrote:
>Vint,
>When I was at the GNSO Council + ICANN Staff meeting in LA earlier this
>year, to go over the Staff's proposals for the new gTLD evaluation and
>schedule, this was discussed.
>
>Which is to say quite a few people wondered out loud just what this was
>for, and how it would help. As an observer I limited myself to "will my
>proposals be charged for a share of the cost of this absurd thing. The
>algorithm then demonstrated gave high "alike" values for things like
>"us" and "eus", the iso3166 code point for the United States, and the
>iso639 code point for the Basque language, which didn't inspire much
>positive awe on my part.
>
>No one seemed to be really impressed with this on its face, and it isn't
>unreasonable to think about how such an "objective" or "widely used"
>thingamabob from some other problem domain is either misapplied in the
>ASCII and ASCII-encoded-mumble evaluation process, or applied with a
>purpose that is unlike its original purpose in its original problem domain.
>
>It was also discussed when Kurt the the stand-up again (in less than two
>days) at ICANN Paris. I don't know who'd be sad if it wandered off
>looking for a better home.
>
>Eric
>
>Vint Cerf wrote:
> >
> > String Similarity Algorithm Update* -- ICANN staff recently completed
> > a workshop with SWORD, the partner who is assisting ICANN with the
> > creation of an algorithm that will help automate the process for
> > assessing similarity among proposed and existing TLD strings. SWORD's
> > verbal search algorithms are used by various patent and trademark
> > offices throughout the world. SWORD has completed a beta algorithm and
> > reviewed several test cases with ICANN staff. This is being done in
> > order to refine the parameters and discuss how the algorithm could be
> > successfully integrated as a tool to help implement the GNSO's
> > recommendation that new gTLD strings should not result in user
> > confusion with existing TLDs.
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Idna-update mailing list
> > Idna-update at alvestrand.no
> > http://www.alvestrand.no/mailman/listinfo/idna-update
> >
>_______________________________________________
>Idna-update mailing list
>Idna-update at alvestrand.no
>http://www.alvestrand.no/mailman/listinfo/idna-update