[Latingp] New version of Proposal for inclusion Latin script letters in next version of MSR

Meikal Mumin meikal.mumin at uni-koeln.de
Fri Jan 19 14:39:05 UTC 2018


Dear colleagues,

I was trying to look for a specific reason why those code points
representing click sounds have been excluded. Looking at the text of MSR-3,
I was able to find only the following line of argumentation on page 23:

"In general, where code points are homoglyphs or near homoglyphs of code
points that are not PVALID,
usually punctuation characters, the Integration Panel has not included such
code points in the MSR.
In particular, the following code points are highly confusable with or
outright homoglyphs of code
points, such as common punctuation characters like apostrophe or
exclamation mark, that are not
PVALID in IDNA2008 or excluded for other reasons:"

I don't see however how the main argument that the code points we suggested
are homogylphs or near homogylphs of such characters they consider
punctuation characters. That argument may be valid in the case of U01C3 or
U0242, but not the three code points we suggested. I think that this stance
taken by IP is overly conservative and reinforces certain systemic biases
in the DNS as part of the internet and that the entire point of our task is
precisely to put and end to such biases and therefore I would like to raise
this issue again.

I would suggest we submit a comment asking what their specific rationale
for excluding these three code points is, and that clearly U01C2 for
example is NOT a homogylph or near homoglyph of any punctuation character,
just as U01C0 and U01C1. Otherwise, I would like to argue that following
their approach 0069 (i.e. i) as well as any "near homoglyph" of it is a
near homogylph of the exclamation mark and should be excluded equally.

Also, I have started working on the proposal, Bill, and I would like to add
your text to it and I don't think it should be an appendix.

Best,

Meikal

On 19 January 2018 at 00:50, Bill Jouris <bill.jouris at insidethestack.com>
wrote:

> Hello all,
>
> Earlier this week, I had been drafting a possible Appendix D for our final
> report, to discuss the overall issue of clicks and stops.  (And it is a
> VERY rough draft.  Note, for example, that the various RFCs and other
> documents are not yet identified.)
>
> With this reply from the IP, it seems like the question may be better
> addressed in comments on MSR-3.  But I have attached what I had for those
> who may be interested.
>
> Bill Jouris
> Inside Products
> bill.jouris at insidethestack.com
> 831-659-8360
> 925-855-9512 (direct)
>
>
> ------------------------------
> *From:* Sarmad Hussain <sarmad.hussain at icann.org>
> *To:* Mirjana Tasić <Mirjana.Tasic at rnids.rs>; Latin GP <latingp at icann.org>
>
> *Cc:* "integrationpanel at icann.org" <integrationpanel at icann.org>
> *Sent:* Wednesday, January 17, 2018 10:00 PM
> *Subject:* Re: [Latingp] New version of Proposal for inclusion Latin
> script letters in next version of MSR
>
> Dear Mirjana, Latin GP members,
>
> Please find below the message from the Integration Panel.
>
> Regards,
> Sarmad
>
> =========
>
> The IP is pleased to acknowledge the input from the Chinese, Japanese and
> Latin GPs to the MSR-3 update of the Maximal Starting Repertoire. MSR-3 has
> just been released for public comment
> <https://www.icann.org/public-comments/msr-3-2018-01-17-en> and contains
> an updated listing of code points as well as the rationale for including or
> excluding particular code points. Based on the input received, the IP has
> extended the list of source sets for the Han ideographs with the net effect
> of adding three code points. The IP has added three Latin code points
> because new evidence provided invalidated the original rationale for their
> exclusion. An additional three Latin code points representing clicks were
> not included because the original rationale for their exclusion remains
> valid. For details see the overview document of MSR-3.
>
> Integration Panel
>
>
> 1.      MSR-3 (HTML
> <https://www.icann.org/sites/default/files/packages/lgr/msr/msr-3-wle-rules-15jan18-en.html>
> , XML
> <https://www.icann.org/sites/default/files/packages/lgr/msr/msr-3-wle-rules-15jan18-en.xml>
> )
> 2.     MSR-3-Annotated-Hangul-Tables
> <https://www.icann.org/en/system/files/files/msr-3-hangul-15jan18-en.pdf> [PDF,
> 1.12 MB]
> 3.     MSR-3-Annotated-Han-Tables
> <https://www.icann.org/en/system/files/files/msr-3-han-15jan18-en.pdf> [PDF,
> 39 MB]
> 4.     MSR-3-Annotated-non-CJK-Tables
> <https://www.icann.org/en/system/files/files/msr-3-non-cjk-15jan18-en.pdf> [PDF,
> 2.16 MB]
> 5.     MSR-3-Overview and Rationale
> <https://www.icann.org/en/system/files/files/msr-3-overview-15jan18-en.pdf> [PDF,
> 1.1 MB]
>
>
> *From:* Mirjana Tasić [mailto:Mirjana.Tasic at rnids.rs]
> *Sent:* Tuesday, January 09, 2018 11:07 PM
> *To:* Sarmad Hussain <sarmad.hussain at icann.org>
> *Cc:* Latin GP <latingp at icann.org>
> *Subject:* [Ext] New version of Proposal for inclusion Latin script
> letters in next version of MSR
>
> Dear Sarmad,
>
> After further investigation of Latin Repertoire, Latin GP has found one
> additional code point which is not included in our previous proposal for
> inclusion in the new version of MSR.
>
> Please find enclosed the new version of our Proposal for inclusion Latin
> script letters in the next version of MSR.
>
> Regards Mirjana
>
>
> _______________________________________________
> Latingp mailing list
> Latingp at icann.org
> https://mm.icann.org/mailman/listinfo/latingp
>
>
>
> _______________________________________________
> Latingp mailing list
> Latingp at icann.org
> https://mm.icann.org/mailman/listinfo/latingp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180119/d5ac92ea/attachment.html>


More information about the Latingp mailing list