Seda: Now that the Community Update is completed, how should we go about contributing to the content for the Self Certification Guide session? On 2023-02-21 09:25, Seda Akbulut via UA-EAI wrote:

Dear EAI WG members,

Attached please find:

1. … 2. Slide template for you to start planning the ICANN76 EAI Self Certification Guide session. I have also upload this file to the Google drive so that you can collectively work on the slide here: https://docs.google.com/presentation/d/12AsOAP8RSjcE6J_tMLbIjPv9vt4CadoS/edi... <https://docs.google.com/presentation/d/12AsOAP8RSjcE6J_tMLbIjPv9vt4CadoS/edi...>

Please find the details of that session here: https://icann76.sched.com/event/1J2M8/universal-acceptance-new-international....

We can continue on this work in our next meeting.

I don't see how I can add comments to a Google Presentation the way I can comment on a Google Doc, so let me just write some comments here. *Who is our audience?* I guess that we will have only ICANN folks in our audience. This means: 1. They likely are all email users, and some run email systems for their organisations. 2. They likely are not email system developers. 3. They have probably heard of UA in general before. *What are the goals for the presentation?* I suggest we want them to: 1. Know that the Self Certification process is coming into existence, and roughly what it is. 2. Get them thinking about taking on the role of email system buyer, and what level of EAI support they would want to buy. 3. Know how to find out more when they want to, and what they should tell their email system vendor about how to self-certify. 4. Spread the word that the path to better EAI support goes through customers asking for Silver, Gold, or Platinum certification, and vendors announcing their products' Silver, Gold, or Platinum certification. *Comments on content* Looking at the existing slides, here are some comments Instead of "Email Address Internationalization (EAI) Overview", make this part of the talk, "Why EAI Self Certification?" . Some points to include: * The goal: improve EAI adoption by activating market forces * EAI overview: all email addresses work, even globally inclusive ones o Silver medal success: I am <Lee@example.com> (limited Latin address), but I can exchange email with <जिम@डाटामेल.भारत> (globally inclusive address) o Gold medal success: I am <जिम@डाटामेल.भारत>, and can exchange email with anyone. * The problem: EAI support is invisible in the marketplace o (Show screenshots of product pages like Exchange 365, Datamail, Coremail, Apple Mail, and point out that they don't say clearly "we let you exchange email with globally inclusive addresses", "we let you host globally inclusive email addresses". o Customer: how does customer explain that they want to use globally inclusive email addresses? o Customer: how does customer know that vendor's product supports globally inclusive email addresses well enough? o Part of the problem is that we lack phrases which mean "EAI support" in specific, useful ways * The solution: EAI Certification levels o We define phrases which mean "EAI Support": "Silver", "Gold", and "Platinum". o We publish a detailed "EAI Self Certification Guide" document which tells vendors how to test their own products. o It is *self-*certification, because we don't have resources to do the testing for vendors. So vendors test themselves. o We have a process by which vendors can ask UASG for help with testing technique, and can tell UASG what their rating is. * Current status of EAI Certification o We have defined phrases and support levels. o "EAI Self Certification Guide" document is solid draft. Getting reviewed. Some early adopters are using it. o We are setting up the process for UASG to support vendors who are self-certifying. I think we don't need the slides on the UA vision. I expect that most of the audience has heard it before, and we have other documents for explaining it. Let's not take time on such basics. I think we don't need the slide "UA Scope and Categories Impacted". We don't have a use for terms like "Unicode@ASCII" later in the talk. We don't need to talk about the 5 UA verbs. I like what the slide "Call for action" is trying to do. I think the above bullet points will explain it more clearly. Instead of "Introduction to the Guide", I suggest broadening it to "Introduction to EAI Self Certification" * Do not attempt to explain every section and every test in the Guide document. It is too long for that. * Start by explaining the self-certification process which we want to set up. What the vendor does, what UASG does. * Give overview of what is in the Guide.  Say that it is a technical document, with detailed instructions on what tests vendor engineers should perform. * Do include the present slide "Defining EAI-Readiness Levels", describing the certification levels: Silver, Gold, Platinum. * Give one or two examples of tests in the Guide, so that people have an idea of its flavour. * Include a link to a draft of the Guide, or at least instructions on how to ask for a copy. * One slide on the spreadsheet for turning test results into a single rating. Having feedback from the Early Adopters is a good idea. I suggest making a time budget, and giving each early adopter a time limit to present their comments. Having a Q&A section is a good idea. I suggest budgeting 30% of the total time for Q&A. I think it would be good to have a Closing section. * One slide of "Call to Action" for the audience. * Summary of the presentation. * Slide with instructions on who to contact, what to do to get more information or to contribute I suggest having a time budget. It looks like the schedule gives us 75 minutes. I would suggest: * 5 minutes on welcome and getting started. Budget 2-4 slides. * 8 minutes on "Why EAI Self Certification?". Budget 6-8 slides. * 14 minutes on "Introduction to EAI Self Certification". Budget 10-13 slides. * 8 minutes for each early adopter's comments + 1 mins overhead = 25 minutes. Budget 5-6 slides each. * 20 minutes on Q&A. * 3 minutes on closing. Budget 3 slides. My rule of thumb is 1 minute of presentation time per slide. But that is for English-only presentations in person. Given the simultaneous translation and use of remote conferencing, maybe 1.2 minutes per slide is safer. That gives the slide budget I listed above. Of course we could add more slides, but I suspect we won't have time to actually talk about them. And, section title slides are not included in these budgets. It may be that our audience will not ask many questions. In that case, what has sometimes worked well for me is to have extra slides. One extra slide topic might be an audience survey: If you were buying a new email system today, would you ask for a Silver, or Gold, or Platinum product, or would you not ask for EAI support? How many percent more would you pay for that level? Why? One extra slide topic might be audience feedback on terminology: give them a slide with the various terms for old and new email addresses, e.g. "limited Latin" and "globally inclusive", "ASCII" and "Unicode", etc. Ask the audience which terms the recommend that UASG should adopt. I hope that is helpful. I welcome the discussion to follow. Best regards,     —Jim DeLaHunt -- . --Jim DeLaHunt,jdlh@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant