[Idngwg] Update draft + PC2 call + ICANN 60 presentations

Sarmad Hussain sarmad.hussain at icann.org
Mon Oct 16 08:44:47 UTC 2017


Dear All,

In drafting the explanation for “uniform” in Guideline 13 in the Additional Note II, we should consider another scenario not yet captured but needed in the uniform treatment of variants across the IDN Tables.

Thus, I have suggested additional text in the Additional Note II (ii) in the updated version 2.9-redline attached.

As an explanation, consider the scenario:

Suppose a registry creates two IDN Tables, one exclusively for Traditional Chinese and other exclusively for Simplified Chinese.  If the additional text is not there the registry could potentially allocate the TC and SC versions of labels to different registrants.  With the proposed text, the variant code points will need to be reviewed for both SC and TC together so even with such IDN Tables, the variant labels for SC and TC will go to the same registrant.

The same case can occur in Arabic script.  If we have Arabic Kaf (‘k’ ك U+0643) in Arabic language table and Persian Kaf (‘k’ ک U+06A9) in Persian language table, then the identical labels کتاب and كتاب (kitab – book) could be allocated to different registrants.  If these are harmonized to be uniform, as described, such cases will be prevented.

This case does not seem to be captured elsewhere in the guidelines.  I think this was originally intended, but when we specified the definition of “uniform”, we did not capture this part.

Kindly see if this version 2.9 is agreeable to proceed (with any further edits suggested) or should we take version 2.8 further.

Regards,
Sarmad


From: idngwg-bounces at icann.org [mailto:idngwg-bounces at icann.org] On Behalf Of Sarmad Hussain
Sent: Sunday, October 15, 2017 1:11 PM
To: idngwg at icann.org
Subject: [Idngwg] Update draft + PC2 call + ICANN 60 presentations

Dear All,

Thank you for the amazing work all of you have done in finalizing the Guidelines document!

As discussed, we will conduct a second public comment on this document.

Following the IDNGWG meeting on 12 October, please find attached the following:


  1.  Call for second public comment (PC2)
  2.  Updated draft of the guidelines (updated redline version + PC2 clean version)
  3.  Updated ICANN 60 presentations (detailed for 90 min session on 29 Oct. + short for 7 minute update on 1 Nov.)

(corresponding PDF versions also attached on request)

I have added only two specific questions at the top of the guidelines document: one on scope and other on value of X.  Kindly confirm that these are Ok, and please share if you would like to add any additional specific questions?

As discussed, second public comment call and corresponding document will be sent in for publication on 18 October, so please share any feedback before 0500 UTC 18 Oct (please make changes directly in the documents).  It will be useful to get your confirmation even if you do not have any suggested changes.

As usual, the recording of the call is available at the wiki page https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_IDN_IDN-2BImplementation-2BGuidelines&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=psZrPi04OpZy2zYuUYGSomCxurkdBugJeqIN31z4UUc&s=SRrRz2lBwei_6_lLDzFWZdrAv06f9FrzPDZr-kbBOqg&e=> and the notes will also be available there soon.

Regards,
Sarmad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20171016/f05a842a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IDN Guidelines 4.0 final draft 2.9 - redline.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 50699 bytes
Desc: IDN Guidelines 4.0 final draft 2.9 - redline.docx
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20171016/f05a842a/IDNGuidelines4.0finaldraft2.9-redline-0001.docx>


More information about the Idngwg mailing list