@sythos/js_barcode_universal 0.1.0

package/licenses/code-93.license

@@ -0,0 +1,71 @@
+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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+Introduced by Intermec in 1982 as a denser successor to Code 39, adding
+two check characters. [TO VERIFY]
+
+
+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]
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+The originating patents date from the 1970s-1980s and are understood to
+have expired long ago. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+No live trademark restriction on implementing Code 93 is known to the
+author. [TO VERIFY] 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.
+
+
+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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, Code 93 is understood to be freely
+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 [TO VERIFY]
+
+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

@@ -0,0 +1,70 @@
+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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+Introduced in 1977 as the European Article Number, extending the
+twelve-digit UPC to thirteen digits. Administered today by GS1.
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+ISO/IEC 15420 — EAN/UPC bar code symbology specification.
+GS1 General Specifications, GS1 AISBL — freely published; redistribution
+terms are GS1's own [TO VERIFY]
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+The originating patents date from the 1970s-1980s and are understood to
+have expired long ago. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+"GS1" and its symbology names are trademarks of GS1 AISBL.
+
+A trademark does not restrict implementing a symbology. It restricts
+branding — how a product names and presents itself.
+
+
+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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, EAN-13 is understood to be freely
+implementable and redistributable, and this project's implementation of it
+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 [TO VERIFY]
+
+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-8.license

@@ -0,0 +1,70 @@
+EAN-8 — format provenance and usability
+==========================================================================
+
+This file records where the EAN-8 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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+The short form of EAN, introduced alongside EAN-13 for packages too small
+to carry the full symbol. Administered by GS1.
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+ISO/IEC 15420 — EAN/UPC bar code symbology specification.
+GS1 General Specifications, GS1 AISBL — freely published; redistribution
+terms are GS1's own [TO VERIFY]
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+The originating patents date from the 1970s-1980s and are understood to
+have expired long ago. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+"GS1" and its symbology names are trademarks of GS1 AISBL.
+
+A trademark does not restrict implementing a symbology. It restricts
+branding — how a product names and presents itself.
+
+
+IMPLEMENTATION BASIS IN THIS PROJECT
+--------------------------------------------------------------------------
+
+EAN-8 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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, EAN-8 is understood to be freely
+implementable and redistributable, and this project's implementation of it
+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 [TO VERIFY]
+
+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/gs1-128.license

@@ -0,0 +1,71 @@
+GS1-128 — format provenance and usability
+==========================================================================
+
+This file records where the GS1-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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+Not a distinct symbology: GS1-128 is Code 128 carrying a leading FNC1
+character, with its data structured by GS1 Application Identifiers.
+Formerly known as UCC/EAN-128.
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+ISO/IEC 15417 — Code 128 (the underlying symbology).
+GS1 General Specifications, GS1 AISBL — freely published; redistribution
+terms are GS1's own [TO VERIFY] (the Application Identifier rules)
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+Inherits Code 128's position; understood expired. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+"GS1" and its symbology names are trademarks of GS1 AISBL. "GS1-128" is a
+GS1 designation — again a constraint on branding, not on implementation.
+
+A trademark does not restrict implementing a symbology. It restricts
+branding — how a product names and presents itself.
+
+
+IMPLEMENTATION BASIS IN THIS PROJECT
+--------------------------------------------------------------------------
+
+GS1-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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, GS1-128 is understood to be freely
+implementable and redistributable, and this project's implementation of it
+is distributed under the MIT License with no additional restriction.
+
+References relied upon:
+  - ISO/IEC 15417, ISO/IEC
+  - GS1 General Specifications, GS1 AISBL — freely published;
+    redistribution terms are GS1's own [TO VERIFY]
+
+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/isbn.license

