The other option that won't require edge cases is to use the license RDF. We publish the license RDF for each license at the license URL + "/rdf". For example:
http://creativecommons.org/licenses/by/3.0/rdf http://creativecommons.org/publicdomain/zero/1.0/rdf As part of our work to bring the API and license chooser into sync with one another, we'll be publishing an update to that RDF that will include metadata about the icons for each license. For example: <foaf:logo rdf:resource="http://i.creativecommons.org/l/by/3.0/88x31.png"/> You can see an example of that RDF file in the source repository at http://code.creativecommons.org/viewgit/license.rdf.git/tree/cc/licenserdf/licenses/creativecommons.org_licenses_by_3.0_.rdf?h=packageify We'll be providing that metadata for CC0, the PDDC, and all the core and ported CC licenses. Nathan On Wed, Mar 17, 2010 at 9:39 AM, John Doig <[email protected]> wrote: > Hi Wendy, > > There are currently no API methods that deal with the license badges solely, > but I think I have a straightforward suggestion for you. > > Here are the URLS to all of the images... > http://i.creativecommons.org/l/%license-code%/3.0/88x31.png > http://i.creativecommons.org/l/zero/1.0/88x31.png > http://i.creativecommons.org/l/publicdomain/88x31.png > > By iterating over the list of license codes you can generate the URL for > each license. CC0 and Public Domain will be edge cases however, and will > need to be hard codes in your repository. > > Note that you can replace "88x31" with "80x15" in any of the above URLs for > a slimmer, smaller icon. > > As for a page discussing each license in detail: > http://creativecommons.org/about/licenses/. > > Regards, > John Doig > > On 03/17/2010 08:52 AM, Wendy J Bossons wrote: > > Hello, > > I recently integrated the CC license api into our repository. In order for > the project to be completed, I want to add an image to the subject page that > represents Creative Commons -- a nice non-specific license image which will > have a url pointing at the creative commons site page where the license type > is described. My other option is to programmatically derive the image for > each license type. Regarding the latter, is there a pattern/algorithm to > follow to build the image url? > > Thanks! > > ..\Wendy > Wendy Bossons > Web Developer > MIT Libraries > Technology Research & Development > Building E25-131 > 77 Massachusetts Ave. > Cambridge, MA 02141-4307 > Phone 617-253-0770 > Fax 617-253-4462 > [email protected] > http://libraries.mit.edu > > > > _______________________________________________ > cc-devel mailing list > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel > > _______________________________________________ > cc-devel mailing list > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel > > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
![http://i.creativecommons.org/l/by/3.0/88x31.png"/](http://i.creativecommons.org/l/by/3.0/88x31.png"/){kind=link}
