Re: [ccnso-idncctld] FW: Adjusted language from todays meeting

[HiroHOTTA <hotta@xxxxxxxxxx>]

Now I'm confused. It may be because I've not read the 
re-drafted whole document and I'm on the far side of 
the knowledge of Latin-based scripts.

I thought Latin-based scripts (which includes decorated 
a-z) are not allowed to apply for IDn ccTLD in the Fast 
Track.

May I ask you whether, for example, German-speaking 
territory can apply for a German territory name as IDN 
ccTLD string in the Fast Track if the string has 'eszett'?

Is there a clear definition of what scripts are 
Latin-based and what are not?  Is Greek script Latin-based?
Is Cyrillic script Latin-based?

Examples may help readers (like me) to avoid misunderstanding. 

Thanks.

Hiro


On Sat, 21 Jun 2008 23:51:44 -0700
Bart Boswinkel <bart.boswinkel@xxxxxxxxx> wrote:
> Dear all,
> Included proposed language to clarify meaning on non-latin and the uniqueness 
> of the label.
> I'll insert this in the report.
> Bart
> 
> ------ Forwarded Message
> From: Cary Karp <ck@nic.museum>
> Date: Sat, 21 Jun 2008 22:40:33 -0700
> To: Bart Boswinkel <bart.boswinkel@xxxxxxxxx>
> Subject: Re: Adjusted language from todays meeting
> 
> Non-ASCII:
> 
> The term "non-ASCII" is used here to designate any script that contains
> elements that are not listed in the US-ASCII character set. This
> includes Latin-based alphabets containing letters additional to the
> twenty-six basic letters "a" through "z" or using those letters with
> combining marks.
> 
> > As we briefly discussed this afternoon can you send me some language
> > on the the uniqueness of a label? As far as I recall and written down
> > it has to do with the requirement to have at least one element in the
> > string that is unique for the script to avoid potential confusion.
> > Thanks, Bart
> 
> A label in any script containing elements that, under common display
> conditions, appear identically to the literal elements of the US-ASCII
> character set, must contain at least one element that is visibly unique
> to the declared script. Where the visual confusability occurs between
> labels in two different non-ASCII scripts, the ambiguity should be
> resolved in a similar manner.
> 
> 
> ------ End of Forwarded Message