Re: Thoughts on current discussion around QR codes

I just looked at the JABCode spec, and while and interesting approach to the problem of finding other ways to encode data – it unfortunately was written/reviewed by people who have no actual understanding of color science and how it is used in today’s world – either digitally or physically.

Given the limited representation of color in the format, it is *impossible* to reliably output and then retrieve the colors, especially across their intended use case of digital->analog (aka print)->digital.

Leonard

From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Sunday, February 16, 2020 at 6:38 AM
To: Credentials Community Group <public-credentials@w3.org>, W3C DID Working Group <public-did-wg@w3.org>
Cc: Wolf McNally <wolf@wolfmcnally.com>, "phil.archer@gs1.org" <phil.archer@gs1.org>
Subject: Re: Thoughts on current discussion around QR codes
Resent-From: <public-credentials@w3.org>
Resent-Date: Sunday, February 16, 2020 at 6:37 AM

If you want to use an optical or RF data carrier, you will be limited by
the capacity of that system. If the data you want to convey exceeds that
capacity, you need to reduce your payload, use a higher-capacity data
carrier, or both. There are higher capacity optical data carriers. In
particular, JAB might be relevant [5]. That's basically a QR code that
uses colour to increase the capacity and is on its way to being an ISO
standard. My colleagues in China are behind another bar code, Han Xin
[6], which also has a higher capacity than QR.

Please jettison, forget, and generally bury the idea of an animated QR code.

Phil

[1] https://www.qrcode.com/en/history/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.qrcode.com%2Fen%2Fhistory%2F&data=02%7C01%7Clrosenth%40adobe.com%7C057ecd9815684bc7a95508d7b2d4c1cd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637174499197273521&sdata=Fz6U9XuZwx1njj%2B7QtHZe3GbSr4wfj29bfwtqeBp8qk%3D&reserved=0>
[2] https://www.iso.org/standard/44230.html<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iso.org%2Fstandard%2F44230.html&data=02%7C01%7Clrosenth%40adobe.com%7C057ecd9815684bc7a95508d7b2d4c1cd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637174499197273521&sdata=%2Fg67yJiJqEQmbG5f5vdzp%2BctGte7XQAlcipTYmQWHts%3D&reserved=0>
[3] https://wicg.github.io/shape-detection-api/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwicg.github.io%2Fshape-detection-api%2F&data=02%7C01%7Clrosenth%40adobe.com%7C057ecd9815684bc7a95508d7b2d4c1cd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637174499197283513&sdata=a6tTpmHQ773v3upmCFHlU8caNaC5pJRfS4QZZUmXtzo%3D&reserved=0>
[4] https://github.com/zxing/zxing<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzxing%2Fzxing&data=02%7C01%7Clrosenth%40adobe.com%7C057ecd9815684bc7a95508d7b2d4c1cd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637174499197283513&sdata=J8UXWbczQti43nWUA01ayiRnXPIglyHhGHMjtW1%2FlSo%3D&reserved=0>
[5] https://jabcode.org/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjabcode.org%2F&data=02%7C01%7Clrosenth%40adobe.com%7C057ecd9815684bc7a95508d7b2d4c1cd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637174499197293506&sdata=N%2BilJuAH8AB4lZvG%2FGUbplon7xG%2Fc2oWWfXGqXJWnh0%3D&reserved=0>
[6] https://www.iso.org/standard/69321.html<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iso.org%2Fstandard%2F69321.html&data=02%7C01%7Clrosenth%40adobe.com%7C057ecd9815684bc7a95508d7b2d4c1cd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637174499197293506&sdata=W%2BIEXEBONJffMAKBwO6HZpRg2qxe0SD8xV%2BI7Q%2B%2FE%2FM%3D&reserved=0>

Here is the reference DID in Jabcode and in iso 69321:

Received on Sunday, 16 February 2020 13:40:04 UTC