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 OSM

which 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 anyone, not necessarily you.