> J. Michael Looney
>
> Hmmm... Not allowing "software" will prohibit plain text files as
> well. I know we went over this before, but I _do_ have a lawyer who
> _still_ says "All computer files are 'software'".
And lets not forget formats that really blur the line, like Postscript,
DHTML or PDF.
> As I said before, what I am planing on doing is creating a product that
> _outputs_ OGC/d20 content, not a OGC software as such. In my mind the
> software that generates the OGC/d20 content is no more than a fancy way of
> rolling dice, looking something up in the d20STL and a typing _very_ fast.
> How would this fit into you vision of d20 software? Or, for that matter,
> a CGI application that generates a d20 "dungeon"? How would you fit
> _that_ into your "no software" concept and _still_ allow D20 modules to be
> "published" via the web?
The trouble is that if you write source code that is based on OGC data
files, then that code is derivative of the data, and hence must be OGC
itself. You would need to sever the lines of derivation by claiming 'rules
only' in order to make this work. I don't think you need to bother - just
claim that the source code is itself OGC, and thus the binary is OGC, mark
the graphics and title of the work as PI, and keep the source code under
wraps (unless it is an Open Source project, in which case publish it
freely). Very few people will be able to make use of the OGC in the binary
file, but it will still follow the letter of the OGL.
-Brad
