Which Copyleft Licence is Suitable for an SVG?
The article explores which copyleft license is most suitable for SVG files, given the format's unique nature as XML-based vector graphics. It discusses the challenges of applying traditional copyleft licenses to SVG images and considers options like the GNU Affero General Public License (AGPL) for ensuring that modifications remain open.
Background
- SVGs are images defined as XML code — they can contain embedded scripts, CSS, and even be linked to external resources, which creates a unique licensing headache compared to bitmap formats like PNG or JPEG.
- Copyleft licenses (e.g., GPL, AGPL) require that derivative or combined works also be released under the same license. For software, this is well understood; for images, especially SVGs, it's legally fuzzy.
- An SVG used as a logo on a website or in a document could be argued to "link" or "combine" with the rest of that page or application, potentially forcing the whole thing to adopt the same copyleft license — a risk most designers don't consider.
- The article explores which existing copyleft license (if any) makes sense for SVGs, given their hybrid nature as both code and artwork.