[arabic-vip] FW: Call summary - Monday 4 July 6:00AM UTC

[Manal Ismail]

Thanks Sarmad & Baher ..
 
I've pasted the below in a word document with some formatting for readability and ease of commenting ..
Please find attached my comments marked in track changes ..
I tried to make commenting text (that would be ultimately deleted from the document) in a different colour ..
 
Kind Regards
 
--Manal

________________________________

From: arabic-vip-bounces at icann.org on behalf of baher.esmat
Sent: Mon 04/07/2011 05:05 PM
To: arabic-vip at icann.org
Subject: [arabic-vip] FW: Call summary - Monday 4 July 6:00AM UTC


Forwarding on behalf of Sarmad. 

-baher

------ Forwarded Message
From: Sarmad Hussain <sarmad.hussain at kics.edu.pk>
Date: Mon, 4 Jul 2011 17:59:45 -0700
To: Baher Esmat <baher.esmat at icann.org>
Subject: FW: [arabic-vip] Next team call: Monday 4 July 6:00AM UTC


 
Dear All,
 
Thank you for those who could join the conference call today.  
 
We discussed the agenda which was circulated see below (but could not get through due to some emailing issues, but was later emailed to all participants on the call).  
 
The discussion focused on Agenda 1 for most of the call, and the overall categories were increased to include the following:
 
-variants
-TLD delegation
-DNSSEC
-Registry operations
-Dispute resolution
-IPv6
 
The first item, "variants" were discussed in more details, as elaborated in A.1.1 -A1.3 below.  
 
A1.1.1 Unicode code points having same shape in at least one of the four forms (beginning, middle, final and isolated)  - this was agreed
A1.1.2 composed and decomposed forms not covered through Unicode which are exactly same- this was agreed

A1.2.1 Unicode code points have shape similar enough that user will get confused and accept them equal (causing security threat, e.g. phishing)
A1.2.1.1 similar shapes- this was agreed
A1.2.1.2 similar marks 
 
A1.2.1.2 (similar marks) was subdivided into two categories: dots/marks and Hamza/madda/etc. for further consideration, instead of including this as A1.3.2.

A1.2.2 composed and decomposed forms same enough to cause user confusion (causing security threat, e.g. phishing) - this was agreed

A1.3.1 conflating level 2 marks (less significance, higher optionality)  (e.g. fatha) 
A1.3.2 conflating level 1 marks  (higher significance, lower optionality) (e.g. hamza above/below)
A1.3.3 conflating level 0(?) marks  (highest significance, no optionality) (e.g. double-fatha) (could this be A 2.1?)

A1.3.2 was to be moved into similar marks category.  
 
>From Arabic language point of view, A1.3.1 and A1.3.3 may be equally optional, though that is not the case for Urdu.  
 
It was suggested that the following sub-categories may be developed for Arabic language:
 
-Fatha/damma/kasra/etc.
-dammatan/etc.
-shadda
 
A similar strategy could be looked at for other languages to finalie the sub-categorization.
 
It was also suggested that all the PVALID Unicode code points be revisited to see if there any which may not be used - this should be looked at in the context of the current work for variants.
 
This discussion will continue through further calls and email.
--------------------
 
It was also decided that we will hold weekly meetings to get the work started and get the requisite momentum in the start.  
 
Baher is requested to circulate another Doodle soon for schedule of weekly meeting.  There will be a single doodle to set same time and day for the rest of the meetings during morning times from M-W.  
 
Remaining agenda will be followed up in future calls.
 
Baher will also circulate the recording of the meeting today.
 
Regards,
Sarmad
 
 
 
 
  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Variants in Arabic Script.doc
Type: application/msword
Size: 33280 bytes
Desc: Variants in Arabic Script.doc
Url : http://mm.icann.org/pipermail/arabic-vip/attachments/20110704/40923643/VariantsinArabicScript-0001.doc