I tried to have a word with OpenDDR contributors on their thoughts, but I guess after all of device-data was contributed using that from such a GitHub or similar module would be perfectly legitimate.
Thus something like let's call it "OpenDDR.next" that does not fall under Apache requirements could use "devicemap-data" and "w3c.jar" together without problems? And the wrapper, Reza sketched would have to be done in a similar way, at least for the W3C compliant module. Werner On Fri, Jan 9, 2015 at 2:02 PM, Bertrand Delacretaz <[email protected]> wrote: > Hi, > > On Fri, Jan 9, 2015 at 1:16 PM, Werner Keil <[email protected]> wrote: > > ...AFAIK W3C has a standard license, a quote can be seen under e.g. > Xerces > > https://xerces.apache.org/ ... > > Xerces is a good example indeed, they have a core dependency on the > Java W3C DOM API, for which source code is available in a form that's > acceptable as a core dependency of an Apache project. > > Taking DOM level 2 as an example, its source code is available at > http://www.w3.org/TR/DOM-Level-2-Core/java-binding.zip > > If you look in there there's a clear copyright notice and license (*), > along with buildable source code that allows one to recreate the w3c > dom level 2 jar file. > > That's what we need for the W3C DDR if you want DeviceMap to be able > to release code that depends on it. > > If such source code is not available, the alternative is for whoever > wants those modules out to fork them on github for example, as a > companion project that's not subject to Apache requirements. That > means changing package and product names to avoid confusion, but that > might be the best way to get something out. > > -Bertrand > > (*) That license is http://opensource.org/licenses/W3C.php which is > listed at http://apache.org/legal/resolved.html as being similar in > terms to the Apache License 2.0, so all clear >
