Mike Milinkovich wrote on 05/31/18 08:29 PM:
To address Bill's original assertion,
there are two things happening which I think *do* permit the
co-development of implementations and specs. At least in certain
communities, using certain licenses.
- The lawyers seems to be comfortable that you can take an
API from an Apache-licensed project and derive a spec
document from that under copyright law. The patent grants
don't extend, but the idea is that every company involved in
the spec project will be granting what patents they have. So
clean on the copyright side, and as long as we have some
significant patent holders involved, we have some patent
aircover. Not bulletproof, but pretty good.
I don't think Oracle legal would be comfortable with that.
If the spec contains Apache licensed and copyrighted material,
that's third party content that's part of the spec, and needs to be
considered when sublicensing the spec or deriving an implementation
from the spec.
We'll need to address this issue explicitly when considering specs
that are related to "reference" implementations that are not Eclipse
projects.
|
