additional classes needed in GS1 WebVoc

[VladimirAlexiev]

@RalphTro, @mgh128, @CraigRe and @philarcher :
As per https://docs.google.com/spreadsheets/d/19lseUd1kHiz48VNtrHXy6kafLTlNzS1GsaYiBqdT4UA/edit, various classes need to be added to https://gs1.org/voc/:

• To cover all TDS identifier types.
• To cover additional needed classes, eg gs1:SensorDevice
• Because they are used in the EPCIS ontology: https://github.com/gs1/EPCIS/blob/master/Ontology/EPCIS.ttl
• It's not just the red types, eg voc doesn't have gs1:ProductBatch
• The second sheet shows extra classes and a class hierarchy.
• After these are added, https://github.com/gs1/EPCIS/blob/master/Ontology/EPCIS.ttl needs to be reviewed and amended, eg to add

epcis:EPCISDocument  rdfs:subClassOf gs1:Document.
epcis:BizTransaction rdfs:subClassOf gs1:Document.

I remember you said a work item needs to be created for the WebVoc maintenance group.
What is the current situation?

[VladimirAlexiev]

• EPC/TDS identifier types missing from WebVoc WebVoc#39 is about props that need to be added
• wrong semantic modeling in GS1DigitalLinkCompressionPrototype WebVoc#38 is about the relations between gs1:Product, gs1:IndividualProduct, gs1:ProductBatch
• ai2voc.html comments WebVoc#33 is about @philarcher's https://philarcher.org/gs1/files/2021-04/ai2voc.html page

[mgh128]

Hi @VladimirAlexiev
Thanks for the reminder. I agree that to keep EPCIS/CBV 2.0 in sync with the GS1 Web vocabulary, we need to make those updates. @philarcher has prepared a related sheet at https://philarcher.org/gs1/files/2021-04/ai2voc.html and we should compare and consolidate that with the sheet at gs1/WebVoc#39 and also consider gs1/WebVoc#38

The good news on this is that there does appear to be internal support for going beyond what has recently been provided at https://ref.gs1.org/tools/gs1-barcode-syntax-resource/ to provide in various formats (e.g. TSV, JSON-LD) a more comprehensive dataset about GS1 Application Identifiers, also including their semantic interpretation and there are plans to tackle this in the near future, with the aim of publishing the extended dataset as a tool on ref.gs1.org and perhaps using it to provide a more capable browser for GS1 Application Identifiers, also at ref.gs1.org. I've previously developed a prototype browser tool for GS1 Application Identifiers using a Linked Data dataset in JSON-LD, so I'm likely to be involved in that effort, as well as making sure that the extended dataset builds on (and aligns with) the previous efforts on GS1 Application Identifier semantics, something we began in the GS1 Digital Link standard, even though it's equally applicable to interpretation of GS1 Application Identifiers expressed in element strings.

[VladimirAlexiev]

I've read https://ref.gs1.org/tools/gs1-barcode-syntax-resource/ and extending it with RDF representation would be great.
But in parallel, WebVoc needs to add these extra classes so that AIs can refer to semantic classes.
@philarcher or @mgh128 is that work planned, or is it in scope of one of the WGs being convened? Eg I got an invite for a "web technologies" WG, would this be tackled in that WG?

[mgh128]

Hi @VladimirAlexiev
That work is planned and is likely to go through the usual GSMP review process at GS1, with corresponding updates to the GS1 Web vocabulary being reviewed by the new Web Technology SMG.