[arabic-vip] agenda for conference call today (on Version 0.8)

Sarmad Hussain sarmad.hussain at kics.edu.pk
Tue Oct 4 08:41:57 UTC 2011


Yes, definitely.

Regards,
Sarmad

>>-----Original Message-----
>>From: Manal Ismail [mailto:manal at tra.gov.eg]
>>Sent: Tuesday, October 04, 2011 12:17 PM
>>To: Sarmad Hussain; arabic-vip at icann.org
>>Subject: Re: [arabic-vip] agenda for conference call today (on Version
>>0.8)
>>
>>Thank you Sarmad ..
>>If you agree, I would like to add, to the below discussion points,
>>Andrew's pending comments on the definition section of version 8.0 of
>>the document ..
>>I believe it would save us much time if we finalize this during the
>>call .. they are not many btw ..
>>
>>Kind Regards
>>
>>--Manal
>>
>>________________________________
>>
>>من: arabic-vip-bounces at icann.org بالنيابة عن Sarmad Hussain
>>تاريخ الإرسال: الثلاثاء 04/10/2011 09:06 ص
>>إلى: arabic-vip at icann.org
>>الموضوع: [arabic-vip] agenda for conference call today (on Version 0.8)
>>
>>
>>
>>Dear all,
>>
>>
>>
>>Thank you for your feedback.
>>
>>
>>
>>
>>
>>Here is a tentative agenda, which is based on Version 0.8 of the report
>>and points which still need discussion and finalization (please feel
>>free to suggest if you would like to add something to it):
>>
>>
>>
>>
>>
>>1.       We have not discussed in greater detail whether we are
>>recommending character level or position level variants.  This is an
>>important point as it has a great impact on the possible variants which
>>are generated (and also the variety of TLDs which are available).  (I
>>am thinking of adding a note on the appendices saying that the current
>>tables are only valid for character level variants and need to be
>>revisited for positional variance)
>>
>>
>>
>>2.       Should we move the normalization table in the “optional”
>>section?
>>
>>
>>
>>3.       We have the following points in the ZWNJ discussion.  We need
>>to discuss whether to include them in the final version.
>>
>>
>>
>>a.  ZWNJ is allowed, however the string with it is considered a variant
>>of the string without it.  This addresses KB, confusability and
>>security issues (but gives the users the choice and flexibility based
>>on their language)
>>
>>
>>
>>b.  ZWNJ is allowed, however, if ZWNJ is allocated, then the variant
>>without it must also be allocated
>>
>>
>>
>>c.  ZWNJ is allowed, however, if ZWNJ is allocated, then the variant
>>without it must also be allocated.  Additionally, the label with ZWNJ
>>cannot be a fundamental label, but can only be a variant
>>
>>
>>
>>d.  ZWNJ is allowed only if the applicant can demonstrate convincingly
>>that the string will not cause security risks, with additional
>>restrictions as discussed above
>>
>>
>>
>>e.  ZWNJ is not allowed at this time
>>
>>
>>
>>4.       The team has spent considerable time on the section on dispute
>>resolution.  There is a suggestion to delete this section as it is not
>>relevant.  The team (with feedback from the IDN VIP team) needs to
>>discuss and decide on this.
>>
>>
>>
>>5.       Discuss the following:
>>
>>
>>
>>“The current registration tools need to be extended to incorporate the
>>entire process automatically, with no (or minimal) manual
>>interaction.[AZ1]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msocom_1>  [AZ2]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msocom_2>  “
>>
>>
>>
>>6.       Discussion on Fees Section
>>
>>
>>
>>7.       Additional entries in tables:
>>
>>
>>
>>U+06D2 (ے)
>>
>>-
>>
>>-
>>
>>ـے
>>
>>ے[AZ3]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msocom_3>  [AZ4]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msocom_4>
>>
>>
>>
>>And
>>
>>
>>
>>U+0622 (آ)
>>
>>-
>>
>>-
>>
>>ـآ
>>
>>أ
>>
>>U+0671 (?)
>>
>>-
>>
>>-
>>
>>ـ?
>>
>>?[SH5]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msocom_5>
>>
>>
>>
>>
>>
>>8.       General note on language use.  I have been using “may” instead
>>of “will” or “should” in the document as a polite but still definite
>>assertion.  Reading the feedback, this may be confusing.  We need to
>>clarify how we use this terminology.
>>
>>
>>
>>9.       Update from Mohammed on formatting process and progress
>>
>>
>>
>>10.   Timelines and further steps towards finalization of the report
>>for submission
>>
>>
>>
>>
>>
>>Regards,
>>Sarmad
>>
>>________________________________
>>
>> [AZ1]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msoanchor_1> This is not applicable to TLD
>>
>>
>>
>> [AZ2]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msoanchor_2> It is applicable because when an Arabic
>>script label is applied for, ICANN should have a mechanism to generate
>>all variants for the TLD to evaluate the application and reserve/block
>>the label variants not applied for
>>
>> [AZ3]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msoanchor_3>  This is needed as the this version of Yeh
>>is considered the same letter Yeh, with just stylistic variation. (This
>>is similar to our treatment of the Kaf  U+06AA (?)
>>
>> [AZ4]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msoanchor_4> Need to discuss this as this is may be
>>specific to Arabic language
>>
>> [SH5]
>><https://mail.tra.gov.eg/exchange/manal/Drafts/%D8%B1%D8%AF:%20[arabic-
>>vip]%20agenda%20for%20conference%20call%20today%20(on%20Version%200.8).
>>EML/1_text.htm#_msoanchor_5> Need to discuss these




More information about the arabic-vip mailing list