Changes

Jump to navigation Jump to search
687 bytes added ,  08:01, 12 October 2020
moved proposed attributes to a new section
Line 23: Line 23:  
* If desired, apps can decide to use new product attributes added on the server without requiring app changes
 
* If desired, apps can decide to use new product attributes added on the server without requiring app changes
   −
= Examples of Product Attributes =
+
= Current list of available Product Attributes =
 +
 
 +
See also the list of proposed attributes at the end of this document.
    
Product Attributes are organized in sections:
 
Product Attributes are organized in sections:
Line 30: Line 32:  
** Nutri-Score (A = 100%, E = 0%)
 
** Nutri-Score (A = 100%, E = 0%)
 
** Low salt / Low sugar / Low fat / Low saturated fat (based on the Nutrition Traffic Lights): 1 product attribute for each so that users who are concerned only by salt can specify it.
 
** Low salt / Low sugar / Low fat / Low saturated fat (based on the Nutrition Traffic Lights): 1 product attribute for each so that users who are concerned only by salt can specify it.
* climate gas emissions
  −
** in t CO2-eq per kg
   
* Transformation
 
* Transformation
 
** No ultra-processed foods (NOVA 1 & 2 = 100%, 4 = 0%)
 
** No ultra-processed foods (NOVA 1 & 2 = 100%, 4 = 0%)
 
** Few additives (0 additives = 100%)
 
** Few additives (0 additives = 100%)
 
* Allergens
 
* Allergens
** for each allergen (not present = 100%, present = 0%, traces = 10% (low threshold that will exclude products if "No [allergen]" is marked as mandatory by the user)
+
** for each allergen (not present = 100%, present = 0%, traces = 20% (low threshold that will exclude products if "No [allergen]" is marked as mandatory by the user)
 
* Ingredients
 
* Ingredients
 
** Vegan
 
** Vegan
Line 44: Line 44:  
** Organic
 
** Organic
 
** Fair trade
 
** Fair trade
* Origin Country
+
* Environment
** in percent of weight of the final product
+
** Eco-Score
    
The list can be quite long and new Product Attributes can be added over time.
 
The list can be quite long and new Product Attributes can be added over time.
Line 195: Line 195:     
Apps can decide to keep the sections of attribute groups (e.g. keeping all allergens together) or not. In the former case, apps would thus first reorder the sections, and then the attributes in each section.
 
Apps can decide to keep the sections of attribute groups (e.g. keeping all allergens together) or not. In the former case, apps would thus first reorder the sections, and then the attributes in each section.
 +
 +
= Proposals for new product attributes =
 +
 +
You can add / discuss proposals for new product attributes below.
 +
 +
Notes:
 +
* Product attributes need to be put in the form of a requirement that can be matched or not
 +
** e.g. "the product has good nutritional quality", "the product does not contain XYZ"
 +
* Adding attributes has a price: to compute them, to return them (e.g for Personal Search the client needs to get all the attributes of potentially hundreds of products for every search query), and also to display attribute choices to users without confusing them.
 +
 +
Proposals:
 +
 +
* climate gas emissions
 +
** in t CO2-eq per kg
 +
* Origin Country
 +
** in percent of weight of the final product
    
[[Category:Project:Personalized_Search]]
 
[[Category:Project:Personalized_Search]]
 
[[Category:ProductOpener]]
 
[[Category:ProductOpener]]

Navigation menu