Comment License management tools: good, bad, or ugly? (Score 1) 26
Something I wrote on this in 2001 and posted to gnu.misc.discuss: https://groups.google.com/g/gn...
"... I definitely do not want to see a future world of only proprietary intellectual property where basically everything I want to do requires agreeing to endless licenses and royalty payments, such as described in [Richard Stallman's essay] "right-to-read".
However, on a practical basis, living in our society as it is right now, any software developer is going to handle lots of packets of information from emails to applications to program modules under a variety of explicit or implied licenses. If a developer is going to do this in a way that makes his or her work most useful to the community (under the terms he or she so chooses), proper attention must be given to the licensing status of all works received and distributed, especially those that form the basis for new derived works to be distributed. Note that even in the case of purely GPL'd works, one still needs to know that a user contributing an extension to a GPL'd work was the original author and/or he or she has permission to distribute the patch (if say an employer owns all the contributor's work).
My question is: should software tools, protocols, and standards play a role in easing this required "due diligence" license management work (at least as far as copyright alone is concerned)?
For example, consider this situation. I go to the Choral Public domain site and download a MIDI tune picked at random, say "Ecce nunc benedicite" by "Giovanni Pierluigi da Palestrina" edited by "Claudio
Macchi". Let's say I like it and want to pass it on.
As soon as I have this file on my computer, much of the "meta data" about licensing is lost, since the meta-data is not all kept in the same file but is implicit from having the file on the site. If I pass the file to you, how do you know it is freely redistributeable? Do you tak my word for it? Do you check the site? Am I myself even sure enough what license it is under when I downloaded it that I can give you assurances you can use it? Why should you trust me if I do? Did you get the identical version I downloaded, or did I slip in a change which I might later use to make a claim against you if you use the file in a work of your own? If I (not the author) bundle the midi file with a CPDL license in a zip file, how do you know I had any right to do that? How much time do you need to take to verify the situation?
Note that ultimately, having such meta-data in every file might require operating system support, or at least very smart tools, like a MIDI player that ignores the meta-data when actually playing the file. That in turn might require a more sophisticated repository approach to storing all file data (at a minimum, perhaps "license forks" like the Macintosh has "data forks", although this doesn't address the notion of one license covering multiple files taken as a whole).