This repository contains some QR codes which special cases which needs special handling during the CBOR Decoding/JSON Processing.
| Description | Occurence | Verifier Action | Issuer Action | QR Code |
|---|---|---|---|---|
| Whitespaces in decoded JSON fields | GR/EL QR Vaccination Codes in Field "mp" | During the CBOR Deserialization, all fields MUST be trimmed for whitespaces. | Issuers MUST trim for whitespace before issuing. | |
| Date of Birth with invalid pattern | BG QR Codes | If the schema is validated during the verifiying, the DOB regex should be ignored. Date/datetime formats should be ignored as well. | The generated QR Code should be deserialized after generation and checked against the schema. |  |
| Dates with invalid Pattern | BG QR Codes in dob field, PL codes in other date fields | Date/datetime formats should be ignored. | The generated QR Code should be deserialized after generation and checked against the schema. |  |
| t,v,r Entries have null values | BG QR Codes for v/t/r | Schema validation should check for ["null","array"]. "One of" should be ignored. | The generated QR Code should be deserialized after generation and checked against the schema. |  |
| Negative doses/Invalid Doses | LV QR Code in Vaccination Certificate (not productive, problem fixed) | Number of doses has in schema a min/max value. Verifiers should remove this limit to accept any kind of doses. | The generated QR Code should be deserialized after generation and checked against the schema. | |
| "null/nil/undefined" values in CBOR | Several QR Codes. Problem occurs when the JSON schema is just used to generate Objects which are filled and serialized later without additional schema validation (JSON creation not performed). | All verifiers should add to schema ["null",{DataType}] or remove null/undefined during the cbor deserialization. | All serializers which are used, must be configured/tested to omitting null values to CBOR. A addtional schema validation can avoid this problem. |  |
| Standardized Name fields (fnt/gnt) with special signs | Several QR Codes | Verifiers should remove pattern checks. Accept any string. | Issuer must strictly check for pattern after the serialization to CBOR. |  |
| Escaped characters in CBOR content | HU/UA QR Codes | Verifiers should escape " correctly with \" otherwise the JSON parsing fails. | Issuers should avoid the usage of JSON special signs, because not all CBOR implementations deserialize directly. |  |
| QR Code contains Version 1.3 Schema, but field "dr" is empty string and as optional in the Test QR Code | NL Test QR Codes | Verifiers should remove all date format checks from date-time values/dates | Issuer MUST avoid additional fields. Add "additionalFields=false" to the Schema for validation of issued QRs |  |
| Interpretation of Validity Dates has a different model. Maximum Lifetime is longer than the validUntil Date. Time Range can be greater than 180 Days. This can lead to an rejection in cause of the 180 days limits for recovery | AT REC Codes | A verifier should check if a holder is in the 180 Day Time Window, instead of checking maximum validity of 180 days. | TBD |  |
| Multiple vaccination events | ES Vaccination Codes | Verifiers shall reject such codes as they do not conform with the specification | Issuers shall ensure one event per DCC |  |
| dn / sd are floats instead of int | IE Vaccination Codes | Verifiers should accept whole number floats (ie 1.0, 2.0) | Issuers should ensure that dn / sd are int values in the CBOR |  |