<<Have you considered that a version of the d20 license could say "At least
5% of your product must be licensed with the OGL 2.0"? Bang, instant spread
of some future OGL 2.0 license.
Joe
>>
Thought about it. Doesn't work, chief, at least not for the intended purpose of mandating that everybody use new rules and regulations in OGL 2.0. Your method only works for d20 licensed products.
Without a new type of "shared content" I can blythely ignore OGL 2.0 _and_ the STL by producing OGL-only products. The only way to get the OGL 2.0 on to all products that I can think of is to propagate a new type of content and release it so widely that you practically need OGL 2.0 if you borrow any new content at all.
Without the STL to bind me to a specific OGL version, if I drop the STL, then I can immediately choose any early version of the OGL.
A new type of content would force a licensing shift for many people who aren't working with exclusively older OGC.
Lee
