I know for the game that I'm running, we're utilizing (or shortly will be) a
similar system to fall under the OGL. The way we're going to put in the
specific information is in news files. One types 'ogl' and you get a full
list of subjects that you can peruse. If you type 'ogl license', for
example, it will pull up the license information. This way, we don't need
to have all the information specifically interwoven into certain aspects of
the game but have all of it detailed in a single location and everything
that falls under 'ogl <whatever>' is ogl specificied.
-Philippe
-----Original Message-----
From: Brad Thompson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 07, 2001 10:24 AM
To: [EMAIL PROTECTED]
Subject: RE: [Ogf-l] SRD, Computer Junk, and Going Nuts...
> Hicks
>
> Would I now be in violation? Since I am not redistributing the binary but
in a
> sense the output is been distributed :(
The output would have to be clearly marked. The binary would not need to be
marked because you are not distributing it. I'm sure you are aware that in
order for this to work it must be a server-side app without a client-side
component (or at least with a client-side that supports clearly marking the
OGC).
Interestingly, the source code for the server-side binary would not need to
be made available to anyone in particular, so if you didn't distribute it
you could cut corners marking the source and nobody would ever be the wiser.
> I'm writting a mud in which I want to
> have OGC but have been limited in that to show the end user what is OGC in
> the classic way done by changing font, cannot be done since the user
> connects to the mud via telnet and I have no control over their
font/colour
> background etc. All I control is the actually text output. Adding [BEGIN
> OGC] [END OGC] would ruin the atmosphere of the game, but if a
> user playing the game though hmmm wonder if this is OGC and then did
> SHOW OGC
Be careful here. The OGL requires that you clearly identify OGC wherever it
appears. That includes in the text of a MUD. It *MIGHT* be Ok if the SHOW
OGC were something persistent that you could toggle (SHOW OGC ON, SHOW OGC
OFF), and it was turned on by default. That way the user would be making
the choice and it would be out of your direct control. It would be very
smart of you in this case to have a text message appear every time they
log-in that tells them that the output of the program contains OGC and that
they have chosen not to see it. Even so, you are still essentially
distributing unmarked OGC, and it could come back and bite you.
Also, [BEGIN OGC][END OGC] are pretty cumbersome tags, there is no reason
that you couldn't use something less obvious: curly braces, brackets,
asterisks or something like that.
-Brad
_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://www.opengamingfoundation.org/mailman/listinfo/ogf-l
_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://www.opengamingfoundation.org/mailman/listinfo/ogf-l
