On Mon, Jul 12, 2010 at 5:19 AM, Robert Knight
<[email protected]>wrote:
> I think it might be better to simply provide a license or, if
> absolutely necessary, a choice of licenses and require that all styles
> in the repository use that license(s) - which I think is what already
> happens in the Zotero style repository? In the case of the creative
> commons licenses, there are already nice simple web pages which
> explain the conditions of a particular license.
>
Revisiting the topic of licensing of CSL styles: I was wondering if it would
make sense (and would be legally sound) to require that any styles hosted at
https://github.com/citation-style-language/styles should be licensed under
CC-BY-SA. Styles with a different license wouldn't be accepted, and any
styles submitted for inclusion in the repository would automatically receive
this license if no license is set. CC-BY-SA is by far the most common
license used (there are 2 LGPL styles, 1 GPL style (!, immunity.csl) and
some styles without licenses), and settling on a single license would make
it far easier to communicate the licensing requirements to any prospective
adopters of CSL.
In related news, I recently updated the CSL schema to disallow the cs:rights
element in cs:info for dependent styles, as I think we shouldn't bother with
licensing those (none of the existing dependent styles include a cs:rights
element).
Rintze
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
