<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Jean:</p>
<p>And you shall have a link to my content, once I write it.</p>
<p>In case my previous message wasn't clear: what I have now is a
proposal only. It is an abstract for a presentation to fill a
50-minute time in a conference in October 2016. I will wait for
the program committee to decide whether to accept this proposal.
If they do, I will then write the actual content. <br>
</p>
<p>And, there will be plenty of time over the summer for UASG
colleagues to review and improve the presentation, if you wish.
The final presentation, licenced under CC-By or the like, will be
available at the time of the conference.<br>
--Jim DeLaHunt<br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-03-24 02:03, Jovenet Consulting
wrote:<br>
</div>
<blockquote
cite="mid:CAMCGQ+_cCuQS2mpO+JOZc2hd-MWfe8L02C8Ngrh1HTZZKsm-Pg@mail.gmail.com"
type="cite">
<div dir="ltr">Hello Jim,
<div>To do the promotion of this to "new gTLD followers"
(LinkedIn new gTLd group, gtld.club, Newlsetter), I need a
link to your content.</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Mar 24, 2017 at 9:12 AM, Jim
DeLaHunt <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jfrom.uasg@jdlh.com" target="_blank">jfrom.uasg@jdlh.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hello, UA colleagues:</p>
<p>Two weeks ago we had a thread about my interest in
seeing Universal Acceptance proposals submitted to the
41st Internationalization and Unicode Conference
(IUC41). Based on that discussion, I am working on a
proposal for a 50-minute presentation. I'd like to run
these by you for your information. I appreciate any
feedback you have.</p>
<hr size="2" width="100%">
<p><b>Presentation title</b>: Universal Acceptance of
non-Latin email addresses and domain names: how does
your framework rate?</p>
<p><b>Abstract</b>:</p>
<p>The next one billion internet users use a wide variety
of languages and scripts. They will demand email
addresses, and domain names, in scripts they can easily
read. App development frameworks, libraries, and
programming languages on all platforms will be called on
to meet this challenge. This is Universal Acceptance
(UA) — of all domain names and email addresses, from <a
moz-do-not-send="true"
class="m_2345364732526976345moz-txt-link-freetext"
href="http://%E6%99%AE%E9%81%8D%E6%8E%A5%E5%8F%97-%E6%B5%8B%E8%AF%95%E3%80%82%E4%B8%96%E7%95%8C"
target="_blank">http://普遍接受-测试。世界</a> [simplifed
Chinese] to مانيش @ أشوكا. الهند [arabic] to
données@fußballplatz.<wbr>technology [latin non-ASCII].
We present technical compliance criteria, a list of
problem areas, and ways to evaluate compliance. We give
our compliance findings so far. Does your library and
platform provide Universal Acceptance? <br>
<br>
Universal Acceptance is a foundational requirement for a
truly multilingual Internet, one in which users around
the world can navigate entirely in local languages. It
is also the key to unlocking the potential of new
generic top-level domains (gTLDs) to foster competition,
consumer choice and innovation in the domain name
industry. To achieve Universal Acceptance, Internet
applications and systems must treat all TLDs in a
consistent manner, including new gTLDs and
internationalized TLDs. Specifically, they must accept,
validate, store, process and display all domain names
and email addresses.<br>
<br>
This talk presents a compliance review plan, for the
programming languages and frameworks with which
applications are built. It has a list of UA features to
check, and gives reference correct results. Application
developers can use these tests to be sure the tools they
use afford Universal Acceptance. Framework developers
can use these tests to be sure that they provide access
to the right scope of Universal Acceptance
functionality, and that it works well. There is a
complementary compliance review plan of application
features, which we will also look at.<br>
<br>
This compliance review plan are the work of the
Universal Acceptance Steering Group (<a
moz-do-not-send="true"
class="m_2345364732526976345moz-txt-link-freetext"
href="https://uasg.tech/" target="_blank">https://uasg.tech/</a>).
An ICANN project, the UASG is a community-based team
working to share this vision for the Internet of the
future with those who construct this space: coders. The
group’s primary objective is to help software developers
and website owners understand how to update their
systems to keep pace with an evolving domain name system
(DNS).<br>
<br>
The UASG has done its own compliance evaluation for
selected frameworks and programming languages. We will
go over these results. <br>
<br>
This talk is complementary with Dr Ajay Data's
presentation on Data Xgen's experience developing email
services with non-Latin email addresses and domain
names. <br>
<br>
This talk is suitable for product owners, application
developers, programming language and framework
developers, testers, domain registars, email hosting
companies, management, and developers. Plus, anyone who
looks forward to using email addresses and domain names
in non-Latin scripts will find this evaluation of
interest.</p>
<p>[Note: I plan to base this mainly on the contents of
"Reviewing programming languages and frameworks for
compliance with Universal Acceptance good practice"]</p>
<p><b>Ram and other leaders</b>: Is it all right for me to
identify myself as a member of UASG, and this talk as
being a UASG presentation, and use the UASG templates?
I don't mind just proposing an individual talk, but I
think having the UASG branding would be stronger.<br>
</p>
<hr size="2" width="100%">
<p>I am also working on a proposal for a 1.5 hour
tutorial. <br>
</p>
<p><b>Tutorial Title</b>: Domain names and email addresses
aren't just ASCII anymore. Now what?</p>
<p><b>Tutorial Concept</b>: Explain IDN and EAI, and their
implications, for an audience that doesn't know either.
The next billion internet users. Explain Punycode and
how it's the ASCII labels that are registered. Show the
thousands of gTLDs, and how to get the current list.
Talk about policy issues like joint registration. Talk
about confusables, as a security issue and a trademark
issue. Introduce UASG and other groups working on these
issues. Review the portfolio of UASG materials and how
participants can apply them, both to the software they
developed, and to that they procure.<br>
</p>
<p>I think the tutorial extends beyond UASG, so I'm
leaning towards presenting it as an individual tutorial.</p>
<p>N.B. It's my practice to freely licence my presentation
materials with CC-BY, so they will be available for
others to re-use. <br>
</p>
<p>Also, as alluded to above, I understand that Dr Ajay
Data has proposed a presentation on Data Xgen's
experience developing email services with non-Latin
email addresses and domain names. I think this will be
interesting by itself, and even better in combination
with the UASG material in my proposal.</p>
<p>Who knows whether the program committee will accept any
of these proposals? They will give us their answer
towards the end of April.</p>
<p>One final reminder: if anyone else wants to propose a
talk, 24. March is the deadline! Details at <<a
moz-do-not-send="true"
href="http://www.unicodeconference.org/call-for-participation.htm"
target="_blank">http://www.unicodeconference.<wbr>org/call-for-participation.htm</a><wbr>>.<br>
</p>
Once again, your feedback is welcome. Best regards,<br>
--Jim DeLaHunt<span class="HOEnZb"><font
color="#888888"><br>
<br>
<pre class="m_2345364732526976345moz-signature" cols="72">--
--Jim DeLaHunt, <a moz-do-not-send="true" class="m_2345364732526976345moz-txt-link-abbreviated" href="mailto:jdlh@jdlh.com" target="_blank">jdlh@jdlh.com</a> <a moz-do-not-send="true" class="m_2345364732526976345moz-txt-link-freetext" href="http://blog.jdlh.com/" target="_blank">http://blog.jdlh.com/</a> (<a moz-do-not-send="true" class="m_2345364732526976345moz-txt-link-freetext" href="http://jdlh.com/" target="_blank">http://jdlh.com/</a>)
multilingual websites consultant
355-1027 Davie St, Vancouver BC V6E 4L2, Canada
Canada mobile <a moz-do-not-send="true" href="tel:%28604%29%20376-8953" value="+16043768953" target="_blank">+1-604-376-8953</a>
</pre>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr"><img moz-do-not-send="true"
src="https://docs.google.com/a/jovenet.consulting/uc?id=0B91jcpmB98eCWnhQTmZIdWVDNFU&export=download"
width="96" height="39"><br>
<div><br>
</div>
<div><b>Jean Guillon</b></div>
<div><a class="moz-txt-link-abbreviated" href="mailto:contact@jovenet.email">contact@jovenet.email</a></div>
<div><span style="font-size:12.8px">Phone: +33.631109837</span></div>
<div><a moz-do-not-send="true"
href="http://www.jovenet.consulting" target="_blank">www.jovenet.consulting</a></div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--Jim DeLaHunt, <a class="moz-txt-link-abbreviated" href="mailto:jdlh@jdlh.com">jdlh@jdlh.com</a> <a class="moz-txt-link-freetext" href="http://blog.jdlh.com/">http://blog.jdlh.com/</a> (<a class="moz-txt-link-freetext" href="http://jdlh.com/">http://jdlh.com/</a>)
multilingual websites consultant
355-1027 Davie St, Vancouver BC V6E 4L2, Canada
Canada mobile +1-604-376-8953
</pre>
</body>
</html>