it should be mentioned that the creative commons website very prominently recommends using 'RDF' metadata to specify licenses as part of the "semantic web" - they even have a wizard to create the metadata for copy/paste[1]
like this or not, it may be a good idea for libreJS to support it as one could imagine CC-licensed javascripts using this declaration format if only because creative commons encourages it - although they plainly recommend against using their licenses for code; one of the options for "work type" is 'interactive' - i cant imagine what else that could be intended for other than software the result is this gorgeous mess: <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/";><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; /></a><br /><span xmlns:dct="http://purl.org/dc/terms/"; href="http://purl.org/dc/dcmitype/InteractiveResource"; property="dct:title" rel="dct:type">TITLE</span> by <a xmlns:cc="http://creativecommons.org/ns#"; href="https://AUTHOR-URL"; property="cc:attributionName" rel="cc:attributionURL">AUTHOR</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons Attribution-ShareAlike 4.0 International License</a>.<br />Based on a work at <a xmlns:dct="http://purl.org/dc/terms/"; href="https://FETCH-URL"; rel="dct:source">https://FETCH-URL</a>.<br />Permissions beyond the scope of this license may be available at <a xmlns:cc="http://creativecommons.org/ns#"; href="https://LICENSE-URL"; rel="cc:morePermissions">https://LICENSE-URL</a> [1]: https://creativecommons.org/choose/#metadata
signature.asc
Description: OpenPGP digital signature
![https://i.creativecommons.org/l/by-sa/4.0/88x31.png"](https://i.creativecommons.org/l/by-sa/4.0/88x31.png"){kind=link}