Hi,
I'm working on a CIM provider package where we need to ship a version (v2.16) of the DMTF CIM schema[1] in our package. The tog-pegasus package does this already, but with a *very* old version (v2.9) that does not include any of the virtualization models.
The DMTF schema files are not (AFAICT) released under any particular license, but they do have this statement at the top-level:
// DMTF is a not-for-profit association of industry members // dedicated to promoting enterprise and systems management and // interoperability. DMTF specifications and documents may be // reproduced for uses consistent with this purpose by members and // non-members, provided that correct attribution is given.
I was planning to put a separate COPYING or LICENSE file in the directory of the tarball/RPM containing the schema, highlighting the above and making it clear that the schema was not covered under the LGPL license of the package.
I would like some advice on how to proceed.
Thanks!
1: http://www.dmtf.org/standards/cim/cim_schema_v216/
On Tue, 2007-12-11 at 07:28 -0800, Dan Smith wrote:
Hi,
I'm working on a CIM provider package where we need to ship a version (v2.16) of the DMTF CIM schema[1] in our package. The tog-pegasus package does this already, but with a *very* old version (v2.9) that does not include any of the virtualization models.
The DMTF schema files are not (AFAICT) released under any particular license, but they do have this statement at the top-level:
// DMTF is a not-for-profit association of industry members // dedicated to promoting enterprise and systems management and // interoperability. DMTF specifications and documents may be // reproduced for uses consistent with this purpose by members and // non-members, provided that correct attribution is given.
I was planning to put a separate COPYING or LICENSE file in the directory of the tarball/RPM containing the schema, highlighting the above and making it clear that the schema was not covered under the LGPL license of the package.
I would like some advice on how to proceed.
That license seems to strongly imply that the schema files are not permitted for commercial use, which is something that we do not permit in Fedora.
It would be worthwhile to contact the DMTF and see if they permit commercial use/distribution of their schemas or not.
~spot
TC> That license seems to strongly imply that the schema files are not TC> permitted for commercial use, which is something that we do not TC> permit in Fedora.
Forgive my legal ignorance, but why does it imply that?
Fedora is already shipping an older version of these files, and a number of other companies (IBM included) ship these files with commercial closed-source products.
TC> It would be worthwhile to contact the DMTF and see if they permit TC> commercial use/distribution of their schemas or not.
They state that the files "may be reproduced for uses consistent with this purpose", with the purpose being "promoting enterprise and systems management and interoperability". Doesn't that imply commercial use?
The DTMF is made up of industry members, but I'll try to get a more official read on this. If I get an email saying "yes, it's fine", what else do I need to do to record that for Fedora?
Thanks!
On Tue, 2007-12-11 at 07:51 -0800, Dan Smith wrote:
TC> That license seems to strongly imply that the schema files are not TC> permitted for commercial use, which is something that we do not TC> permit in Fedora.
Forgive my legal ignorance, but why does it imply that?
They use the phrase "consistent with this purpose", and purpose can be implied to mean "a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability."
More than likely, it is simply that the DTMF is non-profit, not that the schema is restricted to non-profit intentions, but since they don't really specify any terms or rights for the schema files, it would be best to be clear.
The DTMF is made up of industry members, but I'll try to get a more official read on this. If I get an email saying "yes, it's fine", what else do I need to do to record that for Fedora?
That would be sufficient, just toss it in the package as a txt file.
~spot
-
Dan Smith -
Tom Callaway