To allow barcode generation by the Broker, the Open Booking API specification includes an "Extension point for barcode-based access control". This is intended to "help inform future versions of the specification".
Why is this needed?
Barcodes are incredibly complicated, and schema.org itself shied away from "trying to represent the many varied types of barcode system and content that they carry" ref.
This issue is intended to be the start of the discussion around representing the most common barcode types in the sector.
Proposal
As a starter-for-10 proposal for convergence, the following beta property and values are defined:
Proposer
ODI
Use Case
To allow barcode generation by the Broker, the Open Booking API specification includes an "Extension point for barcode-based access control". This is intended to "help inform future versions of the specification".
Why is this needed?
Barcodes are incredibly complicated, and schema.org itself shied away from "trying to represent the many varied types of barcode system and content that they carry" ref.
This issue is intended to be the start of the discussion around representing the most common barcode types in the sector.
Proposal
As a starter-for-10 proposal for convergence, the following beta property and values are defined:
beta:codeType
- The type of barcode, e.g. https://en.wikipedia.org/wiki/Barcode#Linear_barcodes, with two defined valuesCode39
andCode128
Example