Journal of Computer Sciences and Applications
ISSN (Print): 2328-7268 ISSN (Online): 2328-725X Website: http://www.sciepub.com/journal/jcsa Editor-in-chief: Minhua Ma, Patricia Goncalves
Open Access
Journal Browser
Go
Journal of Computer Sciences and Applications. 2018, 6(1), 43-47
DOI: 10.12691/jcsa-6-1-6
Open AccessSpecial Issue

DotCode Damage Testing

Kevin Berisso1,

1Department of Engineering Technology, University of Memphis, Memphis USA

Pub. Date: June 04, 2018
(This article belongs to the Special Issue Information Technology and Computational Intelligence)

Cite this paper:
Kevin Berisso. DotCode Damage Testing. Journal of Computer Sciences and Applications. 2018; 6(1):43-47. doi: 10.12691/jcsa-6-1-6

Abstract

The DotCode bar code symbology is relatively new, having been developed by Dr. Andrew Longacre in 2007. As a result of standards organization work being done on the symbology, it was determined that valid encoding patterns could result in symbols that could not be decoded by the current reference decode algorithm. A solution for resolving the issue involved the introduction of intentional errors that rely on the correct functioning of the Reed-Solomon Error Correction (RSEC) to resolve the original message. However, the actual impacts of such a decision were publicly unknown. This paper has undertaken the task of validating the impacts of intentionally adding additional data bits to the bar code, resulting in the generation of errors in what should otherwise be perfect symbols.

Keywords:
DotCode bar code 2D bar code reed-solomon error correction

Creative CommonsThis work is licensed under a Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/

Figures

Figure of 11

References:

[1]  AIM Global, Information technology — Automatic identification and data capture techniques — Bar code symbology specification — DotCode - Public Review, Cranberry Township, PA: AIM, Inc, 2017.
 
[2]  Burton, T. Proposed “Mask Score, Print Quality Parameter”, 2017.
 
[3]  AIM Global, TSC 1709-29-Min-TSC DotCode Public Review Meeting_Sep17.
 
[4]  Cognex, “The Rise of DotCode,” Cognex, 26 August 2014. [Online]. Available: https://manateeworks.com/blog.[Accessed 21 February 2018].
 
[5]  Dean, K. GS1 DotCode Impact Assesment. Inexto SA, Lausanne, Switzerland, 2017.
 
[6]  Holliday, D. “Traceability Coding for Tobacco Products,” 21 January 2016. [Online]. Available: http://www.labelingnews.com/2016/01/traceability-coding-for-tobacco-products/. [Accessed 21 February 2018].
 
[7]  Nachtrieb, J. “DotCode: A real solution to a real problem - Barcode Test,” Barcode-test, 1 August 2017. [Online]. Available: http://barcode-test.com/dotcode-real-solution-real-problem/. [Accessed 21 February 2018].
 
[8]  Reynolds, P. “Walmart roils the case-coding waters,” 26 April 2016. [Online]. Available: https://www.packworld.com/print/63634. [Accessed 1 March 2018].
 
[9]  Rittenburg, J. “Safety in Numbers,” Pharmaceutical Executive, 26 (6) pp. 46-50, June 2006.
 
[10]  Baguley, T. “Understanding statistical power in the context of applied research,” Applied Ergonomics, 35 (2), pp. 73-80, 2004.
 
[11]  Lin, M., Lucas, H. C. and Shmueli, G. “Too Big to Fail: Large Samples and the p-value problem,” Information Systems Research, 24 (4), pp. 906-917, 2013.