Line 14: |
Line 14: |
| * it enables finding all products that have a category of labels . e.g. all products that make a health claim others? | | * it enables finding all products that have a category of labels . e.g. all products that make a health claim others? |
| * Can be used in a diet app to select products that have the same label category (eg Animal welfare) independent of a specific label and international. (do you recognise the label in Bulgaria?). | | * Can be used in a diet app to select products that have the same label category (eg Animal welfare) independent of a specific label and international. (do you recognise the label in Bulgaria?). |
| + | * Minimise information by using inheritance. |
| | | |
− | == Main level == | + | == Issues == |
| + | * Distinguish between leaves and structural entries |
| + | |
| + | == Structure == |
| + | A possible structure of the labels hierarchy is explored here. |
| + | |
| + | === Main Level === |
| The labels can be split into two groups: | | The labels can be split into two groups: |
| * Product: every label that describes some aspect of the consumable part. | | * Product: every label that describes some aspect of the consumable part. |
| * Packaging: in braille. (anything that is not related to the shape, material or recycling of the packaging) | | * Packaging: in braille. (anything that is not related to the shape, material or recycling of the packaging) |
| * Supply Chain, describing each process from creating to having it at the consumer (Life Cycle). There is a relation with the process implementor (farmer, producer, packager, transporter, distributor). A label might cover multiple processes. | | * Supply Chain, describing each process from creating to having it at the consumer (Life Cycle). There is a relation with the process implementor (farmer, producer, packager, transporter, distributor). A label might cover multiple processes. |
− | == Second Level == | + | |
− | === Product === | + | === Second Level === |
| + | ==== Product ==== |
| The labels in this group describe features of the consumable part. We can distinguish: | | The labels in this group describe features of the consumable part. We can distinguish: |
| * Ingredients: like No Palm Oils, Natural ingredients,... (we should be able to link to the ingredients taxonomy), New recipe, AOP | | * Ingredients: like No Palm Oils, Natural ingredients,... (we should be able to link to the ingredients taxonomy), New recipe, AOP |
Line 29: |
Line 37: |
| * Health claims: lowers cholesterol | | * Health claims: lowers cholesterol |
| | | |
− | === Packaging === | + | ==== Packaging ==== |
| Not sure what to add here. But there is a Braille label. | | Not sure what to add here. But there is a Braille label. |
− | === Supply Chain === | + | ==== Supply Chain ==== |
| Before a product reaches the consumer it goes through multiple steps or processes. We can distinguish the following processes: | | Before a product reaches the consumer it goes through multiple steps or processes. We can distinguish the following processes: |
| * Production: organic, dredge fishing | | * Production: organic, dredge fishing |
Line 54: |
Line 62: |
| ** en:environment | | ** en:environment |
| ** en:food safety | | ** en:food safety |
− | * origins:en: - the origins of an ingredient | + | ** en:standardisation of business practices. |
| + | * origins:en: - the origins of the producers of a product (Belgian Abbey Beer) or the applicability of a label (South African water bottlers) |
| * web:en: the corresponding webpage in English | | * web:en: the corresponding webpage in English |
| * wikidata:en: - the corresponding wikidata entry | | * wikidata:en: - the corresponding wikidata entry |
| * wikipedia:en: the corresponding wikipedia page in English | | * wikipedia:en: the corresponding wikipedia page in English |
| + | * property_type:en: leaf or structural |
| | | |
| == Other aspects == | | == Other aspects == |
Line 67: |
Line 77: |
| == Implementation == | | == Implementation == |
| Do we need a hierarchy or can some aspects be handled by properties? When to decide for one, and when to decide for the other? | | Do we need a hierarchy or can some aspects be handled by properties? When to decide for one, and when to decide for the other? |
− |
| |
− | === Cons ===
| |
− | * adding a child label to a product automatically adds all parents, which could make the labels field messy (it's already messy today, and we have a similar issue with categories: displaying all of them make the product page quite unreadable).
| |
| | | |
| Possible implementations: | | Possible implementations: |
Line 82: |
Line 89: |
| | | |
| * It would be good to implement a solution that could work for other taxonomies than labels | | * It would be good to implement a solution that could work for other taxonomies than labels |
| + | |
| + | == Display == |
| + | * adding a child label to a product automatically adds all parents, which could make the labels field messy (it's already messy today, and we have a similar issue with categories: displaying all of them make the product page quite unreadable). |
| | | |
| | | |
| [[Category:Taxonomies]] | | [[Category:Taxonomies]] |
| [[Category:Labels taxonomy]] | | [[Category:Labels taxonomy]] |