Sources and methodology

What is checked

BarcodeOpsKit checks only the rules named beside each result. Depending on the tool, that can include allowed characters, supported length, a GS1 Modulo-10 check digit, Application Identifier field syntax and boundaries, Digital Link URI placement and encoding, a digital render/decode round trip, or label layout geometry. Calculations and parsers are kept in pure TypeScript so the same input produces reviewable evidence without a network lookup.

Identifier values remain strings so leading zeros survive. Ambiguous supported forms remain visible instead of being guessed. Normalization is shown separately from original input, while stable error codes remain separate from plain-language recovery messages.

What is not checked

A correct check digit is arithmetic evidence only. BarcodeOpsKit does not issue identifiers, search a registry, verify a company prefix, prove ownership, identify a product or location, or establish that encoded facts are true. A successful digital render and self-scan does not measure a physical print, provide a verifier grade, certify a barcode, or guarantee marketplace or retailer acceptance.

Official sources

GS1 structure and terminology are reviewed against publishedGS1 General Specifications, theGS1 Application Identifier reference, the versionedGS1 Syntax Dictionary, and theGS1 Digital Link URI Syntax. Web formats use the relevant W3C or IETF publication. A third-party summary may help locate a source, but it does not replace the primary publication governing an implemented rule.

Local snapshot and version

Mutable standards data is not fetched at runtime. The active implementation uses GS1 General Specifications 26.0.0, GS1 Syntax Dictionary revision 2026-01-27, and GS1 Digital Link URI Syntax 1.6.0, reviewed 2026-07-13. The standards register records source URLs, upstream revision, retrieval and review dates, licence, checksum, entry count, and implemented linter scope.

Affected tools

General identifier and Modulo-10 rules affect the single validator, check-digit calculator, bulk validator, generator validation, label-sheet validation, and scanner interpretation. The vendored AI dictionary affects the GS1 Application Identifier parser and Digital Link builder. Rendering and scanning also depend on the pinned local browser libraries listed in the dependency record; they do not add a registry or product lookup.

Update and review process

1. Identify the primary publication, version, licence, and narrow rule.
2. Prepare a human-readable difference from the current local snapshot.
3. Update the pure implementation and allowed reference vectors.
4. Run boundary, malformed-input, invariant, reference, and regression tests.
5. Update affected pages, dates, provenance, and the evidence report.

A review date means the cited material was examined on that date. It is not a promise that an external publisher will never revise it. Stage reports distinguish commands actually run from manual checks and unverified work.

Correction process

Follow the privacy-safe correction process and include the page path, exact statement, primary source title, version, section, URL, and suggested correction. Calculation or parser changes require a regression test. Never include a real barcode, GS1 string, CSV row, scan, label, filename, or workspace record in a report.

Licensing and non-affiliation

The local standards register identifies the licence associated with each vendored source. Source names and specification titles identify provenance; they do not transfer ownership or imply sponsorship. BarcodeOpsKit is independent and is not affiliated with, endorsed by, or certified by GS1. Production decisions should be checked against the applicable regulator, trading partner, local GS1 organization, and print-verification process.