Property talk:P8957

From Wikidata
Jump to navigation Jump to search

Documentation

GS1 GPC code
code used to classify products in the GS1 Global Product Classification: Segment>Family>Class>Brick, or Attribute Type: Value
Applicable "stated in" valueGlobal Product Classification (Q5570571)
Data typeExternal identifier
Domainproduct (Q2424752)
Allowed values\d{8}
Examplefortified wine (Q722338)10000273
vinegar (Q41354)10000051
television set (Q8075)68010100
10001400
10001405
10001403
Baden (Q6877935)30015368
insecticide (Q181322)30017723
erosion control (Q5395394)30017718
testicle (Q9384)30002433
dry aging (Q106107467)30013615
remote control (Q185091)20000651
gender (Q48277)20000366
female (Q6581072)30003891
unisex (Q76976)30004340
Sourcehttps://www.gs1.org/standards/gpc
Formatter URLhttps://mh1.eu/gpctest/$1
Lists
Proposal discussionProposal discussion
Current uses
Total438
Main statement423 out of 6,073 (7% complete)96.6% of uses
Qualifier153.4% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “\d{8}: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8957#Format, SPARQL
Type “product (Q2424752): item must contain property “instance of (P31), subclass of (P279)” with classes “product (Q2424752)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8957#Type Q2424752, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8957#Unique value, SPARQL (every item), SPARQL (by value)
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8957#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8957#Entity types

Subject class constraint against Type "product" doesn't allow for GPC Segment or Family to be classified[edit]

For example, on clothing (Q11460) the current constraint is causing an issue applying the statement for codifying the Segment 67000000 on it with this GS1 GPC code P8957 property. Segments and Families within GS1 GPC are product subclasses and so this constraint should be removed or more appropriate constraints applied instead.

  • Segment 67000000 Clothing
    • Family 67040000 Underwear
      • Class 67040100 Underwear
        • Brick 10001348 Socks

-- Thadguidry (talk) 16:02, 5 August 2021 (UTC)[reply]

Yes, "product" is way too restrictive. GPC also includes product characteristics geo objects (origins) etc Vladimir Alexiev (talk) 01:31, 28 April 2022 (UTC)[reply]

Wikidata item of this property[edit]

Hi @Tpc:, thanks for deleting the other redundant prop!

Why did you add "Wikidata item of this property=product"? I think that is way too generic and I haven't seen such genericity on other props. I think only the specific item "Global Product Classification" should stay.

I think you can replace this with "is a=WD property related to Products". Cheers--Vladimir Alexiev (talk) 01:38, 28 April 2022 (UTC)[reply]

I mean @ToI:. Sorry to bother you, @TpC: Vladimir Alexiev (talk) 01:40, 28 April 2022 (UTC)[reply]