4 ms·
I'm curious, why do you have a 3-clause BSD-style license on some PDF files that contain specifications? I guess they are a kind of binary built from the page
by georgeorwell 14y ago
I'm curious, why do you have a 3-clause BSD-style license on some PDF files that contain specifications? I guess they are a kind of binary built from the page layout source code, but I haven't really seen this before. I'm not sure if you can license the specification itself, i.e. put conditions on people that want to implement it.
http://blinkprotocol.org/s/specs.html http://blinkprotocol.org/s/specs.html
- jws 14y agoThere is a lawsuit related to the FAST protocol origination. They are certainly aware of this. Best to be explicit.
- alanctgardner2 14y agoI'm not an expert, but you can definitely restrict the documents which describe the standard. Now, if someone sits there and reverse-engineers the spec without ever seeing that doc, that might be tough to prevent. But generally you can apply a license to any creative work you want; this includes technical documents. A good (or bad, depending on how you view it) example is service manuals for laptops.
- randersson 14y agothe license is essentially a statement that the Blink specification is and will be entirely free to use. There has been a lot of discussion re lock-in and we wanted to be clear about our intentions. Implementors are obviously free to choose their own license terms and we may find that some will prefer to use GPL or LGPL, rather than BSD for contributed code.