SyncGuard: Cross-Platform Data Validator

In the article, you claim:> There are also important licensing questions. A user’s permission to send a library to OSM is not automatically the same as having a sufficiently clear right to release that factual information under terms compatible with OSMwhich would imply that you could not make available your database available for download under ODbL. Yet you have made it available under that license.Maybe that part of the article needs further editing?Also, if the data of your tool is now available under ODbL, then the tasks related to importing it into OSM can be effectively performed by any

Maybe an alternate process could use streetcomplete? Make the imported data available in streetcomplete for validation, then include it only after x validations?

No, and this is the issue I have with his write up. Yes all points listed are correct. But do they apply in the same rigor and depth for all imports, likely no. There is a difference between a tiger import or local government address data for thousands of buildings VS a few thousand street libraries. The community review process should/would consider this. I would also guess that it took some time to investigate all of the requirements and write it down. Might as well have written an import plan and discussed it :-)