[arabic-vip] doc structure for dicusssion

Sarmad Hussain sarmad.hussain at kics.edu.pk
Fri Aug 12 03:15:57 UTC 2011


Dear Manal and All,

 

Thank you for the feedback.

 

-          I believe it's a good idea to add 'Arabic Script Characteristics' as suggested by Dr. Zoman, unless it is already included somewhere in the below outline ..

 

This is covered in the general section on “Introduction to the Arabic Script”

 

-          I can only see 'Reserved Names' in the outline, is this because 'Blocked & Delegated Names' will be included in the 'Registration Process' section? 

 

I meant the names which are reserved from registration before sunrise.  This is different from the reserved variant.  But the wording is confusing!!!  So we need to find out a more clear wording in case we need to include this.  I have included the other point more explicitly.

 

-          Should there be differences between variant issues at the TLD level vs. lower Levels (for example Digits) this needs to be highlighted .. will this be mentioned where needed throughout the document? 

 

Sure, have included this as well.

 

-          Is there any differences between issues within ccTLDs vs. gTLDs ?

 

Could you explain further?

 

-          Finally in bullet point 8 "End-user and Application level requirements" .. we need to make sure issues listed here all relate to Variants and not IDNs in general .. We also need to mention somewhere whether the end-user will need some awareness with regards to variants or whether this will be completely addressed at other levels and would hence be transparent to end-users ..

 

Yes, good point, to focus on variants.  We need to discuss this in the upcoming calls.

 

Will send a revised version, with some content later tonight.

 

Kind Regards

 

--Manal     

 

Thanks, 


Sarmad

 

From: arabic-vip-bounces at icann.org [mailto:arabic-vip-bounces at icann.org] On Behalf Of Sarmad Hussain
Sent: Thursday, August 11, 2011 9:22 AM
To: arabic-vip at icann.org
Subject: Re: [arabic-vip] doc structure for dicusssion

 

Dear All,

 

Thanks to Dr. Al-zoman for feedback.  Here is a tentative outline, developed in consultation with Iftikhar, for your further comments and feedback.

 

I will fill in the discussions so far into the template as we finalize it.

 

 

Arabic Variant TLD Issues and Requirements

1.        Background

2.        Introduction to Arabic Script

3.        Terminology

4.        Types of Variants in Arabic Script and its encoding in Unicode

5.        IDN Variant Delegation Issues and Requirements

a.       Delegating Variant TLDs

b.      Management of Language and Variant Tables

c.       Other requirements 

6.        Registration related issues

a.       WHOIS

b.      Reserved Names

c.       Registration Process

d.      Fees

7.        Operations

a.       EPP

b.      DNSSEC

c.       Dispute Resolution

d.      IPv6 

e.       Other requirements

8.        End-user and Application level requirements

a.       Keyboard (soft) issues

b.      Browser  issues

c.       Font issues

d.      Mail, Web and other server administration

e.       Use of Variants inline within end user content

f.       Other issues

9.        List of relevant stakeholders 

10.    Concluding Remarks

11.    References

12.    Appendices 

 

 

Regards,
Sarmad

 

 

 

From: Abdulaziz Al-Zoman [mailto:azoman at citc.gov.sa] 
Sent: Wednesday, August 10, 2011 1:59 AM
To: Sarmad Hussain; arabic-vip at icann.org
Cc: Abdulaziz Al-Zoman
Subject: RE: [arabic-vip] doc structure for dicusssion

 

Option 1

Option one is beyond the scope of the project.

 

Option 2

1. What is a variant in Arabic script (see the email below)

           …. ok

2. How to represent variants formally (table related issues)

           …. Covered by ICANN/IANA definition

3. TLD vs. other level variants in Arabic - what is applicable level wise

           …. Rephrase: Applicable variants at a TLD level

4. Variant TLD delegation

           …. Rephrase: Variant TLD registration management (delegation/blocking)

5. Variant TLD registration 

           …. No need (covered by 4)

6. Variant TLD resolution

           …. No need (it should be standard)

7. Variants and user experience

           …. No need (out of scope)

 

Here is an option 3 … if you allow me

 

Background

 

Terminology

 

Arabic Script Characteristics

 

What is a Variant in Arabic scripts and languages?

 

Variants handling requirements at Application level

 

Variant TLD effects on the whole domain 

 

Variant TLD registration management (delegation/blocking)

 

Management of Language tables and variant tables

 

 

-----------------------------

عبدالعزيز بن حمد الزومان

Abdulaziz H. Al-Zoman

 

From: arabic-vip-bounces at icann.org [mailto:arabic-vip-bounces at icann.org] On Behalf Of Sarmad Hussain
Sent: Wednesday, August 10, 2011 2:47 AM
To: arabic-vip at icann.org
Subject: [arabic-vip] doc structure for dicusssion

 

Option 1

- issues of relevance to ICANN/IANA

- issues of relevance to registries/registrars

- issues of relevance to registrants

- issues of relevance of end-users

 

Option 2

1. What is a variant in Arabic script (see the email below)

2. How to represent variants formally (table related issues)

3. TLD vs. other level variants in Arabic - what is applicable level wise

4. Variant TLD delegation

5. Variant TLD registration 

6. Variant TLD resolution

7. Variants and user experience

 

 

 

----

سرمد حسین 

 

Sarmad Hussain 

Professor and Head

Center for Language Engineering (www.cle.org.pk)

Al-Khawarizmi Institute of Computer Science (www.kics.edu.pk)

University of Engineering and Technology (www.uet.edu.pk)

Lahore, PAKISTAN

 

 

 


-----------------------------------------------------------------------------------
Disclaimer:
This message and its attachment, if any, are confidential and may contain legally
privileged information. If you are not the intended recipient, please contact the
sender immediately and delete this message and its attachment, if any, from your
system. You should not copy this message or disclose its contents to any other
person or use it for any purpose. Statements and opinions expressed in this e-mail
are those of the sender, and do not necessarily reflect those of the Communications
and Information Technology Commission (CITC). CITC accepts no liability for damage
caused by this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm.icann.org/pipermail/arabic-vip/attachments/20110811/baf57ffe/attachment-0001.html 


More information about the arabic-vip mailing list