Re: [idn] what are the IDN identifiers?

[liana Ye <liana.ydisg@juno.com>]

On Thu, 6 Dec 2001 08:57:32 -0500 tedd <tedd@sperling.com> writes:
> Liana:
> 
> >Unicode did give them independent codepoints as well as some
> >shared code points.   This is the reason we need an equivalent
> >set to be implemented so that there is place to check <Kanji-tree>
> >is <Han-tree>, or<Han-TC-tree> is <Han-SC-tree>  to prevent the
> >second registration, given two codepoints are not neccessarily
> >the same.
> 
> Understood, if the code points are not the same, then different 
> registrations are allowed.
> 
> >So does Armenian "nnnn" can be registered and found out later is
> >conflict with Latin "nnnn" as trademark issue, precisely due to
> >they are different codepoints in UCS.
> 
> Certainly, one person can register an  Armenian "nnnn" and someone 
> else register a Latin "nnnn" and still another can register Armenian 
> "nn" followed by a Latin "nn" and all possible combinations thereof. 
> 
> These are a concern in trademark, copyright and business issues. 
> However, this problem is something for the courts and/or WIPO to fix 
> 
> -- not the IDN. The problem is too large.
> 
> >  > Now, with all that said, I wonder if the idn wg is the place to
> >>  discus your problem? For I do not see what anyone could do short 
> of
> >>  assigning different code point for shared characters -- do you?
> >
> >Now, I am confused with your question, which problem I
> >have discussed you don't think belong to idn wg?
> 
> No offense meant, but I think that the issue you have raised, namely 
> trademark concerns, is something that is out of the scope of the IDN 
> WG. From what I gather, the IDN WG is only concerned with: 1) 
> Investigating the feasibility of using multilingual domain names; 2) 
> And, implementing the resultant procedures necessary to use 
> multilingual domain names. In other words, they are trying to get it 
> to work and are not concerned about possible trademark issues.

The investigation yields: there are feasibale solutions 
of using multilingual domain names, but not in the 
frame of western programming scheme.  They are 
in the data centric programming scheme.   Should 
the group look at it or should it be excluded from 
discussion?

The implememed resultant on the table is [nameprep],
and only covers 1463 symbols.  What about the 
the other 30,000 symbols?  If you are the chairs of
this group, can you provide that as a multilingual
domain name solution to declare the job is done 
for this group? 

> Now, I believe that is correct -- however, I may be wrong. Keep in 
> mind that I am only a lurker without the great mind that's required 
> to be on this list.

That is the way many of my colleagues think too.  They 
have disqualified themselves to be on this list, but I think
they are the silent majority on this issue.


> But, in either event, IMO the trademark problem cannot be solved 
> before hand by prohibiting such things as the Armenian "nnnn"  vs 
> the 
> Latin "nnnn" issue because it's too large a problem. Trademark 
> issues 
> WILL most certainly follow regardless of what anyone does in this 
> group because no one can predict how users and businesses will act 
> and react.
> 
> In the US, we have an anti-cybersquatting law where I can't register 
> EXXON.com because of the Trademark owned by EXXON. Likewise, I can't 
> register EXXON?com (note the new multilingual character) because of  
> the same Trademark law. The WIPO appears to be of the same focus and 
> I am sure that other countries will follow with similar legislation. 
> The Trademark problem will work it's self out in the course of time 
> on a case by case basis regardless of any preemptive actions taken 
> by  the IDN WG.
> 
> tedd

  
  Thank you for make the issue clearly stated.  I am posting 
your discussion for others to think about.  May be WIPO
people want to joint this discussion too. 

Liana