October 2016 - UA-discuss - lists.iana.org

Lars Steffen takes on Community Outreach co-ordination role
by Ram Mohan Oct. 14, 2016

Oct. 14, 2016

Dear UA friends, I’m very pleased to announce that Lars Steffen has agreed to be a co-coordinator for the Community Outreach part of our work. Lars has already done a lot for UA, and I look forward to having Lars bring his energy and enthusiasm to moving the Universal Acceptance work onwards and forwards. Please join me in welcoming Lars to his enhanced responsibilities. -Ram Chair, Universal Acceptance Steering Group ------------------------------------------------------------------------------ Ram Mohan o: +1.215.706.5700 x103; m: +1.215.431.0958; f: +1.215.706.5701 Skype:gliderpilot30 |(a)rmohan123|www.linkedin.com/in/rmohan

2 1

Re: [UA-discuss] UA-discuss Digest, Vol 21, Issue 18
by Harish Chowdhary Oct. 5, 2016

Oct. 5, 2016

Hi All,Yes,it may be possible that it may take another 15+ years to resolve all the issues of UA.However, there is recent positive development in India regarding the same.It is  about  the launch of Countries First Make in India IDN based Mobile Email Services on 10th Oct 2016As per the recent announcement of XgenPLUS:XgenPlus is proud to share with you that we have developed Countries first made in India "client-side" implemented mobile app of non-Latin, character-based Internationalized Domain Name (IDN) email to support countries Digital India Mission in various local/regional languages which means client can have email ID in Hindi (हिंदी), Gujrati (ગુજરાતી), Urdu (اردو), Punjabi (ਪੰਜਾਬੀ ਦੇ) , Tamil (தமிழ்), Telgu (తెలుగు), Marathi (मराठी) and lot more.They are launching Country's First Make in India IDN based Mobile Email Services with the name DATAMAIL .It a mileston! e, in pursuit of  complete UA.Thanks,Harish ChowdharyFrom: ua-discuss-request(a)icann.orgSent: Fri, 30 Sep 2016 17:30:11To: ua-discuss(a)icann.orgSubject: UA-discuss Digest, Vol 21, Issue 18Send UA-discuss mailing list submissions to   ua-discuss(a)icann.orgTo subscribe or unsubscribe via the World Wide Web, visit   https://mm.icann.org/mailman/listinfo/ua-discussor, via email, send a message with subject or body 'help' to   ua-discuss-request(a)icann.orgYou can reach the person managing the list at   ua-discuss-owner(a)icann.orgWhen replying, please edit your Subject line so it is more specificthan "Re: Contents of UA-discuss digest..."Today's Topics:  1. Re: Some universal acceptance problems last 15+   years...     (Richard Merdinger)  2. IDNs & i18n (Andre Schappo)----------------------------------------------------------------------Message: 1Date: Th! u, 29 Sep 2016 16:47:32 +0000From: Richard Merdinger <rmerdinger@go daddy.com>To: Ram Mohan <rmohan(a)afilias.info>, Kurt Pritz <kurt(a)kjpritz.com>Cc: ua-discuss <UA-discuss(a)icann.org>Subject: Re: [UA-discuss] Some universal acceptance problems last 15+   years...Message-ID: <BCDB84B0-0CF7-4E5B-AF20-F2527A2A68E9(a)godaddy.com>Content-Type: text/plain; charset="utf-8"As we look at outreach and efforts to accept issue reports and loop-close on reported issues, it will be extremely useful to include links to materials that will enable bosses to send to their engineering teams saying?hey, do it like this.--RichFrom: <ua-discuss-bounces(a)icann.org> on behalf of Ram Mohan <rmohan(a)afilias.info>Date: Thursday, September 29, 2016 at 3:03 AMTo: Kurt Pritz <kurt(a)kjpritz.com>Cc: ua-discuss <UA-discuss(a)icann.org>Subject: Re: [UA-discuss] Some universal acceptance problems last 15+ years...I blame it on the culture, and on the humans who enable it. Agree that it's not *just* the pro! grammer's fault, although in your example below, he must have been semi sedated to write code that catches a non 3/4 character tld, and then pop up an error message; so inefficient :)It's literally no extra work to change a regular expression match in code. It's a kind of laziness combined with apathy that drives this.Some developers depend on a dns lookup to determine a valid tld, while others lookup a static list. Poor programming choices, much heartbreak lies in those directions, too.RamOn Sep 29, 2016 2:51 PM, "Kurt Pritz" <kurt@kjpritz.com<mailto:kurt@kjpritz.com>> wrote:Ram:I wouldn't necessarily blame it on the programmer:Boss: Hello young man. We have a bit of a problem to solve. Some of our web site users are mis-typing their email addresses. When different government departments need to get hold of them to correct an error on a form they submitted, we cannot. These government departments want us to do a check on their email ad! dresses to at least make sure they are the right format and allowable content.Programmer: Sure thing. What's our budget for this?Boss: Zero.So, semi-smart solution for no budget.Kurt________________Kurt Pritzkurt@kjpritz.com<mailto:kurt@kjpritz.com>+1.310.400.4184<tel:%2B1.310.400.4184>Skype: kjpritzOn Sep 29, 2016, at 12:32 PM, "Jiankang Yao" <yaojk@cnnic.cn<mailto:yaojk@cnnic.cn>> wrote:Dear Ram,  I think that you can be titled as UA pioneer.Another 15+ years are needed for UA work.________________________________Jiankang YaoFrom: Ram Mohan<mailto:rmohan@afilias.info>Date: 2016-09-29 01:50To: UA-discuss<mailto:UA-discuss@icann.org>Subject: [UA-discuss] Some universal acceptance problems last 15+ years...On Sep 12, 2001, I helped launch the first non 2/3 character TLD, .INFO. Many of you have heard about how we struggled to get applications, browsers, web forms and email systems to recognize the world?s first four-character TLD as a legitimate extension, including my creation of the Offic! e of the CTO (in a 3 person startup) to get large companies to return my calls.Well, 15+ years later, today I was on the website of the Pennsylvania state government, and filled in my email address (ending in .INFO). I hit submit, and here is the prompt that came up. I hit OK, and the site accepted my email and I moved forward with my tasks, but it?s galling that some programmer _recently_ decided that a non 2/3 character TLD based email address merited a warning message.<image001(09-29-10-27-48).png>Goes to show how long bad habits persist. Also goes to show why the UASG?s work is important.-Ram------------------------------------------------------------------------------Ram MohanExecutive Vice President & CTOAfilias |Ireland|Canada|USA|India|Chinao: +1.215.706.5700 x103<tel:%2B1.215.706.5700%20x103>; m: +1.215.431.0958<tel:%2B1.215.431.0958>; f: +1.215.706.5701<tel:%2B1.215.706.5701>Skype:gliderpilot30 |(a)rmohan123|www.linkedin.com/in/rmohan<! http://www.linkedin.com/in/rmohan>-------------- next part -------- ------An HTML attachment was scrubbed...URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20160929/19d0886d/attachment-0001.html>------------------------------Message: 2Date: Fri, 30 Sep 2016 09:55:16 +0000From: Andre Schappo <A.Schappo(a)lboro.ac.uk>To: ua-discuss <UA-discuss(a)icann.org>Subject: [UA-discuss] IDNs & i18nMessage-ID: <92B3C736-8906-4742-A895-CF9755997843(a)lboro.ac.uk>Content-Type: text/plain; charset="utf-8"My focus in this email will be IDNs and Internationalisation.As I have previously stated, a fundamental problem is the lack of Internationalisation in University Computer Science teaching. Computer Science departments are still dominated by 7bit ASCII text processing. There should be in depth study and practice of Unicode text processing in Computer Science departments. Students graduating from such ASCII cultures will not have the skills necessary to properly implement IDNs. Even worse they will not even think abo! ut non ASCII text and how to design systems that will process non ASCII text. So the UA problem, along with lots of other problems, are embedded into systems right from the start.Unicode is a part of internationalisation of Computer Science. For years I have been encouraging Computer Science educators to internationalise their teaching with little success.I recently changed my tactics. There are groups that promote "Internationalisation of the Curriculum" i.e. all curricula and not just Computer Science. I am reaching out to some of these groups and maybe UASG should also reach out to these groups. I have written an initial short blog article ? http://schappo.blogspot.co.uk/2016/09/computer-science-curriculum.htmlI have not yet had much response from the groups I have contacted but it is still early days.When I get time I will write further blog articles i.e.? advantages of internationalising Computer Science teaching? the negative consequences of not internationa! lising Computer Science teaching ? one of these being the lack of supp ort for IDNs and EAI in so many systemsWe need every Computer Science student to graduate with an understanding of internationalisation and hence Unicode and hence IDNs. We need this critical mass. I am one of few.Andr? Schappo-------------- next part --------------An HTML attachment was scrubbed...URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20160930/b19eda81/attachment-0001.html>------------------------------_______________________________________________UA-discuss mailing listUA-discuss@icann.orghttps://mm.icann.org/mailman/listinfo/ua-discussEnd of UA-discuss Digest, Vol 21, Issue 18****************************************** ------------------------------------------------------------------------------------------------------------------------------- [NIXI is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/nixiindia & Twitter: @inregistry ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. -------------------------------------------------------------------------------------------------

