I am creating an open source tool which leverages some XSLT stylesheets in order to do its work, which is transforming XML to Java code. One of the stylesheets that I want to use is licensed under LGPL v2.0. My tool will be license under the Apache License v2.0.
I read somewhere that if you link your Apache-licensed program to an LGPL library dynamically, it's ok. I see the link between my program and the stylesheet as dynamic, since it only depends on a filename and could easily be replaced with a different stylesheet by replacing a single file.
Can I infer from this that it's OK to use LGPL XSLT stylesheets or am I making an error in judgement here?
The file would be included in the nodejs package project directory
- the package would be distributed through npmjs.org.
- my own source files would be in
lib/transform.js), licensed under ASLv2.0.
- the stylesheet would be in
xslt/' (e.g.xslt/java/xml-to-java.xslt`) licensed under its original license (in this case LGPLv2.0).
- the program does not provide an interface to change the used stylesheet, but the user has to go into the filesystem, look for the install directory of my package and manually replace the file with another if so desired.
The file provides essential functionality to the program
- my own stylesheets convert to a format that this stylesheet understands
- without it, I would have to provide a stylesheet with the same behavior (same input format, same output format).
- So basically my program delegates the last transformation phase that is part of my program's behaviour.
To be clear: the file that I am trying to include into my package may retain its original license, I am only interested in adding its functionality to my program, because without it, my program loses so much of its functionality that it becomes useless. The reason I'm asking this question is that I want to distribute the file along with my project, because I would like my tool to work out of the box, not have the user download the xslt separately from the developers website.