UA Self-certification guide "<Email> Use Cases" notation
EAI Colleagues: Thank you for a good working group meeting today, reviewing the *EAI Readiness Self-Certification Guide*. During the discussion, I became interested in the notation "<Email> Use Cases", which occurs in 10 places in the Guide. I think I tracked this notation down to the UASG21 work, /Email Address Internationalization (EAI): Evaluation of Major Email Software and Services/, <https://uasg.tech/download/uasg-021a-eai-evaluation-of-major-email-software-...>, from 2018. Specifically, it occurs in the test cases spreadsheet, UASG021A.xlsx. That spreadsheet has a tab, "<email> use cases". The tab contains a list of email addresses, most with non-ASCII parts, to be used in tests. See also John Levine's very useful *Eaitesttools* at <https://github.com/jrlevine/eaitesttools>. So, I think the notation "<Email> Use Cases" means, the email addresses to use in tests. We now have UASG004, /Test Cases for UA Readiness Evaluation EN/ <https://uasg.tech/download/uasg-004-use-cases-for-ua-readiness-evaluation-en...>, as a source of addresses to use in tests. I proposed changes to the Guide in all 10 places where it used the notation "<Email> Use Cases". This typically was a change in the Description from wording like "This test case excludes <Email> Use Cases with a non-ASCII local part" to wording like "When testing this, use only email addresses with ASCII-only local parts". Those proposed changes are annotated in the Guide draft, ready for review at our next meeting. Happy solstice and holidays, everyone! See you in 2023 (as defined by ISO 8601). Best regards, —Jim DeLaHunt -- . --Jim DeLaHunt,jdlh@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant
Good suggestion! From: UA-EAI <ua-eai-bounces@icann.org> On Behalf Of Jim DeLaHunt via UA-EAI Sent: Tuesday, December 20, 2022 9:38 AM To: uaeai <ua-eai@icann.org> Subject: [EXTERNAL] [UA-EAI] UA Self-certification guide "<Email> Use Cases" notation EAI Colleagues: Thank you for a good working group meeting today, reviewing the EAI Readiness Self-Certification Guide. During the discussion, I became interested in the notation "<Email> Use Cases", which occurs in 10 places in the Guide. I think I tracked this notation down to the UASG21 work, Email Address Internationalization (EAI): Evaluation of Major Email Software and Services, <https://uasg.tech/download/uasg-021a-eai-evaluation-of-major-email-software-and-services-part-1-en/><https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuasg.tech%2Fdownload%2Fuasg-021a-eai-evaluation-of-major-email-software-and-services-part-1-en%2F&data=05%7C01%7Cmarksv%40microsoft.com%7C999933dbd8f342ffaec808dae2b0f176%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071546847510775%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=poQTmZdSkddDaLkBcktjnrteoMOvKXXqzigmGUrZHPI%3D&reserved=0>, from 2018. Specifically, it occurs in the test cases spreadsheet, UASG021A.xlsx. That spreadsheet has a tab, "<email> use cases". The tab contains a list of email addresses, most with non-ASCII parts, to be used in tests. See also John Levine's very useful Eaitesttools at <https://github.com/jrlevine/eaitesttools><https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjrlevine%2Feaitesttools&data=05%7C01%7Cmarksv%40microsoft.com%7C999933dbd8f342ffaec808dae2b0f176%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071546847510775%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mNrZBIIjtgd851hZrX%2Fs3mKZatGpgO5oQK4ACyVefKI%3D&reserved=0>. So, I think the notation "<Email> Use Cases" means, the email addresses to use in tests. We now have UASG004, Test Cases for UA Readiness Evaluation EN <https://uasg.tech/download/uasg-004-use-cases-for-ua-readiness-evaluation-en/><https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuasg.tech%2Fdownload%2Fuasg-004-use-cases-for-ua-readiness-evaluation-en%2F&data=05%7C01%7Cmarksv%40microsoft.com%7C999933dbd8f342ffaec808dae2b0f176%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071546847510775%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=B%2F54fEnsxZLVMu2H6yO7p3UEAvVJHJhGYd%2BGsSsscKU%3D&reserved=0>, as a source of addresses to use in tests. I proposed changes to the Guide in all 10 places where it used the notation "<Email> Use Cases". This typically was a change in the Description from wording like "This test case excludes <Email> Use Cases with a non-ASCII local part" to wording like "When testing this, use only email addresses with ASCII-only local parts". Those proposed changes are annotated in the Guide draft, ready for review at our next meeting. Happy solstice and holidays, everyone! See you in 2023 (as defined by ISO 8601). Best regards, -Jim DeLaHunt -- . --Jim DeLaHunt, jdlh@jdlh.com<mailto:jdlh@jdlh.com> http://blog.jdlh.com/<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.jdlh.com%2F&data=05%7C01%7Cmarksv%40microsoft.com%7C999933dbd8f342ffaec808dae2b0f176%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071546847510775%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zkkE6gfAcarbkhne6pJsDHHxD3MOQUmLGn33yQoe6TM%3D&reserved=0> (http://jdlh.com/<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjdlh.com%2F&data=05%7C01%7Cmarksv%40microsoft.com%7C999933dbd8f342ffaec808dae2b0f176%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071546847510775%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=70WXsXQzZ8xD0e0VpmLqebO45Hf6hHcMCksaQLxTKok%3D&reserved=0>) multilingual websites consultant
participants (2)
-
Jim DeLaHunt -
Mark Svancarek (CELA)