3 3

Program for Face to Face meeting of UASG Coordination Group - October 11 & 12, Washington, DC - USA
by Don Hollander Oct. 4, 2016

Oct. 4, 2016

Please find attached the program for the forthcoming meeting of the UASG Coordination Group. If there are particular sections that you would like to participate in remotely, please let me know and I’ll try to provide a head’s up if we’re not running to time. If you are planning on attending in person, would you please let me know. And, of course, if you have any questions or comments, let me know those too. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

1 0

Some universal acceptance problems last 15+ years...
by Ram Mohan Oct. 4, 2016

Oct. 4, 2016

On Sep 12, 2001, I helped launch the first non 2/3 character TLD, .INFO. Many of you have heard about how we struggled to get applications, browsers, web forms and email systems to recognize the world’s first four-character TLD as a legitimate extension, including my creation of the Office of the CTO (in a 3 person startup) to get large companies to return my calls. Well, 15+ years later, today I was on the website of the Pennsylvania state government, and filled in my email address (ending in .INFO). I hit submit, and here is the prompt that came up. I hit OK, and the site accepted my email and I moved forward with my tasks, but it’s galling that some programmer _*recently*_ decided that a non 2/3 character TLD based email address merited a warning message. Goes to show how long bad habits persist. Also goes to show why the UASG’s work is important. -Ram ------------------------------------------------------------------------------ Ram Mohan Executive Vice President & CTO Afilias |Ireland|Canada|USA|India|China o: +1.215.706.5700 x103; m: +1.215.431.0958; f: +1.215.706.5701 Skype:gliderpilot30 |(a)rmohan123|www.linkedin.com/in/rmohan

10 17

Re: [UA-discuss] Language - how do you refer to non-ASCII to a non-technical audience?
by Naomi Pearce Oct. 3, 2016

Oct. 3, 2016

I keep tripping up on referring to language being "non-" something. Here's why. If I ask you to think of an elephant that isn't blue, what's the first thing you think of? Often, it's a blue elephant first, then one works to get to non-blue. In sports, coaches deal with this all the time. For example, if a coach tells a baseball pitcher to avoid pitching low and inside, sure enough, the tendency will be low, or inside. Therefore, the coach is the one who has to do the translation of what it is they actually want, rather than what they don't want -- in the example, to pitch to the outside, or to pitch higher. [Feel free to adjust the example to any sport, or coached activity, that you like.] In our case, I ask myself if it would be better to focus on what the language is, rather than isn't. That's where it gets challenging. A half-step would be talking about languages 'beyond' English. It still has a fair amount of the blue-elephant problem. I think 'domains in world languages' is heading in the right direction, though it's a tad dense in that I have no idea what a 'world language' is unless I mentally work really hard. Ergo, some brainstormed notions below... take what you need and leave the rest. On 7/22/16 at 12:41 PM, jothan(a)jothan.com (Jothan Frakes) wrote: >Not sure if 'domains in world languages' In case any of these suggestions or ideas resonate, how about: 'domains in all languages' 'domains in all written languages' 'domains in every language' 'domains in any major language' 'domains in any language used in the world' 'domains in most major languages' 'domains in many kinds of languages' 'domains in various languages used in the world' 'domains in the native languages used in the world' 'domains in native languages' 'domains in local languages' Just thoughts... -- TTFN, tah tah for now, Naomi Pearce Pearce Communications 510/528-0824 *********************************************************** "Any fool can farm flatland!" -- Walter Camp ***********************************************************

6 10