<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: creative-commons</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/creative-commons.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2023-10-10T04:17:09+00:00</updated><author><name>Simon Willison</name></author><entry><title>Wikimedia Commons: Photographs by Gage Skidmore</title><link href="https://simonwillison.net/2023/Oct/10/wikimedia-commons-photographs-by-gage-skidmore/#atom-tag" rel="alternate"/><published>2023-10-10T04:17:09+00:00</published><updated>2023-10-10T04:17:09+00:00</updated><id>https://simonwillison.net/2023/Oct/10/wikimedia-commons-photographs-by-gage-skidmore/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://commons.m.wikimedia.org/wiki/Category:Photographs_by_Gage_Skidmore"&gt;Wikimedia Commons: Photographs by Gage Skidmore&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Gage Skidmore is a Wikipedia legend: this category holds 93,458 photographs taken by Gage and released under a Creative Commons license, including a vast number of celebrities taken at events like San Diego Comic-Con. CC licensed photos of celebrities are generally pretty hard to come by so if you see a photo of any celebrity on Wikipedia there’s a good chance it’s credited to Gage.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://twitter.com/visakanv/status/1711569744263074105"&gt;@visakanv&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/photography"&gt;photography&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wikipedia"&gt;wikipedia&lt;/a&gt;&lt;/p&gt;



</summary><category term="creative-commons"/><category term="photography"/><category term="wikipedia"/></entry><entry><title>Flickr Shapefiles Public Dataset 1.0</title><link href="https://simonwillison.net/2009/May/22/shapefiles/#atom-tag" rel="alternate"/><published>2009-05-22T18:12:10+00:00</published><updated>2009-05-22T18:12:10+00:00</updated><id>https://simonwillison.net/2009/May/22/shapefiles/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://code.flickr.com/blog/2009/05/21/flickr-shapefiles-public-dataset-10/"&gt;Flickr Shapefiles Public Dataset 1.0&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Another awesome Geo dataset from the Yahoo! stable—this time it’s Flickr releasing shapefiles (geometrical shapes) for hundreds of thousands of places around the world, under the CC0 license which makes them essentially public domain. The shapes themselves have been crowdsourced from geocoded photos uploaded to Flickr, where users can “correct” the textual location assigned to each photo. Combine this with the GeoPlanet WOE data and you get a huge, free dataset describing the human geography of the world.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/crowdsourcing"&gt;crowdsourcing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/flickr"&gt;flickr&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/geoplanet"&gt;geoplanet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/geospatial"&gt;geospatial&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/maps"&gt;maps&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/shapefiles"&gt;shapefiles&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/yahoo"&gt;yahoo&lt;/a&gt;&lt;/p&gt;



</summary><category term="creative-commons"/><category term="crowdsourcing"/><category term="flickr"/><category term="geoplanet"/><category term="geospatial"/><category term="maps"/><category term="shapefiles"/><category term="yahoo"/></entry><entry><title>Yahoo! Geo: Announcing GeoPlanet Data</title><link href="https://simonwillison.net/2009/May/20/geoplanet/#atom-tag" rel="alternate"/><published>2009-05-20T21:12:24+00:00</published><updated>2009-05-20T21:12:24+00:00</updated><id>https://simonwillison.net/2009/May/20/geoplanet/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.ygeoblog.com/2009/05/announcing-geoplanet-data/"&gt;Yahoo! Geo: Announcing GeoPlanet Data&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The Yahoo! WhereOnEarth geographic data set is fantastic, but I’ve always felt slightly uncomfortable about building applications against it in case the API went away. That’s not an issue any more—the entire dataset is now available to download and use under a Creative Commons Attribution license. It’s not entirely clear what the attribution requirements are—do you have to put “data from GeoPlanet” on every page or can you get away with just tucking the attribution away in an “about this site” page? UPDATE: The data doesn’t include latitude/longitude or bounding boxes, which severely reduces its utility.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/attribution"&gt;attribution&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/data"&gt;data&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/geoplanet"&gt;geoplanet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/geospatial"&gt;geospatial&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/whereonearth"&gt;whereonearth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/yahoo"&gt;yahoo&lt;/a&gt;&lt;/p&gt;



