Hi, Peter-san

Thank you for your quick reply.
I think that this profile is similar to the nickname profile too.

However, even though NKFC has the benefit of increasing the probability of 
comparison matching, 
the aggressive normalization may create a problem. Using NKFC on some 
characters may cause
 changes on the character’s form and byte length that would confuse users. 
For this reason, I chose NFC and width mapping.

Last year, I conducted a research in Singapore (a country that uses English, 
Chinese, 
and Malay as the official languages) on the names that are attached on hosts by 
users. 
I found that there were several machines that use special characters as host 
names. 
Thus, this profile is intended to allow as many characters as possible while 
increasing 
the probability of comparison matching and I think NFC and width mapping would 
be 
appropriate for preprocessing of names for aliases of machines that are used on 
daily basis.

For this reason, I would like to do a little more research to understand the 
necessity of this profile processing.
Please let me know if you have any questions and concerns. Your comment will be 
greatly appreciated.


Regards,

Nemo

2014/11/13 15:11、Peter Saint-Andre - &yet <[email protected]> のメール:

> On 11/13/14, 4:51 PM, Takahiro Nemoto wrote:
>> Dear all,
>> 
>> Although belated, Daniel (new co-author) and I submitted new PRECIS
>> profile document.
>> I would greatly appreciate your comments/suggestions.
> 
> As section 5.1 of draft-ietf-precis-framework-19 says, "profiles must not be 
> multiplied beyond necessity". Therefore, I wonder why we need this profile, 
> because it is very similar to the nickname profile in 
> draft-ietf-precis-nickname. The only difference I can see is the use of NFKC 
> and therefore no width mapping in the nickname profile (intended to reduce 
> the possibility of confusion) vs. the use of NFC and width mapping in the 
> alternative names profile.
> 
> Peter
> 
> -- 
> Peter Saint-Andre
> https://andyet.com/
> 
> _______________________________________________
> precis mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/precis

_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis

Reply via email to