Skip to content

Build with DPP-CAR-002 v3; describe how the Nu Html Checker is updated - #33

Merged
fabianekc merged 1 commit into
mainfrom
car002-v3
Oct 26, 2026
Merged

fabianekc merged 1 commit into
mainfrom
car002-v3

Conversation

@fabianekc

Copy link
Copy Markdown
Member

DPP-CAR-002 version 3

The image is built with the dpp-criteria commit that brings DPP-CAR-002 version 3:

  • the warning says that the GTIN of the GS1 Digital Link carries the GS1 prefix 952 (before, it stated the expectation and read as if the prefix were missing);
  • the prefix is also found in a GTIN-8, unpadded or padded to 12, 13 or 14 digits.

dpplint itself does not change. The integration test now checks the wording of the warning and adds a GTIN-8 padded to 14 digits.

Updating the Nu Html Checker

The README, section "Deployment", now says:

  • How often: the digest of the checker is compared with the latest release once a month, and at once when a security notice concerns the checker or its image.

  • How:

    1. Write the new digest into the manifest and into the README of the test vectors.
    2. Record the answers to the test vectors again and run the test suite.
    3. Check the example passports with the new checker before the manifest is applied.

    The dpplint image does not change for this.

kubernetes/deployment.yaml names the digest of the new dpplint image.

The image is built with the dpp-criteria commit in which the warning of
DPP-CAR-002 says that the GTIN carries the GS1 prefix 952 and the prefix is
also found in a GTIN-8. The integration test checks the wording of the
warning and a GTIN-8 padded to 14 digits.

The README says how often the digest of the Nu Html Checker is compared with
the latest release and how the checker is updated: new digest in the
manifest, the answers to the test vectors recorded again, the example
passports checked with the new checker.
@fabianekc
fabianekc merged commit 4311fc6 into main Oct 26, 2026
2 checks passed
@fabianekc
fabianekc deleted the car002-v3 branch October 26, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant