Actually you hit the nail on the head. 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
from then on all text that is OGC would be output with the [BEGIN ... and
END tags. This would make it clearly identifiable to any user that plays the
mud and wants to identify it. The fact that they need to type SHOW OGC would
not be a problem since this would be on the main screen saying OGC can be
viewed by typing the command SHOW OGC. Which any mud user would know how to
do.
Hope this method would be acceptable :-)
I think I'll do this and the seperate folder/file method, then at least
its clearly identified from my point of view, if anyone objects then I've 30
days to correct it, or simply remove it.
bb.
----- Original Message -----
From: "Michael Hahn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 03, 2001 7:07 PM
Subject: Re: [Ogf-l] SRD, Computer Junk, and Going Nuts...
> >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
>
_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://www.opengamingfoundation.org/mailman/listinfo/ogf-l
