Dear Chris, I will deeply study the ToDo list, and your comments, which may take some more time. Before finishing my homework, I would like to make two points for consideration: 1. Up to now, what we are working on is limited to character (and its variants)- based label generation, we have not defined string/word based rule yet. Especial, we have not define the language and/or context sensitive string/word yet. It seems quite complicated, but is inevitable to work on it in the next stage. For examples, (1) Exception treatment, such as ��-�l-�k and��/ � (2) C-J sensitive : ��-�I-亣���-ˇ-ܿ�� (3) ͬ��� Synonym as label��word based variant string��: ��λ��-���ֻ� ������-���䣬�㵱-�͵� (4) Rules like: No simplified/traditional/variant mixing in labels. (important for CGP) 2. Some visible differences amongst Hanzi/Hanja/Kanji would be so-called Z-difference in Unicode/UniHan, say, ��I have also been looking for differences between Traditional Chinese characters and Korean hanja. So far I have found one: characters with the progression radical tend to start with two dots in hanja: �� and only one in Traditional Chinese: ��.�� Actually, both are encoded at U+9003, but rendered in different fonts. If I may participate the coming Seoul meeting, we may discuss in detail. Looking forward to seeing you there. Regards, Zhang ������: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] �� �� Dillon, Chris ����ʱ��: 2015��4��27�� 20:43 �ռ���: hotta@jprs.co.jp; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org ����: Re: [ChineseGP] [Koreangp] Proposed Action items before Seoul meeting Dear colleagues, Here are some comments, as requested by Hiro. I reckon I have now caught up after missing the Dallas meeting. I believe Mr Yoneya��s algorithm will work. I have spent some amount of time looking for exceptions to various statements in it e.g. Slide 5 ��there exists at least one identical ideograph��. (No exception found.) It is fortunate that �C ��machine�� / �� ��desk�� and �k ��send�� / � ��hair�� seem to be the only cases where (at least commonly used) different characters in Japanese are the same character in Simplified Chinese. (I haven��t spent as much time with looking for characters that are separate in Chinese but brought together in Japanese. �� replaces at least three characters in Chinese, but I think none are common. I can imagine a . �͵� TLD, so that may be good news for bento companies.) I note the options for the disposition of variants not defined in the LGR-1s (Slide 6), i.e.: - Blocked if the variant is not in the LGR-1 / Allocatable otherwise - Blocked if the variant is not in the LGR-1 / Inherit its original disposition in the LGR-1 (Allocatable/Simp/Trad/Both) Both case studies are most interesting. I note that there are some labels, e.g. �� (with the first character, I think used only in Japan and the second only in Simplified Chinese) that perhaps we would prefer not to see allocatable in the ideal world, but suspect that blocking them would involve adding horrendous complexity. I note that it is difficult to understand Japanese LGR-1, as the characters are not visible. I have also been looking for differences between Traditional Chinese characters and Korean hanja. So far I have found one: characters with the progression radical tend to start with two dots in hanja: �� and only one in Traditional Chinese: ��. Looking forward to Seoul, Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon <http://www.ucl.ac.uk/dis/people/chrisdillon> -----Original Message----- From: koreangp-bounces@icann.org <mailto:koreangp-bounces@icann.org> [mailto:koreangp-bounces@icann.org] On Behalf Of HiroHOTTA Sent: 25 April 2015 18:05 To: KoreanGP@icann.org <mailto:KoreanGP@icann.org> ; ChineseGP@icann.org <mailto:ChineseGP@icann.org> ; JapaneseGP@icann.org <mailto:JapaneseGP@icann.org> Subject: [Koreangp] Proposed Action items before Seoul meeting Dear colleagues in CGP/JGP/KGP, If I may, in order for us to make our Seoul meeting efficient and fruitful, I'd like to propose what each of us is expected to prepare well before the meeting. I know I am very pushy but I think at least we must not use our precious time just to understand the information in front of us for a long time. Please give comments and let's discuss online about the ToDo's before Seoul meeting . == [[Premise]] ToDo-1 <must> Each participant understands what RootLGR is and what is expected for GPs to do. ToDo-2 <must> Each participant understands Yoneya's algorithm that was already sent to CGP/JGP/KGP by Yoneya and also agreed by C and J in Dallas, which is attached to this mail as well ToDo-3 <must> Each participant understands MSS concept that was already sent to CGP/JGP/KGP by Dr. Wang Wei, which is attached to this mail along with HiroHOTTA's response ToDo-4 <expected> Participants agree on Yoneya's algorithm as a framework and also agree on partial usage of MSS to accelerate our discussion ("partial" means "J doesn't need to be considered to be incorporated into MSS") This is expected to be discussed and finalized online before our meeting [[Integration Algorithm]] ToDo-5 <expected> J gets IP's feedback on Yoneya's algorithm [[MSS/LGR-1]] ToDo-6 <must> C prepares MSS repertoire, which may be equivalent to Chinese LGR-1 repertoire (done?) ToDo-7 <expected> C prepares Chinese variants within MSS, which may be equivalent to Chinese LGR-1 (planned date is expected to be declared, if not in time for the meeting) ToDo-8 <must> J prepares Japanese LGR-1 repertoire and variants (there's no variants in Japanese LGR-1 : they were already sent to CGP/JGP/KGP) ToDo-9 <must> K prepares the basic idea of Korean LGR-1 repertoire and variants ToDo-10<expected> K prepares Korean LGR-1 repertoire and variants (planned date is expected to be declared, ift LGR-1 does not come in time for the meeting) ToDo-11<expected> each of CGP/JGP/KGP assesses the repertoires and variants that have already been provided by other GPs as far as possible [[Logistics/etc.]] ToDo-12<must> each CGP/JGP/KGP Chair designates a person in charge of ToDo-5 to ToDo-11 well in advance to the meeting (expected to post the (names) in replying this mail by May 1st) - this may accelerate the coordination a lot ToDo-13<must> convener fixes the agenda through consultation with CJK colleagues (Hiro is pleased to behave as the convener until someone will raise his/her hand) Hiro _______________________________________________ Koreangp mailing list <mailto:Koreangp@icann.org> Koreangp@icann.org <https://mm.icann.org/mailman/listinfo/koreangp> https://mm.icann.org/mailman/listinfo/koreangp