Fields affecting downstream apps, may need to constrain the characters used.

[thorwolpert]

Some downstream / partner integrations support limited character sets.

For example the BN service from the Federal Gov't will not accept the full UTF8 character set for names.

Some work needs to be done to determine what that character set is.

Character set CP863 is a Canada char set, and while a subset of ISO-8859-15 it is still too broad.

The valid charset under legislation is English and French, so it may be the following set of chars

ascii_lowercase 'abcdefghijklmnopqrstuvwxyz'
ascii_uppercase 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'
digits '0123456789'
punctuation !"#$%&'()*+,-./:;<=>?@[]^_`{|}~.
whitespace ' '
french_lower 'œàâçèéîïùûê'
french_upper 'ŒÀÂÇÈÉÎÏÙÛÊ'

[jdyck-fw]

Wael Helal (IT Ops) spoke to this being an issue during the Stakeholder Demo this week. Thor suggested that we may want to slip this in before we go live with having another set of corps on-boarded.

I'll bring this up at PO sync unless you see a better path forward for it @Kaineatthelab & @lmcclung

[sienna-oldaccountdontuse]

Linda messaged Michael Kagis for more info

[whelalbc]

'#' is not accepted by CRA in address fields while '-' is.

[jdyck-fw]

Added you as the assignee since it sounds like you will have more to add to it, Linda.

[thorwolpert]

@whelalbc I think there are lots of chars to watch, I'm not even sure the French additions will work everywhere.
Names used to be constricted to only ascii.

But I know FN chars are on the horizon and current citizens have things like ! (not pronounced like *nix folks would say bang, but as one of several different tongue clicks) so we should do our best to support as much as we can.

I'm surprised # isn't allowed as I can certainly see someone grabbing a DBA with a trendy hashtag.

[severinbeauvais]

So how do we move ahead on this? Should we do something in the UIs to prevent the entry of invalid chars? And who's the right person to determine what chars the Fed Gov BN service will accept?

[whelalbc]

Home Team BA’s can reach out to CRA. My experience with this issue is straight ASCII, not extended ASCII to 256 just the 128. For example I have seen à (ASCII 194) accepted but not  (ASCII195). Our database isn’t great at accepting French characters either. Wael Helal Supervisor, IT Operations Support Registries and Online Services, Service BC Ministry of Citizens’ Services T: 250-952-0568 | Web: http://www.servicebc.gov.bc.ca<http://www.servicebc.gov.bc.ca/> “Access to government services made easy” From: Séverin Beauvais ***@***.***> Sent: March 10, 2022 2:09 PM To: bcgov/entity ***@***.***> Cc: Helal, Wael CITZ:EX ***@***.***>; Mention ***@***.***> Subject: Re: [bcgov/entity] Fields affecting downstream apps, may need to constrain the characters used. (#7957) [EXTERNAL] This email came from an external source. Only open attachments or links that you are expecting from a known sender. So how do we move ahead on this? Should we do something in the UIs to prevent the entry of invalid chars? And who's the right person to determine what chars the Fed Gov BN service will accept? — Reply to this email directly, view it on GitHub<https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgh.neting.cc%2Fbcgov%2Fentity%2Fissues%2F7957%23issuecomment-1064553034&data=04%7C01%7Cwael.helal%40gov.bc.ca%7C6bbfd67a12614537999708da02e2a229%7C6fdb52003d0d4a8ab036d3685e359adc%7C0%7C0%7C637825469645410866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=OnL4KU018z7je2Mvo6XsyrYz%2FYjP8TcB6VBRq%2F0TKng%3D&reserved=0>, or unsubscribe<https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgh.neting.cc%2Fnotifications%2Funsubscribe-auth%2FAKDNEJ6KRNFPIQYW42E2H23U7JXJFANCNFSM462U7T5Q&data=04%7C01%7Cwael.helal%40gov.bc.ca%7C6bbfd67a12614537999708da02e2a229%7C6fdb52003d0d4a8ab036d3685e359adc%7C0%7C0%7C637825469645410866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=5ZByLlexcU5d3C0Mh2Xe1rYLo81K3uSR4f%2FGca86uak%3D&reserved=0>. Triage notifications on the go with GitHub Mobile for iOS<https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Cwael.helal%40gov.bc.ca%7C6bbfd67a12614537999708da02e2a229%7C6fdb52003d0d4a8ab036d3685e359adc%7C0%7C0%7C637825469645410866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=noEjAqcO9HhqDmSi7ZdXj7IcePwgjbRN%2BNjsX4upRzA%3D&reserved=0> or Android<https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Cwael.helal%40gov.bc.ca%7C6bbfd67a12614537999708da02e2a229%7C6fdb52003d0d4a8ab036d3685e359adc%7C0%7C0%7C637825469645410866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=d2kxipQumS9F1VU8Cy4Zg44DepwpXaei0R%2Fmw9pGCow%3D&reserved=0>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>