ODBL non-compliance: Difference between revisions

From Open Food Facts wiki
(+ Tous Anti Inflation)
(Updates)
Line 54: Line 54:
|[[User:Charlesnepote|Charles Nepote]] on 2021-05-26
|[[User:Charlesnepote|Charles Nepote]] on 2021-05-26
|[[User:Charlesnepote|Charles Nepote]] on 2021-05-26 via slack + 2021-06-30 followup
|[[User:Charlesnepote|Charles Nepote]] on 2021-05-26 via slack + 2021-06-30 followup
+ 2023-06-12 followup via Slack and email
|
|
|
|
Line 127: Line 128:
| -
| -
|[[User:Charlesnepote|Charles Nepote]] on 2023-04-18
|[[User:Charlesnepote|Charles Nepote]] on 2023-04-18
|[[User:Charlesnepote|Charles Nepote]] on 2023-04-18 via slack  
|[[User:Charlesnepote|Charles Nepote]] on 2023-04-18 via slack
+ 2023-06-12 followup on Slack
|
|
|
|

Revision as of 16:53, 12 June 2023

This page has mostly been inspired from the great work of OpenStreetMap community.

Please first check ODBL License to understand ODBL (non-)compliance.

Process (suggestion)

  1. When you discover a license non-compliance, check first if the usage of Open Food Facts data is substantial. If the usage of Open Food Facts data is substantial, continue with the next steps. If you are not sure, ask other people on a suitable place: #license channel on slack, or contact@openfoodfacts.org.
  2. In fact, even if you are sure, you should definitely share your case with other people before.
  3. Add an entry to the bottom of the table below. If you are unsure about the non-compliance, discuss it on the one of our common communication channels (see above). If you are sure, you can report it on slack, at forum or a mailing list, too.
  4. Contact the publisher with a suitable pleasant and non-threatening email and update the record with the date you've contacted them.
  5. Wait for a response for a suitable period. If that does not create the desired response then you should follow up with a second attempt to contact the publisher.
  6. If that does not work and the violation is considered serious then report it, if not done yet, at #license channel on slack or contact@openfoodfacts.org.

Hints to contributors

Be gentle! We are a project for providing food transparency and not to argue with somebody about legal issues. It doesn't help anybody playing the police and collecting as much cases as possible. This could give Open Food Facts a bad image. Don't be too correct. If they give it their best then it is ok.

List of usages which doesn't comply with ODBL license

Page Attribution ok Share-Alike ok Added by Dates contacted Date fixed Comments
https://www.bonasavoir.ch/nutriscan partially, ODBL not mentioned - Charles Nepote on 2020-11-09 Open Food Facts is briefly mentioned in the "Les labels" page (without link) nor license, and at the end of the Nutri-Score page, with a link to openfoodfacts.org and a mention to the fact that anyone can contribute to the database.
https://www.lapplidesconsos.com/ no no Charles Nepote on 2020-11-19
https://jobothoniel.com/foodfacts/ no no Charles Nepote on 2021-05-26 Charles Nepote on 2021-05-26 via email + 2021-06-30 followup Data are the same. Photos are directly linked to Open Food Facts website.


Access to photo blocked on 2021-07-13.

Halal ou Pas ? no - Charles Nepote on 2021-05-26 Charles Nepote on 2021-05-26 via slack + 2021-06-30 followup

+ 2023-06-12 followup via Slack and email

Treev no - Charles Nepote on 2021-07-02 Charles Nepote on 2021-07-02 via slack + 2021-11-02 followup + 2021-12-02 (slack msg + email)

2022-02-10 (slack msg + email: last call before action)

ScannerFood no - Charles Nepote on 2021-07-02 Charles Nepote on 2021-12-02 via email
Zediet.fr yes no Charles Nepote on 2021-12-20 The website is mixing data from Open Food Facts with other kind of data; e.g. https://www.zediet.fr/aliments/7613035648494/decryptage.html
Scrapp no no Charles Nepote on 2022-01-10 Charles Nepote on 2022-02-10 via email and contact form
Digit-Eyes no no Charles Nepote on 2022-01-10 Sometimes Open Food Facts data is not sourced because they reuse data from one of our reusers, eg. : https://www.digit-eyes.com/cgi-bin/digiteyes.cgi?upcCode=3039824000313&action=lookupUpc&go=Go%21

Sometimes Open Food Facts data is clearly sourced. We have to check if share-alike clause is respected: eg. https://www.digit-eyes.com/cgi-bin/digiteyes.cgi?upcCode=3048405000024&action=lookupUpc&go=Go%21

Food Facts partially - Charles Nepote on 2022-05-02 Open Food Facts is not mentioned in the app. The name of the app and the logo are nearly the same as Open Food Facts' name and logo.
Food Scanner no Charles Nepote on 2022-08-29 Open Food Facts is not mentioned on the App Store.
Food Facts - Charles Nepote on 2022-08-29 The name of the app and some logos/contents are nearly the same as Open Food Facts' name and logo.
Insekten Warn App no - Charles Nepote on 2023-04-18 Charles Nepote on 2023-04-18 via slack

+ 2023-06-12 followup on Slack

Tous Anti Inflation no no Charles Nepote on 2023-06-01 Charles Nepote on 2023-06-01 via email
Page Attribution ok Share-Alike ok Added by Dates contacted Date fixed Comments

Banning access?

When the people do not answer after one month, and the website or app is still not compliant with the ODBL or Creative Commons licences, it is possible to temporary ban access from the app or website. (See this example to allow banning from referrer.)

Banning should always be the last solution.

Fixed cases

Page Attribution ok Share-Alike ok Added by Dates contacted Date fixed Comments
Food Checklist: https://chester-sw.com/food-checklist/ no - Charles Nepote on 2021-05-26 Charles Nepote on 2021-11-02 via email 2020-11-09 2021-11-29: website and Android Play Store's product page now mention Open Food Facts.
https://www.food-watching.com/ no no Charles Nepote on 2020-11-03 Charles Nepote on 2020-11-04 via email 2020-11-09

See also