Line 9:
Line 9:
=== Make the API re-user centric ===
=== Make the API re-user centric ===
−
'''Description'''
+
==== Description ====
The Open Food Facts API is used by a wide variety of applications (more than 200 of them) helping people making better choice around food.
The Open Food Facts API is used by a wide variety of applications (more than 200 of them) helping people making better choice around food.
It has grown organically with time, on a volunteer bases, and is sometime messy and complicated to understand. This is a barrier to re-use and does make every one loose time.
It has grown organically with time, on a volunteer bases, and is sometime messy and complicated to understand. This is a barrier to re-use and does make every one loose time.
−
'''Expected outcomes'''
+
==== Expected outcomes ====
−
Propose a new API, limited to most important items, that is Open API compatible, well designed and easy to understand.
Propose a new API, limited to most important items, that is Open API compatible, well designed and easy to understand.
Line 25:
Line 24:
Along the way, the current API documentation should be improved, and a full Open API compliant specification for the new API must be written.
Along the way, the current API documentation should be improved, and a full Open API compliant specification for the new API must be written.
−
'''Project information'''
+
==== Project information ====
*repository: https://github.com/openfoodfacts/openfoodfacts-server/
*repository: https://github.com/openfoodfacts/openfoodfacts-server/
*Slack channels: #productopener
*Slack channels: #productopener