nemesis wrote:
> 
> Yes, i've read about the threshold of originality.  Well, i think if we dig
> too much deep we're going nowhere.  Source code licensing is as far as i'll
> go.

If you don't address the issue that for some kinds on include files 
using them results in creating derivate works and for some it does not 
you will end up with a license that means different things for different 
files and that has an unclear meaning for most of them.  This is the 
case *for all licenses discussed so far* although you would of course 
always be on the safe side if you regard the image as a derived work.

If you want the use of the include files in a scene render to be 
completely unrestricted the way to go would be to create a wrapper 
license that defines 'use' (like for example rendering of a scene 
#including the file) and puts all other uses (and only those) under one 
of the discussed licenses.  This kind of resembles the way the POV-Ray 
license is designed (with separate use, distribution and source code 
license texts).

Christoph

-- 
POV-Ray tutorials, include files, Landscape of the week:
http://www.imagico.de/ (Last updated 15 Oct. 2006)
MegaPOV with mechanics simulation: http://megapov.inetart.net/

Post a reply to this message