On Mon, Oct 21, 2013 at 8:40 PM, Dan Mills <[email protected]> wrote: > Chiming into this a bit late... but I don't think there's good reason > to call out to a CC API for the WP plugin. Licenses change very > infrequently, there is no reason to introduce a dynamic call of any > kind at runtime just to populate the license options.
FWIW, I totally agree with Dan. Probably if I were doing it I'd list the pertinent licenses (I guess 7; CC0 and 6 4.0 licenses) and have an option to enter the URL and title of another license if user wants something other than those. As far as metadata, anything other than annotating the license link with rel="license" is not worth it, unless you're also planning to integrate with the WordPress media manager, which would be a bigger job. This, or even fewer features, works for almost every major CC integration. The partner interface still works fairly well if you really want a Q&A style "chooser". It, and the a bit later the CC API, were developed when CC might've been developing a lot of different licenses (in a way it did via porting of course...), making more navigation than a list conceivably useful. The CC API was developed when it still seemed non-web clients were important. May or may not have been a good choice then, but certainly not now. Yet another option that may not have been mentioned here is http://wiki.creativecommons.org/LicenseChooser.js which seems to be used by yet another old CC WordPress thing. Mike _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
