I'm guessing so!Hmm... I can't see the quote that's being responded to here. That means the respondee has ignored me I presume?![]()
![]()
I'm guessing so!Hmm... I can't see the quote that's being responded to here. That means the respondee has ignored me I presume?![]()
![]()
yes this, that it binds the person to these restrictions outside the context of the document they are publishing under the OGL.Which interpretation?
If you're talking about section 7, all I'm doing is reading the plain words of the first clause:
You - the licensee, as per section 1 - agree not to Use any Product Identity
Lets start with the plain meaning of Section 7. An earlier post emphasizes the first two sentences, and a contrast between them.If you're talking about section 7, all I'm doing is reading the plain words of the first clause:
no it doesn't, it releases you of the requirement not to use any WotC Product Identiy (not that this means you actually now can, it just no longer violates your license agreement...).Of relevance here, "You agree to not use any Product Identity."
By updating "your" product to use the ORC and a new ORE (Open RPG Engine), "you" are not using any Hasbro-WotC Product Identity.
Switching to the ORC satisfies the stipulation.
no it doesn't, see above, only now you print on your adventure 'Compatible with D&D(tm)', something the OGL would again not have allowedSecond sentence.
"You agree not to indicate compatibility or co-adaptability with any Trademark or Registered Trademark in conjunction with a work containing Open Game Content except as expressly licensed in another, independent Agreement with the owner of such Trademark or Registered Trademark."
Of relevance here, "You agree not to indicate compatibality ... with any Trademark ... in conjunction with a work containing Open Game Content."
By updating "your" product to use the ORC and the ORE, "your" product does not contain Open Game Content.
Switching to the ORC satisfies the stipulation.
maybe, but not for the reasons you are givingTo abandon the OGL and its Open Gaming Content, is the end of the matter.
Thats the point.it just no longer violates your license agreement
If you release an adventure under ORC, then you never agreed to the OGL. You never committed yourself to the terms of the OGL. Your product has nothing to do with the OGL.If you release an adventure under ORC and then use a Beholder in the adventure, then you are using WotC's product identity, and you do so in a way the OGL would not have allowed.
I get that this is how it works, but doesn't that basically avoid the whole scenario we were discussing? For that you need to first have something published under OGL, and then the question becomes whether that only imposed the limitations on that one product, or on you across products. If you bypass the first step, you never entered into the agreement that is being discussed.Thats the point.
[...]
If your product uses a "Beholder", then the product violates normal copyright laws.
That's interesting, but a bit surprising given the words of the licence.yes this, that it binds the person to these restrictions outside the context of the document they are publishing under the OGL.
I am not saying you are reading it wrong, it’s just not something I would have even considered a possibility.
Actually, doesn't this break down actually counter your argument? The second sentence explicitly refers to work containing OGC, while the first sentence do not?Lets start with the plain meaning of Section 7. An earlier post emphasizes the first two sentences, and a contrast between them.
I am using this source, as convenient reference: opengamingfoundation .org/ogl.html
First sentence.
"
7. Use of Product Identity:
You agree not to Use any Product Identity,
including as an indication as to compatibility,
except as expressly licensed in another, independent Agreement
with the owner of each element of that Product Identity.
"
Of relevance here, "You agree to not use any Product Identity."
By updating "your" product to use the ORC and a new ORE (Open RPG Engine), "you" are not using any Hasbro-WotC Product Identity.
Switching to the ORC satisfies the stipulation.
Second sentence.
"
You agree not to indicate compatibility or co-adaptability with any Trademark or Registered Trademark in conjunction with a work containing Open Game Content except as expressly licensed in another, independent Agreement with the owner of such Trademark or Registered Trademark.
"
Of relevance here, "You agree not to indicate compatibality ... with any Trademark ... in conjunction with a work containing Open Game Content."
By updating "your" product to use the ORC and the ORE, "your" product does not contain Open Game Content.
Switching to the ORC satisfies the stipulation.
To abandon the OGL and its Open Gaming Content, is the end of the matter.
The strength of what I am saying relies on: the existence of a new ORE ("Open RPG Engine") for the game rules.Actually, doesn't this break down actually counter your argument? The second sentence explicitly refers to work containing OGC, while the first sentence do not?
It would hence seem that if you have at any point entered an ogl contract, using anything you in that contract agreed to regard as PI independent of context would constitute breach of the contract.
Just to be clear. Any product that has the OGL remains in place.Immediate effect seem to be that the contract terminates automatically if made aware
Yeah.I can add that I think such an outside your work interpretation of PI actually make sense given the context and intention around the introduction of the OGL. It appear to have been a private attempt at privately clarifying the important boundaries very murky copyright law for the rpg domain. In this light OGC is sort of intended as declaring what material you consider not "copyrightable", and in order for the licensor to conclude this, the lisensee need to assert in return that they will treat everything declared as PI to be fully "copyrightable" (with stronger protections than the laws alone provide).