Fw: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt

["FDU - Sung Jae Shim" <sshim@mailbox.fdu.edu>]

The same email was sent from an email account which is not listed on the
mailing list. I am sorry about that.

Sung

----- Original Message -----
From: DualName - ShimSungJae <shimsungjae@dualname.com>
To: Mark Davis <mark@macchiato.com>; <idn@ops.ietf.org>; Paul Hoffman / IMC
<phoffman@imc.org>
Sent: Sunday, November 19, 2000 6:49 PM
Subject: Re: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt


> Mark,
>
> Thank you for your comments. Please see below for my responses to your
> comments.
>
> Sung
>
> P.S. I have already responded to the comments provided by Mr. Paul
Hoffman.
>
> ----- Original Message -----
> From: Mark Davis <mark@macchiato.com>
> To: <idn@ops.ietf.org>; Paul Hoffman / IMC <phoffman@imc.org>
> Sent: Friday, November 17, 2000 12:37 AM
> Subject: Re: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt
>
>
> > I agree completely.
> >
> > a. There is no accepted set of rules for romanizations of all languages.
>
> Sung: That is one of the reasons why VIDN uses the phonemes as a medium of
> the transliteration. Phonemes are very universal, being applicable to any
> language. In fact, most transliteration schemes are based upon the
> systems of sounds of the respective two languages and the units of such
> systems are phonemes.
>
> > b. Moreover, to be useful according to the proposal, the romanization
> would
> > have to provide a "round-trip" mapping.
>
> Sung: Again, since VIDN uses the phonemes as a medium of the
> transliteration, a "two-way" mapping is possible. That is, VIDN
> transliterates between two languages using the phonemes that have the same
> or very proximate sounds.
>
> > c. Furthermore, the romanizations will be subject to accidental
collisions
> > between different scripts.
>
> Sung: Such collisions between different scripts may occur when the
different
> scripts are actually used and registered as internationalized domain
> names. Please note that VIDN do NOT create and register any
> internationalized domain name, BUT it allows using internationalized
domain
> names virtually. Thus, as long as the characters in different scripts
> represent the phonemes that have the same or very proximate sounds, VIDN
> returns the same characters in English.
>
> Sung: Also, since domain names in English already exist, conversion from
one
> local language into another local language can be done via English
> language. For example, a virtual domain name entered in Korean can be
> converted into the corresponding domain name in English, which can be also
> converted from another virtual domain name entered in Japanese. Using
domain
> names in English as liaison between virtual domain names in two local
> languages can minimize the possibilities for such collisions between the
two
> local languages.
>
> > d. And finally, the mechanisms for doing romanization need to be fairly
> > sophisticated. Look at ICU's, for example:
> >
> > http://oss.software.ibm.com/icu/userguide/Transliteration.html
> >
>
> Sung: "Sophisticated" does not necessarily mean "impossible." In fact,
VIDN
> uses the knowledge base of transliteration, which is very comprehensive,
if
> not complete. For example, several experts in Korean and English phonemics
> and linguistics have consulted in constructing the knowledge base of VIDN
> for Korean-English conversion. The knowledge base includes not only the
> general principles of transliteration but also common usages, idiomatic
> expressions, and possible variations that may occur in transliteration.
>
> > Mark
> >
> > (I'm replying to a slightly broader list on this message).
>
>