@sythos/js_barcode_universal 1.2.5 → 1.3.1

package/licenses/README.md

@@ -8,65 +8,42 @@ on which this project implements and redistributes it.
 The library is MIT licensed in full — see [`../LICENSE`](../LICENSE), whose
 appendix carries the consolidated inventory these files expand on.
 
-| Format | File | Review status |
+| Format | File | `[TO VERIFY]` items |
 |---|---|---:|
-| Aztec Code | [`aztec-code.license`](aztec-code.license) | Scoped labels |
-| QR Code | [`qr-code.license`](qr-code.license) | Scoped labels |
-| Data Matrix ECC 200 | [`data-matrix.license`](data-matrix.license) | Scoped labels |
-| PDF417 | [`pdf417.license`](pdf417.license) | Scoped labels |
-| MicroPDF417 | [`micropdf417.license`](micropdf417.license) | Scoped labels |
-| EAN-13 | [`ean-13.license`](ean-13.license) | Scoped labels |
-| EAN-8 | [`ean-8.license`](ean-8.license) | Scoped labels |
-| UPC-A | [`upc-a.license`](upc-a.license) | Scoped labels |
-| UPC-E | [`upc-e.license`](upc-e.license) | Scoped labels |
-| ISBN (Bookland EAN-13) | [`isbn.license`](isbn.license) | Scoped labels |
-| Code 128 | [`code-128.license`](code-128.license) | Scoped labels |
-| GS1-128 | [`gs1-128.license`](gs1-128.license) | Scoped labels |
-| Code 39 | [`code-39.license`](code-39.license) | Scoped labels |
-| Code 93 | [`code-93.license`](code-93.license) | Scoped labels |
-| ITF (Interleaved 2 of 5) | [`itf.license`](itf.license) | Scoped labels |
-| ITF-14 | [`itf-14.license`](itf-14.license) | Scoped labels |
-| Codabar | [`codabar.license`](codabar.license) | Scoped labels |
-| Code 11 | [`code-11.license`](code-11.license) | Scoped labels |
-| MSI Plessey | [`msi-plessey.license`](msi-plessey.license) | Scoped labels |
-| Pharmacode | [`pharmacode.license`](pharmacode.license) | Scoped labels |
-
-## Review labels
-
-The inventory now uses scoped labels instead of one generic marker:
-
-- `[VERIFIED FACT]` — supported by a primary or authoritative public source.
-- `[REGISTRY CHECK REQUIRED]` — a live trademark, ownership or registration
-  status still needs a current office-record search.
-- `[PATENT FAMILY REVIEW REQUIRED]` — a patent family, continuation,
-  jurisdiction, term adjustment or maintenance record still needs review.
-- `[LICENSE TERMS REVIEW REQUIRED]` — the standard or publisher's text,
-  copyright and redistribution terms still need confirmation.
-- `[LEGAL REVIEW]` — an attribution, commercial conclusion or jurisdictional
-  issue should be reviewed by qualified counsel before relying on it.
-
-These labels distinguish engineering facts from unresolved legal questions.
-They do not certify that a format is free of patent, trademark or copyright
-constraints in every country.
-
-The primary references used for the current review include:
-
-- [ISO/IEC 24778:2024 — Aztec Code](https://www.iso.org/standard/82441.html)
-- [GS1 EAN/UPC standards](https://www.gs1.org/standards/barcodes/ean-upc)
-- [GS1 Application Identifiers](https://www.gs1.org/gs1-application-identifiers)
-- [GS1 DataMatrix Guideline](https://www.gs1.org/sites/default/files/docs/barcodes/GS1_DataMatrix_Guideline.pdf)
-- [ISO/IEC 15438:2015 — PDF417](https://www.iso.org/standard/65502.html)
-- [ISO/IEC 24728:2006 — MicroPDF417](https://www.iso.org/standard/38838.html)
-- [MicroPDF417 overview](https://en.wikipedia.org/wiki/MicroPDF417)
-- [US 6,047,892 record](https://patents.google.com/patent/US6047892A/en) and [direct PDF](https://patentimages.storage.googleapis.com/0a/79/f5/e8d374043414f3/US6047892.pdf)
-- [ZXing-C++ consultative interoperability reference](https://github.com/zxing-cpp/zxing-cpp)
-- [AIM USS-PDF417 public reference](https://www.expresscorp.com/uploads/specifications/44/USS-PDF-417.pdf)
-- [US 5,243,655 patent record](https://patents.google.com/patent/US5243655A/en)
-- [US 5,304,786 patent record](https://patents.google.com/patent/US5304786A/en)
-- [DENSO QR Code technology position](https://www.denso.com/global/home/business/innovation/qrcode/)
-- [USPTO Aztec patent dedication notice](https://www.uspto.gov/web/offices/com/sol/og/1997/week24/patdisc.htm)
-- [USPTO patent-term guidance](https://www.uspto.gov/web/offices/pac/mpep/s2701.html)
-- [U.S. Copyright Office — ideas, methods and systems](https://www.copyright.gov/circs/circ31.pdf)
+| Aztec Code | [`aztec-code.license`](aztec-code.license) | 2 |
+| QR Code | [`qr-code.license`](qr-code.license) | 2 |
+| Data Matrix ECC 200 | [`data-matrix.license`](data-matrix.license) | 2 |
+| PDF417 | [`pdf417.license`](pdf417.license) | 2 |
+| MicroPDF417 | [`micropdf417.license`](micropdf417.license) | 2 |
+| EAN-13 | [`ean-13.license`](ean-13.license) | 2 |
+| EAN-8 | [`ean-8.license`](ean-8.license) | 2 |
+| UPC-A | [`upc-a.license`](upc-a.license) | 2 |
+| UPC-E | [`upc-e.license`](upc-e.license) | 2 |
+| ISBN (Bookland EAN-13) | [`isbn.license`](isbn.license) | 2 |
+| Code 128 | [`code-128.license`](code-128.license) | 2 |
+| GS1-128 | [`gs1-128.license`](gs1-128.license) | 2 |
+| Code 39 | [`code-39.license`](code-39.license) | 2 |
+| Code 93 | [`code-93.license`](code-93.license) | 2 |
+| ITF (Interleaved 2 of 5) | [`itf.license`](itf.license) | 2 |
+| ITF-14 | [`itf-14.license`](itf-14.license) | 2 |
+| Codabar | [`codabar.license`](codabar.license) | 2 |
+| Code 11 | [`code-11.license`](code-11.license) | 2 |
+| MSI Plessey | [`msi-plessey.license`](msi-plessey.license) | 2 |
+| Pharmacode | [`pharmacode.license`](pharmacode.license) | 2 |
+| Micro QR Code | [`micro-qr.license`](micro-qr.license) | 2 |
+| rMQR Code | [`rmqr.license`](rmqr.license) | 2 |
+| Frame QR / Sythos Canvas QR profile | [`frameqr.license`](frameqr.license) | 2 |
+
+## On the `[TO VERIFY]` markers
+
+They are the point, not a defect. Patent expiry, trademark status and
+rights-holder positions are exactly the claims where being confidently
+wrong causes harm, so anything not independently confirmed is marked rather
+than smoothed over. A file with more markers is being more honest, not less
+reliable.
+
+**No trademark search was performed.** Where a file says no mark is known,
+that describes the limit of what the author knows, not a finding.
 
 These are engineering assessments, **not legal advice**. If your use is
 commercially sensitive, obtain your own legal review.

package/licenses/aztec-code.license

@@ -4,16 +4,16 @@ Aztec Code — format provenance and usability
 This file records where the Aztec Code symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
 ORIGIN
 --------------------------------------------------------------------------
 
-Created by Andrew Longacre, Jr. of Welch Allyn in the 1990s. The inventor,
-assignee and public dedication are supported by the USPTO Official Gazette;
-ownership history outside that record remains [LEGAL REVIEW].
+Created by Andrew Longacre, Jr. of Welch Allyn in the 1990s. The exact
+attribution, ownership history and release terms have not been
+independently confirmed by the author. [LEGAL REVIEW]
 
 
 SPECIFICATION
@@ -32,16 +32,16 @@ redistribute or excerpt any specification document.
 PATENT STATUS
 --------------------------------------------------------------------------
 
-The original US patent was dedicated to the public, as recorded by the USPTO.
-International patent families, continuations and current effects remain
-[PATENT FAMILY REVIEW REQUIRED].
+The status of patents associated with Aztec Code, including any original
+rights-holder statements and their current effect, has not been
+independently confirmed by the author. [LEGAL REVIEW]
 
 
 TRADEMARK
 --------------------------------------------------------------------------
 
 The current registration status and ownership of the words "Aztec Code"
-have not been independently established. [REGISTRY CHECK REQUIRED] The name is used
+have not been independently established. [LEGAL REVIEW] The name is used
 descriptively here and does not imply endorsement by any rights holder.
 
 A trademark does not restrict implementing a symbology. It restricts
@@ -53,8 +53,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 Aztec Code is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -63,12 +65,12 @@ CONCLUSION
 This project's original implementation is distributed under the MIT
 License. The ISO/IEC reference establishes the technical standard; this
 engineering inventory does not claim to have resolved the patent or
-trademark entries that remain open for review.
+trademark entries that remain marked [LEGAL REVIEW].
 
 References relied upon:
   - ISO/IEC 24778:2024, ISO/IEC
   - Aztec Code origin, patent position and trademark status [LEGAL REVIEW]
 
-This is an engineering assessment, not legal advice. Open review labels
-identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.

package/licenses/codabar.license

@@ -4,18 +4,18 @@ Codabar — format provenance and usability
 This file records where the Codabar symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
 ORIGIN
 --------------------------------------------------------------------------
 
-Developed in the early 1970s. [LEGAL REVIEW] COMPETING ATTRIBUTIONS CIRCULATE
-in secondary sources — Monarch Marking Systems and Pitney Bowes are both
-cited — so the credit is deliberately NOT treated as settled here and no
-single originator is asserted. Long used by blood banks, libraries and
-courier services.
+Developed in the early 1970s. [LEGAL REVIEW] COMPETING ATTRIBUTIONS
+CIRCULATE in secondary sources — Monarch Marking Systems and Pitney Bowes
+are both cited — so the credit is deliberately NOT treated as settled here
+and no single originator is asserted. Long used by blood banks, libraries
+and courier services.
 
 
 SPECIFICATION
@@ -24,7 +24,8 @@ SPECIFICATION
 AIM USS-Codabar (Uniform Symbology Specification) is understood to exist,
 but no document number is asserted here because none has been confirmed.
 [LEGAL REVIEW]
-Also known as NW-7, and in the United States as Code 2 of 7. [LEGAL REVIEW]
+Also known as NW-7, and in the United States as Code 2 of 7. [LEGAL
+REVIEW]
 
 Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
 describes is not — an encoding scheme is a system, not a work of
@@ -36,15 +37,15 @@ PATENT STATUS
 --------------------------------------------------------------------------
 
 The originating patents date from the 1970s-1980s and are understood to
-have expired long ago. [PATENT FAMILY REVIEW REQUIRED]
+have expired long ago. [LEGAL REVIEW]
 
 
 TRADEMARK
 --------------------------------------------------------------------------
 
 No live trademark restriction on implementing Codabar is known to the
-author. [REGISTRY CHECK REQUIRED] That is a statement about the author's knowledge, not
-a finding that no mark subsists: no trademark search was carried out.
+author. [LEGAL REVIEW] That is a statement about the author's knowledge,
+not a finding that no mark subsists: no trademark search was carried out.
 
 A trademark does not restrict implementing a symbology. It restricts
 branding — how a product names and presents itself.
@@ -55,8 +56,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 Codabar is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -67,8 +70,8 @@ implementable and redistributable, and this project's implementation of it
 is distributed under the MIT License with no additional restriction.
 
 References relied upon:
-  - AIM USS-Codabar [LICENSE TERMS REVIEW REQUIRED]
+  - AIM USS-Codabar [LEGAL REVIEW]
 
-This is an engineering assessment, not legal advice. Open review labels
-Open review labels identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.

package/licenses/code-11.license

@@ -4,7 +4,7 @@ Code 11 — format provenance and usability
 This file records where the Code 11 symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
@@ -31,15 +31,15 @@ PATENT STATUS
 --------------------------------------------------------------------------
 
 The originating patents date from the 1970s-1980s and are understood to
-have expired long ago. [PATENT FAMILY REVIEW REQUIRED]
+have expired long ago. [LEGAL REVIEW]
 
 
 TRADEMARK
 --------------------------------------------------------------------------
 
 No live trademark restriction on implementing Code 11 is known to the
-author. [REGISTRY CHECK REQUIRED] That is a statement about the author's knowledge, not
-a finding that no mark subsists: no trademark search was carried out.
+author. [LEGAL REVIEW] That is a statement about the author's knowledge,
+not a finding that no mark subsists: no trademark search was carried out.
 
 A trademark does not restrict implementing a symbology. It restricts
 branding — how a product names and presents itself.
@@ -50,8 +50,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 Code 11 is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -62,8 +64,8 @@ implementable and redistributable, and this project's implementation of it
 is distributed under the MIT License with no additional restriction.
 
 References relied upon:
-  - AIM published specification for Code 11 [LICENSE TERMS REVIEW REQUIRED]
+  - AIM published specification for Code 11 [LEGAL REVIEW]
 
-This is an engineering assessment, not legal advice. Open review labels
-Open review labels identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.

package/licenses/code-128.license

@@ -4,7 +4,7 @@ Code 128 — format provenance and usability
 This file records where the Code 128 symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
@@ -31,15 +31,15 @@ PATENT STATUS
 --------------------------------------------------------------------------
 
 The originating patents date from the 1970s-1980s and are understood to
-have expired long ago. [PATENT FAMILY REVIEW REQUIRED]
+have expired long ago. [LEGAL REVIEW]
 
 
 TRADEMARK
 --------------------------------------------------------------------------
 
 No live trademark restriction on implementing Code 128 is known to the
-author. [REGISTRY CHECK REQUIRED] That is a statement about the author's knowledge, not
-a finding that no mark subsists: no trademark search was carried out.
+author. [LEGAL REVIEW] That is a statement about the author's knowledge,
+not a finding that no mark subsists: no trademark search was carried out.
 
 A trademark does not restrict implementing a symbology. It restricts
 branding — how a product names and presents itself.
@@ -50,8 +50,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 Code 128 is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -64,6 +66,6 @@ is distributed under the MIT License with no additional restriction.
 References relied upon:
   - ISO/IEC 15417, ISO/IEC
 
-This is an engineering assessment, not legal advice. Open review labels
-Open review labels identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.

package/licenses/code-39.license

@@ -4,7 +4,7 @@ Code 39 — format provenance and usability
 This file records where the Code 39 symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
@@ -32,15 +32,15 @@ PATENT STATUS
 --------------------------------------------------------------------------
 
 The originating patents date from the 1970s-1980s and are understood to
-have expired long ago. [PATENT FAMILY REVIEW REQUIRED]
+have expired long ago. [LEGAL REVIEW]
 
 
 TRADEMARK
 --------------------------------------------------------------------------
 
 No live trademark restriction on implementing Code 39 is known to the
-author. [REGISTRY CHECK REQUIRED] That is a statement about the author's knowledge, not
-a finding that no mark subsists: no trademark search was carried out.
+author. [LEGAL REVIEW] That is a statement about the author's knowledge,
+not a finding that no mark subsists: no trademark search was carried out.
 
 A trademark does not restrict implementing a symbology. It restricts
 branding — how a product names and presents itself.
@@ -51,8 +51,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 Code 39 is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -65,6 +67,6 @@ is distributed under the MIT License with no additional restriction.
 References relied upon:
   - ISO/IEC 16388, ISO/IEC
 
-This is an engineering assessment, not legal advice. Open review labels
-Open review labels identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.

package/licenses/code-93.license

@@ -4,7 +4,7 @@ Code 93 — format provenance and usability
 This file records where the Code 93 symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
@@ -12,16 +12,16 @@ ORIGIN
 --------------------------------------------------------------------------
 
 Introduced by Intermec in 1982 as a denser successor to Code 39, adding
-two check characters. [VERIFIED FACT]
+two check characters. [LEGAL REVIEW]
 
 
 SPECIFICATION
 --------------------------------------------------------------------------
 
-AIM symbology specification for Code 93. Terms vary by document. [TO
-VERIFY]
-ISO/IEC 16388 covers Code 39; Code 93 is documented separately. [TO
-VERIFY]
+AIM symbology specification for Code 93. Terms vary by document. [LEGAL
+REVIEW]
+ISO/IEC 16388 covers Code 39; Code 93 is documented separately. [LEGAL
+REVIEW]
 
 Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
 describes is not — an encoding scheme is a system, not a work of
@@ -33,15 +33,15 @@ PATENT STATUS
 --------------------------------------------------------------------------
 
 The originating patents date from the 1970s-1980s and are understood to
-have expired long ago. [PATENT FAMILY REVIEW REQUIRED]
+have expired long ago. [LEGAL REVIEW]
 
 
 TRADEMARK
 --------------------------------------------------------------------------
 
 No live trademark restriction on implementing Code 93 is known to the
-author. [REGISTRY CHECK REQUIRED] That is a statement about the author's knowledge, not
-a finding that no mark subsists: no trademark search was carried out.
+author. [LEGAL REVIEW] That is a statement about the author's knowledge,
+not a finding that no mark subsists: no trademark search was carried out.
 
 A trademark does not restrict implementing a symbology. It restricts
 branding — how a product names and presents itself.
@@ -52,8 +52,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 Code 93 is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -64,8 +66,8 @@ implementable and redistributable, and this project's implementation of it
 is distributed under the MIT License with no additional restriction.
 
 References relied upon:
-  - AIM published specification for Code 93 [LICENSE TERMS REVIEW REQUIRED]
+  - AIM published specification for Code 93 [LEGAL REVIEW]
 
-This is an engineering assessment, not legal advice. Open review labels
-Open review labels identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.

package/licenses/data-matrix.license

@@ -4,7 +4,7 @@ Data Matrix ECC 200 — format provenance and usability
 This file records where the Data Matrix ECC 200 symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
@@ -13,8 +13,8 @@ ORIGIN
 
 Data Matrix emerged from industrial automatic-identification work
 associated with International Data Matrix and later RVSI/CI Matrix in the
-late 1980s and early 1990s. The patent record supports the International Data
-Matrix attribution; the complete corporate chronology remains [LEGAL REVIEW].
+late 1980s and early 1990s. The exact corporate chronology and attribution
+have not been independently confirmed by the author. [LEGAL REVIEW]
 
 
 SPECIFICATION
@@ -38,16 +38,16 @@ PATENT STATUS
 Patent rights associated with ECC 200 have been reported as released for
 public use by an earlier rights holder, but the original patents, chain of
 title and release terms have not been independently confirmed by the
-author. [PATENT FAMILY REVIEW REQUIRED]
+author. [LEGAL REVIEW]
 
 
 TRADEMARK
 --------------------------------------------------------------------------
 
 The current registration status and ownership of the words "Data Matrix"
-have not been independently established. [REGISTRY CHECK REQUIRED] "GS1" and "GS1
+have not been independently established. [LEGAL REVIEW] "GS1" and "GS1
 DataMatrix" are GS1 designations; their use is descriptive here and does
-not imply endorsement. [REGISTRY CHECK REQUIRED]
+not imply endorsement. [LEGAL REVIEW]
 
 A trademark does not restrict implementing a symbology. It restricts
 branding — how a product names and presents itself.
@@ -58,8 +58,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 Data Matrix ECC 200 is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -68,15 +70,15 @@ CONCLUSION
 This project's original implementation is distributed under the MIT
 License. The ISO/IEC and GS1 references establish the technical standards;
 this engineering inventory does not claim to have resolved the
-patent-release or trademark entries that remain open for review.
+patent-release or trademark entries that remain marked [LEGAL REVIEW].
 
 References relied upon:
   - ISO/IEC 16022:2024, ISO/IEC
   - GS1 General Specifications, GS1 AISBL
   - GS1 DataMatrix Guideline, GS1 AISBL
-  - Reported ECC 200 patent-release position [PATENT FAMILY REVIEW REQUIRED]
-  - Data Matrix trademark status and ownership [REGISTRY CHECK REQUIRED]
+  - Reported ECC 200 patent-release position [LEGAL REVIEW]
+  - Data Matrix trademark status and ownership [LEGAL REVIEW]
 
-This is an engineering assessment, not legal advice. Open review labels
-Open review labels identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.

package/licenses/ean-13.license

@@ -4,7 +4,7 @@ EAN-13 — format provenance and usability
 This file records where the EAN-13 symbology comes from, what governs
 it, and the basis on which this project implements and redistributes it.
 
-It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items carrying a review label
+It is an ENGINEERING INVENTORY, NOT LEGAL ADVICE. Items marked [TO VERIFY]
 have not been independently confirmed by the author.
 
 
@@ -20,7 +20,7 @@ SPECIFICATION
 
 ISO/IEC 15420 — EAN/UPC bar code symbology specification.
 GS1 General Specifications, GS1 AISBL — freely published; redistribution
-terms are GS1's own [LICENSE TERMS REVIEW REQUIRED]
+terms are GS1's own [LEGAL REVIEW]
 
 Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
 describes is not — an encoding scheme is a system, not a work of
@@ -32,7 +32,7 @@ PATENT STATUS
 --------------------------------------------------------------------------
 
 The originating patents date from the 1970s-1980s and are understood to
-have expired long ago. [PATENT FAMILY REVIEW REQUIRED]
+have expired long ago. [LEGAL REVIEW]
 
 
 TRADEMARK
@@ -49,8 +49,10 @@ IMPLEMENTATION BASIS IN THIS PROJECT
 
 EAN-13 is implemented here from published descriptions of the format,
 which are systems and facts rather than works of authorship. No source
-code and no constant table from any other barcode implementation was used,
-consulted or copied, under any licence.
+code or constant table from any other barcode implementation is copied or
+shipped. Public technical material and independent implementations may be
+consulted for engineering review or black-box verification; provenance is
+recorded in NOTICE.md.
 
 
 CONCLUSION
@@ -63,8 +65,8 @@ is distributed under the MIT License with no additional restriction.
 References relied upon:
   - ISO/IEC 15420, ISO/IEC
   - GS1 General Specifications, GS1 AISBL — freely published;
-    redistribution terms are GS1's own [LICENSE TERMS REVIEW REQUIRED]
+    redistribution terms are GS1's own [LEGAL REVIEW]
 
-This is an engineering assessment, not legal advice. Open review labels
-Open review labels identify claims that have not been independently confirmed by the author. If your
+This is an engineering assessment, not legal advice. Items marked
+[TO VERIFY] have not been independently confirmed by the author. If your
 use is commercially sensitive, obtain your own legal review.