4 ms·
For those who aren't aware, many Kaggle competitions allow external data (this one did) but require disclosure, and often there is some back-and-forth to clarif
by nl 6y ago
For those who aren't aware, many Kaggle competitions allow external data (this one did) but require disclosure, and often there is some back-and-forth to clarify the exact details of what is used.
In this case the disqualified participants are well respected and haven't previously been involved in any dubious behavior. They properly disclosed what they were doing and despite there being other clarifications there was none that person releases for CC-BY data would be required.
Obviously this is a ridiculous requirement. There's no way for that team to be able to do that, but they did take proper care to use data that Facebook could reasonably use. It's unreasonable for FB/Kaggle to expect participants in a data science competition to suddenly know what Facebook's data ethics department is demanding this week outside what is legally required.
- mkagenius 6y agoYes, this seems like a clear case of bullying by FB and in turn by Kaggle. As a contestant I would be furious too. If I shared what data I am using during the contest and to other participants, and then I won then its completely fair. After the match, suddenly the Facebook legal team wakes up, they should have been awake during the whole contest. Ideally, they should give the prizes and then do another contest where the legal team is involved throughout
- deleted 6y ago[deleted]
- kuu 6y agoIf they disclosed the data, I agree with you that the decision should have been done during the competition, not after it...
- Hendrikto 6y ago> There's no way for that team to be able to do that There is an extremely simple solution to that: Do not use the data. There are countries in which privacy is considered important. Data being public has no influence on whether is is considered personal in the EU. Also, copyright has nothing to do with the issue.
- jasonlotito 6y agoThe requirements were clearly spelled out. “ A. If any part of the submission documentation depicts, identifies, or includes any person that is not an individual participant or Team member, you must have all permissions and rights from the individual depicted, identified, or included and you agree to provide Competition Sponsor and PAI with written confirmation of those permissions and rights upon request.” Notice the permission is from people identified and depicted, not the copyright holder. I’m not a lawyer and even I find that straight forward and clear.
- nl 6y agoThat was part of the "Winning Submission Documentation", not part of the rules. It's true that it was there, but to quote the authors: We suspect that most competitors also did not realise these additional restrictions existed - we are unable to find any data posted in the External Data Thread which meets this threshold with a brief scan. During the competition, the rules on external data were repeatedly clarified, so this leaves us wondering why Kaggle never took the opportunity to clarify that external data must additionally follow the more restrictive rules for winning submission documentation.[1] Here's a Kaggle competition admin saying: he deadline to declare external data is on March 3rd. So you cannot add new external datasets after that deadline, but you can use any datasets that have been declared (which are not prohibited) on this thread.[2] and clarrfying licensing: So it is expected that competitors understand the external data they’re using and ensure it matches the requirements in the rules. I’ve answered the question about BY-NC not being available for use by all (non-commercial use) and therefore violating the requirement that external data be available for use by all participants.[3] Note nothing about there being extra "rules" in the "Winning Submission Documentation". [1] https://www.kaggle.com/c/deepfake-detection-challenge/discussion/157983 https://www.kaggle.com/c/deepfake-detection-challenge/discus... [2] https://www.kaggle.com/c/deepfake-detection-challenge/discussion/121203#743403 https://www.kaggle.com/c/deepfake-detection-challenge/discus... [3] https://www.kaggle.com/c/deepfake-detection-challenge/discussion/121203#732954 https://www.kaggle.com/c/deepfake-detection-challenge/discus...