<<
Yes you can - in which case, feel free to go back to the original source.>>
I should not have to go back to the original source to verify OGC status of _anything_.
<<> Your answer seems most insufficient.
No - it is not what you want to hear. This is the difference. As I have
said before on this list, we are not trying to make OGC toolkits with our books - if we were, we would automatically make all text open in order to make things as easy as possible. >>
I asked a specific question -- did you use ANY verbatim text (including verbatim feat names) from any non-Mongoose products. If so, your OGC declaration doesn't convey that information.
This has NOTHING to do with what I want to hear. _IF_ I knew that you used:
a) no verbatim feat names from non-Mongoose products
b) no verbatim paragraphs from non-Mongoose products
Then your declaration would probably suit me fine, and I'd go buy your product. I'm asking if your declaration inadvertently closes up content declared as open by others. This has nothing to do with what I want or don't want to hear.
If you said: "Lee, there's not a single feat name that was open that we have closed -- all the feat names are OUR product identity. Nobody came up with those feat names but us. Moreover, there's not a single paragraph of verbatim text we listed from anywhere else."
I'd say -- "Good for you!"
Then I'd know that I could rely on your OGC declaration as being accurate, neither restricting nor granting any rights it shouldn't.
If you took feat names and/or feat descriptions from other sources, however, then the OGC declaration is insufficient.
My questions were pretty specific. This should be a fairly trivial issue to resolve -- it should be answerable with a couple "yes" or "no" responses.
I don't see how this is really a very complicated point of debate.
Lee