@@ -0,0 +1,76 @@
+ISBN (Bookland EAN-13) — format provenance and usability
+==========================================================================
+
+This file records where the ISBN (Bookland 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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+ISBN is a NUMBERING scheme, not a symbology. An ISBN barcode is an
+ordinary EAN-13 carrying a 978 or 979 prefix — the so-called "Bookland"
+country code. The number itself is administered by the International ISBN
+Agency under ISO 2108; the symbol is EAN-13 under GS1's rules.
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+ISO 2108 — International Standard Book Number (the numbering rules).
+ISO/IEC 15420 — EAN/UPC bar code symbology specification (the symbol).
+GS1 General Specifications, GS1 AISBL — freely published; redistribution
+terms are GS1's own [TO VERIFY]
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+No patent encumbrance is known for either the numbering scheme or the
+EAN-13 symbol used to print it. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+No live trademark restriction is known on implementing ISBN encoding.
+"ISBN" is a standard designation administered by the International ISBN
+Agency. [TO VERIFY]
+
+A trademark does not restrict implementing a symbology. It restricts
+branding — how a product names and presents itself.
+
+
+IMPLEMENTATION BASIS IN THIS PROJECT
+--------------------------------------------------------------------------
+
+ISBN (Bookland 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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, ISBN (Bookland EAN-13) is understood to be freely
+implementable and redistributable, and this project's implementation of it
+is distributed under the MIT License with no additional restriction.
+
+References relied upon:
+  - ISO 2108, ISO
+  - ISO/IEC 15420, ISO/IEC
+  - GS1 General Specifications, GS1 AISBL — freely published;
+    redistribution terms are GS1's own [TO VERIFY]
+
+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/itf-14.license

@@ -0,0 +1,69 @@
+ITF-14 — format provenance and usability
+==========================================================================
+
+This file records where the ITF-14 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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+Not a distinct symbology: ITF-14 is Interleaved 2 of 5 fixed at fourteen
+digits, used by GS1 to mark shipping containers with a GTIN.
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+ISO/IEC 16390 — Interleaved 2 of 5 (the underlying symbology).
+GS1 General Specifications, GS1 AISBL — freely published; redistribution
+terms are GS1's own [TO VERIFY] (the fourteen-digit GTIN rules)
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+Inherits ITF's position; understood expired. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+"GS1" and its symbology names are trademarks of GS1 AISBL.
+
+A trademark does not restrict implementing a symbology. It restricts
+branding — how a product names and presents itself.
+
+
+IMPLEMENTATION BASIS IN THIS PROJECT
+--------------------------------------------------------------------------
+
+ITF-14 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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, ITF-14 is understood to be freely
+implementable and redistributable, and this project's implementation of it
+is distributed under the MIT License with no additional restriction.
+
+References relied upon:
+  - ISO/IEC 16390, ISO/IEC
+  - GS1 General Specifications, GS1 AISBL — freely published;
+    redistribution terms are GS1's own [TO VERIFY]
+
+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/itf.license

@@ -0,0 +1,70 @@
+ITF (Interleaved 2 of 5) — format provenance and usability
+==========================================================================
+
+This file records where the ITF (Interleaved 2 of 5) 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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+Developed from the earlier Code 2 of 5 family; the interleaving of digit
+pairs into bars and spaces roughly doubles the density. Attributed to
+Intermec, 1972. [TO VERIFY]
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+ISO/IEC 16390 — Interleaved 2 of 5 bar code symbology specification.
+Published by ISO/IEC; specification TEXT is copyrighted and paywalled.
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+The originating patents date from the 1970s-1980s and are understood to
+have expired long ago. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+No live trademark restriction on implementing ITF is known to the author.
+[TO VERIFY] 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.
+
+
+IMPLEMENTATION BASIS IN THIS PROJECT
+--------------------------------------------------------------------------
+
+ITF (Interleaved 2 of 5) 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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, ITF (Interleaved 2 of 5) is understood to be freely
+implementable and redistributable, and this project's implementation of it
+is distributed under the MIT License with no additional restriction.
+
+References relied upon:
+  - ISO/IEC 16390, ISO/IEC
+
+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/msi-plessey.license

@@ -0,0 +1,72 @@
+MSI Plessey — format provenance and usability
+==========================================================================
+
+This file records where the MSI Plessey 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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+A variant of the Plessey Code, developed by the MSI Data Corporation. [TO
+VERIFY] Chiefly used for retail shelf labelling and inventory.
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+No ISO/IEC standard exists for MSI. It is documented through
+vendor and industry publications rather than a formal standard. [TO
+VERIFY]
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+The originating patents date from the 1970s and are understood to have
+expired. [TO VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+No live trademark restriction on implementing MSI is known to the author.
+[TO VERIFY] That is a statement about the author's knowledge, not a
+finding that no mark subsists: no trademark search was carried out. MSI
+Data Corporation is understood no longer to exist as an independent
+entity. [TO VERIFY]
+
+A trademark does not restrict implementing a symbology. It restricts
+branding — how a product names and presents itself.
+
+
+IMPLEMENTATION BASIS IN THIS PROJECT
+--------------------------------------------------------------------------
+
+MSI Plessey 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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, MSI Plessey is understood to be freely
+implementable and redistributable, and this project's implementation of it
+is distributed under the MIT License with no additional restriction.
+
+References relied upon:
+  - Published descriptions of the MSI and Plessey symbologies [TO VERIFY]
+
+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/pharmacode.license

@@ -0,0 +1,71 @@
+Pharmacode — format provenance and usability
+==========================================================================
+
+This file records where the Pharmacode 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 marked [TO VERIFY]
+have not been independently confirmed by the author.
+
+
+ORIGIN
+--------------------------------------------------------------------------
+
+Devised by Laetus GmbH for pharmaceutical packaging control. [TO VERIFY]
+Unusual among linear symbologies: it encodes an integer directly in a
+bijective base-2 form rather than digit by digit, and carries no check
+digit at all.
+
+
+SPECIFICATION
+--------------------------------------------------------------------------
+
+No ISO/IEC standard exists for Pharmacode. It is documented by
+Laetus and reproduced in industry literature. [TO VERIFY]
+
+Specification TEXT is copyrighted by its publisher. The SYMBOLOGY it
+describes is not — an encoding scheme is a system, not a work of
+authorship. This project implements the symbology; it does not reproduce,
+redistribute or excerpt any specification document.
+
+
+PATENT STATUS
+--------------------------------------------------------------------------
+
+No live patent encumbrance is known; the format dates from the 1970s. [TO
+VERIFY]
+
+
+TRADEMARK
+--------------------------------------------------------------------------
+
+"Pharmacode" is associated with Laetus GmbH; whether a live trademark
+subsists has NOT been confirmed. [TO VERIFY] This is among the least
+certain entries in this directory — treat it with corresponding caution.
+
+A trademark does not restrict implementing a symbology. It restricts
+branding — how a product names and presents itself.
+
+
+IMPLEMENTATION BASIS IN THIS PROJECT
+--------------------------------------------------------------------------
+
+Pharmacode 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.
+
+
+CONCLUSION
+--------------------------------------------------------------------------
+
+On the basis of the references below, Pharmacode is understood to be freely
+implementable and redistributable, and this project's implementation of it
+is distributed under the MIT License with no additional restriction.
+
+References relied upon:
+  - Laetus published description of Pharmacode [TO VERIFY]
+
+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.