William Hindmarch wrote: >Where should the OGL be displayed on a web site with no materials intended >for download? > As a seperate file (say, "OGL.TXT") that each and every accessable-by-design page has a logcical link to. A small font hyperlink labeled "legal info" directing to a page that has the OGL, your copryight, and identification of PI and OGC (and possibly a note about what you consider the extent of the work to be) and the OGL would do nicely.
Of course, this is only for a site that's actually COVERED by the OGL. One that's just *about* d20 products (like, oh, any company's web site, ENWorld, www.castlesteelstone.com) doesn't need to worry about the OGL since it's not covered by it. Two things that you also might consider are the brute-force "OGL on every page" approach, or an "OGL in the comments" approach. Heck, you could do both--if you don't mind the OGL slowing down every HTML page, that is. >I know we've been through this question before, and I know the answer in >the OGF webpage's Q&A, so I'm concerned less with a legal answer and more >with an operations answer. Of course, I'll also feel better to here you >local authorities state the legal answer again, too. :) > Well, I'd guess that the OGL has to be somewhere within the "work" that a "reasonable man" could find, and that somehow "clearly identifies" what's OGC and what's not. >Is there a customary location for the license developing on your web sites? >Does a garden variety web page with HTML text classify as material >"designed to be downloaded?" Are any customs developing regarding hyperlinks >to the license, etc? > Well, there is that little suggestion about putting your URL into Section 15... DM > _______________________________________________ Ogf-l mailing list [EMAIL PROTECTED] http://www.opengamingfoundation.org/mailman/listinfo/ogf-l
