4 ms·

The requirements were clearly spelled out. “ A. If any part of the submission documentation depicts, identifies, or includes any person that is not an individu

The 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 ago
That 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...

nl 6y ago

That 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...