Good Afternoon,

 

Thanks for the update Brian, looking forward to getting back to this work.

 

In response (mostly so I don’t forget J).

 

Not that you were suggesting this but I think the group should not mandate “automated” methods for detecting, I think we should suggest “automated” but leave it up to the implementers as how they want to detect.

 

In regards to the last point, and as I have stated before in different ways, my expectation coming out of the T/T PDP was that transformation (in its entirety) was not mandatory. And to me this meant none of the recommendations were mandatory but that if you did translate and/or transliterate then these recommendations would apply. My expectation for the T/T implementation group was to come up with an implementation for those that choose to translate and/or transliterate.

 

Happy New Year everyone!!

 

 

Thanks

Roger

 

 

From: translationtransliterationirt-bounces@icann.org [mailto:translationtransliterationirt-bounces@icann.org] On Behalf Of Brian Aitchison
Sent: Thursday, January 05, 2017 1:32 PM
To: translationtransliterationirt@icann.org
Subject: [Translationtransliterationirt] T/T Update

 

Dear T/T IRT members,

 

Happy New Year! I hope you all had a relaxing holiday. 

 

I’ve had a chance to review our last call, and there’s a number of nuanced issues we need to sort out regarding the T/T WG Recommendations, ie:

• How to approach language and script tags. Some discussion was had on whether we need these at all. Which leads to…
• Requirements for gathering language data, if any. The IRT seems to be gravitating toward automated methods for detecting script. Some discussion was had on whether parties requesting transformation should bear the burden of inferring what language was entered by a registrant based on the country he/she entered into the RDS system, script used, and any other method the requesting party deems appropriate to make their transformation. 
• Reconciling the optional provisions contained within the T/T WG recommendations—especially Rec. 1—with any requirements we identify for contracted parties to gather language and script data to enable transformations. 

Some of our team is still out on holiday, so we won’t have a chance to brainstorm possible approaches and solutions to these issues until next week. Once we’ve had a chance to do so, I’ll send out a doodle poll and invite as usual. I expect our next call to take place during the week of the 16th.

 

Thanks all very much for your thoughtful contributions to this project. I look forward to our discussions this year.

 

All best,

 

Brian 

 

Brian Aitchison, MRes, PhD

Lead Researcher

Operations & Policy Research

Internet Corporation for Assigned Names and Numbers (ICANN)

12025 Waterfront Drive, Suite 300

Los Angeles, CA 90094-2536

 

Direct Line: +1 310 578 8688

Mobile: +1 424 353 9041

Email: brian.aitchison@icann.org

Skype: brian.aitchison.icann

Twitter: @BrianAitch

LinkedIn: linkedin.com/in/baitchison

www.icann.org 

 

CONFIDENTIALITY NOTICE:  This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged.  If you have received this email in error, please notify the sender by reply email and delete the message.  Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited.