Re: Adding a gtin12 property to schema.org ? (based on existing gtin8, gtin13, gtin14)

All:

+1 for adding gtin12. When designing GoodRelations, which provided the GTIN properties to schema.org, I had assumed that the UPC code had been superseded by GTIN-13. Thus GoodRelations defined only GTIN-8, GTIN-13, and GTIN-14 and recommended converting 12-digit UPC codes to GTIN-13 by simply adding a zero at the beginning. But if GTIN-12/UPC is here to stay, it is better to have a property for it.

See 

    http://www.heppnetz.de/ontologies/goodrelations/v1.html#hasEAN_UCC-13

which was the former propery for GTIN-13 in the original namespace.


Martin

-----------------------------------
martin hepp  http://www.heppnetz.de
mhepp@computer.org          @mfhepp







> On 29 Apr 2015, at 22:02, Eric Kauz <eric.kauz@gs1.org> wrote:
> 
> Hi Dan
> 
> No complications but I am suggesting we add an additional line from our General Specification which specifies that the GTIN-12 is 12 digits in length.
> 
> "The GTIN-12 code http://apps.gs1.org/GDD/glossary/Pages/GTIN-12.aspx of the product, or the product to which the offer refers. The GTIN-12 is the 12-digit GS1 Identification Key composed of a U.P.C. Company Prefix, Item Reference, and Check Digit used to identify trade items.  See GS1 GTIN Summary <http://www.gs1.org/gtin> for more details."
> 
> Best Regards
> 
> Eric
> 
> -----Original Message-----
> From: Dan Brickley [mailto:danbri@google.com] 
> Sent: Wednesday, April 29, 2015 3:36 PM
> To: Eric Kauz; Steve Bratt; Mark Harrison
> Cc: schema.org Mailing List
> Subject: Adding a gtin12 property to schema.org ? (based on existing gtin8, gtin13, gtin14)
> 
> Hi GS1 team, (/cc W3C schema.org community group)
> 
> We have an open issue "Evaluate addition of gtin12"
> https://github.com/schemaorg/schemaorg/issues/122
> 
> Mark Harrison previously provided some useful comments, copied in the blog post.
> 
> Excerpting, "gtin12 is no less important than gtin13, so if you already have schema.org properties for gtin8, gtin13 and gtin14, then I see no valid reason not to define a gtin12 property directly, for completeness, rather than coerce people to use a schema:gtin13 property."
> 
> We are just wrapping up the next version of schema.org now, and need to decide whether to bump this to future Q2 work or try to squeeze it in. From all I read, adding a gtin12 property makes sense. And we already have gtin8, gtin14, gtin13 in http://schema.org/Product. In for a penny, in for a pound.
> 
> Would the following definition work (and be accurate)?
> 
> "The GTIN-12 code
> <http://apps.gs1.org/GDD/glossary/Pages/GTIN-12.aspx> of the product, or the product to which the offer refers. See GS1 GTIN Summary <http://www.gs1.org/gtin> for more details."
> 
> Are there any complications (as listed in http://schema.org/gtin13 ) that we ought to document, if we do this?
> 
> Thanks for any advice,
> 
> Dan
> 
> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). 
> If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. 
> GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. 
> GS1 may monitor communications. 
> Third party rights acknowledged. 
> (c) 2012.
> </a>

Received on Wednesday, 29 April 2015 20:34:00 UTC