</summary><category term="attribution"/><category term="creative-commons"/><category term="data"/><category term="geoplanet"/><category term="geospatial"/><category term="whereonearth"/><category term="yahoo"/></entry><entry><title>Map Maker for Developers</title><link href="https://simonwillison.net/2009/Feb/21/google/#atom-tag" rel="alternate"/><published>2009-02-21T09:05:57+00:00</published><updated>2009-02-21T09:05:57+00:00</updated><id>https://simonwillison.net/2009/Feb/21/google/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://googlegeodevelopers.blogspot.com/2009/02/map-maker-for-developers.html"&gt;Map Maker for Developers&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Tiles from Google’s Map Maker crowdsourcing effort are now available in the JS and static maps APIs on an opt-in basis. Maybe I’m misunderstanding something here, but Google Map Maker seems like a big step backwards for open geographic data. People donate their mapping efforts to Google, who keep them—unlike OpenStreetMap, where the donated efforts are made available under a Creative Commons license.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/crowdsourcing"&gt;crowdsourcing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/googlemapmaker"&gt;googlemapmaker&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google-maps-api"&gt;google-maps-api&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openstreetmap"&gt;openstreetmap&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/staticmaps"&gt;staticmaps&lt;/a&gt;&lt;/p&gt;



</summary><category term="creative-commons"/><category term="crowdsourcing"/><category term="google"/><category term="googlemapmaker"/><category term="google-maps-api"/><category term="openstreetmap"/><category term="staticmaps"/></entry><entry><title>ficlets memorial</title><link href="https://simonwillison.net/2009/Jan/14/ficlets/#atom-tag" rel="alternate"/><published>2009-01-14T22:02:42+00:00</published><updated>2009-01-14T22:02:42+00:00</updated><id>https://simonwillison.net/2009/Jan/14/ficlets/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://ficlets.ficly.com/"&gt;ficlets memorial&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Here’s a great argument for Creative Commons—AOL shut down Ficlets without providing an archive or export tool, but the license meant Ficlets co-creator Kevin Lawver could scrape and preserve all of the content anyway.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/aol"&gt;aol&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/archive"&gt;archive&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/data"&gt;data&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ficlets"&gt;ficlets&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/kevin-lawver"&gt;kevin-lawver&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/preservation"&gt;preservation&lt;/a&gt;&lt;/p&gt;



</summary><category term="aol"/><category term="archive"/><category term="creative-commons"/><category term="data"/><category term="ficlets"/><category term="kevin-lawver"/><category term="preservation"/></entry><entry><title>Dopplr: New city pages, with public tips and Creative-Commons-licenced, Flickr-powered goodness</title><link href="https://simonwillison.net/2008/Dec/1/dopplr/#atom-tag" rel="alternate"/><published>2008-12-01T00:43:03+00:00</published><updated>2008-12-01T00:43:03+00:00</updated><id>https://simonwillison.net/2008/Dec/1/dopplr/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.dopplr.com/2008/11/27/new-city-pages/"&gt;Dopplr: New city pages, with public tips and Creative-Commons-licenced, Flickr-powered goodness&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Explains why I’ve been unable to convince any of the Dopplr crew to come out and do fun things for the past month.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/dopplr"&gt;dopplr&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/flickr"&gt;flickr&lt;/a&gt;&lt;/p&gt;



</summary><category term="creative-commons"/><category term="dopplr"/><category term="flickr"/></entry><entry><title>License Hacking</title><link href="https://simonwillison.net/2008/Nov/10/license/#atom-tag" rel="alternate"/><published>2008-11-10T22:46:21+00:00</published><updated>2008-11-10T22:46:21+00:00</updated><id>https://simonwillison.net/2008/Nov/10/license/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://fishbowl.pastiche.org/2008/11/11/license_hacking/"&gt;License Hacking&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Wikipedia is making the switch to a CC license, by asking the Free Software Foundation to include that as an option in the latest version of the Free Documentation License which Wikipedia currently uses and which includes an auto-upgrade clause. Devious.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/fdl"&gt;fdl&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/free-software-foundation"&gt;free-software-foundation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/licensing"&gt;licensing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/open-source"&gt;open-source&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wikipedia"&gt;wikipedia&lt;/a&gt;&lt;/p&gt;



</summary><category term="creative-commons"/><category term="fdl"/><category term="free-software-foundation"/><category term="licensing"/><category term="open-source"/><category term="wikipedia"/></entry><entry><title>Free licenses upheld by US "IP" court</title><link href="https://simonwillison.net/2008/Aug/14/huge/#atom-tag" rel="alternate"/><published>2008-08-14T09:33:49+00:00</published><updated>2008-08-14T09:33:49+00:00</updated><id>https://simonwillison.net/2008/Aug/14/huge/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://lessig.org/blog/2008/08/huge_and_important_news_free_l.html"&gt;Free licenses upheld by US &amp;quot;IP&amp;quot; court&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Free software and CC licenses which dictate conditions that, when violated, turn you in to a copyright infringer now have precedence in US law.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/copyright"&gt;copyright&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/freesoftware"&gt;freesoftware&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/law"&gt;law&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/lawrence-lessig"&gt;lawrence-lessig&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/licensing"&gt;licensing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/open-source"&gt;open-source&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/uslaw"&gt;uslaw&lt;/a&gt;&lt;/p&gt;



</summary><category term="copyright"/><category term="creative-commons"/><category term="freesoftware"/><category term="law"/><category term="lawrence-lessig"/><category term="licensing"/><category term="open-source"/><category term="uslaw"/></entry><entry><title>Virgin Mobile Botches Creative Commons-Driven Ad Campaign</title><link href="https://simonwillison.net/2007/Jul/13/virgin/#atom-tag" rel="alternate"/><published>2007-07-13T16:57:16+00:00</published><updated>2007-07-13T16:57:16+00:00</updated><id>https://simonwillison.net/2007/Jul/13/virgin/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.cadenhead.org/workbench/news/3232/virgin-mobile-botches-creative"&gt;Virgin Mobile Botches Creative Commons-Driven Ad Campaign&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Virgin Mobile Australia used CC Flickr photos (and added offensive captions) for an ad campaign, but failed to get model releases from the people in the photos. Hopefully this won’t result in a backlash against CC; it’s Virgin who are at fault.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/areyouwithusorwhat"&gt;areyouwithusorwhat&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/flickr"&gt;flickr&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/virgin"&gt;virgin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/virginmobile"&gt;virginmobile&lt;/a&gt;&lt;/p&gt;



</summary><category term="areyouwithusorwhat"/><category term="creative-commons"/><category term="flickr"/><category term="virgin"/><category term="virginmobile"/></entry><entry><title>On RSS and the coming wave of content theft</title><link href="https://simonwillison.net/2005/Oct/5/rss/#atom-tag" rel="alternate"/><published>2005-10-05T11:25:32+00:00</published><updated>2005-10-05T11:25:32+00:00</updated><id>https://simonwillison.net/2005/Oct/5/rss/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.i-marco.nl/weblog/archive/2005/10/05/on_rss_and_the_coming_wave_of_"&gt;On RSS and the coming wave of content theft&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A reason to avoid commercial-use-allowed Creative Commons licenses.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;&lt;/p&gt;



</summary><category term="creative-commons"/></entry><entry><title>Creative commons query</title><link href="https://simonwillison.net/2003/Mar/2/creativeCommonsQuery/#atom-tag" rel="alternate"/><published>2003-03-02T23:34:25+00:00</published><updated>2003-03-02T23:34:25+00:00</updated><id>https://simonwillison.net/2003/Mar/2/creativeCommonsQuery/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://www.aaronsw.com/weblog/000850" title="Trip Report"&gt;Aaron Swartz&lt;/a&gt; has been talking to Google about indexing &lt;a href="http://creativecommons.org/"&gt;Creative Commons&lt;/a&gt; licensed works:&lt;/p&gt;

&lt;blockquote cite="http://www.aaronsw.com/weblog/000850"&gt;&lt;p&gt;
From Google the news was mixed. He said he wouldn’t start indexing .0 URIs, which includes the URIs for all our licenses. He also said that he wouldn’t parse RDF for at least six months, since it required involved changes to their system and added overhead (which you need to keep down when parsing 3B pages). However, he did say that if we added &amp;lt;meta&amp;gt; tags for license information, they’d add a new search key like link: or inurl: right away, since they already had a meta tag parser.
&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Did they say anything about &lt;a href="/2002/Dec/19/creativeCommonsCopyrightLink/"&gt;using the link element&lt;/a&gt; instead?&lt;/p&gt; 

    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="creative-commons"/></entry><entry><title>Creative Commons copyright link</title><link href="https://simonwillison.net/2002/Dec/19/creativeCommonsCopyrightLink/#atom-tag" rel="alternate"/><published>2002-12-19T00:41:31+00:00</published><updated>2002-12-19T00:41:31+00:00</updated><id>https://simonwillison.net/2002/Dec/19/creativeCommonsCopyrightLink/#atom-tag</id><summary type="html">
    &lt;p&gt;It's great to see the &lt;a href="http://creativecommons.org/"&gt;Creative Commons&lt;/a&gt; getting an overwhelmingly positive reception - as Lessig &lt;a href="http://cyberlaw.stanford.edu/lessig/blog/archives/2002_12.shtml#000737" title="cc launch"&gt;says on his blog&lt;/a&gt;, &lt;q cite="http://cyberlaw.stanford.edu/lessig/blog/archives/2002_12.shtml#000737"&gt;'Tis the season to be giving, and this will be a great gift to the Commons&lt;/q&gt;. If you haven't seen their explanatory flash animation, &lt;a href="http://mirrors.creativecommons.org/" title="Dubious permalink"&gt;Get Creative&lt;/a&gt;, you should really check it out.&lt;/p&gt;

&lt;p&gt;That said, I have to admit I have a few reservations about the machine readable form of the &lt;acronym title="Creative Commons"&gt;CC&lt;/acronym&gt; licenses. The recommended way of including them in a page is &lt;acronym title="Resource Description Framework"&gt;RDF&lt;/acronym&gt; embedded in a comment, similar to Moveable Type's &lt;a href="http://www.movabletype.org/trackback/"&gt;Trackback&lt;/a&gt; system. This is fine for &lt;acronym title="HyperText Markup Language"&gt;HTML&lt;/acronym&gt; documents (although it feels like a bit of a cludge) but is problematic when used with &lt;acronym title="eXtensible HyperText Markup Language"&gt;XHTML&lt;/acronym&gt;. Why? Because &lt;acronym title="eXtensible HyperText Markup Language"&gt;XHTML&lt;/acronym&gt; documents are &lt;acronym title="eXtensible Markup Language"&gt;XML&lt;/acronym&gt; documents, and the &lt;acronym title="eXtensible Markup Language"&gt;XML&lt;/acronym&gt; specification &lt;a href="http://www.w3.org/TR/REC-xml#sec-comments" title="Extensible Markup Language (XML) 1.0 (Second Edition) - Section 2.5: Comments"&gt;states&lt;/a&gt; that &lt;q cite="http://www.w3.org/TR/REC-xml#sec-comments"&gt;an XML processor may, but need not, make it possible for an application to retrieve the text of comments&lt;/q&gt;. The logical way of extracting Creative Commons information from an &lt;acronym title="eXtensible HyperText Markup Language"&gt;XHTML&lt;/acronym&gt; document would be to parse it with an &lt;acronym title="eXtensible Markup Language"&gt;XML&lt;/acronym&gt; processor, but it is likely that many processors will be unable to extract the comments (and even those with the ability to extract them will not treat them as &lt;acronym title="eXtensible Markup Language"&gt;XML&lt;/acronym&gt;, requiring a second run of the &lt;acronym title="eXtensible Markup Language"&gt;XML&lt;/acronym&gt; parser to extract information from the &lt;acronym title="Resource Description Framework"&gt;RDF&lt;/acronym&gt;). In practical terms this is unlikely to be a problem as regular expressions can be used instead, but from an idealogical point of view it leaves something of a bad taste in the mouth.&lt;/p&gt;

&lt;p&gt;If I'm going to criticise the embedded &lt;acronym title="Resource Description Framework"&gt;RDF&lt;/acronym&gt; approach I should probably suggest an alternative. The HTML 4 specification &lt;a href="http://www.w3.org/TR/REC-html40/types.html#h-6.12" title="Basic HTML data types: 6.12 Link types"&gt;describes&lt;/a&gt; a "Copyright" link type which is defined as follows:&lt;/p&gt;

&lt;blockquote cite="http://www.w3.org/TR/REC-html40/types.html#h-6.12"&gt;
&lt;dl&gt;
&lt;dt&gt;Copyright&lt;/dt&gt;
&lt;dd&gt;Refers to a copyright statement for the current document.&lt;/dd&gt;
&lt;/dl&gt;
&lt;/blockquote&gt;

&lt;p&gt;I suggest using a &lt;code&gt;link&lt;/code&gt; element in the &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt; section of a document which points to the Creative Commons license governing the page in question (or to an &lt;acronym title="Resource Description Framework"&gt;RDF&lt;/acronym&gt; document similar to that currently used by the embedded comments method). If you view source on your page you will see that I have done exactly that.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/creative-commons"&gt;creative-commons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/lawrence-lessig"&gt;lawrence-lessig&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="creative-commons"/><category term="lawrence-lessig"/></entry></feed>