Its like requiring a degree in mechanical engineering to be a racecar driver, and being told to assemble an engine during your interview.
18 karma · joined March 28, 2016
Its like requiring a degree in mechanical engineering to be a racecar driver, and being told to assemble an engine during your interview.
Its not an attribution issue. Its more that if the data is mixed into the database in a certain way, that data must also be made available under terms similar to the ODBl. So if I have the locations of the best Thai restaurants in a city, and I add this data to OpenStreetMap data, refine it based on the existing OSM data and present it, I must make my restaurant data available under the terms of the ODBl.
If you are just overlaying data on top of image tiles generated from OSM data I think you are okay, but once you mix the data it becomes weird. For example if the OSM data has a few of those restaurants in it, and you modify your data set to remove them so there's no duplicates, I think thats a case where you must share your data back with the OSM project. You can check out the OSM (non-dev) mailing lists for more discussion on this.
The ODBL is kind of like copyleft license for databases (gross oversimplification)
The reason I like this model is it encourages use in areas where you have multiple users but you aren't using the software to make any money like in schools.
Also what made you decide to go with 'number of users' as the determining factor for payment over a democratization model like with Unreal Engine?
There's some flowery language there about having a genuine desire to want to hire you unlike those 'other evil companies!'... sounds like the same shit pretty much every other company does to me.