@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:
@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, SGTINgs1:globalLocationNumber
: PGLN, SGLNWe 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:Cons:
schema:propertyID "GRAI"
has no global meaning because it's a string; a URL/resource likegs1:grai
has global meaningAlso, prop names should be consistently spelled (either in full or abbreviated):
gs1:globalTradeItemNumber, gs1:globalLocationNumber
gs1:gtin, gs1:gln
We should not copy the current inconsistency from schema.org.
I personally prefer the full spelling.