Re: [OSM-legal-talk] images are Produced Works
On Mon, Mar 2, 2009 at 5:10 PM, Richard Weait rich...@weait.com wrote: My position is that images are Produced Works, not a derived OSM database. Rendered images are a creative work that requires skill and judgement. This is an important use case and ODbL Section 1 Definitions specifically includes images in the definition of Produced Work. Cool, I definitely agree with you on this, when considering the cycle map. However, instead of rasters, what about vector images, e.g. SVG? To me they could be construed as mini databases, since they're a structured list of attributes and properties. I'd be interested in what you think on this. Cheers, Andy ___ legal-talk mailing list legal-t...@openstreetmap.org http://lists.openstreetmap.org/listinfo/legal-talk
Re: [OSM-legal-talk] images are Produced Works
On Tue, Mar 03, 2009 at 09:40:08AM -0500, Richard Weait wrote: I see SVG as just another image. Raster or Vector; the image format is not a problem. […} The problem is behaviour. In this case the potential problem is Some Jerk trying to use OSM database without living up to their license obligations. An SVG image may contain a attributes that are far closer to the those from the orignal data, but that makes 4.7 “Reverse Engineering” no less applicable. Just because it is potentially trivial to extract the data from the SVG file does not mean the licence ceases to apply. Simon -- A complex system that works is invariably found to have evolved from a simple system that works.—John Gall signature.asc Description: Digital signature ___ legal-talk mailing list legal-t...@openstreetmap.org http://lists.openstreetmap.org/listinfo/legal-talk
[OSM-legal-talk] images are Produced Works
My position is that images are Produced Works, not a derived OSM database. Rendered images are a creative work that requires skill and judgement. This is an important use case and ODbL Section 1 Definitions specifically includes images in the definition of Produced Work. I further believe that a directory tree full of images ./zoom/x/y are still Produced Work and that even a database of these Produced Work images is still a Produced Work. In the special case of somebody creating a renderer that takes input from the OSM database and renders it as OCR text, then uses a post-processing step to OCR-to-text back into a database; that is reverse engineering and covered in the Reverse Engineering clause. Rendered images being Produced Work is an important use case judging from the level of discussion. Perhaps the legal team can assure us that we are fine and the the legal reading supports our goals. If not perhaps they can fix the terms of the license and / or the preamble to make this both clearer to laymen and clear in law. Best regards, Richard ___ legal-talk mailing list legal-t...@openstreetmap.org http://lists.openstreetmap.org/listinfo/legal-talk
