I would suggest that both the data[source] and the program[output] show
which content is OGC... that way you protect yourself from the court's
definition of "reasonable person".
-John J. Kaufman
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Alec A.
Burkhardt
Sent: Sunday, June 03, 2001 10:54 PM
To: [EMAIL PROTECTED]
Subject: Re: [Ogf-l] SRD, Computer Junk, and Going Nuts...
On Sun, 3 Jun 2001, RealmsCrafters wrote:
> [Originally posted to email by mistake. Sorry Alec.]
>
> >>>>
> ------Original Message------
> From: "Alec A. Burkhardt" <[EMAIL PROTECTED]>
>
> It's fairly clear that whenever OGC appears it must be identified, so
> the separate folder idea is out since when someone is looking at the
> source code they must be able to identify the OGC. <<<<
>
> I'm sorry Alec, but I find this statement rather confusing. You are
> assuming that source code must be released with OGL software.
I don't know if that's what I'm assuming, since I'm not a programmer. By
source code I meant the software program itself must use _identified_ OGC.
You can't use OGC in the program which is not identified and then simply
include a separate listing of all the OGC content used in the program.
The OGC content must be identified in the program so that anyone who can
and does examine the program (itself, not what it outputs) can tell what
is OGC.
_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://www.opengamingfoundation.org/mailman/listinfo/ogf-l
