-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICAO Implementation differs from test implementation #209
Comments
This is a bug. Dots should be omitted. I will forward it to our devs. |
Hi @jona7o , I'm following issues with ICAO transliterations as it causes problems when there's a mismatch of associating DCCs to one person by their standardized names.
what do you mean concretely? Your repsonse could help to move on in the issue of harmonizing ICAO transliterations across different implementations in the overall-workflow of DCCs associated with TSI (RAT portal & backend API partners), and Ubirch: corona-warn-app/cwa-quick-test-frontend#185 (comment) Thanks very much in advance, |
Hi,
we are a software development company with a product for COVID19 test- and vaccination centers. For this use case we create both, vaccination certificates over ubirch/ibm api and test certificates over the cwa endpoint. Today I found a miss match between these two certificates for the same input.
I think this bug is located in the ubirch/ibm api because i think the dot char "." is not specified for a machine readable string and gets replaced by nothing and not with an "<" char. If it is defined this is a bug in the reference implementation of the cwa. I'll open these requests in both github repositorys and link each other. Could someone clarify which implementation is correct?
Example for Vaccination certificates with Ubirch/IBM API:
"fn": "Dr. Mustermann",
"gn": "Max",
"fnt": "DR<<MUSTERMANN",
"gnt": "MAX"
Example for Test over CWA API
"fn": "Dr. Mustermann",
"gn": "Max",
"fnt": "DR<MUSTERMANN",
"gnt": "MAX"
Regards, Tobias
corona-warn-app/cwa-quicktest-onboarding#68
The text was updated successfully, but these errors were encountered: