EPC/TDS identifier types missing from WebVoc

[VladimirAlexiev]

@mgh128 @philarcher
this sheet lists 18 types of EPC/TDS identifiers (plus 6 that are crossed out). I added col id prop that maps them to WebVoc properties.

Currently WebVoc has 2 id props that cover 5 cases (in some cases, in combination with "extra prop")

• gs1:gtin: GTIN, LGTIN, SGTIN
• gs1:globalLocationNumber: PGLN, SGLN

We need extra props to cover the other identifiers (gs1:grai, gs1:giai, etc). Currently one is forced to use schema.org constructs (schema:identifier, schema:PropertyValue) to capture them, eg:

<$GRAI_CRATE1> a gs1:ReturnableAsset;
  schema:identifier [a schema:PropertyValue; schema:propertyID "GRAI"; schema:value "$GRAI1"];
  schema:additionalType "crate".

<$SSCC_UNIT1> a gs1:LogisticUnit;
  schema:identifier [a schema:PropertyValue; schema:propertyID "SSCC"; schema:value "$SSCC1"].

<$GSIN_SHIPMENT1> a gs1:Shipment;
  schema:identifier [a schema:PropertyValue; schema:propertyID "GSIN"; schema:value "$GSIN1"].

Cons:

• This is cumbersome
• schema:propertyID "GRAI" has no global meaning because it's a string; a URL/resource like gs1:grai has global meaning
• gs1: should be able to represent all GS1 identifiers on its own

---

Also, prop names should be consistently spelled (either in full or abbreviated):

• either gs1:globalTradeItemNumber, gs1:globalLocationNumber
• or gs1:gtin, gs1:gln

We should not copy the current inconsistency from schema.org.

I personally prefer the full spelling.