Changes

Jump to navigation Jump to search
Line 51: Line 51:  
The OFF web site, and apps, '''should only use these OFF processed fields''' to display the nutrition data:
 
The OFF web site, and apps, '''should only use these OFF processed fields''' to display the nutrition data:
   −
* <code>{nutrient-id}_100g</code> or <code>{nutrient-id}_serving</code> (depending on the value of nutrition_data_per): value in g or in kJ. The values are passed as float/double???
+
* <code>{nutrient-id}_100g</code> or <code>{nutrient-id}_serving</code> (depending on the value of the value of <code>nutrition_data_per</code>): value in g or in kJ. The values are passed as float/double???
* <code>{nutrient-id}_value</code>: to show the original entered/passed data (useful for characters as "<" or "~").
+
* <code>{nutrient-id}_modifier</code> to get the value modifier ("<", ">", "~")
 +
* <code>{nutrient-id}_value</code>: to show the original entered/passed data.
    
The web site and apps '''must''':
 
The web site and apps '''must''':
Line 71: Line 72:  
== Possible improvements to make things (a bit) simpler ==
 
== Possible improvements to make things (a bit) simpler ==
   −
* In the API, rename the "nutrient-id" fields (such as energy-kj, saturated-fat) to "nutrient-id_value", so that it matches the name of the field stored. It also makes clearer where the value is coded.
+
* In the API, rename the <code>{nutrient-id}</code> fields (such as <code>energy-kj</code>, <code>saturated-fat</code>) to <code>{nutrient-id}_value</code>, so that it matches the name of the field stored. It also makes clearer where the value is coded.
* Store the energy-kcal values in kcal, without converting them to kJ
+
* Store the <code>energy-kcal</code> values in kcal, without converting them to kJ
 
** This is probably what people intuitively expect
 
** This is probably what people intuitively expect
 
** It removes unnecessary conversions from kcal to kJ and back (which is not trivial, as some people/apps may choose a different conversion factor, such as 4.2 or 4.185)
 
** It removes unnecessary conversions from kcal to kJ and back (which is not trivial, as some people/apps may choose a different conversion factor, such as 4.2 or 4.185)
 
** This would be a breaking change if some apps use the energy-kcal_100g/serving or energy-kj_100g/serving fields
 
** This would be a breaking change if some apps use the energy-kcal_100g/serving or energy-kj_100g/serving fields
 +
* Expose only the recommended fields (see [[Nutrients_handling_in_Open_Food_Facts#Data_display|data display]])
    
== Possible improvements to make things (a bit) more complex ==
 
== Possible improvements to make things (a bit) more complex ==
72

edits

Navigation menu