Fedora Account System
Red Hat Associate
Red Hat Customer
Right now we hardcode the copyright into the Content Spec. The copyright, and license, should come from the topics that are in the book, however - in the same way that author information does. So the topics need licensing and copyright information, and the processor needs to derive the information from that. To support a wider use case than "ECS books" it will need to generate a copyright information file with merged copyright and license information.
Moving this to the Skynet queue as it is a change required by Skynet as well and will need to be done first/at the same time.
Our manuals currently comprise material created under a variety of "copyleft" licences. Unfortunately, not all of these licences are interoperable. We need to have a way of flagging material that is licenced differently from our default CC-BY-SA. We need to store at least the copyright owner and the licenses under which it's published (remembering that some content might be multilicensed). A further enhancement would be to warn or block incompatible licensing. (for example, GFDL material appearing in a book that's licensed only CC-BY-SA).
Is there some way to know what licenses are incompatible (without actually knowing anything about the license itself)?
Maybe a compatibility matrix framework, populatde with information from Richard Fontana / legal? Here are some abstractions: Semantic web (RDF, which enables machine reasoning): http://iswc2012.semanticweb.org/sites/default/files/paper_23.pdf http://answers.semanticweb.com/questions/388/what-things-should-you-include-to-describe-the-current-rdf-document http://creativecommons.org/ns Less extensible (conclusions are hardwired): http://stackoverflow.com/questions/1978511/is-there-a-chart-of-which-oss-license-is-compatible-with-which
Also: http://ceur-ws.org/Vol-905/VillataAndGandon_COLD2012.pdf
Sorry, those two special tag names should be: License Compatibility Info License Incompatibility Info
Verified that this works as mentioned. There is a slight usability issue I believe, in that the license names are hyperlinks and clicking them just goes back to the up to the list of licences. However that isn't a blocker, so marking this as RELEASE_PENDING.