<< Why doesnt it seem right? What you agreed to is the OGL which specifically states that can be done. >> << Because you're agreeing to a contract you didn't read, have no say in the writing of, and can't withdraw from if you don't like that terms. That just seems wrong, legally. >>
As someone else said, *you* are not bound by the terms of another version of the OGL if someone re-releases the OGC you designated. The person who re-released the content is. Even then, they can only use your OGC. << There should be, in my opinion. If you release something under version X of the OGL, that's how you released your work. You didn't release it under version Y, so no one should have any right to rerelease it under a different version. >> Ah, but the OGL grants anyone the right to reuse your OGC, not your entire work. Even if a later version of the OGL removed PI and required everything to be open, the only thing from a work of yours that someone could use is what you had declared was Open. By declaring something as OGC, you're letting others do what ever they want to it as long as it remains open, and under the OGL. << Granted all I know about contract law could fit in this email, but I didn't think you could bind people to unseen terms with no chance of withdrawal. >> You can't bind someone to unseen terms. Even if the terms of the contract changed (like the d20 stl can be), the contract would have to be renegotiated, giving you the option of opting out. -- Korath, "He was already dead, he died a year ago, the moment he touched her. They're all dead, they just don't know it." --Eric Draven, The Crow _______________________________________________ Ogf-l mailing list [EMAIL PROTECTED] http://mail.opengamingfoundation.org/mailman/listinfo/ogf-l
