Jon
Freedoom Bloke

Posts: 1165
Registered: 09-00 |
Ok first question. Where did the data in the TEXTURE? lumps in freedoom from? Were the patch offsets copied verbatim from doom or re-implemented in some fashion? I don't have the means to check this right now, which is why I ask. If someone looked at a texture definition and "guessed" the patch composition offsets and wrote those into the freedoom lumps, there would be no problem. If the definitions were copied directly, we might have an issue. One question then is whether that data is copyrightable or not. Consider http://www.softwarefreedom.org/reso...e-analysis.html for example (a code analysis of a driver in Linux derived from some code that was in one of the BSDs). This document (prepared by software copyright law experts) covers the various types of stuff in the .c and .h files, and seems to conclude that some things, like register offset definitions and the like, are not. Quoting
This file is primarily an arrangement of constants, storage structures, and the like for the Atheros cards. The extent to which this type of work is copyrightable is debatable.
The file primarily includes constants and structures related to the card. Again, the copyrightability of such work is minimal
and It should be noted, however, that a table of constants, such as that found in ath5k_reg.h, is not necessarily within scope of copyright.
The implication from a further paragraph suggests that to be copyrightable the code must be a "novel and creative work".
So, I'm not sure what relevance this has but it's some food for thought.
|