>From Alec A. Burkhardt:
> There still exists the big issue of making all OGC both available and
> clearly identified. Programs that use OGC beneath the surface face
the
> problem that the OGL requires that OGC be available for others to use.
I
> don't have any ideas on how to solve this issue but there probably is
one.
> Perhaps the separate folder idea works here, but that still leaves the
> other problem. The fact that OGC must be clearly identified
everywhere it
> appears means that having a separate place where all OGC is collected
is
> not sufficient. The OGL doesn't permit someone to publish a book
where
> the OGC is only identified by collecting the OGC from the main text
and
> putting it in appendix. OGC must be clearly identified everywhere it
> appears. The same rules apply to software applications as apply to
> published text. So OGC must be identified within the program
> itself. There simply is no way around this, no do I see any reason
there
> should be since it is the only way of guaranteeing OGC remains OGC.
The way I would handle this, if I were to write a piece of software,
would be for a game, include an option on the main menu to "Display Open
Gaming Content" which would do exactly that. If it were an application,
I would do so in a splash screen. If I were distributing source code, as
well as binaries, I'd also indicate through comments in the code itself
anywhere the OGC could be found. I am pretty sure that this would meet
the requirements of OGC being clearly indicated, but feel free to point
out what I'm missing, if I am.
Michael Hahn
http://users.csionline.net/~silver
"Life is what happens in between plans."
_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://www.opengamingfoundation.org/mailman/listinfo/ogf-l
