> This is how separate IP elements are handled.  You put them in
> external data
> files and then the GPL'd code reads those files at runtime.  As
> long as the
> two files are not compiled together into one file or linked statically, or
> linked dynamically with defined references through an API, you
> don't need to
> use the GPL license with that external file.
>
> Thus, if you have an external data file that does not contain Open Game
> Content, and is not a part of an executable or designed to be
> compiled into
> an executable, that material does not have to be GPL'd.  If you have an
> external data file that >does< contain Open Game Content, you have to GPL
> that file.
>
> Ryan


I just want to probe this for a second to make sure I understand it clearly.

What if I created an executable that used the non-GPL data that passed API
information to a GPL executable that used non-GPL data as well...  It seems
like a stretch to say that any executable that "links" to GPL data would
come under the GPL license... what about the Windows operating system that
interprets executable code for display on a computer?  It certainly doesn't
fall under GPL.  The rendering API is directly interacting with the
executable that accesses GPL data, etc...  I'm not sure where you can draw
the line.

What about discovery and proprietary interests.... If I had separate .dlls
or .exes that I wanted to retain a proprietary interest in, I certainly
would not want to be challenged to "prove" that it was separate, which would
either mean reverse engineering it to see or revealing source.

This gets a bit too hairy on the software side... at least the capitalist
pig side of me says so.

I suppose the main thing this whole thing accomplishes is to provide a means
for fan-boy gamers to "add to the pile" of D&D supporting materials, but is
certainly focused on preventing any commercialization due to utilizing
OGL'ed material.. except for the Hasbro side.  Not a big deal, but it does
indicate the core reasoning behind the support of the OGL and the WotC Open
Source push... which is to expand the network of D&D gamers and D&D
consumers with a clearly defined set of "permissions" to donate work and get
a bit of glory on the side.. your name in lights as it were.  One
interesting aspect of this is that "permission" to utilize game "rules" is
really not even necessary (IANAL), but it's like when your mom knows you're
going to stay out past midnight anyway, so she gives you permission...

I'm still going to help publish books however, since the means of
recapturing revenue is still preserved by selling books.  Software's a nix
though.

Jared Nielsen
www.GameCodex.com

-------------
For more information, please link to www.opengamingfoundation.org

Reply via email to