| | Re: License Intent Jacob Sparre Andersen
|
| | (...) It wouldn't. But I would (could) prevent him (and everybody else) from distributing renderings that includes parts from the Parts Library, since these are derivative works of the parts in the Parts Library. (...) Agreed. But Larry's problem is (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | |
| | | | Re: License Intent Orion Pobursky
|
| | | | (...) So exactly how would someone release a rendering in complience with open source ? The DAT file associated with the render is not subject to the open source rules (since it is not a derivative work but merely references the library as a tool) (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | |
| | | | | | Re: License Intent Jacob Sparre Andersen
|
| | | | (...) That depends on the license on the LDraw Parts Library and the LDraw file for the model/scene. (...) Exactly. (...) But since the _rendering_ of the DAT file _is_ a derivative work of the LDraw Parts Library, distributing the rendering may (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | |
| | | | | | Re: License Intent Don Heyse
|
| | | | | (...) Perhaps the book authors could share some insight on this, because there are many books out there containing renderings. What legal hoops did they jump through in order to publish? Don (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | | |
| | | | | | | Re: License Intent Tim Courtney
|
| | | | | | (...) From my recollection (and this is digging back, you made me think here) I went off of the LDraw.exe LICENSE.TXT. The clause I presumed gave permission to publish commercially was: -- USAGE PROVISIONS: Permission is granted to the user to use (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | | | |
| | | | | | Re: License Intent Kyle McDonald
|
| | | | (...) Actually I beliee that this is the exact case where the LGPL differes from the GPL. Since the Parts 'library' will only be referecned as a library, I think that (if the LGPL were used on it,) it's license wouldn't pollute the license of the (...) (20 years ago, 11-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | |
| | | | | | Re: License Intent Jacob Sparre Andersen
|
| | | | (...) From (URL): »However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable (...) (20 years ago, 12-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | |
| | | | | | Re: License Intent Wayne Gramlich
|
| | | | (...) [snip] (...) I read the exact same clause and come to exactly the opposite conclusion. My reasoning is that because linking is something you do to code, not LDraw parts; the clause has no bearing to LDraw parts. Is my interpretation right, or (...) (20 years ago, 12-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | |
| | | | | | Re: License Intent Jacob Sparre Andersen
|
| | | | Just for the record: IANAL (...) Mine. LDraw files are source code (at least according to the definition in the LGPL). And unless you consider rendering a specific kind of compilation, LGPL would not allow you to do anything useful with a parts (...) (20 years ago, 12-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | |
| | | | | | Re: License Intent Don Heyse
|
| | | | (...) I don't know. I think when something is statically linked you can recover the original code with a disassembler. It's really still there in a different form. There's no way to disassemble a picture into the ldraw code without using the ldraw (...) (20 years ago, 13-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| | | | |