W3C home > Mailing lists > Public > public-schemaorg@w3.org > April 2015

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

From: Dan Brickley <danbri@google.com>
Date: Wed, 29 Apr 2015 20:36:15 +0100
Message-ID: <CAK-qy=6nVgnt18yqsC8=E_efQnEc7pjuFX8oDSOGy9M0t1MJ1A@mail.gmail.com>
To: Eric Kauz <eric.kauz@gs1.org>, Steve Bratt <steve.bratt@gs1.org>, Mark Harrison <mark.harrison@cantab.net>
Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
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
Received on Wednesday, 29 April 2015 19:36:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 29 April 2015 19:36:44 UTC