search

w3c / tpac2023-breakouts

Repository setup to collect and organize breakout session proposals for TPAC 2023
4 stars 2 forks source link

After 50 years, GS1 is replacing the barcode with QR codes. That matters for devs, for consumers, for brands, for retailers, for trust on the Web. #16

Open philarcher opened 1 year ago

philarcher commented 1 year ago

Session description

The first barcode went beep at a checkout in Ohio almost 50 years ago (1974-06-26T08:01:00+05:00). GS1, the global organization behind the numbering system embedded in billions of barcodes around the world, is working with industry to replace it with higher-capacity, more functional alternatives. You won't be surprised to learn that in many cases this will be a QR code that contains a URI. But the URI has additional structure that encodes not just the basic product identifier but things like batch numbers, serial numbers, expiry dates and more. The ambition is that by the end of 2027, the original 1970s barcode can begin to retire.

This presents substantial opportunities for the Web. Some claim it also presents opportunities for bad actors. This breakout session is about:

  1. How do I recognize a "GS1 Digital Link URI" when I see it? (example: https://example.com/01/09506000134352/10/ABC)

  2. What can I do with it? Linked Data? HATEOS? (try https://id.gs1.org/01/09506000134352/10/ABC?linkType=all)

  3. Whaddyamean the domain name isn't part of the identifier?? That's nuts! (it's also true)

  4. How does this tie in with product conformance certificates, trade digitization, the forthcoming EU Digital Product Passport regulation, traceability, sustainability and generally 'selling more stuff'

  5. Ah, forget it, it's a URL so I can do what I like... (true)

Session goal

To discuss the future possibilities - good and bad - that the change to Web-enabled barcodes offer. How it ties in with DIDs and VCs, and how it can be used to improve consumer experiences online.

One specific question: does putting URIs with additional structure into QR codes on millions of products create a massive security headache?

Additional session chairs (Optional)

No response

IRC channel (Optional)

qr

Who can attend

Anyone may attend (Default)

Session duration

60 minutes (Default)

Other sessions where we should avoid scheduling conflicts (Optional)

73, #69, #31, #12, #28

Estimated number of in-person attendees

Don't know (Default)

Instructions for meeting planners (Optional)

Happy to merge this into one of the other sessions listed if those session leaders are willing. I've adapted this from the original pitch for a lightning talk.

Agenda, minutes, slides, etc. (Optional)

tidoust commented 1 year ago

(Moving agenda to a separate comment linked from the issue description for formatting purpose)

Agenda: Short presentation followed by discussion