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
Dear Hotta San, Thanks for preparing these todo items. It does help to maximize the outcome of the meeting. We have to complete the intensive homework before the meeting. Regards Kenny Huang On 26 April 2015 at 01:05, HiroHOTTA <hotta@jprs.co.jp> wrote:
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
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Dear CJK colleagues,
ToDo-12<must> each CGP/JGP/KGP Chair designates a person in charge of ToDo-5 to ToDo-11
JGP designates Yoneya as a person in charge of ToDo-5 to ToDo-11. Please e-mail <yoshiro.yoneya@jprs.co.jp> while CC-ing to <hotta@jprs.co.jp> when you want to discuss with him especially when the discussion themes are about details. Regards, Hiro On Sun, 26 Apr 2015 02:05:17 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
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
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear ALL For CGP, ToDo-6 has been done. ToDo-7 will be sent out after double check this week. -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 HiroHOTTA 发送时间: 2015年4月26日 1:05 收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 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 _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Dear CGP/KGP members,
[[Premise]] 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
Because the file seemed unattached, I attatched explanation of proposed CJK integration algorithm (Yoneya's algorithm). Please note that WLE in step 5 (slide 8) is omitted from Case Study examples (slide 11 and 15) because it is obvious. Please feel free to ask me if you have any questions. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Sun, 26 Apr 2015 02:05:17 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
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
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear all, I'm so sorry that I forgot to attach files. Yoneya kindly sent out Yoneya's algorithm. Here I attach the file that was referred to in
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
Hiro On Mon, 27 Apr 2015 18:01:52 +0900 Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote:
Dear CGP/KGP members,
[[Premise]] 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
Because the file seemed unattached, I attatched explanation of proposed CJK integration algorithm (Yoneya's algorithm). Please note that WLE in step 5 (slide 8) is omitted from Case Study examples (slide 11 and 15) because it is obvious.
Please feel free to ask me if you have any questions.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Sun, 26 Apr 2015 02:05:17 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
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
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
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 -----Original Message----- From: koreangp-bounces@icann.org [mailto:koreangp-bounces@icann.org] On Behalf Of HiroHOTTA Sent: 25 April 2015 18:05 To: KoreanGP@icann.org; ChineseGP@icann.org; 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 Koreangp@icann.org<mailto:Koreangp@icann.org> https://mm.icann.org/mailman/listinfo/koreangp
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
Dear Professor Zhang, Thank you for your summary of issues that we will face in the mid to long term. �� Seems, fortunately, to be a smaller problem than I would have expected, but there seems to be no solution. �� I suspect that a solution for (3) could be based on what happens with labels containing the sorts of variants listed in (2). However, (3) would be a new departure for labels; for example, such situations as English www.pictures.com<http://www.pictures.com>, www.photo.com<http://www.photo.com>, German www.foto.com<http://www.foto.com> have traditionally been regarded as probably being different sites (I haven��t checked this example �C if I��m unlucky perhaps some of them are the same company!). �� (4) may well be desirable but difficult for all panels. 2. I have fallen into a trap as I have no list of variant issues dealt with at font level. I��m sure I��ve seen such a list (I did find a short list which I have attached) and would be grateful if any colleague has a better list. In this case the Chinese Simsun font has one dot and the Korean Malgun font has two. I do hope we meet in 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> From: Joe Zhang [mailto:joezhang43@hotmail.com] Sent: 28 April 2015 04:28 To: Dillon, Chris; hotta@jprs.co.jp; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: ��: [ChineseGP] [Koreangp] Proposed Action items before Seoul meeting 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> [mailto:chinesegp-bounces@icann.org] ���� Dillon, Chris ����ʱ��: 2015��4��27�� 20:43 �ռ���: hotta@jprs.co.jp<mailto:hotta@jprs.co.jp>; KoreanGP@icann.org<mailto:KoreanGP@icann.org>; ChineseGP@icann.org<mailto:ChineseGP@icann.org>; JapaneseGP@icann.org<mailto: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.
Dear Chris-san, Thank you for your comments. Followings are my responses for some of them.
I believe Mr Yoneya’s algorithm will work.
Thank you, it encourages me a lot.
It is fortunate that 機 ’machine’ / 机 ’desk’ and 発 ’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.)
JGP assessed CGP's draft LGR-1 how it affects to the usage of Japanese IDN. What JGP did and tentatively concluded are: - Comparison of CGP's draft LGR-1 and JGP's draft LGR-1 (with possible variants) - JGP tentatively concluded that serious influence of CGP's variant to Japanese IDN might be very limited - Assessment of occurence of 'may be seriously affected' variants in Japanese JP domain name - JGP tentatively concluded that such variants are mostly used as different character in Japanese IDN
From this assessment, we proposed Japanese LGR-1 with no variant. So, at this moment, JGP does not have much interest to search different variants.
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)
For JGP, both is OK. For CGP, the latter seems to be more acceptable. I'd like to have consensus on this during the meeting.
I note that it is difficult to understand Japanese LGR-1, as the characters are not visible.
Attached Japanese LGR-1 repertoire list with visible characters. I hope this is helpful. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Mon, 27 Apr 2015 12:42:30 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
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 機 ’machine’ / 机 ’desk’ and 発 ’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
-----Original Message----- From: koreangp-bounces@icann.org [mailto:koreangp-bounces@icann.org] On Behalf Of HiroHOTTA Sent: 25 April 2015 18:05 To: KoreanGP@icann.org; ChineseGP@icann.org; 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
Koreangp@icann.org<mailto:Koreangp@icann.org>
Dear Yoneya-san, Thank you for the spreadsheet with the characters. Seeing them really makes a difference. The general impression is of a generous list containing especially at the end of it some characters I've seen for example in novels or old literature over the last 35 years, and some I've never seen at all. However, obviously, as a non-native speaker I have not read anything like as much as most native speakers have. The situation (i.e. containing rarer characters) may well be the same with the Chinese tables, but I can't comment at all there, as I have read so little modern Chinese. I did study Classical Chinese at university. (The Chinese students used to laugh if I pronounced 孔子曰 as Koushi iwaku ... as many did not realize that there is a system for reading Classical Chinese in Japanese.) I think the JGP's conclusions are probably correct, but I reckon the best way to be sure is to look at things from as many angles as possible and to try to find any exceptions to and problems with every statement. Thank you also for clarifying the situation as regards the options on Slide 6. Looking forward to seeing you in 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 -----Original Message----- From: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] Sent: 28 April 2015 09:56 To: Dillon, Chris Cc: hotta@jprs.co.jp; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [Koreangp] Proposed Action items before Seoul meeting Dear Chris-san, Thank you for your comments. Followings are my responses for some of them.
I believe Mr Yoneya’s algorithm will work.
Thank you, it encourages me a lot.
It is fortunate that 機 ’machine’ / 机 ’desk’ and 発 ’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.)
JGP assessed CGP's draft LGR-1 how it affects to the usage of Japanese IDN. What JGP did and tentatively concluded are: - Comparison of CGP's draft LGR-1 and JGP's draft LGR-1 (with possible variants) - JGP tentatively concluded that serious influence of CGP's variant to Japanese IDN might be very limited - Assessment of occurence of 'may be seriously affected' variants in Japanese JP domain name - JGP tentatively concluded that such variants are mostly used as different character in Japanese IDN From this assessment, we proposed Japanese LGR-1 with no variant. So, at this moment, JGP does not have much interest to search different variants.
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)
For JGP, both is OK. For CGP, the latter seems to be more acceptable. I'd like to have consensus on this during the meeting.
I note that it is difficult to understand Japanese LGR-1, as the characters are not visible.
Attached Japanese LGR-1 repertoire list with visible characters. I hope this is helpful. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Mon, 27 Apr 2015 12:42:30 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
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 機 ’machine’ / 机 ’desk’ and 発 ’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.
Dear Chris-san,
I think the JGP's conclusions are probably correct, but I reckon the best way to be sure is to look at things from as many angles as possible and to try to find any exceptions to and problems with every statement.
As you see, Japanese LGR-1 includes rare characters. This is because the source of Japanese LGR-1 is from Japanese Industrial Standard (JIS) repertoire. To provide details, Kanji repertoire in Japanese LGR-1 is the same with Kanji defined in level 1 and level 2 of JIS X 0208[1]. JIS X 0208 has more than 30 years history, and is widely used in Japan. JGP considered more narrow/wide range of repertoire, but tentatively concluded that the repertoire of JIS X 0208 is reasonable selection for Japanese LGR-1 repertoire. [1] JIS X 0208 <http://en.wikipedia.org/wiki/JIS_X_0208> <http://zh.wikipedia.org/wiki/JIS_X_0208> <http://ko.wikipedia.org/wiki/JIS_X_0208> Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Wed, 29 Apr 2015 08:22:31 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
Thank you for the spreadsheet with the characters. Seeing them really makes a difference. The general impression is of a generous list containing especially at the end of it some characters I've seen for example in novels or old literature over the last 35 years, and some I've never seen at all. However, obviously, as a non-native speaker I have not read anything like as much as most native speakers have. The situation (i.e. containing rarer characters) may well be the same with the Chinese tables, but I can't comment at all there, as I have read so little modern Chinese. I did study Classical Chinese at university. (The Chinese students used to laugh if I pronounced 孔子曰 as Koushi iwaku ... as many did not realize that there is a system for reading Classical Chinese in Japanese.)
I think the JGP's conclusions are probably correct, but I reckon the best way to be sure is to look at things from as many angles as possible and to try to find any exceptions to and problems with every statement.
Thank you also for clarifying the situation as regards the options on Slide 6.
Looking forward to seeing you in 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
-----Original Message----- From: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] Sent: 28 April 2015 09:56 To: Dillon, Chris Cc: hotta@jprs.co.jp; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [Koreangp] Proposed Action items before Seoul meeting
Dear Chris-san,
Thank you for your comments. Followings are my responses for some of them.
I believe Mr Yoneya’s algorithm will work.
Thank you, it encourages me a lot.
It is fortunate that 機 ’machine’ / 机 ’desk’ and 発 ’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.)
JGP assessed CGP's draft LGR-1 how it affects to the usage of Japanese IDN.
What JGP did and tentatively concluded are: - Comparison of CGP's draft LGR-1 and JGP's draft LGR-1 (with possible variants) - JGP tentatively concluded that serious influence of CGP's variant to Japanese IDN might be very limited - Assessment of occurence of 'may be seriously affected' variants in Japanese JP domain name - JGP tentatively concluded that such variants are mostly used as different character in Japanese IDN
From this assessment, we proposed Japanese LGR-1 with no variant. So, at this moment, JGP does not have much interest to search different variants.
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)
For JGP, both is OK. For CGP, the latter seems to be more acceptable. I'd like to have consensus on this during the meeting.
I note that it is difficult to understand Japanese LGR-1, as the characters are not visible.
Attached Japanese LGR-1 repertoire list with visible characters. I hope this is helpful.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 27 Apr 2015 12:42:30 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
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 機 ’machine’ / 机 ’desk’ and 発 ’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.
Dear Yoneya-san, JIS X 0208 looks rather familiar to me; when I was working in the British Library in the 1990s I once improved the character candidate listings in a Japanese Front End Processor used with a DOS bibliographic database. I've been scrolling through J-LGR-s.xlsx and found some interesting things, mostly minor (see below and in red in the attached file). One thing isn't minor and I'll write about it in a separate email. - Some code points are close to being punctuation, e.g. ゝ 309D and ー 30FC. - It's difficult to imagine small hiragana in labels e.g. 3041 ぁ. - I can just about imagine historic kana being used in cafe names e.g. 3090 ゐ. - There are quite a few code points that look like parts of characters e.g. 4E3F 丿. 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 -----Original Message----- From: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] Sent: 30 April 2015 06:42 To: Dillon, Chris Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [Koreangp] Proposed Action items before Seoul meeting Dear Chris-san,
I think the JGP's conclusions are probably correct, but I reckon the best way to be sure is to look at things from as many angles as possible and to try to find any exceptions to and problems with every statement.
As you see, Japanese LGR-1 includes rare characters. This is because the source of Japanese LGR-1 is from Japanese Industrial Standard (JIS) repertoire. To provide details, Kanji repertoire in Japanese LGR-1 is the same with Kanji defined in level 1 and level 2 of JIS X 0208[1]. JIS X 0208 has more than 30 years history, and is widely used in Japan. JGP considered more narrow/wide range of repertoire, but tentatively concluded that the repertoire of JIS X 0208 is reasonable selection for Japanese LGR-1 repertoire. [1] JIS X 0208 <http://en.wikipedia.org/wiki/JIS_X_0208> <http://zh.wikipedia.org/wiki/JIS_X_0208> <http://ko.wikipedia.org/wiki/JIS_X_0208> Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Wed, 29 Apr 2015 08:22:31 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
Thank you for the spreadsheet with the characters. Seeing them really makes a difference. The general impression is of a generous list containing especially at the end of it some characters I've seen for example in novels or old literature over the last 35 years, and some I've never seen at all. However, obviously, as a non-native speaker I have not read anything like as much as most native speakers have. The situation (i.e. containing rarer characters) may well be the same with the Chinese tables, but I can't comment at all there, as I have read so little modern Chinese. I did study Classical Chinese at university. (The Chinese students used to laugh if I pronounced 孔子曰 as Koushi iwaku ... as many did not realize that there is a system for reading Classical Chinese in Japanese.)
I think the JGP's conclusions are probably correct, but I reckon the best way to be sure is to look at things from as many angles as possible and to try to find any exceptions to and problems with every statement.
Thank you also for clarifying the situation as regards the options on Slide 6.
Looking forward to seeing you in 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
-----Original Message----- From: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] Sent: 28 April 2015 09:56 To: Dillon, Chris Cc: hotta@jprs.co.jp; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [Koreangp] Proposed Action items before Seoul meeting
Dear Chris-san,
Thank you for your comments. Followings are my responses for some of them.
I believe Mr Yoneya’s algorithm will work.
Thank you, it encourages me a lot.
It is fortunate that 機 ’machine’ / 机 ’desk’ and 発 ’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.)
JGP assessed CGP's draft LGR-1 how it affects to the usage of Japanese IDN.
What JGP did and tentatively concluded are: - Comparison of CGP's draft LGR-1 and JGP's draft LGR-1 (with possible variants) - JGP tentatively concluded that serious influence of CGP's variant to Japanese IDN might be very limited - Assessment of occurence of 'may be seriously affected' variants in Japanese JP domain name - JGP tentatively concluded that such variants are mostly used as different character in Japanese IDN
From this assessment, we proposed Japanese LGR-1 with no variant. So, at this moment, JGP does not have much interest to search different variants.
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)
For JGP, both is OK. For CGP, the latter seems to be more acceptable. I'd like to have consensus on this during the meeting.
I note that it is difficult to understand Japanese LGR-1, as the characters are not visible.
Attached Japanese LGR-1 repertoire list with visible characters. I hope this is helpful.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 27 Apr 2015 12:42:30 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
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 機 ’machine’ / 机 ’desk’ and 発 ’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.
Dear Chris-san, Thank you for your deep review and comments.
- Some code points are close to being punctuation, e.g. ゝ 309D and ー 30FC.
Those characters are usually used after other character. And those are important component of Japanese words. Therefore, they cannot be omitted from J-LGR-1.
- It's difficult to imagine small hiragana in labels e.g. 3041 ぁ. - I can just about imagine historic kana being used in cafe names e.g. 3090 ゐ. - There are quite a few code points that look like parts of characters e.g. 4E3F 丿.
In my personal opinion, perhaps those will be rarely used in Japanese IDN TLD. But I can't predict the chance is zero. And I don't have rational reason to omit them from J-LGR-1. If those are used in applied-for string, properness of the string will be checked by manned panel. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Mon, 11 May 2015 13:51:53 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
JIS X 0208 looks rather familiar to me; when I was working in the British Library in the 1990s I once improved the character candidate listings in a Japanese Front End Processor used with a DOS bibliographic database.
I've been scrolling through J-LGR-s.xlsx and found some interesting things, mostly minor (see below and in red in the attached file). One thing isn't minor and I'll write about it in a separate email.
- Some code points are close to being punctuation, e.g. ゝ 309D and ー 30FC. - It's difficult to imagine small hiragana in labels e.g. 3041 ぁ. - I can just about imagine historic kana being used in cafe names e.g. 3090 ゐ. - There are quite a few code points that look like parts of characters e.g. 4E3F 丿.
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
-----Original Message----- From: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] Sent: 30 April 2015 06:42 To: Dillon, Chris Cc: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [Koreangp] Proposed Action items before Seoul meeting
Dear Chris-san,
I think the JGP's conclusions are probably correct, but I reckon the best way to be sure is to look at things from as many angles as possible and to try to find any exceptions to and problems with every statement.
As you see, Japanese LGR-1 includes rare characters. This is because the source of Japanese LGR-1 is from Japanese Industrial Standard (JIS) repertoire. To provide details, Kanji repertoire in Japanese LGR-1 is the same with Kanji defined in level 1 and level 2 of JIS X 0208[1]. JIS X 0208 has more than 30 years history, and is widely used in Japan. JGP considered more narrow/wide range of repertoire, but tentatively concluded that the repertoire of JIS X 0208 is reasonable selection for Japanese LGR-1 repertoire.
[1] JIS X 0208 <http://en.wikipedia.org/wiki/JIS_X_0208> <http://zh.wikipedia.org/wiki/JIS_X_0208> <http://ko.wikipedia.org/wiki/JIS_X_0208>
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Wed, 29 Apr 2015 08:22:31 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
Dear Yoneya-san,
Thank you for the spreadsheet with the characters. Seeing them really makes a difference. The general impression is of a generous list containing especially at the end of it some characters I've seen for example in novels or old literature over the last 35 years, and some I've never seen at all. However, obviously, as a non-native speaker I have not read anything like as much as most native speakers have. The situation (i.e. containing rarer characters) may well be the same with the Chinese tables, but I can't comment at all there, as I have read so little modern Chinese. I did study Classical Chinese at university. (The Chinese students used to laugh if I pronounced 孔子曰 as Koushi iwaku ... as many did not realize that there is a system for reading Classical Chinese in Japanese.)
I think the JGP's conclusions are probably correct, but I reckon the best way to be sure is to look at things from as many angles as possible and to try to find any exceptions to and problems with every statement.
Thank you also for clarifying the situation as regards the options on Slide 6.
Looking forward to seeing you in 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
-----Original Message----- From: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] Sent: 28 April 2015 09:56 To: Dillon, Chris Cc: hotta@jprs.co.jp; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org Subject: Re: [Japanesegp] [Koreangp] Proposed Action items before Seoul meeting
Dear Chris-san,
Thank you for your comments. Followings are my responses for some of them.
I believe Mr Yoneya’s algorithm will work.
Thank you, it encourages me a lot.
It is fortunate that 機 ’machine’ / 机 ’desk’ and 発 ’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.)
JGP assessed CGP's draft LGR-1 how it affects to the usage of Japanese IDN.
What JGP did and tentatively concluded are: - Comparison of CGP's draft LGR-1 and JGP's draft LGR-1 (with possible variants) - JGP tentatively concluded that serious influence of CGP's variant to Japanese IDN might be very limited - Assessment of occurence of 'may be seriously affected' variants in Japanese JP domain name - JGP tentatively concluded that such variants are mostly used as different character in Japanese IDN
From this assessment, we proposed Japanese LGR-1 with no variant. So, at this moment, JGP does not have much interest to search different variants.
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)
For JGP, both is OK. For CGP, the latter seems to be more acceptable. I'd like to have consensus on this during the meeting.
I note that it is difficult to understand Japanese LGR-1, as the characters are not visible.
Attached Japanese LGR-1 repertoire list with visible characters. I hope this is helpful.
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Mon, 27 Apr 2015 12:42:30 +0000 "Dillon, Chris" <c.dillon@ucl.ac.uk> wrote:
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 機 ’machine’ / 机 ’desk’ and 発 ’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.
Dear Yoneya-san, Many apologies! I forgot to attach the annotated spreadsheet to my earlier email. 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
Dear All CGP updates the code points and variants in CGP-MSS, which will be used as CGP LGR1 to coordinate with J and K. Please find the attached XML file generated by Mr. QI Chao. Also, we provide a readable EXCEL version for your review. Please feel free to give your comments Best Regards Wang Wei -----邮件原件----- 发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2015年4月27日 10:15 收件人: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' 主题: 答复: [ChineseGP] Proposed Action items before Seoul meeting Dear ALL For CGP, ToDo-6 has been done. ToDo-7 will be sent out after double check this week. -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 HiroHOTTA 发送时间: 2015年4月26日 1:05 收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 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 _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Supplementary note: Compared to the last version (CGP MSS proposal sent out on 19th Apr) In this 20150430 version, 32 CDNC code points were added into MSS, because they are variant-linked to code points in IICore or Normalized table. 4FC1 俁 4F21 伡 359E 㖞 556F 啯 58D6 壖 5AAF 媯 6A87 檇 3CE0 㳠 7185 熅 7B7F 筿 4337 䌷 7F0D 缍 8183 膃 4729 䜩 8EFF 軿 94B8 钸 94C7 铇 94E6 铦 9559 镙 930B 錋 4985 䦅 9689 隉 98E3 飣 9916 餖 9A94 骔 4CA1 䲡 9CC6 鳆 9D02 鴂 8B7E 譾 8F40 轀 84E8 蓨 9A52 驒 -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代表 王伟 发送时间: 2015年4月30日 23:45 收件人: hotta@jprs.co.jp; KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 答复: Proposed Action items before Seoul meeting Dear All CGP updates the code points and variants in CGP-MSS, which will be used as CGP LGR1 to coordinate with J and K. Please find the attached XML file generated by Mr. QI Chao. Also, we provide a readable EXCEL version for your review. Please feel free to give your comments Best Regards Wang Wei -----邮件原件----- 发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2015年4月27日 10:15 收件人: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' 主题: 答复: [ChineseGP] Proposed Action items before Seoul meeting Dear ALL For CGP, ToDo-6 has been done. ToDo-7 will be sent out after double check this week. -----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 HiroHOTTA 发送时间: 2015年4月26日 1:05 收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 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 _______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Dear Wang Wei san and all, Thank you for CGP's effort. I checked mss-var-20150430.xml from two viewpoints below: (1) Whether Yoneya's algorithm work fine with C and J LGR-1 (2) Whether C-LGR-1 has conflicts of disposition type For (1), it seemed working fine. - There was no difference between C-LGR-1 and generated C-LGR-2 (This is because J-LGR-1 has no variant) - Variants in generated J-LGR-2 were the same with C and J LGR-M (please let me know if you want to see J-LGR-2) For (2), I found hundreds of conflicts listed below. Here, each mark means the disposition type as: - S: simp - T: trad - B: both - b: blocked CP disposition types U+4E10: SB U+4E11: BS U+4E18: BS U+4E30: BbS U+4E43: BSS U+4E48: BTSS U+4E7E: BTTbbS U+4E86: BSS U+4E91: BS U+4E95: SB U+4EC6: BS U+4EC7: BSbb U+4ED9: BSS U+4EF2: BS U+4EFF: BSbS U+4F0A: BS U+4F19: BS U+4F59: BSb U+4F5B: BBSS U+4F60: TBbbb U+4F63: BS U+4F69: BS U+4F84: BS U+4FDD: BS U+4FDE: BBS U+4FEF: SBS U+500F: BS U+501F: BSS U+5026: BbS U+506C: BS U+5077: BBS U+508D: BS U+50ED: SB U+50F5: BS U+5149: BS U+514B: BSS U+518F: BS U+51A2: BS U+51AC: BS U+51B1: BS U+51C6: BSS U+51CC: BS U+51E0: BS U+51F6: SB U+51FA: BS U+5212: BS U+5228: BS U+522E: BS U+5236: BS U+5238: bBT U+5243: BS U+5269: BBS U+526F: BS U+527D: BS U+527F: BS U+52D6: BS U+52E4: BS U+5343: bBS U+5347: BSS U+535C: BbS U+5360: SB U+5377: BBS U+5382: BS U+5384: BS U+5398: BS U+53CD: BS U+53EA: BSS U+53F0: BSSS U+5401: BS U+5403: BS U+5408: BS U+540A: BS U+540C: bBS U+540E: BS U+5411: BSS U+543B: BSB U+5446: BS U+5468: BS U+5471: BT U+5475: BTbb U+547C: BBbS U+548C: BSS U+549D: BS U+54B1: SB U+54B8: BS U+54BD: BS U+54C4: BSS U+5507: BS U+5546: BS U+5556: BSS U+5582: BS U+5591: BS U+55A7: BS U+563B: BS U+566A: BS U+56DE: BSSS U+56F0: BS U+572D: BS U+5730: BS U+5740: BS U+574F: BbSS U+5751: BS U+5807: BSS U+5824: BS U+58D6: SB U+590D: BSSb U+5925: TB U+592B: SB U+592D: BS U+5938: BS U+5976: bbBbS U+5978: BS U+5996: BS U+5999: BSB U+59DC: BS U+59F9: SB U+5A18: BSS U+5A49: SB U+5B81: BSSbSSb U+5B83: BS U+5BB4: BS U+5BB6: SB U+5C38: BS U+5C40: SBS U+5CA9: BSSS U+5CAD: BBS U+5CB3: BS U+5D0E: SBS U+5D4F: BS U+5DE8: BSb U+5E03: SB U+5E18: BS U+5E19: BS U+5E2D: BS U+5E55: BS U+5E72: SSBSSb U+5E76: SSSBBS U+5E78: SB U+5E84: BSS U+5E95: SB U+5EFF: SB U+5F04: BBS U+5F26: BS U+5F69: BS U+5F81: BSS U+5FA1: BS U+5FAD: SB U+5FB5: TTB U+5FCF: BSS U+5FD7: BS U+5FF5: SB U+601C: BS U+604D: SB U+6052: SB U+6064: SBB U+6096: BS U+60E0: BBS U+6108: BSS U+6127: SB U+613F: BS U+6167: BS U+6247: BS U+624D: BS U+624E: bbBbSSS U+6251: BS U+6258: BS U+625B: BS U+6263: BS U+626F: BS U+627C: BS U+6298: BS U+62AC: BS U+62B5: bBbbS U+62D0: BS U+62DA: SB U+633D: BS U+6346: BS U+634D: bBT U+636E: BSS U+63EA: BS U+647A: TB U+64B0: BS U+6548: SBB U+6597: BSSSSS U+65A4: BbS U+65C5: BS U+65CB: BSb U+65D7: SB U+6606: SSB U+6635: BS U+6696: BS U+6697: SBS U+66F2: BBS U+6717: BS U+671B: BS U+672C: TB U+672D: SSbBbbb U+6731: BS U+6734: BS U+6746: BS U+6760: BS U+676F: BSS U+6770: SB U+677E: BS U+677F: BS U+6781: BS U+6784: SSBS U+679C: BS U+67DC: BS U+67F1: BS U+6816: SBS U+6817: SB U+6838: BS U+6840: BS U+6881: BS U+68CB: BBS U+68F0: BS U+68F1: BS U+68F9: bBS U+6994: SB U+699C: BS U+69A8: SB U+69B7: SB U+6A3D: BS U+6A90: BS U+6A97: BS U+6B32: SB U+6BB7: SB U+6BD7: BS U+6C1B: BS U+6C61: SBB U+6C78: BS U+6C88: BbS U+6CBE: BS U+6CC4: BSb U+6CDB: SSB U+6CDE: BS U+6CE0: BS U+6CE8: BS U+6D01: BS U+6D3C: BSS U+6D3D: SB U+6D59: BS U+6D63: BS U+6D69: BS U+6D82: BSB U+6D8C: BS U+6DC0: BS U+6DCB: BbSbb U+6DEB: SB U+6E05: SBB U+6E38: BS U+6EAA: BBS U+6EAF: SBB U+6F13: BS U+6F2B: BS U+6F3E: BS U+6F84: SB U+7095: SB U+70AE: BSS U+70B3: bSB U+710A: BSS U+7130: BBS U+7167: SSB U+71D5: BS U+72F7: BS U+72F8: BS U+732C: BS U+733F: BS U+73C9: bBS U+73F6: BT U+7403: SB U+7405: BS U+7483: SBS U+7487: SBS U+74F6: BBS U+753A: SB U+754E: SB U+75B1: BS U+75C7: BS U+75F1: SB U+75F4: BS U+75F9: SBS U+7682: SB U+768E: BS U+7693: BSBS U+7696: SB U+772F: BS U+7737: BS U+773A: BS U+777F: SB U+77AD: TbB U+77B0: BS U+77E9: TB U+7827: BS U+786C: TB U+7887: SB U+788C: BS U+7897: TBBS U+78B0: SBS U+7947: BS U+79CB: BBS U+79D8: SB U+79FB: BS U+7A11: BS U+7A17: BS U+7A57: BBS U+7B2E: BS U+7B51: BS U+7B52: BS U+7B56: BBS U+7BA1: SB U+7BAC: BS U+7BEA: SB U+7C97: BSBS U+7CC7: BS U+7CCA: BS U+7CCD: BS U+7CDF: BS U+7CFB: SBSS U+7D2F: BS U+7DAE: SB U+7E9B: BS U+7F38: SB U+7F50: BS U+7F6E: SB U+7F8E: SB U+7FA1: BS U+7FFB: SBB U+8000: bSB U+8003: SB U+809B: SB U+80B4: BS U+80C4: SB U+80CC: SB U+80DC: SB U+80E1: BS U+80ED: BS U+80F3: SB U+814A: SBS U+8198: BS U+81BB: SB U+81F4: SB U+820D: SBB U+82B1: BS U+82B8: BS U+82DF: SB U+8303: SB U+8347: BS U+8349: SBS U+8350: BS U+83F0: TbB U+83F1: BS U+8431: BS U+8457: TB U+8499: SSSB U+8511: BS U+854A: SBBB U+85AF: BS U+85C9: TbB U+85DC: SB U+85E4: SB U+85E9: SB U+8616: SB U+866C: BS U+866E: BS U+86B6: BS U+86D4: SSB U+8737: BS U+8776: SB U+8782: SB U+8815: SB U+8822: SB U+8868: BS U+8892: BS U+88F8: SB U+8C37: SB U+8C46: SB U+8D9F: BS U+8DD6: BS U+8E0A: BS U+8E29: SB U+8F9F: BbS U+8FA8: bbBS U+8FE4: SB U+903E: SB U+9041: BS U+90C1: SBSS U+916C: SBBB U+91C7: SB U+91CC: SSB U+91CE: SB U+962A: TB U+9676: SB U+9699: TB U+96C1: BS U+96C7: SB U+96CD: BS U+96D5: bSBS U+9709: BS U+9713: SB U+9762: BSSS U+99A8: BS U+9B03: bSbB U+9B41: SB U+9D02: BS U+9EBB: bSbBB U+9F39: SB U+9F96: BS Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Thu, 30 Apr 2015 23:44:32 +0800 王伟 <wangwei@cnic.cn> wrote:
Dear All
CGP updates the code points and variants in CGP-MSS, which will be used as CGP LGR1 to coordinate with J and K.
Please find the attached XML file generated by Mr. QI Chao. Also, we provide a readable EXCEL version for your review.
Please feel free to give your comments
Best Regards Wang Wei
-----邮件原件----- 发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2015年4月27日 10:15 收件人: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' 主题: 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear ALL
For CGP, ToDo-6 has been done.
ToDo-7 will be sent out after double check this week.
-----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 HiroHOTTA 发送时间: 2015年4月26日 1:05 收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 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
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Dear Yoneya San Thanks for your work. It seems we already have a unanimous agreement on the repertoire so far. For your first question, yes, we would like to see J-LGR-2. Please send it to us when you ready. For the conflicts you mentioned, from CDNC's perspective, we don��t treat them as conflicts. Let's take 4E10ؤfor example, CGP will follow CDNC's variant setting and rule, it goes like the follows: �D, ؤ(S), �D(T) ؤ, ؤ(B), �D(b) Which means, the preferred simplified code points and traditional code points would be different, the variant corresponding actions are asymmetric, considering the actual language environment usage difference. In this case, because J-LGR-1 has 4E10 too (but has no 4E0F), so I assume JGP variant action would follow CGP's action be like ؤ, ؤ(B), �D(b) I am not sure if the above case will work for JGP. As you listed in the last mail, CGP has many code points as above, including the most important��-�l-�kand��/ �. Looking forward to your reply. Regards Wang Wei -----�ʼ�ԭ��----- ������: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] ����ʱ��: 2015��5��1�� 21:03 �ռ���: wangwei@cnic.cn ����: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org ����: Re: [Japanesegp] ��: [ChineseGP] Proposed Action items before Seoul meeting Dear Wang Wei san and all, Thank you for CGP's effort. I checked mss-var-20150430.xml from two viewpoints below: (1) Whether Yoneya's algorithm work fine with C and J LGR-1 (2) Whether C-LGR-1 has conflicts of disposition type For (1), it seemed working fine. - There was no difference between C-LGR-1 and generated C-LGR-2 (This is because J-LGR-1 has no variant) - Variants in generated J-LGR-2 were the same with C and J LGR-M (please let me know if you want to see J-LGR-2) For (2), I found hundreds of conflicts listed below. Here, each mark means the disposition type as: - S: simp - T: trad - B: both - b: blocked CP disposition types U+4E10: SB U+4E11: BS U+4E18: BS U+4E30: BbS U+4E43: BSS U+4E48: BTSS U+4E7E: BTTbbS U+4E86: BSS U+4E91: BS U+4E95: SB U+4EC6: BS U+4EC7: BSbb U+4ED9: BSS U+4EF2: BS U+4EFF: BSbS U+4F0A: BS U+4F19: BS U+4F59: BSb U+4F5B: BBSS U+4F60: TBbbb U+4F63: BS U+4F69: BS U+4F84: BS U+4FDD: BS U+4FDE: BBS U+4FEF: SBS U+500F: BS U+501F: BSS U+5026: BbS U+506C: BS U+5077: BBS U+508D: BS U+50ED: SB U+50F5: BS U+5149: BS U+514B: BSS U+518F: BS U+51A2: BS U+51AC: BS U+51B1: BS U+51C6: BSS U+51CC: BS U+51E0: BS U+51F6: SB U+51FA: BS U+5212: BS U+5228: BS U+522E: BS U+5236: BS U+5238: bBT U+5243: BS U+5269: BBS U+526F: BS U+527D: BS U+527F: BS U+52D6: BS U+52E4: BS U+5343: bBS U+5347: BSS U+535C: BbS U+5360: SB U+5377: BBS U+5382: BS U+5384: BS U+5398: BS U+53CD: BS U+53EA: BSS U+53F0: BSSS U+5401: BS U+5403: BS U+5408: BS U+540A: BS U+540C: bBS U+540E: BS U+5411: BSS U+543B: BSB U+5446: BS U+5468: BS U+5471: BT U+5475: BTbb U+547C: BBbS U+548C: BSS U+549D: BS U+54B1: SB U+54B8: BS U+54BD: BS U+54C4: BSS U+5507: BS U+5546: BS U+5556: BSS U+5582: BS U+5591: BS U+55A7: BS U+563B: BS U+566A: BS U+56DE: BSSS U+56F0: BS U+572D: BS U+5730: BS U+5740: BS U+574F: BbSS U+5751: BS U+5807: BSS U+5824: BS U+58D6: SB U+590D: BSSb U+5925: TB U+592B: SB U+592D: BS U+5938: BS U+5976: bbBbS U+5978: BS U+5996: BS U+5999: BSB U+59DC: BS U+59F9: SB U+5A18: BSS U+5A49: SB U+5B81: BSSbSSb U+5B83: BS U+5BB4: BS U+5BB6: SB U+5C38: BS U+5C40: SBS U+5CA9: BSSS U+5CAD: BBS U+5CB3: BS U+5D0E: SBS U+5D4F: BS U+5DE8: BSb U+5E03: SB U+5E18: BS U+5E19: BS U+5E2D: BS U+5E55: BS U+5E72: SSBSSb U+5E76: SSSBBS U+5E78: SB U+5E84: BSS U+5E95: SB U+5EFF: SB U+5F04: BBS U+5F26: BS U+5F69: BS U+5F81: BSS U+5FA1: BS U+5FAD: SB U+5FB5: TTB U+5FCF: BSS U+5FD7: BS U+5FF5: SB U+601C: BS U+604D: SB U+6052: SB U+6064: SBB U+6096: BS U+60E0: BBS U+6108: BSS U+6127: SB U+613F: BS U+6167: BS U+6247: BS U+624D: BS U+624E: bbBbSSS U+6251: BS U+6258: BS U+625B: BS U+6263: BS U+626F: BS U+627C: BS U+6298: BS U+62AC: BS U+62B5: bBbbS U+62D0: BS U+62DA: SB U+633D: BS U+6346: BS U+634D: bBT U+636E: BSS U+63EA: BS U+647A: TB U+64B0: BS U+6548: SBB U+6597: BSSSSS U+65A4: BbS U+65C5: BS U+65CB: BSb U+65D7: SB U+6606: SSB U+6635: BS U+6696: BS U+6697: SBS U+66F2: BBS U+6717: BS U+671B: BS U+672C: TB U+672D: SSbBbbb U+6731: BS U+6734: BS U+6746: BS U+6760: BS U+676F: BSS U+6770: SB U+677E: BS U+677F: BS U+6781: BS U+6784: SSBS U+679C: BS U+67DC: BS U+67F1: BS U+6816: SBS U+6817: SB U+6838: BS U+6840: BS U+6881: BS U+68CB: BBS U+68F0: BS U+68F1: BS U+68F9: bBS U+6994: SB U+699C: BS U+69A8: SB U+69B7: SB U+6A3D: BS U+6A90: BS U+6A97: BS U+6B32: SB U+6BB7: SB U+6BD7: BS U+6C1B: BS U+6C61: SBB U+6C78: BS U+6C88: BbS U+6CBE: BS U+6CC4: BSb U+6CDB: SSB U+6CDE: BS U+6CE0: BS U+6CE8: BS U+6D01: BS U+6D3C: BSS U+6D3D: SB U+6D59: BS U+6D63: BS U+6D69: BS U+6D82: BSB U+6D8C: BS U+6DC0: BS U+6DCB: BbSbb U+6DEB: SB U+6E05: SBB U+6E38: BS U+6EAA: BBS U+6EAF: SBB U+6F13: BS U+6F2B: BS U+6F3E: BS U+6F84: SB U+7095: SB U+70AE: BSS U+70B3: bSB U+710A: BSS U+7130: BBS U+7167: SSB U+71D5: BS U+72F7: BS U+72F8: BS U+732C: BS U+733F: BS U+73C9: bBS U+73F6: BT U+7403: SB U+7405: BS U+7483: SBS U+7487: SBS U+74F6: BBS U+753A: SB U+754E: SB U+75B1: BS U+75C7: BS U+75F1: SB U+75F4: BS U+75F9: SBS U+7682: SB U+768E: BS U+7693: BSBS U+7696: SB U+772F: BS U+7737: BS U+773A: BS U+777F: SB U+77AD: TbB U+77B0: BS U+77E9: TB U+7827: BS U+786C: TB U+7887: SB U+788C: BS U+7897: TBBS U+78B0: SBS U+7947: BS U+79CB: BBS U+79D8: SB U+79FB: BS U+7A11: BS U+7A17: BS U+7A57: BBS U+7B2E: BS U+7B51: BS U+7B52: BS U+7B56: BBS U+7BA1: SB U+7BAC: BS U+7BEA: SB U+7C97: BSBS U+7CC7: BS U+7CCA: BS U+7CCD: BS U+7CDF: BS U+7CFB: SBSS U+7D2F: BS U+7DAE: SB U+7E9B: BS U+7F38: SB U+7F50: BS U+7F6E: SB U+7F8E: SB U+7FA1: BS U+7FFB: SBB U+8000: bSB U+8003: SB U+809B: SB U+80B4: BS U+80C4: SB U+80CC: SB U+80DC: SB U+80E1: BS U+80ED: BS U+80F3: SB U+814A: SBS U+8198: BS U+81BB: SB U+81F4: SB U+820D: SBB U+82B1: BS U+82B8: BS U+82DF: SB U+8303: SB U+8347: BS U+8349: SBS U+8350: BS U+83F0: TbB U+83F1: BS U+8431: BS U+8457: TB U+8499: SSSB U+8511: BS U+854A: SBBB U+85AF: BS U+85C9: TbB U+85DC: SB U+85E4: SB U+85E9: SB U+8616: SB U+866C: BS U+866E: BS U+86B6: BS U+86D4: SSB U+8737: BS U+8776: SB U+8782: SB U+8815: SB U+8822: SB U+8868: BS U+8892: BS U+88F8: SB U+8C37: SB U+8C46: SB U+8D9F: BS U+8DD6: BS U+8E0A: BS U+8E29: SB U+8F9F: BbS U+8FA8: bbBS U+8FE4: SB U+903E: SB U+9041: BS U+90C1: SBSS U+916C: SBBB U+91C7: SB U+91CC: SSB U+91CE: SB U+962A: TB U+9676: SB U+9699: TB U+96C1: BS U+96C7: SB U+96CD: BS U+96D5: bSBS U+9709: BS U+9713: SB U+9762: BSSS U+99A8: BS U+9B03: bSbB U+9B41: SB U+9D02: BS U+9EBB: bSbBB U+9F39: SB U+9F96: BS Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Thu, 30 Apr 2015 23:44:32 +0800 ��ΰ <wangwei@cnic.cn> wrote:
Dear All
CGP updates the code points and variants in CGP-MSS, which will be used as CGP LGR1 to coordinate with J and K.
Please find the attached XML file generated by Mr. QI Chao. Also, we provide a readable EXCEL version for your review.
Please feel free to give your comments
Best Regards Wang Wei
-----�ʼ�ԭ��----- ������: ��ΰ [mailto:wangwei@cnic.cn] ����ʱ��: 2015��4��27�� 10:15 �ռ���: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' ����: ��: [ChineseGP] Proposed Action items before Seoul meeting
Dear ALL
For CGP, ToDo-6 has been done.
ToDo-7 will be sent out after double check this week.
-----�ʼ�ԭ��----- ������: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] �� �� HiroHOTTA ����ʱ��: 2015��4��26�� 1:05 �ռ���: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org ����: [ChineseGP] 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
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Sorry for the mistake in the last mail. For JGP, the case should go like: ؤ, ؤ(A), �D(o) regards -----�ʼ�ԭ��----- ������: ��ΰ [mailto:wangwei@cnic.cn] ����ʱ��: 2015��5��5�� 19:02 �ռ���: 'Yoshiro YONEYA' ����: 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' ����: ��: [Japanesegp] ��: [ChineseGP] Proposed Action items before Seoul meeting Dear Yoneya San Thanks for your work. It seems we already have a unanimous agreement on the repertoire so far. For your first question, yes, we would like to see J-LGR-2. Please send it to us when you ready. For the conflicts you mentioned, from CDNC's perspective, we don��t treat them as conflicts. Let's take 4E10ؤfor example, CGP will follow CDNC's variant setting and rule, it goes like the follows: �D, ؤ(S), �D(T) ؤ, ؤ(B), �D(b) Which means, the preferred simplified code points and traditional code points would be different, the variant corresponding actions are asymmetric, considering the actual language environment usage difference. In this case, because J-LGR-1 has 4E10 too (but has no 4E0F), so I assume JGP variant action would follow CGP's action be like ؤ, ؤ(B), �D(b) I am not sure if the above case will work for JGP. As you listed in the last mail, CGP has many code points as above, including the most important��-�l-�kand��/ �. Looking forward to your reply. Regards Wang Wei -----�ʼ�ԭ��----- ������: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] ����ʱ��: 2015��5��1�� 21:03 �ռ���: wangwei@cnic.cn ����: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org ����: Re: [Japanesegp] ��: [ChineseGP] Proposed Action items before Seoul meeting Dear Wang Wei san and all, Thank you for CGP's effort. I checked mss-var-20150430.xml from two viewpoints below: (1) Whether Yoneya's algorithm work fine with C and J LGR-1 (2) Whether C-LGR-1 has conflicts of disposition type For (1), it seemed working fine. - There was no difference between C-LGR-1 and generated C-LGR-2 (This is because J-LGR-1 has no variant) - Variants in generated J-LGR-2 were the same with C and J LGR-M (please let me know if you want to see J-LGR-2) For (2), I found hundreds of conflicts listed below. Here, each mark means the disposition type as: - S: simp - T: trad - B: both - b: blocked CP disposition types U+4E10: SB U+4E11: BS U+4E18: BS U+4E30: BbS U+4E43: BSS U+4E48: BTSS U+4E7E: BTTbbS U+4E86: BSS U+4E91: BS U+4E95: SB U+4EC6: BS U+4EC7: BSbb U+4ED9: BSS U+4EF2: BS U+4EFF: BSbS U+4F0A: BS U+4F19: BS U+4F59: BSb U+4F5B: BBSS U+4F60: TBbbb U+4F63: BS U+4F69: BS U+4F84: BS U+4FDD: BS U+4FDE: BBS U+4FEF: SBS U+500F: BS U+501F: BSS U+5026: BbS U+506C: BS U+5077: BBS U+508D: BS U+50ED: SB U+50F5: BS U+5149: BS U+514B: BSS U+518F: BS U+51A2: BS U+51AC: BS U+51B1: BS U+51C6: BSS U+51CC: BS U+51E0: BS U+51F6: SB U+51FA: BS U+5212: BS U+5228: BS U+522E: BS U+5236: BS U+5238: bBT U+5243: BS U+5269: BBS U+526F: BS U+527D: BS U+527F: BS U+52D6: BS U+52E4: BS U+5343: bBS U+5347: BSS U+535C: BbS U+5360: SB U+5377: BBS U+5382: BS U+5384: BS U+5398: BS U+53CD: BS U+53EA: BSS U+53F0: BSSS U+5401: BS U+5403: BS U+5408: BS U+540A: BS U+540C: bBS U+540E: BS U+5411: BSS U+543B: BSB U+5446: BS U+5468: BS U+5471: BT U+5475: BTbb U+547C: BBbS U+548C: BSS U+549D: BS U+54B1: SB U+54B8: BS U+54BD: BS U+54C4: BSS U+5507: BS U+5546: BS U+5556: BSS U+5582: BS U+5591: BS U+55A7: BS U+563B: BS U+566A: BS U+56DE: BSSS U+56F0: BS U+572D: BS U+5730: BS U+5740: BS U+574F: BbSS U+5751: BS U+5807: BSS U+5824: BS U+58D6: SB U+590D: BSSb U+5925: TB U+592B: SB U+592D: BS U+5938: BS U+5976: bbBbS U+5978: BS U+5996: BS U+5999: BSB U+59DC: BS U+59F9: SB U+5A18: BSS U+5A49: SB U+5B81: BSSbSSb U+5B83: BS U+5BB4: BS U+5BB6: SB U+5C38: BS U+5C40: SBS U+5CA9: BSSS U+5CAD: BBS U+5CB3: BS U+5D0E: SBS U+5D4F: BS U+5DE8: BSb U+5E03: SB U+5E18: BS U+5E19: BS U+5E2D: BS U+5E55: BS U+5E72: SSBSSb U+5E76: SSSBBS U+5E78: SB U+5E84: BSS U+5E95: SB U+5EFF: SB U+5F04: BBS U+5F26: BS U+5F69: BS U+5F81: BSS U+5FA1: BS U+5FAD: SB U+5FB5: TTB U+5FCF: BSS U+5FD7: BS U+5FF5: SB U+601C: BS U+604D: SB U+6052: SB U+6064: SBB U+6096: BS U+60E0: BBS U+6108: BSS U+6127: SB U+613F: BS U+6167: BS U+6247: BS U+624D: BS U+624E: bbBbSSS U+6251: BS U+6258: BS U+625B: BS U+6263: BS U+626F: BS U+627C: BS U+6298: BS U+62AC: BS U+62B5: bBbbS U+62D0: BS U+62DA: SB U+633D: BS U+6346: BS U+634D: bBT U+636E: BSS U+63EA: BS U+647A: TB U+64B0: BS U+6548: SBB U+6597: BSSSSS U+65A4: BbS U+65C5: BS U+65CB: BSb U+65D7: SB U+6606: SSB U+6635: BS U+6696: BS U+6697: SBS U+66F2: BBS U+6717: BS U+671B: BS U+672C: TB U+672D: SSbBbbb U+6731: BS U+6734: BS U+6746: BS U+6760: BS U+676F: BSS U+6770: SB U+677E: BS U+677F: BS U+6781: BS U+6784: SSBS U+679C: BS U+67DC: BS U+67F1: BS U+6816: SBS U+6817: SB U+6838: BS U+6840: BS U+6881: BS U+68CB: BBS U+68F0: BS U+68F1: BS U+68F9: bBS U+6994: SB U+699C: BS U+69A8: SB U+69B7: SB U+6A3D: BS U+6A90: BS U+6A97: BS U+6B32: SB U+6BB7: SB U+6BD7: BS U+6C1B: BS U+6C61: SBB U+6C78: BS U+6C88: BbS U+6CBE: BS U+6CC4: BSb U+6CDB: SSB U+6CDE: BS U+6CE0: BS U+6CE8: BS U+6D01: BS U+6D3C: BSS U+6D3D: SB U+6D59: BS U+6D63: BS U+6D69: BS U+6D82: BSB U+6D8C: BS U+6DC0: BS U+6DCB: BbSbb U+6DEB: SB U+6E05: SBB U+6E38: BS U+6EAA: BBS U+6EAF: SBB U+6F13: BS U+6F2B: BS U+6F3E: BS U+6F84: SB U+7095: SB U+70AE: BSS U+70B3: bSB U+710A: BSS U+7130: BBS U+7167: SSB U+71D5: BS U+72F7: BS U+72F8: BS U+732C: BS U+733F: BS U+73C9: bBS U+73F6: BT U+7403: SB U+7405: BS U+7483: SBS U+7487: SBS U+74F6: BBS U+753A: SB U+754E: SB U+75B1: BS U+75C7: BS U+75F1: SB U+75F4: BS U+75F9: SBS U+7682: SB U+768E: BS U+7693: BSBS U+7696: SB U+772F: BS U+7737: BS U+773A: BS U+777F: SB U+77AD: TbB U+77B0: BS U+77E9: TB U+7827: BS U+786C: TB U+7887: SB U+788C: BS U+7897: TBBS U+78B0: SBS U+7947: BS U+79CB: BBS U+79D8: SB U+79FB: BS U+7A11: BS U+7A17: BS U+7A57: BBS U+7B2E: BS U+7B51: BS U+7B52: BS U+7B56: BBS U+7BA1: SB U+7BAC: BS U+7BEA: SB U+7C97: BSBS U+7CC7: BS U+7CCA: BS U+7CCD: BS U+7CDF: BS U+7CFB: SBSS U+7D2F: BS U+7DAE: SB U+7E9B: BS U+7F38: SB U+7F50: BS U+7F6E: SB U+7F8E: SB U+7FA1: BS U+7FFB: SBB U+8000: bSB U+8003: SB U+809B: SB U+80B4: BS U+80C4: SB U+80CC: SB U+80DC: SB U+80E1: BS U+80ED: BS U+80F3: SB U+814A: SBS U+8198: BS U+81BB: SB U+81F4: SB U+820D: SBB U+82B1: BS U+82B8: BS U+82DF: SB U+8303: SB U+8347: BS U+8349: SBS U+8350: BS U+83F0: TbB U+83F1: BS U+8431: BS U+8457: TB U+8499: SSSB U+8511: BS U+854A: SBBB U+85AF: BS U+85C9: TbB U+85DC: SB U+85E4: SB U+85E9: SB U+8616: SB U+866C: BS U+866E: BS U+86B6: BS U+86D4: SSB U+8737: BS U+8776: SB U+8782: SB U+8815: SB U+8822: SB U+8868: BS U+8892: BS U+88F8: SB U+8C37: SB U+8C46: SB U+8D9F: BS U+8DD6: BS U+8E0A: BS U+8E29: SB U+8F9F: BbS U+8FA8: bbBS U+8FE4: SB U+903E: SB U+9041: BS U+90C1: SBSS U+916C: SBBB U+91C7: SB U+91CC: SSB U+91CE: SB U+962A: TB U+9676: SB U+9699: TB U+96C1: BS U+96C7: SB U+96CD: BS U+96D5: bSBS U+9709: BS U+9713: SB U+9762: BSSS U+99A8: BS U+9B03: bSbB U+9B41: SB U+9D02: BS U+9EBB: bSbBB U+9F39: SB U+9F96: BS Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Thu, 30 Apr 2015 23:44:32 +0800 ��ΰ <wangwei@cnic.cn> wrote:
Dear All
CGP updates the code points and variants in CGP-MSS, which will be used as CGP LGR1 to coordinate with J and K.
Please find the attached XML file generated by Mr. QI Chao. Also, we provide a readable EXCEL version for your review.
Please feel free to give your comments
Best Regards Wang Wei
-----�ʼ�ԭ��----- ������: ��ΰ [mailto:wangwei@cnic.cn] ����ʱ��: 2015��4��27�� 10:15 �ռ���: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' ����: ��: [ChineseGP] Proposed Action items before Seoul meeting
Dear ALL
For CGP, ToDo-6 has been done.
ToDo-7 will be sent out after double check this week.
-----�ʼ�ԭ��----- ������: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] �� �� HiroHOTTA ����ʱ��: 2015��4��26�� 1:05 �ռ���: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org ����: [ChineseGP] 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
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Dear Wang Wei san, Thank you for your answers.
For your first question, yes, we would like to see J-LGR-2. Please send it to us when you ready.
Please find attached J-LGR-2 repertoire. Please note that it is Excel file and is not XML format, because it will be more convenient for most of receipients. And it omits preambles (including language tag) and WLE rules.
For the conflicts you mentioned, from CDNC's perspective, we don’t treat them as conflicts.
Thank you for your explanation. I understood CGP's intention. I still concern about 3 characters which has both T and S disposition types: U+4E48(么) U+4E7E(乾) U+7897(碗) If it is not matter for Chinese, please ignore my concern.
For JGP, the case should go like: 丐, 丐(A), 丏(o)
This case comes to this (see line 195 and 196 of attached file): 丏, 丏(o), 丐(b) 丐, 丏(b), 丐(A) The differences are because the line 195 is generated by step 4, and the line 196 is generated by step 3. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Tue, 5 May 2015 19:18:29 +0800 王伟 <wangwei@cnic.cn> wrote:
Sorry for the mistake in the last mail.
For JGP, the case should go like: 丐, 丐(A), 丏(o)
regards
-----邮件原件----- 发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2015年5月5日 19:02 收件人: 'Yoshiro YONEYA' 抄送: 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' 主题: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear Yoneya San
Thanks for your work. It seems we already have a unanimous agreement on the repertoire so far. For your first question, yes, we would like to see J-LGR-2. Please send it to us when you ready.
For the conflicts you mentioned, from CDNC's perspective, we don’t treat them as conflicts. Let's take 4E10丐for example, CGP will follow CDNC's variant setting and rule, it goes like the follows: 丏, 丐(S), 丏(T) 丐, 丐(B), 丏(b) Which means, the preferred simplified code points and traditional code points would be different, the variant corresponding actions are asymmetric, considering the actual language environment usage difference.
In this case, because J-LGR-1 has 4E10 too (but has no 4E0F), so I assume JGP variant action would follow CGP's action be like 丐, 丐(B), 丏(b)
I am not sure if the above case will work for JGP. As you listed in the last mail, CGP has many code points as above, including the most important发-發-発and发/ 髮.
Looking forward to your reply.
Regards Wang Wei
-----邮件原件----- 发件人: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] 发送时间: 2015年5月1日 21:03 收件人: wangwei@cnic.cn 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: Re: [Japanesegp] 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear Wang Wei san and all,
Thank you for CGP's effort. I checked mss-var-20150430.xml from two viewpoints below:
(1) Whether Yoneya's algorithm work fine with C and J LGR-1 (2) Whether C-LGR-1 has conflicts of disposition type
For (1), it seemed working fine. - There was no difference between C-LGR-1 and generated C-LGR-2 (This is because J-LGR-1 has no variant) - Variants in generated J-LGR-2 were the same with C and J LGR-M
(please let me know if you want to see J-LGR-2)
For (2), I found hundreds of conflicts listed below. Here, each mark means the disposition type as: - S: simp - T: trad - B: both - b: blocked
CP disposition types U+4E10: SB U+4E11: BS U+4E18: BS U+4E30: BbS U+4E43: BSS U+4E48: BTSS U+4E7E: BTTbbS U+4E86: BSS U+4E91: BS U+4E95: SB U+4EC6: BS U+4EC7: BSbb U+4ED9: BSS U+4EF2: BS U+4EFF: BSbS U+4F0A: BS U+4F19: BS U+4F59: BSb U+4F5B: BBSS U+4F60: TBbbb U+4F63: BS U+4F69: BS U+4F84: BS U+4FDD: BS U+4FDE: BBS U+4FEF: SBS U+500F: BS U+501F: BSS U+5026: BbS U+506C: BS U+5077: BBS U+508D: BS U+50ED: SB U+50F5: BS U+5149: BS U+514B: BSS U+518F: BS U+51A2: BS U+51AC: BS U+51B1: BS U+51C6: BSS U+51CC: BS U+51E0: BS U+51F6: SB U+51FA: BS U+5212: BS U+5228: BS U+522E: BS U+5236: BS U+5238: bBT U+5243: BS U+5269: BBS U+526F: BS U+527D: BS U+527F: BS U+52D6: BS U+52E4: BS U+5343: bBS U+5347: BSS U+535C: BbS U+5360: SB U+5377: BBS U+5382: BS U+5384: BS U+5398: BS U+53CD: BS U+53EA: BSS U+53F0: BSSS U+5401: BS U+5403: BS U+5408: BS U+540A: BS U+540C: bBS U+540E: BS U+5411: BSS U+543B: BSB U+5446: BS U+5468: BS U+5471: BT U+5475: BTbb U+547C: BBbS U+548C: BSS U+549D: BS U+54B1: SB U+54B8: BS U+54BD: BS U+54C4: BSS U+5507: BS U+5546: BS U+5556: BSS U+5582: BS U+5591: BS U+55A7: BS U+563B: BS U+566A: BS U+56DE: BSSS U+56F0: BS U+572D: BS U+5730: BS U+5740: BS U+574F: BbSS U+5751: BS U+5807: BSS U+5824: BS U+58D6: SB U+590D: BSSb U+5925: TB U+592B: SB U+592D: BS U+5938: BS U+5976: bbBbS U+5978: BS U+5996: BS U+5999: BSB U+59DC: BS U+59F9: SB U+5A18: BSS U+5A49: SB U+5B81: BSSbSSb U+5B83: BS U+5BB4: BS U+5BB6: SB U+5C38: BS U+5C40: SBS U+5CA9: BSSS U+5CAD: BBS U+5CB3: BS U+5D0E: SBS U+5D4F: BS U+5DE8: BSb U+5E03: SB U+5E18: BS U+5E19: BS U+5E2D: BS U+5E55: BS U+5E72: SSBSSb U+5E76: SSSBBS U+5E78: SB U+5E84: BSS U+5E95: SB U+5EFF: SB U+5F04: BBS U+5F26: BS U+5F69: BS U+5F81: BSS U+5FA1: BS U+5FAD: SB U+5FB5: TTB U+5FCF: BSS U+5FD7: BS U+5FF5: SB U+601C: BS U+604D: SB U+6052: SB U+6064: SBB U+6096: BS U+60E0: BBS U+6108: BSS U+6127: SB U+613F: BS U+6167: BS U+6247: BS U+624D: BS U+624E: bbBbSSS U+6251: BS U+6258: BS U+625B: BS U+6263: BS U+626F: BS U+627C: BS U+6298: BS U+62AC: BS U+62B5: bBbbS U+62D0: BS U+62DA: SB U+633D: BS U+6346: BS U+634D: bBT U+636E: BSS U+63EA: BS U+647A: TB U+64B0: BS U+6548: SBB U+6597: BSSSSS U+65A4: BbS U+65C5: BS U+65CB: BSb U+65D7: SB U+6606: SSB U+6635: BS U+6696: BS U+6697: SBS U+66F2: BBS U+6717: BS U+671B: BS U+672C: TB U+672D: SSbBbbb U+6731: BS U+6734: BS U+6746: BS U+6760: BS U+676F: BSS U+6770: SB U+677E: BS U+677F: BS U+6781: BS U+6784: SSBS U+679C: BS U+67DC: BS U+67F1: BS U+6816: SBS U+6817: SB U+6838: BS U+6840: BS U+6881: BS U+68CB: BBS U+68F0: BS U+68F1: BS U+68F9: bBS U+6994: SB U+699C: BS U+69A8: SB U+69B7: SB U+6A3D: BS U+6A90: BS U+6A97: BS U+6B32: SB U+6BB7: SB U+6BD7: BS U+6C1B: BS U+6C61: SBB U+6C78: BS U+6C88: BbS U+6CBE: BS U+6CC4: BSb U+6CDB: SSB U+6CDE: BS U+6CE0: BS U+6CE8: BS U+6D01: BS U+6D3C: BSS U+6D3D: SB U+6D59: BS U+6D63: BS U+6D69: BS U+6D82: BSB U+6D8C: BS U+6DC0: BS U+6DCB: BbSbb U+6DEB: SB U+6E05: SBB U+6E38: BS U+6EAA: BBS U+6EAF: SBB U+6F13: BS U+6F2B: BS U+6F3E: BS U+6F84: SB U+7095: SB U+70AE: BSS U+70B3: bSB U+710A: BSS U+7130: BBS U+7167: SSB U+71D5: BS U+72F7: BS U+72F8: BS U+732C: BS U+733F: BS U+73C9: bBS U+73F6: BT U+7403: SB U+7405: BS U+7483: SBS U+7487: SBS U+74F6: BBS U+753A: SB U+754E: SB U+75B1: BS U+75C7: BS U+75F1: SB U+75F4: BS U+75F9: SBS U+7682: SB U+768E: BS U+7693: BSBS U+7696: SB U+772F: BS U+7737: BS U+773A: BS U+777F: SB U+77AD: TbB U+77B0: BS U+77E9: TB U+7827: BS U+786C: TB U+7887: SB U+788C: BS U+7897: TBBS U+78B0: SBS U+7947: BS U+79CB: BBS U+79D8: SB U+79FB: BS U+7A11: BS U+7A17: BS U+7A57: BBS U+7B2E: BS U+7B51: BS U+7B52: BS U+7B56: BBS U+7BA1: SB U+7BAC: BS U+7BEA: SB U+7C97: BSBS U+7CC7: BS U+7CCA: BS U+7CCD: BS U+7CDF: BS U+7CFB: SBSS U+7D2F: BS U+7DAE: SB U+7E9B: BS U+7F38: SB U+7F50: BS U+7F6E: SB U+7F8E: SB U+7FA1: BS U+7FFB: SBB U+8000: bSB U+8003: SB U+809B: SB U+80B4: BS U+80C4: SB U+80CC: SB U+80DC: SB U+80E1: BS U+80ED: BS U+80F3: SB U+814A: SBS U+8198: BS U+81BB: SB U+81F4: SB U+820D: SBB U+82B1: BS U+82B8: BS U+82DF: SB U+8303: SB U+8347: BS U+8349: SBS U+8350: BS U+83F0: TbB U+83F1: BS U+8431: BS U+8457: TB U+8499: SSSB U+8511: BS U+854A: SBBB U+85AF: BS U+85C9: TbB U+85DC: SB U+85E4: SB U+85E9: SB U+8616: SB U+866C: BS U+866E: BS U+86B6: BS U+86D4: SSB U+8737: BS U+8776: SB U+8782: SB U+8815: SB U+8822: SB U+8868: BS U+8892: BS U+88F8: SB U+8C37: SB U+8C46: SB U+8D9F: BS U+8DD6: BS U+8E0A: BS U+8E29: SB U+8F9F: BbS U+8FA8: bbBS U+8FE4: SB U+903E: SB U+9041: BS U+90C1: SBSS U+916C: SBBB U+91C7: SB U+91CC: SSB U+91CE: SB U+962A: TB U+9676: SB U+9699: TB U+96C1: BS U+96C7: SB U+96CD: BS U+96D5: bSBS U+9709: BS U+9713: SB U+9762: BSSS U+99A8: BS U+9B03: bSbB U+9B41: SB U+9D02: BS U+9EBB: bSbBB U+9F39: SB U+9F96: BS
Regards,
-- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
On Thu, 30 Apr 2015 23:44:32 +0800 王伟 <wangwei@cnic.cn> wrote:
Dear All
CGP updates the code points and variants in CGP-MSS, which will be used as CGP LGR1 to coordinate with J and K.
Please find the attached XML file generated by Mr. QI Chao. Also, we provide a readable EXCEL version for your review.
Please feel free to give your comments
Best Regards Wang Wei
-----邮件原件----- 发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2015年4月27日 10:15 收件人: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' 主题: 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear ALL
For CGP, ToDo-6 has been done.
ToDo-7 will be sent out after double check this week.
-----邮件原件----- 发件人: chinesegp-bounces@icann.org [mailto:chinesegp-bounces@icann.org] 代 表 HiroHOTTA 发送时间: 2015年4月26日 1:05 收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: [ChineseGP] 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
_______________________________________________ ChineseGP mailing list ChineseGP@icann.org https://mm.icann.org/mailman/listinfo/chinesegp
Dear Yoneya San The three characters you mentioned in CGP-LGR go like: Code Character S T Blocked 4E48 么 么(4E48) 么(4E48)麼(9EBC) 幺(5E7A)麽(9EBD) 9EBC 麼 么(4E48) 麼(9EBC) 幺(5E7A)麽(9EBD) 9EBD 麽 麽(9EBD)么(4E48) 麼(9EBC) 幺(5E7A) 5E7A 幺 幺(5E7A) 么(4E48) 麼(9EBC)麽(9EBD) 4E81 亁 干(5E72) 乾(4E7E) 幹(5E79)榦(69A6)漧(6F27) 5E79 幹 干(5E72) 幹(5E79) 乾(4E7E)亁(4E81)榦(69A6)漧(6F27) registr 4E7E 乾 乾(4E7E)干(5E72) 乾(4E7E) 亁(4E81)幹(5E79)榦(69A6)漧(6F27) 5E72 干 干(5E72) 干(5E72)乾(4E7E)幹(5E79) 亁(4E81)榦(69A6)漧(6F27) 69A6 榦 干(5E72) 榦(69A6) 乾(4E7E)亁(4E81)幹(5E79)漧(6F27) 6F27 漧 乾(4E7E) 漧(6F27) 亁(4E81)干(5E72)幹(5E79)榦(69A6) 6900 椀 椀(6900) 碗(7897) 盌(76CC)鋺(92FA) 7897 碗 碗(7897) 碗(7897) 椀(6900)盌(76CC)鋺(92FA) 92FA 鋺 碗(7897) 鋺(92FA) 椀(6900)盌(76CC) 76CC 盌 碗(7897) 碗(7897) 椀(6900)鋺(92FA) The above disposition is the compromise result between simplified area and traditional area ( just like a coordination between Simplified GP and Traditional GP) For example, 5E72 干 干(5E72) 干(5E72)乾(4E7E)幹(5E79) 亁(4E81)榦(69A6)漧(6F27) for code point 5E72, China mainland will use 5E72 as simplified preferred character, however, 5E72, 4E7E and 5E79 could all possible traditional code points to 5E72. it is hard for Taiwan to predict which one is the actual code points a specific registrant really want, so they keep all three code points “ALLOCATABLE”, “BLOCK” the others three (4E81, 69A6, 6F27) so for your question, U+4E48(么), U+4E7E(乾), U+7897(碗) have both T and S disposition, is not matter for Chinese. Anyway, I noticed JGP’s disposition for 丏(o) and丐(b) “丐, 丏(b), 丐(A)” is generated in Step3 and “丏, 丏(o), 丐(b)” is generated in Step 4 I am a little worried about the meaning of “丏, 丏(o), 丐(b)” Does that mean even “丏” is an out-of-repertoire-variant for J-TAG, not existing n Japanese script, applicants are still able to apply for a label like丏丏with J-TAG. The disposition will go like “丏丏” get out-variant-blocked and “丐丐” label get also blocked at the same time. In this case, applicant get nothing, but in the root database, 丏丏 and 丐丐 are both blocked. ( this is nonsense ) A more rational action should go like, the application for 丏丏with J-TAG be rejected, with a warning “not a Japanese character” Then applicant could try to apply丏丏 with C-TAG again. If we want to do this, some changes are needed in Step3 and Step4. What’s your opinion to the above case? Regards Wang Wei -----邮件原件----- 发件人: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] 发送时间: 2015年5月7日 19:16 收件人: 王伟 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: Re: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before Seoul meeting Dear Wang Wei san, Thank you for your answers.
For your first question, yes, we would like to see J-LGR-2. Please
send it to us when you ready.
Please find attached J-LGR-2 repertoire. Please note that it is Excel file and is not XML format, because it will be more convenient for most of receipients. And it omits preambles (including language tag) and WLE rules.
For the conflicts you mentioned, from CDNC's perspective, we don’t
treat them as conflicts.
Thank you for your explanation. I understood CGP's intention. I still concern about 3 characters which has both T and S disposition types: U+4E48(么) U+4E7E(乾) U+7897(碗) If it is not matter for Chinese, please ignore my concern.
For JGP, the case should go like:
丐, 丐(A), 丏(o)
This case comes to this (see line 195 and 196 of attached file): 丏, 丏(o), 丐(b) 丐, 丏(b), 丐(A) The differences are because the line 195 is generated by step 4, and the line 196 is generated by step 3. Regards, -- Yoshiro YONEYA < <mailto:yoshiro.yoneya@jprs.co.jp> yoshiro.yoneya@jprs.co.jp> On Tue, 5 May 2015 19:18:29 +0800 王伟 < <mailto:wangwei@cnic.cn> wangwei@cnic.cn> wrote:
Sorry for the mistake in the last mail.
For JGP, the case should go like:
丐, 丐(A), 丏(o)
regards
-----邮件原件-----
发件人: 王伟 [mailto:wangwei@cnic.cn]
发送时间: 2015年5月5日 19:02
收件人: 'Yoshiro YONEYA'
抄送: 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org'
主题: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before
Seoul meeting
Dear Yoneya San
Thanks for your work.
It seems we already have a unanimous agreement on the repertoire so
far.
For your first question, yes, we would like to see J-LGR-2. Please
send it to us when you ready.
For the conflicts you mentioned, from CDNC's perspective, we don’t
treat them as conflicts.
Let's take 4E10丐for example, CGP will follow CDNC's variant setting
and rule, it goes like the follows:
丏, 丐(S), 丏(T)
丐, 丐(B), 丏(b)
Which means, the preferred simplified code points and traditional
code points would be different, the variant corresponding actions are
asymmetric, considering the actual language environment usage difference.
In this case, because J-LGR-1 has 4E10 too (but has no 4E0F), so I
assume JGP variant action would follow CGP's action be like
丐, 丐(B), 丏(b)
I am not sure if the above case will work for JGP.
As you listed in the last mail, CGP has many code points as above,
including the most important发-發-発and发/ 髮.
Looking forward to your reply.
Regards
Wang Wei
-----邮件原件-----
发件人: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp]
发送时间: 2015年5月1日 21:03
收件人: wangwei@cnic.cn
抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org
主题: Re: [Japanesegp] 答复: [ChineseGP] Proposed Action items before
Seoul meeting
Dear Wang Wei san and all,
Thank you for CGP's effort. I checked mss-var-20150430.xml from two
viewpoints below:
(1) Whether Yoneya's algorithm work fine with C and J LGR-1
(2) Whether C-LGR-1 has conflicts of disposition type
For (1), it seemed working fine.
- There was no difference between C-LGR-1 and generated C-LGR-2
(This is because J-LGR-1 has no variant)
- Variants in generated J-LGR-2 were the same with C and J LGR-M
(please let me know if you want to see J-LGR-2)
For (2), I found hundreds of conflicts listed below.
Here, each mark means the disposition type as:
- S: simp
- T: trad
- B: both
- b: blocked
CP disposition types
U+4E10: SB
U+4E11: BS
U+4E18: BS
U+4E30: BbS
U+4E43: BSS
U+4E48: BTSS
U+4E7E: BTTbbS
U+4E86: BSS
U+4E91: BS
U+4E95: SB
U+4EC6: BS
U+4EC7: BSbb
U+4ED9: BSS
U+4EF2: BS
U+4EFF: BSbS
U+4F0A: BS
U+4F19: BS
U+4F59: BSb
U+4F5B: BBSS
U+4F60: TBbbb
U+4F63: BS
U+4F69: BS
U+4F84: BS
U+4FDD: BS
U+4FDE: BBS
U+4FEF: SBS
U+500F: BS
U+501F: BSS
U+5026: BbS
U+506C: BS
U+5077: BBS
U+508D: BS
U+50ED: SB
U+50F5: BS
U+5149: BS
U+514B: BSS
U+518F: BS
U+51A2: BS
U+51AC: BS
U+51B1: BS
U+51C6: BSS
U+51CC: BS
U+51E0: BS
U+51F6: SB
U+51FA: BS
U+5212: BS
U+5228: BS
U+522E: BS
U+5236: BS
U+5238: bBT
U+5243: BS
U+5269: BBS
U+526F: BS
U+527D: BS
U+527F: BS
U+52D6: BS
U+52E4: BS
U+5343: bBS
U+5347: BSS
U+535C: BbS
U+5360: SB
U+5377: BBS
U+5382: BS
U+5384: BS
U+5398: BS
U+53CD: BS
U+53EA: BSS
U+53F0: BSSS
U+5401: BS
U+5403: BS
U+5408: BS
U+540A: BS
U+540C: bBS
U+540E: BS
U+5411: BSS
U+543B: BSB
U+5446: BS
U+5468: BS
U+5471: BT
U+5475: BTbb
U+547C: BBbS
U+548C: BSS
U+549D: BS
U+54B1: SB
U+54B8: BS
U+54BD: BS
U+54C4: BSS
U+5507: BS
U+5546: BS
U+5556: BSS
U+5582: BS
U+5591: BS
U+55A7: BS
U+563B: BS
U+566A: BS
U+56DE: BSSS
U+56F0: BS
U+572D: BS
U+5730: BS
U+5740: BS
U+574F: BbSS
U+5751: BS
U+5807: BSS
U+5824: BS
U+58D6: SB
U+590D: BSSb
U+5925: TB
U+592B: SB
U+592D: BS
U+5938: BS
U+5976: bbBbS
U+5978: BS
U+5996: BS
U+5999: BSB
U+59DC: BS
U+59F9: SB
U+5A18: BSS
U+5A49: SB
U+5B81: BSSbSSb
U+5B83: BS
U+5BB4: BS
U+5BB6: SB
U+5C38: BS
U+5C40: SBS
U+5CA9: BSSS
U+5CAD: BBS
U+5CB3: BS
U+5D0E: SBS
U+5D4F: BS
U+5DE8: BSb
U+5E03: SB
U+5E18: BS
U+5E19: BS
U+5E2D: BS
U+5E55: BS
U+5E72: SSBSSb
U+5E76: SSSBBS
U+5E78: SB
U+5E84: BSS
U+5E95: SB
U+5EFF: SB
U+5F04: BBS
U+5F26: BS
U+5F69: BS
U+5F81: BSS
U+5FA1: BS
U+5FAD: SB
U+5FB5: TTB
U+5FCF: BSS
U+5FD7: BS
U+5FF5: SB
U+601C: BS
U+604D: SB
U+6052: SB
U+6064: SBB
U+6096: BS
U+60E0: BBS
U+6108: BSS
U+6127: SB
U+613F: BS
U+6167: BS
U+6247: BS
U+624D: BS
U+624E: bbBbSSS
U+6251: BS
U+6258: BS
U+625B: BS
U+6263: BS
U+626F: BS
U+627C: BS
U+6298: BS
U+62AC: BS
U+62B5: bBbbS
U+62D0: BS
U+62DA: SB
U+633D: BS
U+6346: BS
U+634D: bBT
U+636E: BSS
U+63EA: BS
U+647A: TB
U+64B0: BS
U+6548: SBB
U+6597: BSSSSS
U+65A4: BbS
U+65C5: BS
U+65CB: BSb
U+65D7: SB
U+6606: SSB
U+6635: BS
U+6696: BS
U+6697: SBS
U+66F2: BBS
U+6717: BS
U+671B: BS
U+672C: TB
U+672D: SSbBbbb
U+6731: BS
U+6734: BS
U+6746: BS
U+6760: BS
U+676F: BSS
U+6770: SB
U+677E: BS
U+677F: BS
U+6781: BS
U+6784: SSBS
U+679C: BS
U+67DC: BS
U+67F1: BS
U+6816: SBS
U+6817: SB
U+6838: BS
U+6840: BS
U+6881: BS
U+68CB: BBS
U+68F0: BS
U+68F1: BS
U+68F9: bBS
U+6994: SB
U+699C: BS
U+69A8: SB
U+69B7: SB
U+6A3D: BS
U+6A90: BS
U+6A97: BS
U+6B32: SB
U+6BB7: SB
U+6BD7: BS
U+6C1B: BS
U+6C61: SBB
U+6C78: BS
U+6C88: BbS
U+6CBE: BS
U+6CC4: BSb
U+6CDB: SSB
U+6CDE: BS
U+6CE0: BS
U+6CE8: BS
U+6D01: BS
U+6D3C: BSS
U+6D3D: SB
U+6D59: BS
U+6D63: BS
U+6D69: BS
U+6D82: BSB
U+6D8C: BS
U+6DC0: BS
U+6DCB: BbSbb
U+6DEB: SB
U+6E05: SBB
U+6E38: BS
U+6EAA: BBS
U+6EAF: SBB
U+6F13: BS
U+6F2B: BS
U+6F3E: BS
U+6F84: SB
U+7095: SB
U+70AE: BSS
U+70B3: bSB
U+710A: BSS
U+7130: BBS
U+7167: SSB
U+71D5: BS
U+72F7: BS
U+72F8: BS
U+732C: BS
U+733F: BS
U+73C9: bBS
U+73F6: BT
U+7403: SB
U+7405: BS
U+7483: SBS
U+7487: SBS
U+74F6: BBS
U+753A: SB
U+754E: SB
U+75B1: BS
U+75C7: BS
U+75F1: SB
U+75F4: BS
U+75F9: SBS
U+7682: SB
U+768E: BS
U+7693: BSBS
U+7696: SB
U+772F: BS
U+7737: BS
U+773A: BS
U+777F: SB
U+77AD: TbB
U+77B0: BS
U+77E9: TB
U+7827: BS
U+786C: TB
U+7887: SB
U+788C: BS
U+7897: TBBS
U+78B0: SBS
U+7947: BS
U+79CB: BBS
U+79D8: SB
U+79FB: BS
U+7A11: BS
U+7A17: BS
U+7A57: BBS
U+7B2E: BS
U+7B51: BS
U+7B52: BS
U+7B56: BBS
U+7BA1: SB
U+7BAC: BS
U+7BEA: SB
U+7C97: BSBS
U+7CC7: BS
U+7CCA: BS
U+7CCD: BS
U+7CDF: BS
U+7CFB: SBSS
U+7D2F: BS
U+7DAE: SB
U+7E9B: BS
U+7F38: SB
U+7F50: BS
U+7F6E: SB
U+7F8E: SB
U+7FA1: BS
U+7FFB: SBB
U+8000: bSB
U+8003: SB
U+809B: SB
U+80B4: BS
U+80C4: SB
U+80CC: SB
U+80DC: SB
U+80E1: BS
U+80ED: BS
U+80F3: SB
U+814A: SBS
U+8198: BS
U+81BB: SB
U+81F4: SB
U+820D: SBB
U+82B1: BS
U+82B8: BS
U+82DF: SB
U+8303: SB
U+8347: BS
U+8349: SBS
U+8350: BS
U+83F0: TbB
U+83F1: BS
U+8431: BS
U+8457: TB
U+8499: SSSB
U+8511: BS
U+854A: SBBB
U+85AF: BS
U+85C9: TbB
U+85DC: SB
U+85E4: SB
U+85E9: SB
U+8616: SB
U+866C: BS
U+866E: BS
U+86B6: BS
U+86D4: SSB
U+8737: BS
U+8776: SB
U+8782: SB
U+8815: SB
U+8822: SB
U+8868: BS
U+8892: BS
U+88F8: SB
U+8C37: SB
U+8C46: SB
U+8D9F: BS
U+8DD6: BS
U+8E0A: BS
U+8E29: SB
U+8F9F: BbS
U+8FA8: bbBS
U+8FE4: SB
U+903E: SB
U+9041: BS
U+90C1: SBSS
U+916C: SBBB
U+91C7: SB
U+91CC: SSB
U+91CE: SB
U+962A: TB
U+9676: SB
U+9699: TB
U+96C1: BS
U+96C7: SB
U+96CD: BS
U+96D5: bSBS
U+9709: BS
U+9713: SB
U+9762: BSSS
U+99A8: BS
U+9B03: bSbB
U+9B41: SB
U+9D02: BS
U+9EBB: bSbBB
U+9F39: SB
U+9F96: BS
Regards,
--
Yoshiro YONEYA < <mailto:yoshiro.yoneya@jprs.co.jp> yoshiro.yoneya@jprs.co.jp>
On Thu, 30 Apr 2015 23:44:32 +0800 王伟 < <mailto:wangwei@cnic.cn> wangwei@cnic.cn> wrote:
Dear All
CGP updates the code points and variants in CGP-MSS, which will be
used as CGP LGR1 to coordinate with J and K.
Please find the attached XML file generated by Mr. QI Chao.
Also, we provide a readable EXCEL version for your review.
Please feel free to give your comments
Best Regards
Wang Wei
-----邮件原件-----
发件人: 王伟 [mailto:wangwei@cnic.cn]
发送时间: 2015年4月27日 10:15
收件人: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org';
'ChineseGP@icann.org'; 'JapaneseGP@icann.org'
主题: 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear ALL
For CGP, ToDo-6 has been done.
ToDo-7 will be sent out after double check this week.
-----邮件原件-----
发件人: chinesegp-bounces@icann.org
[mailto:chinesegp-bounces@icann.org]
代
表 HiroHOTTA
发送时间: 2015年4月26日 1:05
收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org
主题: [ChineseGP] 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
_______________________________________________
ChineseGP mailing list
<mailto:ChineseGP@icann.org> ChineseGP@icann.org
<https://mm.icann.org/mailman/listinfo/chinesegp> https://mm.icann.org/mailman/listinfo/chinesegp
To continue the my assumption about “丏丏” with J-TAG. If IP have a higher-level disposition rule, when founding all label combination failed (blocked or out-of-repertoire-blocked), and the application will be cancelled. Which means, nothing happens, then the applicant could try丏丏 with C-TAG or K-TAG. Thus, Yoneya’s algorithm works perfect, nothing needs to change. : ) 发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2015年5月8日 15:38 收件人: 'Yoshiro YONEYA' 抄送: 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' 主题: 答复: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before Seoul meeting Dear Yoneya San The three characters you mentioned in CGP-LGR go like: Code Character S T Blocked 4E48 么 么(4E48) 么(4E48)麼(9EBC) 幺(5E7A)麽(9EBD) 9EBC 麼 么(4E48) 麼(9EBC) 幺(5E7A)麽(9EBD) 9EBD 麽 麽(9EBD)么(4E48) 麼(9EBC) 幺(5E7A) 5E7A 幺 幺(5E7A) 么(4E48) 麼(9EBC)麽(9EBD) 4E81 亁 干(5E72) 乾(4E7E) 幹(5E79)榦(69A6)漧(6F27) 5E79 幹 干(5E72) 幹(5E79) 乾(4E7E)亁(4E81)榦(69A6)漧(6F27) registr 4E7E 乾 乾(4E7E)干(5E72) 乾(4E7E) 亁(4E81)幹(5E79)榦(69A6)漧(6F27) 5E72 干 干(5E72) 干(5E72)乾(4E7E)幹(5E79) 亁(4E81)榦(69A6)漧(6F27) 69A6 榦 干(5E72) 榦(69A6) 乾(4E7E)亁(4E81)幹(5E79)漧(6F27) 6F27 漧 乾(4E7E) 漧(6F27) 亁(4E81)干(5E72)幹(5E79)榦(69A6) 6900 椀 椀(6900) 碗(7897) 盌(76CC)鋺(92FA) 7897 碗 碗(7897) 碗(7897) 椀(6900)盌(76CC)鋺(92FA) 92FA 鋺 碗(7897) 鋺(92FA) 椀(6900)盌(76CC) 76CC 盌 碗(7897) 碗(7897) 椀(6900)鋺(92FA) The above disposition is the compromise result between simplified area and traditional area ( just like a coordination between Simplified GP and Traditional GP) For example, 5E72 干 干(5E72) 干(5E72)乾(4E7E)幹(5E79) 亁(4E81)榦(69A6)漧(6F27) for code point 5E72, China mainland will use 5E72 as simplified preferred character, however, 5E72, 4E7E and 5E79 could all possible traditional code points to 5E72. it is hard for Taiwan to predict which one is the actual code points a specific registrant really want, so they keep all three code points “ALLOCATABLE”, “BLOCK” the others three (4E81, 69A6, 6F27) so for your question, U+4E48(么), U+4E7E(乾), U+7897(碗) have both T and S disposition, is not matter for Chinese. Anyway, I noticed JGP’s disposition for 丏(o) and丐(b) “丐, 丏(b), 丐(A)” is generated in Step3 and “丏, 丏(o), 丐(b)” is generated in Step 4 I am a little worried about the meaning of “丏, 丏(o), 丐(b)” Does that mean even “丏” is an out-of-repertoire-variant for J-TAG, not existing n Japanese script, applicants are still able to apply for a label like丏丏with J-TAG. The disposition will go like “丏丏” get out-variant-blocked and “丐丐” label get also blocked at the same time. In this case, applicant get nothing, but in the root database, 丏丏 and 丐丐 are both blocked. ( this is nonsense ) A more rational action should go like, the application for 丏丏with J-TAG be rejected, with a warning “not a Japanese character” Then applicant could try to apply丏丏 with C-TAG again. If we want to do this, some changes are needed in Step3 and Step4. What’s your opinion to the above case? Regards Wang Wei -----邮件原件----- 发件人: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] 发送时间: 2015年5月7日 19:16 收件人: 王伟 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: Re: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before Seoul meeting Dear Wang Wei san, Thank you for your answers.
For your first question, yes, we would like to see J-LGR-2. Please
send it to us when you ready.
Please find attached J-LGR-2 repertoire. Please note that it is Excel file and is not XML format, because it will be more convenient for most of receipients. And it omits preambles (including language tag) and WLE rules.
For the conflicts you mentioned, from CDNC's perspective, we don’t
treat them as conflicts.
Thank you for your explanation. I understood CGP's intention. I still concern about 3 characters which has both T and S disposition types: U+4E48(么) U+4E7E(乾) U+7897(碗) If it is not matter for Chinese, please ignore my concern.
For JGP, the case should go like:
丐, 丐(A), 丏(o)
This case comes to this (see line 195 and 196 of attached file): 丏, 丏(o), 丐(b) 丐, 丏(b), 丐(A) The differences are because the line 195 is generated by step 4, and the line 196 is generated by step 3. Regards, -- Yoshiro YONEYA < <mailto:yoshiro.yoneya@jprs.co.jp> yoshiro.yoneya@jprs.co.jp> On Tue, 5 May 2015 19:18:29 +0800 王伟 < <mailto:wangwei@cnic.cn> wangwei@cnic.cn> wrote:
Sorry for the mistake in the last mail.
For JGP, the case should go like:
丐, 丐(A), 丏(o)
regards
-----邮件原件-----
发件人: 王伟 [mailto:wangwei@cnic.cn]
发送时间: 2015年5月5日 19:02
收件人: 'Yoshiro YONEYA'
抄送: 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org'
主题: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before
Seoul meeting
Dear Yoneya San
Thanks for your work.
It seems we already have a unanimous agreement on the repertoire so
far.
For your first question, yes, we would like to see J-LGR-2. Please
send it to us when you ready.
For the conflicts you mentioned, from CDNC's perspective, we don’t
treat them as conflicts.
Let's take 4E10丐for example, CGP will follow CDNC's variant setting
and rule, it goes like the follows:
丏, 丐(S), 丏(T)
丐, 丐(B), 丏(b)
Which means, the preferred simplified code points and traditional
code points would be different, the variant corresponding actions are
asymmetric, considering the actual language environment usage difference.
In this case, because J-LGR-1 has 4E10 too (but has no 4E0F), so I
assume JGP variant action would follow CGP's action be like
丐, 丐(B), 丏(b)
I am not sure if the above case will work for JGP.
As you listed in the last mail, CGP has many code points as above,
including the most important发-發-発and发/ 髮.
Looking forward to your reply.
Regards
Wang Wei
-----邮件原件-----
发件人: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp]
发送时间: 2015年5月1日 21:03
收件人: wangwei@cnic.cn
抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org
主题: Re: [Japanesegp] 答复: [ChineseGP] Proposed Action items before
Seoul meeting
Dear Wang Wei san and all,
Thank you for CGP's effort. I checked mss-var-20150430.xml from two
viewpoints below:
(1) Whether Yoneya's algorithm work fine with C and J LGR-1
(2) Whether C-LGR-1 has conflicts of disposition type
For (1), it seemed working fine.
- There was no difference between C-LGR-1 and generated C-LGR-2
(This is because J-LGR-1 has no variant)
- Variants in generated J-LGR-2 were the same with C and J LGR-M
(please let me know if you want to see J-LGR-2)
For (2), I found hundreds of conflicts listed below.
Here, each mark means the disposition type as:
- S: simp
- T: trad
- B: both
- b: blocked
CP disposition types
U+4E10: SB
U+4E11: BS
U+4E18: BS
U+4E30: BbS
U+4E43: BSS
U+4E48: BTSS
U+4E7E: BTTbbS
U+4E86: BSS
U+4E91: BS
U+4E95: SB
U+4EC6: BS
U+4EC7: BSbb
U+4ED9: BSS
U+4EF2: BS
U+4EFF: BSbS
U+4F0A: BS
U+4F19: BS
U+4F59: BSb
U+4F5B: BBSS
U+4F60: TBbbb
U+4F63: BS
U+4F69: BS
U+4F84: BS
U+4FDD: BS
U+4FDE: BBS
U+4FEF: SBS
U+500F: BS
U+501F: BSS
U+5026: BbS
U+506C: BS
U+5077: BBS
U+508D: BS
U+50ED: SB
U+50F5: BS
U+5149: BS
U+514B: BSS
U+518F: BS
U+51A2: BS
U+51AC: BS
U+51B1: BS
U+51C6: BSS
U+51CC: BS
U+51E0: BS
U+51F6: SB
U+51FA: BS
U+5212: BS
U+5228: BS
U+522E: BS
U+5236: BS
U+5238: bBT
U+5243: BS
U+5269: BBS
U+526F: BS
U+527D: BS
U+527F: BS
U+52D6: BS
U+52E4: BS
U+5343: bBS
U+5347: BSS
U+535C: BbS
U+5360: SB
U+5377: BBS
U+5382: BS
U+5384: BS
U+5398: BS
U+53CD: BS
U+53EA: BSS
U+53F0: BSSS
U+5401: BS
U+5403: BS
U+5408: BS
U+540A: BS
U+540C: bBS
U+540E: BS
U+5411: BSS
U+543B: BSB
U+5446: BS
U+5468: BS
U+5471: BT
U+5475: BTbb
U+547C: BBbS
U+548C: BSS
U+549D: BS
U+54B1: SB
U+54B8: BS
U+54BD: BS
U+54C4: BSS
U+5507: BS
U+5546: BS
U+5556: BSS
U+5582: BS
U+5591: BS
U+55A7: BS
U+563B: BS
U+566A: BS
U+56DE: BSSS
U+56F0: BS
U+572D: BS
U+5730: BS
U+5740: BS
U+574F: BbSS
U+5751: BS
U+5807: BSS
U+5824: BS
U+58D6: SB
U+590D: BSSb
U+5925: TB
U+592B: SB
U+592D: BS
U+5938: BS
U+5976: bbBbS
U+5978: BS
U+5996: BS
U+5999: BSB
U+59DC: BS
U+59F9: SB
U+5A18: BSS
U+5A49: SB
U+5B81: BSSbSSb
U+5B83: BS
U+5BB4: BS
U+5BB6: SB
U+5C38: BS
U+5C40: SBS
U+5CA9: BSSS
U+5CAD: BBS
U+5CB3: BS
U+5D0E: SBS
U+5D4F: BS
U+5DE8: BSb
U+5E03: SB
U+5E18: BS
U+5E19: BS
U+5E2D: BS
U+5E55: BS
U+5E72: SSBSSb
U+5E76: SSSBBS
U+5E78: SB
U+5E84: BSS
U+5E95: SB
U+5EFF: SB
U+5F04: BBS
U+5F26: BS
U+5F69: BS
U+5F81: BSS
U+5FA1: BS
U+5FAD: SB
U+5FB5: TTB
U+5FCF: BSS
U+5FD7: BS
U+5FF5: SB
U+601C: BS
U+604D: SB
U+6052: SB
U+6064: SBB
U+6096: BS
U+60E0: BBS
U+6108: BSS
U+6127: SB
U+613F: BS
U+6167: BS
U+6247: BS
U+624D: BS
U+624E: bbBbSSS
U+6251: BS
U+6258: BS
U+625B: BS
U+6263: BS
U+626F: BS
U+627C: BS
U+6298: BS
U+62AC: BS
U+62B5: bBbbS
U+62D0: BS
U+62DA: SB
U+633D: BS
U+6346: BS
U+634D: bBT
U+636E: BSS
U+63EA: BS
U+647A: TB
U+64B0: BS
U+6548: SBB
U+6597: BSSSSS
U+65A4: BbS
U+65C5: BS
U+65CB: BSb
U+65D7: SB
U+6606: SSB
U+6635: BS
U+6696: BS
U+6697: SBS
U+66F2: BBS
U+6717: BS
U+671B: BS
U+672C: TB
U+672D: SSbBbbb
U+6731: BS
U+6734: BS
U+6746: BS
U+6760: BS
U+676F: BSS
U+6770: SB
U+677E: BS
U+677F: BS
U+6781: BS
U+6784: SSBS
U+679C: BS
U+67DC: BS
U+67F1: BS
U+6816: SBS
U+6817: SB
U+6838: BS
U+6840: BS
U+6881: BS
U+68CB: BBS
U+68F0: BS
U+68F1: BS
U+68F9: bBS
U+6994: SB
U+699C: BS
U+69A8: SB
U+69B7: SB
U+6A3D: BS
U+6A90: BS
U+6A97: BS
U+6B32: SB
U+6BB7: SB
U+6BD7: BS
U+6C1B: BS
U+6C61: SBB
U+6C78: BS
U+6C88: BbS
U+6CBE: BS
U+6CC4: BSb
U+6CDB: SSB
U+6CDE: BS
U+6CE0: BS
U+6CE8: BS
U+6D01: BS
U+6D3C: BSS
U+6D3D: SB
U+6D59: BS
U+6D63: BS
U+6D69: BS
U+6D82: BSB
U+6D8C: BS
U+6DC0: BS
U+6DCB: BbSbb
U+6DEB: SB
U+6E05: SBB
U+6E38: BS
U+6EAA: BBS
U+6EAF: SBB
U+6F13: BS
U+6F2B: BS
U+6F3E: BS
U+6F84: SB
U+7095: SB
U+70AE: BSS
U+70B3: bSB
U+710A: BSS
U+7130: BBS
U+7167: SSB
U+71D5: BS
U+72F7: BS
U+72F8: BS
U+732C: BS
U+733F: BS
U+73C9: bBS
U+73F6: BT
U+7403: SB
U+7405: BS
U+7483: SBS
U+7487: SBS
U+74F6: BBS
U+753A: SB
U+754E: SB
U+75B1: BS
U+75C7: BS
U+75F1: SB
U+75F4: BS
U+75F9: SBS
U+7682: SB
U+768E: BS
U+7693: BSBS
U+7696: SB
U+772F: BS
U+7737: BS
U+773A: BS
U+777F: SB
U+77AD: TbB
U+77B0: BS
U+77E9: TB
U+7827: BS
U+786C: TB
U+7887: SB
U+788C: BS
U+7897: TBBS
U+78B0: SBS
U+7947: BS
U+79CB: BBS
U+79D8: SB
U+79FB: BS
U+7A11: BS
U+7A17: BS
U+7A57: BBS
U+7B2E: BS
U+7B51: BS
U+7B52: BS
U+7B56: BBS
U+7BA1: SB
U+7BAC: BS
U+7BEA: SB
U+7C97: BSBS
U+7CC7: BS
U+7CCA: BS
U+7CCD: BS
U+7CDF: BS
U+7CFB: SBSS
U+7D2F: BS
U+7DAE: SB
U+7E9B: BS
U+7F38: SB
U+7F50: BS
U+7F6E: SB
U+7F8E: SB
U+7FA1: BS
U+7FFB: SBB
U+8000: bSB
U+8003: SB
U+809B: SB
U+80B4: BS
U+80C4: SB
U+80CC: SB
U+80DC: SB
U+80E1: BS
U+80ED: BS
U+80F3: SB
U+814A: SBS
U+8198: BS
U+81BB: SB
U+81F4: SB
U+820D: SBB
U+82B1: BS
U+82B8: BS
U+82DF: SB
U+8303: SB
U+8347: BS
U+8349: SBS
U+8350: BS
U+83F0: TbB
U+83F1: BS
U+8431: BS
U+8457: TB
U+8499: SSSB
U+8511: BS
U+854A: SBBB
U+85AF: BS
U+85C9: TbB
U+85DC: SB
U+85E4: SB
U+85E9: SB
U+8616: SB
U+866C: BS
U+866E: BS
U+86B6: BS
U+86D4: SSB
U+8737: BS
U+8776: SB
U+8782: SB
U+8815: SB
U+8822: SB
U+8868: BS
U+8892: BS
U+88F8: SB
U+8C37: SB
U+8C46: SB
U+8D9F: BS
U+8DD6: BS
U+8E0A: BS
U+8E29: SB
U+8F9F: BbS
U+8FA8: bbBS
U+8FE4: SB
U+903E: SB
U+9041: BS
U+90C1: SBSS
U+916C: SBBB
U+91C7: SB
U+91CC: SSB
U+91CE: SB
U+962A: TB
U+9676: SB
U+9699: TB
U+96C1: BS
U+96C7: SB
U+96CD: BS
U+96D5: bSBS
U+9709: BS
U+9713: SB
U+9762: BSSS
U+99A8: BS
U+9B03: bSbB
U+9B41: SB
U+9D02: BS
U+9EBB: bSbBB
U+9F39: SB
U+9F96: BS
Regards,
--
Yoshiro YONEYA < <mailto:yoshiro.yoneya@jprs.co.jp> yoshiro.yoneya@jprs.co.jp>
On Thu, 30 Apr 2015 23:44:32 +0800 王伟 < <mailto:wangwei@cnic.cn> wangwei@cnic.cn> wrote:
Dear All
CGP updates the code points and variants in CGP-MSS, which will be
used as CGP LGR1 to coordinate with J and K.
Please find the attached XML file generated by Mr. QI Chao.
Also, we provide a readable EXCEL version for your review.
Please feel free to give your comments
Best Regards
Wang Wei
-----邮件原件-----
发件人: 王伟 [mailto:wangwei@cnic.cn]
发送时间: 2015年4月27日 10:15
收件人: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org';
'ChineseGP@icann.org'; 'JapaneseGP@icann.org'
主题: 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear ALL
For CGP, ToDo-6 has been done.
ToDo-7 will be sent out after double check this week.
-----邮件原件-----
发件人: chinesegp-bounces@icann.org
[mailto:chinesegp-bounces@icann.org]
代
表 HiroHOTTA
发送时间: 2015年4月26日 1:05
收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org
主题: [ChineseGP] 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
_______________________________________________
ChineseGP mailing list
<mailto:ChineseGP@icann.org> ChineseGP@icann.org
<https://mm.icann.org/mailman/listinfo/chinesegp> https://mm.icann.org/mailman/listinfo/chinesegp
Dear Wang Wei San, Thank you for your explanation about 3 code points. I understood Chinese situation. I really appreciate CGP's effort.
To continue the my assumption about “丏丏” with J-TAG.
If IP have a higher-level disposition rule, when founding all label combination failed (blocked or out-of-repertoire-blocked), and the application will be cancelled.
Which means, nothing happens, then the applicant could try丏丏 with C-TAG or K-TAG.
My opinion is the same above. 丏 is not in J-LGR-1 repertoire, so basically "丏丏" can't apply with J-TAG. I think labels including "out-of-repertoire-var" character (that is, invalid labels) must be rejected. Regards, -- Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> On Fri, 8 May 2015 15:56:29 +0800 王伟 <wangwei@cnic.cn> wrote:
To continue the my assumption about “丏丏” with J-TAG.
If IP have a higher-level disposition rule, when founding all label combination failed (blocked or out-of-repertoire-blocked), and the application will be cancelled.
Which means, nothing happens, then the applicant could try丏丏 with C-TAG or K-TAG.
Thus, Yoneya’s algorithm works perfect, nothing needs to change.
: )
发件人: 王伟 [mailto:wangwei@cnic.cn] 发送时间: 2015年5月8日 15:38 收件人: 'Yoshiro YONEYA' 抄送: 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org' 主题: 答复: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear Yoneya San
The three characters you mentioned in CGP-LGR go like:
Code
Character
S
T
Blocked
4E48
么
么(4E48)
么(4E48)麼(9EBC)
幺(5E7A)麽(9EBD)
9EBC
麼
么(4E48)
麼(9EBC)
幺(5E7A)麽(9EBD)
9EBD
麽
麽(9EBD)么(4E48)
麼(9EBC)
幺(5E7A)
5E7A
幺
幺(5E7A)
么(4E48)
麼(9EBC)麽(9EBD)
4E81
亁
干(5E72)
乾(4E7E)
幹(5E79)榦(69A6)漧(6F27)
5E79
幹
干(5E72)
幹(5E79)
乾(4E7E)亁(4E81)榦(69A6)漧(6F27)
registr
4E7E
乾
乾(4E7E)干(5E72)
乾(4E7E)
亁(4E81)幹(5E79)榦(69A6)漧(6F27)
5E72
干
干(5E72)
干(5E72)乾(4E7E)幹(5E79)
亁(4E81)榦(69A6)漧(6F27)
69A6
榦
干(5E72)
榦(69A6)
乾(4E7E)亁(4E81)幹(5E79)漧(6F27)
6F27
漧
乾(4E7E)
漧(6F27)
亁(4E81)干(5E72)幹(5E79)榦(69A6)
6900
椀
椀(6900)
碗(7897)
盌(76CC)鋺(92FA)
7897
碗
碗(7897)
碗(7897)
椀(6900)盌(76CC)鋺(92FA)
92FA
鋺
碗(7897)
鋺(92FA)
椀(6900)盌(76CC)
76CC
盌
碗(7897)
碗(7897)
椀(6900)鋺(92FA)
The above disposition is the compromise result between simplified area and traditional area ( just like a coordination between Simplified GP and Traditional GP)
For example,
5E72
干
干(5E72)
干(5E72)乾(4E7E)幹(5E79)
亁(4E81)榦(69A6)漧(6F27)
for code point 5E72, China mainland will use 5E72 as simplified preferred character, however, 5E72, 4E7E and 5E79 could all possible traditional code points to 5E72.
it is hard for Taiwan to predict which one is the actual code points a specific registrant really want, so they keep all three code points “ALLOCATABLE”, “BLOCK” the others three (4E81, 69A6, 6F27)
so for your question, U+4E48(么), U+4E7E(乾), U+7897(碗) have both T and S disposition, is not matter for Chinese.
Anyway, I noticed JGP’s disposition for 丏(o) and丐(b)
“丐, 丏(b), 丐(A)” is generated in Step3 and “丏, 丏(o), 丐(b)” is generated in Step 4
I am a little worried about the meaning of “丏, 丏(o), 丐(b)”
Does that mean even “丏” is an out-of-repertoire-variant for J-TAG, not existing n Japanese script, applicants are still able to apply for a label like丏丏with J-TAG.
The disposition will go like “丏丏” get out-variant-blocked and “丐丐” label get also blocked at the same time.
In this case, applicant get nothing, but in the root database, 丏丏 and 丐丐 are both blocked. ( this is nonsense )
A more rational action should go like, the application for 丏丏with J-TAG be rejected, with a warning “not a Japanese character”
Then applicant could try to apply丏丏 with C-TAG again. If we want to do this, some changes are needed in Step3 and Step4.
What’s your opinion to the above case?
Regards
Wang Wei
-----邮件原件----- 发件人: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp] 发送时间: 2015年5月7日 19:16 收件人: 王伟 抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org 主题: Re: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear Wang Wei san,
Thank you for your answers.
For your first question, yes, we would like to see J-LGR-2. Please
send it to us when you ready.
Please find attached J-LGR-2 repertoire. Please note that it is Excel file and is not XML format, because it will be more convenient for most of receipients. And it omits preambles (including language tag) and WLE rules.
For the conflicts you mentioned, from CDNC's perspective, we don’t
treat them as conflicts.
Thank you for your explanation. I understood CGP's intention.
I still concern about 3 characters which has both T and S disposition
types:
U+4E48(么)
U+4E7E(乾)
U+7897(碗)
If it is not matter for Chinese, please ignore my concern.
For JGP, the case should go like:
丐, 丐(A), 丏(o)
This case comes to this (see line 195 and 196 of attached file):
丏, 丏(o), 丐(b)
丐, 丏(b), 丐(A)
The differences are because the line 195 is generated by step 4, and the line 196 is generated by step 3.
Regards,
--
Yoshiro YONEYA < <mailto:yoshiro.yoneya@jprs.co.jp> yoshiro.yoneya@jprs.co.jp>
On Tue, 5 May 2015 19:18:29 +0800 王伟 < <mailto:wangwei@cnic.cn> wangwei@cnic.cn> wrote:
Sorry for the mistake in the last mail.
For JGP, the case should go like:
丐, 丐(A), 丏(o)
regards
-----邮件原件-----
发件人: 王伟 [mailto:wangwei@cnic.cn]
发送时间: 2015年5月5日 19:02
收件人: 'Yoshiro YONEYA'
抄送: 'KoreanGP@icann.org'; 'ChineseGP@icann.org'; 'JapaneseGP@icann.org'
主题: 答复: [Japanesegp] 答复: [ChineseGP] Proposed Action items before
Seoul meeting
Dear Yoneya San
Thanks for your work.
It seems we already have a unanimous agreement on the repertoire so
far.
For your first question, yes, we would like to see J-LGR-2. Please
send it to us when you ready.
For the conflicts you mentioned, from CDNC's perspective, we don’t
treat them as conflicts.
Let's take 4E10丐for example, CGP will follow CDNC's variant setting
and rule, it goes like the follows:
丏, 丐(S), 丏(T)
丐, 丐(B), 丏(b)
Which means, the preferred simplified code points and traditional
code points would be different, the variant corresponding actions are
asymmetric, considering the actual language environment usage difference.
In this case, because J-LGR-1 has 4E10 too (but has no 4E0F), so I
assume JGP variant action would follow CGP's action be like
丐, 丐(B), 丏(b)
I am not sure if the above case will work for JGP.
As you listed in the last mail, CGP has many code points as above,
including the most important发-發-発and发/ 髮.
Looking forward to your reply.
Regards
Wang Wei
-----邮件原件-----
发件人: Yoshiro YONEYA [mailto:yoshiro.yoneya@jprs.co.jp]
发送时间: 2015年5月1日 21:03
收件人: wangwei@cnic.cn
抄送: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org
主题: Re: [Japanesegp] 答复: [ChineseGP] Proposed Action items before
Seoul meeting
Dear Wang Wei san and all,
Thank you for CGP's effort. I checked mss-var-20150430.xml from two
viewpoints below:
(1) Whether Yoneya's algorithm work fine with C and J LGR-1
(2) Whether C-LGR-1 has conflicts of disposition type
For (1), it seemed working fine.
- There was no difference between C-LGR-1 and generated C-LGR-2
(This is because J-LGR-1 has no variant)
- Variants in generated J-LGR-2 were the same with C and J LGR-M
(please let me know if you want to see J-LGR-2)
For (2), I found hundreds of conflicts listed below.
Here, each mark means the disposition type as:
- S: simp
- T: trad
- B: both
- b: blocked
CP disposition types
U+4E10: SB
U+4E11: BS
U+4E18: BS
U+4E30: BbS
U+4E43: BSS
U+4E48: BTSS
U+4E7E: BTTbbS
U+4E86: BSS
U+4E91: BS
U+4E95: SB
U+4EC6: BS
U+4EC7: BSbb
U+4ED9: BSS
U+4EF2: BS
U+4EFF: BSbS
U+4F0A: BS
U+4F19: BS
U+4F59: BSb
U+4F5B: BBSS
U+4F60: TBbbb
U+4F63: BS
U+4F69: BS
U+4F84: BS
U+4FDD: BS
U+4FDE: BBS
U+4FEF: SBS
U+500F: BS
U+501F: BSS
U+5026: BbS
U+506C: BS
U+5077: BBS
U+508D: BS
U+50ED: SB
U+50F5: BS
U+5149: BS
U+514B: BSS
U+518F: BS
U+51A2: BS
U+51AC: BS
U+51B1: BS
U+51C6: BSS
U+51CC: BS
U+51E0: BS
U+51F6: SB
U+51FA: BS
U+5212: BS
U+5228: BS
U+522E: BS
U+5236: BS
U+5238: bBT
U+5243: BS
U+5269: BBS
U+526F: BS
U+527D: BS
U+527F: BS
U+52D6: BS
U+52E4: BS
U+5343: bBS
U+5347: BSS
U+535C: BbS
U+5360: SB
U+5377: BBS
U+5382: BS
U+5384: BS
U+5398: BS
U+53CD: BS
U+53EA: BSS
U+53F0: BSSS
U+5401: BS
U+5403: BS
U+5408: BS
U+540A: BS
U+540C: bBS
U+540E: BS
U+5411: BSS
U+543B: BSB
U+5446: BS
U+5468: BS
U+5471: BT
U+5475: BTbb
U+547C: BBbS
U+548C: BSS
U+549D: BS
U+54B1: SB
U+54B8: BS
U+54BD: BS
U+54C4: BSS
U+5507: BS
U+5546: BS
U+5556: BSS
U+5582: BS
U+5591: BS
U+55A7: BS
U+563B: BS
U+566A: BS
U+56DE: BSSS
U+56F0: BS
U+572D: BS
U+5730: BS
U+5740: BS
U+574F: BbSS
U+5751: BS
U+5807: BSS
U+5824: BS
U+58D6: SB
U+590D: BSSb
U+5925: TB
U+592B: SB
U+592D: BS
U+5938: BS
U+5976: bbBbS
U+5978: BS
U+5996: BS
U+5999: BSB
U+59DC: BS
U+59F9: SB
U+5A18: BSS
U+5A49: SB
U+5B81: BSSbSSb
U+5B83: BS
U+5BB4: BS
U+5BB6: SB
U+5C38: BS
U+5C40: SBS
U+5CA9: BSSS
U+5CAD: BBS
U+5CB3: BS
U+5D0E: SBS
U+5D4F: BS
U+5DE8: BSb
U+5E03: SB
U+5E18: BS
U+5E19: BS
U+5E2D: BS
U+5E55: BS
U+5E72: SSBSSb
U+5E76: SSSBBS
U+5E78: SB
U+5E84: BSS
U+5E95: SB
U+5EFF: SB
U+5F04: BBS
U+5F26: BS
U+5F69: BS
U+5F81: BSS
U+5FA1: BS
U+5FAD: SB
U+5FB5: TTB
U+5FCF: BSS
U+5FD7: BS
U+5FF5: SB
U+601C: BS
U+604D: SB
U+6052: SB
U+6064: SBB
U+6096: BS
U+60E0: BBS
U+6108: BSS
U+6127: SB
U+613F: BS
U+6167: BS
U+6247: BS
U+624D: BS
U+624E: bbBbSSS
U+6251: BS
U+6258: BS
U+625B: BS
U+6263: BS
U+626F: BS
U+627C: BS
U+6298: BS
U+62AC: BS
U+62B5: bBbbS
U+62D0: BS
U+62DA: SB
U+633D: BS
U+6346: BS
U+634D: bBT
U+636E: BSS
U+63EA: BS
U+647A: TB
U+64B0: BS
U+6548: SBB
U+6597: BSSSSS
U+65A4: BbS
U+65C5: BS
U+65CB: BSb
U+65D7: SB
U+6606: SSB
U+6635: BS
U+6696: BS
U+6697: SBS
U+66F2: BBS
U+6717: BS
U+671B: BS
U+672C: TB
U+672D: SSbBbbb
U+6731: BS
U+6734: BS
U+6746: BS
U+6760: BS
U+676F: BSS
U+6770: SB
U+677E: BS
U+677F: BS
U+6781: BS
U+6784: SSBS
U+679C: BS
U+67DC: BS
U+67F1: BS
U+6816: SBS
U+6817: SB
U+6838: BS
U+6840: BS
U+6881: BS
U+68CB: BBS
U+68F0: BS
U+68F1: BS
U+68F9: bBS
U+6994: SB
U+699C: BS
U+69A8: SB
U+69B7: SB
U+6A3D: BS
U+6A90: BS
U+6A97: BS
U+6B32: SB
U+6BB7: SB
U+6BD7: BS
U+6C1B: BS
U+6C61: SBB
U+6C78: BS
U+6C88: BbS
U+6CBE: BS
U+6CC4: BSb
U+6CDB: SSB
U+6CDE: BS
U+6CE0: BS
U+6CE8: BS
U+6D01: BS
U+6D3C: BSS
U+6D3D: SB
U+6D59: BS
U+6D63: BS
U+6D69: BS
U+6D82: BSB
U+6D8C: BS
U+6DC0: BS
U+6DCB: BbSbb
U+6DEB: SB
U+6E05: SBB
U+6E38: BS
U+6EAA: BBS
U+6EAF: SBB
U+6F13: BS
U+6F2B: BS
U+6F3E: BS
U+6F84: SB
U+7095: SB
U+70AE: BSS
U+70B3: bSB
U+710A: BSS
U+7130: BBS
U+7167: SSB
U+71D5: BS
U+72F7: BS
U+72F8: BS
U+732C: BS
U+733F: BS
U+73C9: bBS
U+73F6: BT
U+7403: SB
U+7405: BS
U+7483: SBS
U+7487: SBS
U+74F6: BBS
U+753A: SB
U+754E: SB
U+75B1: BS
U+75C7: BS
U+75F1: SB
U+75F4: BS
U+75F9: SBS
U+7682: SB
U+768E: BS
U+7693: BSBS
U+7696: SB
U+772F: BS
U+7737: BS
U+773A: BS
U+777F: SB
U+77AD: TbB
U+77B0: BS
U+77E9: TB
U+7827: BS
U+786C: TB
U+7887: SB
U+788C: BS
U+7897: TBBS
U+78B0: SBS
U+7947: BS
U+79CB: BBS
U+79D8: SB
U+79FB: BS
U+7A11: BS
U+7A17: BS
U+7A57: BBS
U+7B2E: BS
U+7B51: BS
U+7B52: BS
U+7B56: BBS
U+7BA1: SB
U+7BAC: BS
U+7BEA: SB
U+7C97: BSBS
U+7CC7: BS
U+7CCA: BS
U+7CCD: BS
U+7CDF: BS
U+7CFB: SBSS
U+7D2F: BS
U+7DAE: SB
U+7E9B: BS
U+7F38: SB
U+7F50: BS
U+7F6E: SB
U+7F8E: SB
U+7FA1: BS
U+7FFB: SBB
U+8000: bSB
U+8003: SB
U+809B: SB
U+80B4: BS
U+80C4: SB
U+80CC: SB
U+80DC: SB
U+80E1: BS
U+80ED: BS
U+80F3: SB
U+814A: SBS
U+8198: BS
U+81BB: SB
U+81F4: SB
U+820D: SBB
U+82B1: BS
U+82B8: BS
U+82DF: SB
U+8303: SB
U+8347: BS
U+8349: SBS
U+8350: BS
U+83F0: TbB
U+83F1: BS
U+8431: BS
U+8457: TB
U+8499: SSSB
U+8511: BS
U+854A: SBBB
U+85AF: BS
U+85C9: TbB
U+85DC: SB
U+85E4: SB
U+85E9: SB
U+8616: SB
U+866C: BS
U+866E: BS
U+86B6: BS
U+86D4: SSB
U+8737: BS
U+8776: SB
U+8782: SB
U+8815: SB
U+8822: SB
U+8868: BS
U+8892: BS
U+88F8: SB
U+8C37: SB
U+8C46: SB
U+8D9F: BS
U+8DD6: BS
U+8E0A: BS
U+8E29: SB
U+8F9F: BbS
U+8FA8: bbBS
U+8FE4: SB
U+903E: SB
U+9041: BS
U+90C1: SBSS
U+916C: SBBB
U+91C7: SB
U+91CC: SSB
U+91CE: SB
U+962A: TB
U+9676: SB
U+9699: TB
U+96C1: BS
U+96C7: SB
U+96CD: BS
U+96D5: bSBS
U+9709: BS
U+9713: SB
U+9762: BSSS
U+99A8: BS
U+9B03: bSbB
U+9B41: SB
U+9D02: BS
U+9EBB: bSbBB
U+9F39: SB
U+9F96: BS
Regards,
--
Yoshiro YONEYA < <mailto:yoshiro.yoneya@jprs.co.jp> yoshiro.yoneya@jprs.co.jp>
On Thu, 30 Apr 2015 23:44:32 +0800 王伟 < <mailto:wangwei@cnic.cn> wangwei@cnic.cn> wrote:
Dear All
CGP updates the code points and variants in CGP-MSS, which will be
used as CGP LGR1 to coordinate with J and K.
Please find the attached XML file generated by Mr. QI Chao.
Also, we provide a readable EXCEL version for your review.
Please feel free to give your comments
Best Regards
Wang Wei
-----邮件原件-----
发件人: 王伟 [mailto:wangwei@cnic.cn]
发送时间: 2015年4月27日 10:15
收件人: 'hotta@jprs.co.jp'; 'KoreanGP@icann.org';
'ChineseGP@icann.org'; 'JapaneseGP@icann.org'
主题: 答复: [ChineseGP] Proposed Action items before Seoul meeting
Dear ALL
For CGP, ToDo-6 has been done.
ToDo-7 will be sent out after double check this week.
-----邮件原件-----
发件人: chinesegp-bounces@icann.org
[mailto:chinesegp-bounces@icann.org]
代
表 HiroHOTTA
发送时间: 2015年4月26日 1:05
收件人: KoreanGP@icann.org; ChineseGP@icann.org; JapaneseGP@icann.org
主题: [ChineseGP] 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
_______________________________________________
ChineseGP mailing list
<mailto:ChineseGP@icann.org> ChineseGP@icann.org
<https://mm.icann.org/mailman/listinfo/chinesegp> https://mm.icann.org/mailman/listinfo/chinesegp
Dear CJK Colleagues, Below I marked the progress status to each ToDo item except ToDo-1 to 4, which request each participant to build his/her own capacity about RootLGR. I put the progress status after "==>" following each ToDo in the list pasted below.. Please check the progress status of your ToDo's. If correction is needed, please let me know. I added one ToDo which is == ToDo-14<expected> each of CGP/JGP/KGP reviews the feedback from IP (a result of ToDo-5), drafts questions and comments to IP, and sends it to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May and then, Hiro and Yoneya will compile the questions and comments into one file and send it to IP on Tuesday morning I added this because I believe we need to raise questions and comments to IP's response given in ToDo-5. I attach the subject document, which is the IP's response, for your reference. I hope you will work on this ToDo-14 and send your questions and comments to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May. Regards, Hiro ======================================================================== ToDo's 2nd draft (as of noon KST on 8 May) == [[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 ==> done [[MSS/LGR-1]] ToDo-6 <must> C prepares MSS repertoire, which may be equivalent to Chinese LGR-1 repertoire (done?) ==> 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) ==> done 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) ==> done ToDo-9 <must> K prepares the basic idea of Korean LGR-1 repertoire and variants ==> working (hopefully to be done by 14 May) 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) ==> working (hopefully to be done by 14 May) 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 ==> working (C and J are assesing each other) [[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 ==> working (C:Wang Wei, J:Yoneya, K:???) 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) ==> working (to be fixed Monday night, 11 May) [[Integration Algorithm - additional]] ToDo-14<expected> each of CGP/JGP/KGP reviews the feedback from IP as a result of ToDo-5, and drafts questions and comments to IP and sends it to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May, and then Hiro and Yoneya will compile the questions and comments into one file and send it to IP on Tuesday morning ==> just begun ======================================================================== On Sun, 26 Apr 2015 02:05:17 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
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
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
Dear CJK colleagues, <regarding ToDo-14> JGP drafted its comments to IP's feedback on Yoneya's algorithm. I hope CGP and KGP draft their own comments and send them to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May. JGP will compile them all and send the comments to UP. IP's feedback, which was sent to us at midnight of 28 April, is attached to this file for your reference. Regards Hiro ======== (1) about the annotation on slide #3 Could you elaborate more on what this annotation means? Especially, we need to know exactly how 'script' should be used in RootLGR project. For example, Japanese language uses Kanji, Hiragana and Katakana. In this case, is 'Japanese script' a proper usage? Or, is 'Kanji script' a proper usage? (2) about WLE (to annotation on slide #4) Does this annotation intend to be based on the situation "some of the WLE rules may be for strings that contain characters in multiple scripts"? For example, it refers to WLE rules for strings containing both Kanji and Hiragana, which are very common as Japanese words ? The annotation says that "WLE rules are not script-specific in the procedure: there is only a single, common set.". Does this mean every LGR-2 has the same WLE? If so, development of RootLGR won't finish until the last Script LGR finished. Or does it mean every LGR-2 which shares the same script has the same WLE? If the answer is latter, CJK coordination steps has to have WLE integration step which will require human intervention. I would like to see the concrete image of LGR-2. (3) about the term 'disposition' (to annotation on slide #6) The annotation says that "Note: in the XML schema this is done via the "type" attribute, on the <var> element and only labels have dispositions". When we say "disposition" in LGR context, does it mean label disposition? How can we say "attribute on the <var> element" shortly? Attribute? Type? Disposition type? It is very helpful if we (IP and GPs) use the same terminology. (4) about (o) (disposition) type (to annotate on slide #11) The annotation says that "Should be (b)?". Someone feels it should be (o), and someone feels it should be (b). Whether it is (b) or (o) doesn't make the result of WLE different (the label is invalid). Is our understanding correct? (5) about minimization of allocatable variant labels (to annotate on slide #12 & #13 & #16) The annotation says that "Overall, the goal of the IP is to help the CJK-GPs to arrive at coordinated LGRs, such that the number of allocatable variant labels is minimized.". My understanding is that selection of delegated label(s) from "allocatable label(s)" is by decision of applicant. And it is out of scope of RootLGR. For Japanese language, it is impossible to predict which character is allocatable and which is blocked individually because all characters are allocatable independently. It depends on the applicant's thought. JGP doesn't say all the variant labels should be delegated. The number of delegated labels will be at most 2 or 3. But, for example, which labels are appropriate among the 16 variant labels to be allocated cannot be predefined in the RootLGR level. Such limitation should be done in application proposal and its evaluation because all the variant labels are valid in Japanese case. As a summary, we should not try to solve all the issuees by RootLGR, we should think about appropriate mixture of RootLGR and application evaluation rules/guidelines. (6) about Han and Kana mixed labels (to annotate on slide #16) The annotation says that "What about the case where a label is applied for that combines Han and Kana characters in Japanese. Which cases do we expect that the Han-variant can be substituted for the applied for Han code point in such a mixed label? -- This issue is specific to JGP, but it is affected by the design of the Han variants -- unless JGP has a WLE rule to "block" variants for mixed labels altogether.". For Japanese language, Han and Kana can use with any combination. As mentioned above, it is impossible to predict which character is allocatable and which is blocked individually. Mixed use of Han and Kana does not affect it. ======== On Fri, 08 May 2015 17:11:04 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
Dear CJK Colleagues,
Below I marked the progress status to each ToDo item except ToDo-1 to 4, which request each participant to build his/her own capacity about RootLGR. I put the progress status after "==>" following each ToDo in the list pasted below..
Please check the progress status of your ToDo's. If correction is needed, please let me know.
I added one ToDo which is == ToDo-14<expected> each of CGP/JGP/KGP reviews the feedback from IP (a result of ToDo-5), drafts questions and comments to IP, and sends it to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May and then, Hiro and Yoneya will compile the questions and comments into one file and send it to IP on Tuesday morning
I added this because I believe we need to raise questions and comments to IP's response given in ToDo-5. I attach the subject document, which is the IP's response, for your reference.
I hope you will work on this ToDo-14 and send your questions and comments to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May.
Regards, Hiro
========================================================================
ToDo's 2nd draft (as of noon KST on 8 May)
==
[[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
==> done
[[MSS/LGR-1]]
ToDo-6 <must> C prepares MSS repertoire, which may be equivalent to Chinese LGR-1 repertoire (done?)
==> 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)
==> done
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)
==> done
ToDo-9 <must> K prepares the basic idea of Korean LGR-1 repertoire and variants
==> working (hopefully to be done by 14 May)
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)
==> working (hopefully to be done by 14 May)
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
==> working (C and J are assesing each other)
[[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
==> working (C:Wang Wei, J:Yoneya, K:???)
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)
==> working (to be fixed Monday night, 11 May)
[[Integration Algorithm - additional]]
ToDo-14<expected> each of CGP/JGP/KGP reviews the feedback from IP as a result of ToDo-5, and drafts questions and comments to IP and sends it to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May, and then Hiro and Yoneya will compile the questions and comments into one file and send it to IP on Tuesday morning
==> just begun
========================================================================
On Sun, 26 Apr 2015 02:05:17 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
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
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
As I haven't received additional comments, I will send JGP's comments to IP in a separate mail. If you come up with further comments, please send them directly to IP. Hiro On Sun, 10 May 2015 00:01:27 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
Dear CJK colleagues,
<regarding ToDo-14>
JGP drafted its comments to IP's feedback on Yoneya's algorithm. I hope CGP and KGP draft their own comments and send them to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May. JGP will compile them all and send the comments to UP.
IP's feedback, which was sent to us at midnight of 28 April, is attached to this file for your reference.
Regards Hiro
======== (1) about the annotation on slide #3
Could you elaborate more on what this annotation means? Especially, we need to know exactly how 'script' should be used in RootLGR project.
For example, Japanese language uses Kanji, Hiragana and Katakana. In this case, is 'Japanese script' a proper usage? Or, is 'Kanji script' a proper usage?
(2) about WLE (to annotation on slide #4)
Does this annotation intend to be based on the situation "some of the WLE rules may be for strings that contain characters in multiple scripts"? For example, it refers to WLE rules for strings containing both Kanji and Hiragana, which are very common as Japanese words ?
The annotation says that "WLE rules are not script-specific in the procedure: there is only a single, common set.". Does this mean every LGR-2 has the same WLE? If so, development of RootLGR won't finish until the last Script LGR finished. Or does it mean every LGR-2 which shares the same script has the same WLE? If the answer is latter, CJK coordination steps has to have WLE integration step which will require human intervention. I would like to see the concrete image of LGR-2.
(3) about the term 'disposition' (to annotation on slide #6)
The annotation says that "Note: in the XML schema this is done via the "type" attribute, on the <var> element and only labels have dispositions". When we say "disposition" in LGR context, does it mean label disposition? How can we say "attribute on the <var> element" shortly? Attribute? Type? Disposition type? It is very helpful if we (IP and GPs) use the same terminology.
(4) about (o) (disposition) type (to annotate on slide #11)
The annotation says that "Should be (b)?". Someone feels it should be (o), and someone feels it should be (b). Whether it is (b) or (o) doesn't make the result of WLE different (the label is invalid). Is our understanding correct?
(5) about minimization of allocatable variant labels (to annotate on slide #12 & #13 & #16)
The annotation says that "Overall, the goal of the IP is to help the CJK-GPs to arrive at coordinated LGRs, such that the number of allocatable variant labels is minimized.". My understanding is that selection of delegated label(s) from "allocatable label(s)" is by decision of applicant. And it is out of scope of RootLGR.
For Japanese language, it is impossible to predict which character is allocatable and which is blocked individually because all characters are allocatable independently. It depends on the applicant's thought. JGP doesn't say all the variant labels should be delegated. The number of delegated labels will be at most 2 or 3. But, for example, which labels are appropriate among the 16 variant labels to be allocated cannot be predefined in the RootLGR level. Such limitation should be done in application proposal and its evaluation because all the variant labels are valid in Japanese case.
As a summary, we should not try to solve all the issuees by RootLGR, we should think about appropriate mixture of RootLGR and application evaluation rules/guidelines.
(6) about Han and Kana mixed labels (to annotate on slide #16)
The annotation says that "What about the case where a label is applied for that combines Han and Kana characters in Japanese. Which cases do we expect that the Han-variant can be substituted for the applied for Han code point in such a mixed label? -- This issue is specific to JGP, but it is affected by the design of the Han variants -- unless JGP has a WLE rule to "block" variants for mixed labels altogether.". For Japanese language, Han and Kana can use with any combination. As mentioned above, it is impossible to predict which character is allocatable and which is blocked individually. Mixed use of Han and Kana does not affect it.
========
On Fri, 08 May 2015 17:11:04 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
Dear CJK Colleagues,
Below I marked the progress status to each ToDo item except ToDo-1 to 4, which request each participant to build his/her own capacity about RootLGR. I put the progress status after "==>" following each ToDo in the list pasted below..
Please check the progress status of your ToDo's. If correction is needed, please let me know.
I added one ToDo which is == ToDo-14<expected> each of CGP/JGP/KGP reviews the feedback from IP (a result of ToDo-5), drafts questions and comments to IP, and sends it to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May and then, Hiro and Yoneya will compile the questions and comments into one file and send it to IP on Tuesday morning
I added this because I believe we need to raise questions and comments to IP's response given in ToDo-5. I attach the subject document, which is the IP's response, for your reference.
I hope you will work on this ToDo-14 and send your questions and comments to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May.
Regards, Hiro
========================================================================
ToDo's 2nd draft (as of noon KST on 8 May)
==
[[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
==> done
[[MSS/LGR-1]]
ToDo-6 <must> C prepares MSS repertoire, which may be equivalent to Chinese LGR-1 repertoire (done?)
==> 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)
==> done
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)
==> done
ToDo-9 <must> K prepares the basic idea of Korean LGR-1 repertoire and variants
==> working (hopefully to be done by 14 May)
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)
==> working (hopefully to be done by 14 May)
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
==> working (C and J are assesing each other)
[[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
==> working (C:Wang Wei, J:Yoneya, K:???)
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)
==> working (to be fixed Monday night, 11 May)
[[Integration Algorithm - additional]]
ToDo-14<expected> each of CGP/JGP/KGP reviews the feedback from IP as a result of ToDo-5, and drafts questions and comments to IP and sends it to Hiro<hotta@jprs.co.jp> and Yoneya<yoshiro.yoneya@jprs.co.jp> by Monday night, 11 May, and then Hiro and Yoneya will compile the questions and comments into one file and send it to IP on Tuesday morning
==> just begun
========================================================================
On Sun, 26 Apr 2015 02:05:17 +0900 HiroHOTTA <hotta@jprs.co.jp> wrote:
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
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp
I've received a response from Asmus in IP to JGP's question. Here I share the response with all the CGP/JGP/KGP colleagues for your reference. Hiro
>>>>>>>>>>>> forwarding starts here <<<<<<<<<<<<<<<<<<<<
Forwarded by HiroHOTTA <hotta@jprs.co.jp> ----------------------- Original Message ----------------------- From: Asmus Freytag <asmusf@ix.netcom.com> To: hotta@jprs.co.jp, Wil Tan <wil@cloudregistry.net>, Marc Blanchet <marc.blanchet@viagenie.ca>, Michel Suignard <michel@suignard.com>, Nicholas Ostler <nicholas@ostler.net> Cc: Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>, Wang Wei <wangwei@cnic.cn>, Kenny Huang <huangksh@gmail.com>, KIM Kyongsok <gimgs0@gmail.com>, Dongman Lee <dlee@cs.kaist.ac.kr>, Sarmad Hussain <sarmad.hussain@icann.org> Date: Tue, 12 May 2015 10:39:00 -0700 Subject: Re: Issues to be coordinated between CJK GPs and IP ---- On 5/11/2015 10:59 PM, HiroHOTTA wrote:
Dear IP,
Thank you for your feedback on Yoneya's algorithm.
Please find below the questions and response from Yoneya and me to your feedback. I hope they will be answered before or in the Seoul meeting on 15 May.
Regards, Hiro
======== (1) about the annotation on slide #3
Could you elaborate more on what this annotation means? Especially, we need to know exactly how 'script' should be used in RootLGR project.
For example, Japanese language uses Kanji, Hiragana and Katakana. In this case, is 'Japanese script' a proper usage? Or, is 'Kanji script' a proper usage?
Dear Hotta-san, "Script" is used in two senses. A "pure" sense, mostly used in Unicode, where Han, Hiragana and Katakana are "scripts". But also loosely, in the sense of ISO 15924, where "Jpan" is a code for "script" that represents the mixture of these three element scripts. When speaking about Unicode properties (and classification of characters by them) then the IP uses the term script in the former sense. When speaking about the scope of a "single-script" GP, the IP uses the term "script" in the latter sense. (The IP usually avoids speaking of a 'Japanese script', preferring expressions such as "repertoire corresponding to script code 'Jpan'" or similar wording).
(2) about WLE (to annotation on slide #4)
Does this annotation intend to be based on the situation "some of the WLE rules may be for strings that contain characters in multiple scripts"? For example, it refers to WLE rules for strings containing both Kanji and Hiragana, which are very common as Japanese words ?
The annotation says that "WLE rules are not script-specific in the procedure: there is only a single, common set.". Does this mean every LGR-2 has the same WLE? If so, development of RootLGR won't finish until the last Script LGR finished. Or does it mean every LGR-2 which shares the same script has the same WLE? If the answer is latter, CJK coordination steps has to have WLE integration step which will require human intervention. I would like to see the concrete image of LGR-2.
In practice, not all WLEs apply to all labels. The various <rule> and <action> elements are often crafted so that they get triggered only for code points or variants from specific subsets of the Root Zone repertoire. Formally, though, "WLE rules are not script-specific". That means, when the IP integrates all LGR files from the various GPs, it will create a single <rules> element (which contains all the individual <rule> and <action> elements). For the CJK GP's this issue has more importance, because so much of the Han script repertoire is shared. Any <rule> that is effective for strings from the Han script, must be the same for C, J and K. However, note, that any <action> that is triggered solely by variant-types can be written to be selective. If a certain variant type is only defined by the J GP, then any <action> triggered by some combination of this type is only ever triggered by a J label. Because of this, in practice, the problem is not as difficult as it could theoretically be. It is entirely like that the IP would be able to release, for example, a first version of the Root Zone LGR covering the Arabic and Armenian scripts, without risk of introducing compatibility issues, if the second version of the Root Zone LGR were to add the C, J, and K LGRs later. It is extremely unlikely that any Arabic WLE would ever be triggered by a CJK label or vice versa. Yes, WLE integration will use human intervention, and this is one of the areas that the IP will help. One of the things the IP will do, if necessary, is to rewrite the XML so that any apparent conflict between unrelated WLE rules can be avoided --- as long as that can be done without changing the intended result of the rules.
(3) about the term 'disposition' (to annotation on slide #6)
The annotation says that "Note: in the XML schema this is done via the "type" attribute, on the <var> element and only labels have dispositions". When we say "disposition" in LGR context, does it mean label disposition? How can we say "attribute on the <var> element" shortly? Attribute? Type? Disposition type? It is very helpful if we (IP and GPs) use the same terminology.
The integration panel usually speaks of "variant types". Or, if several types can lead to an allocatable label, they might be referred to as "subtypes".
(4) about (o) (disposition) type (to annotate on slide #11)
The annotation says that "Should be (b)?". Someone feels it should be (o), and someone feels it should be (b). Whether it is (b) or (o) doesn't make the result of WLE different (the label is invalid). Is our understanding correct?
For a reflexive variant, where code point C is mapped to itself, as in C-->C, the type should always be (o), whenever C is not part of the repertoire. In the unlikely case that a reflexive variant is defined for a code point C that is in the repertoire, but should not be part of a valid label, then "blocked" (or some other type) can be used. There is a small difference between "blocked" and "invalid". A blocked label does exist and is tested for collisions against registered labels (from any script). An "invalid" label does not exist and for that reason would not be tested for collisions.
(5) about minimization of allocatable variant labels (to annotate on slide #12 & #13 & #16)
The annotation says that "Overall, the goal of the IP is to help the CJK-GPs to arrive at coordinated LGRs, such that the number of allocatable variant labels is minimized.". My understanding is that selection of delegated label(s) from "allocatable label(s)" is by decision of applicant. And it is out of scope of RootLGR.
As you point out, there are two sets of labels "allocatable" and "delegated". The IP understands the required minimization to minimize the first set, to make it as small as is required. The applicant may then decide to select out of that small set. For some scripts, initial drafts of the LGR would allow hundreds of allocatable labels. The IP does not look favorably on any LGR that has the potential to generate a large number of allocatable variants; it would make it completely unpredictable which variant or variants might be chosen by the applicant. In contrast, if a well-chosen set of variant types can be used to limit allocatable C-LGR labels to "all traditional", "all simplified" and "original label", the applicant has effectively three items to choose from (a bit more, because the applicant is free to pick a particular "original" label). With such a design, users would know to attempt to reproduce a label in at most three forms (as seen, as written in traditional and as written in simplified form). One, or perhaps all, of these can be expected to be successful. Random mixtures of variants, on the other hand, would seem to rarely lead to an improved user experience. That was behind the procedure's imperative to minimize the number of allocatable labels.
For Japanese language, it is impossible to predict which character is allocatable and which is blocked individually because all characters are allocatable independently. It depends on the applicant's thought. JGP doesn't say all the variant labels should be delegated. The number of delegated labels will be at most 2 or 3. But, for example, which labels are appropriate among the 16 variant labels to be allocated cannot be predefined in the RootLGR level. Such limitation should be done in application proposal and its evaluation because all the variant labels are valid in Japanese case.
The question would be, whether, in this situation, there really is a overriding need for the same Japanese applicant to apply for multiple variants of the same label. And whether such situation is really common. Without interaction of the C-GP's LGR, and its definition of variant, we understand that Japanese usually view these characters as unrelated, and that in the second level, two labels might independently be registered in a Japanese domain that would be variants in a Chinese domain. If these labels are really considered independent, wouldn't it be the case that they commonly are not registered by the same applicant, but by different applicants, just like the domains .color and .colour in English can be registered fully independently? If that is indeed the common case, then it would seem that making all of the variants introduced by the C-LGR "allocatable" in the J-LGR doesn't really address the need. Because they would then be restricted to the _same_ applicant. The IP would want to have evidence that such a scenario is not only common, but essential. Finally, if the applicant ends up picking 2 or 3 variant labels out of a set of 16, for example, how will the users be able to guess which ones to try? Allocatable variants create definite costs in the DNS. This cost should be offset by a clear benefit to the users, by meeting an essential need for both applicants and users.
As a summary, we should not try to solve all the issues by RootLGR, we should think about appropriate mixture of RootLGR and application evaluation rules/guidelines.
For the Root Zone, it would be prudent for the LGR to be a bit more restrictive, which would also make it more predictable. This is carefully addressed in the procedure, for example in the Conservatism Principle.
(6) about Han and Kana mixed labels (to annotate on slide #16)
The annotation says that "What about the case where a label is applied for that combines Han and Kana characters in Japanese. Which cases do we expect that the Han-variant can be substituted for the applied for Han code point in such a mixed label? -- This issue is specific to JGP, but it is affected by the design of the Han variants -- unless JGP has a WLE rule to "block" variants for mixed labels altogether.". For Japanese language, Han and Kana can use with any combination. As mentioned above, it is impossible to predict which character is allocatable and which is blocked individually. Mixed use of Han and Kana does not affect it.
It would be instructive to know of examples of actual registrations from the second level where the same applicant had registered two labels differing on only the Han component -- and where that applicant is treating them as variants (leading to the same content). It would also be instructive to know how common this phenomenon is, and whether it is "defensive" in nature. (Similar to registering a "typo" for an English label, so as to avoid it being captured by an unrelated party). Such "defensive" use would be unnecessary if the variant is "blocked". I hope this clarifies some of the issues, any remaining items can of course be taken up during the discussion at the meeting. A./
========
On Tue, 28 Apr 2015 08:45:02 -0700 Asmus Freytag <asmusf@ix.netcom.com> wrote:
Dear Yoneya-san,
attached you will find your document with annotations from the Integration Panel. Let us know if you need anything more.
Wishing you success in your upcoming meeting with the other GPs,
Sincerly, A./
--------------------- Original Message Ends --------------------
participants (6)
-
Dillon, Chris -
HiroHOTTA -
Joe Zhang -
Kenny Huang, Ph.D. -
Yoshiro YONEYA -
王伟