[OSM-legal-talk] When does a produced work has to be share-alike?
Hi. ODbL don't want produced works to be share-alike, but wants the underlying database to be. So what's the deal when I'm strictly separating ODbL licensed data from data under another license? In Illustrator, I could load a SVG created by qGIS with OSM data. I could only *link* to this SVG only without embedding it. So it's in a complete seperate file / XML DB, which can't or doesn't have to be edited. Now I could add other layers with my own streets or even with data under a properity license. When storing the new file, the OSM-data doesn't get changed anymore. Sure, I have to release the SVG file or the workflow under share-alike, that's fine so far. But when I press export to PDF, will this be an intermidiate database, which also has to be share-alike? This simply wouldn't be possible pecause of the use of non-free data. In my eyes, the only solution could be to find a printers' shop, which directly printers from Illustrator to T-Shirts... But why does ODbL do this to users of the data? I think, ODbL harms the actual use of its data with other datasources. Nearly all commercial spatial data under a properity license allows you to mix the data when you give the right credits (f.e. rivers: (C) A. Corp, streets: (C) B. Corp). ODbL forces you to release your data mashed-up. That's way too strict and doesn't have to do anything with being open, but with being free. I hope, anyone is still active in this mailing-list... Best regards, Lars-Daniel ___ legal-talk mailing list legal-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/legal-talk
Re: [OSM-legal-talk] When does a produced work has to be share-alike?
On 29/03/15 16:43, Lars-Daniel Weber wrote: Sure, I have to release the SVG file or the workflow under share-alike, that's fine so far. But when I press export to PDF, will this be an intermidiate database, which also has to be share-alike? This simply wouldn't be possible pecause of the use of non-free data. In my eyes, the only solution could be to find a printers' shop, which directly printers from Illustrator to T-Shirts... I'm not sure if a PDF counts as a database; probably only if accurate spatial data can be derived from it. But in any case, you only have to release a derivative database if it is published. If all you're doing with it is sending it to a printer, who is working for you, and who will not make the file available to anyone else, then that's not a publicly used database, so the share-alike requirement doesn't apply. Jonathan. -- Dr Jonathan Harley SpiffyMap Ltd j...@spiffymap.net 0845 3138457www.spiffymap.com The Venture Centre, Sir William Lyons Road, Coventry CV4 7EZ, UK ___ legal-talk mailing list legal-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/legal-talk
Re: [OSM-legal-talk] When does a produced work has to be share-alike?
Hi, On 03/29/2015 05:43 PM, Lars-Daniel Weber wrote: In Illustrator, I could load a SVG created by qGIS with OSM data. I could only *link* to this SVG only without embedding it. So it's in a complete seperate file / XML DB, which can't or doesn't have to be edited. Now I could add other layers with my own streets or even with data under a properity license. When storing the new file, the OSM-data doesn't get changed anymore. Provided that you don't edit your other data set based on the OSM data you now see on the screen (uh, this road is now there twice, let me remove it... etc.) Sure, I have to release the SVG file or the workflow under share-alike, that's fine so far. But when I press export to PDF, will this be an intermidiate database, which also has to be share-alike? I don't have enough information to say whether the PDF will be a produced work or a database, but even if it were a database, it could be a collective database in which case share-alike would only apply to the ODbL part inside. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ legal-talk mailing list legal-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/legal-talk
