[arabic-vip] Final draft of Arabic Case Study Issues Document (combined with definitions)

[Raed Al-Fayez]

Dear Sarmad,

Thanks for your response ..

The mechanism for incorporating or eliminating suggestion and comments are not based on a well-defended (from my point of view I consider it as a biased mechanism).

For example: when I send an email regarding "Preliminary list for technical issues that a registry should consider" that the team asked me to do (see my email on Sun 17/7/2011 10:44 AM with the subject "Variants implications on registry operations and DNSSEC") many items was deleted (in the phone conference and the face-to-face meeting) because they were not related to the root registry; Personally I was more than happy with this decision because it make sense and the initial request was general for all registries; However when I put the same comments on many parts of the document it was ignored?! [BTW this is just an example and I have more].

Anyway I also agree with you that we should have a conference call to discuss the remaining items.

With best regards,

Raed I. Al-Fayez
------------------------------------------
Senior IT Projects Specialist, M.Sc, PMP
Saudi Network Information Center (SaudiNIC)
Communication and Information Technology Commission (CITC)
Tel: + 966-1-2639235   - Fax: + 966-1-2639393
http://www.nic.net.sa<http://www.nic.net.sa/>

From: sarmad.hussain at kics.edu.pk [mailto:sarmad.hussain at kics.edu.pk] On Behalf Of Dr.Sarmad Hussain
Sent: Saturday, October 01, 2011 3:31 PM
To: Raed Al-Fayez
Cc: arabic-vip at icann.org
Subject: Re: [arabic-vip] Final draft of Arabic Case Study Issues Document (combined with definitions)

 Dear Raed,


I am still wondering why many of my comments was not taken into account when you revised the document!

I have spent lots of effort and time in revising the document and I believe my comments should be at least discussed or clarified before discarding them.

As I wrote earlier, it is not possible to accommodate all comments by everybody (as in some cases they may be conflicting; in which case I have tried to capture what the general consensus seems to be; though I can certainly confirm that I have gone through all the comments from everybody carefully in the process).  I am certainly not the final person to make the final call and that is why I have requested to kindly raise in email or document the points which you feel are essential and still not addressed and we can discuss them explicitly.  And if there is need, we can do a conference call.


BTW I have reordered the table rows in the appendixes based on the code point number, and change the naming of many code points to be aligned with the Unicode naming, also I have converted many images to tables to make all the tables in the same format, and added some extra code points that was not covered and I am disappointed when all that effort was ignored!


Don't be disappointed :-)  These are formatting issues and as per our arrangement these are left to Mohammed and his team to address in the final formatting of the document.  They will also make the spellings consistent with Unicode, etc.  I have not addressed any significant formatting issues in my re-writing, where my focus has been on re-writing the content.  Of course Mohammed is requested to accommodate this.  If there are missing content issues, please also point that out and we can adjust.


With best regards,

Raed I. Al-Fayez


regards,
Sarmad

-----------------------------------------------------------------------------------
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/20111002/6f203f47/attachment-0001.html