Hi there -
Recently -- within the last couple of weeks or so -- one of our processes
here that relies on a call to the CC API stopped working.
We use cURL and PHP to post data to the CC API and get back the license URI.
Here's the function that we use -- this hasn't been changed in months:
function makeCCLicense($commercial, $derivatives, $jurisdiction)
{
$ch = curl_init('
http://api.creativecommons.org/rest/1.5/license/standard/get');
curl_setopt($ch, CURLOPT_POST, TRUE);
curl_setopt($ch, CURLOPT_POSTFIELDS, 'commercial=' . $commercial .
'&derivatives=' . $derivatives . '&jurisdiction=' . $jurisdiction);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
$result = curl_exec($ch);
curl_close($ch);
....}
I've been testing for clues and have set this up to print the contents of
the $result variable to the screen. I get "None". I used to get something
like "http://creativecommons.org/licenses/by-nc-nd/3.0/us/";, depending on
the chooser's choices.
I've run out of things to check/tweak on our side. I'm now wondering if we
are experiencing this problem due to the changes that you all just did to
the API?
Appreciate any help you can offer - thanks!
~Lisa
Lisa M. Brooks
Co-director
IssueLab: bringing nonprofit research into focus - http://www.issuelab.org
[email protected]
773-649-1790
On Tue, Jan 25, 2011 at 12:21 PM, <[email protected]>wrote:
> Send cc-devel mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.ibiblio.org/mailman/listinfo/cc-devel
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of cc-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: CC REST API Updated for Public Domain Mark (Asheesh Laroia)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 25 Jan 2011 10:16:44 -0500 (EST)
> From: Asheesh Laroia <[email protected]>
> To: [email protected]
> Subject: Re: [cc-devel] CC REST API Updated for Public Domain Mark
> Message-ID: <[email protected]>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> On Thu, 13 Jan 2011, John Doig wrote:
>
> > Hello everyone,
> >
> > This morning, the CC REST API was updated to include support for the
> > Public Domain Mark and to deprecate the issuing of the retired Public
> > Domain Certification and Dedication. We have also added a new element,
> > `deprecated`, in license responses, that denotes whether or not the
> > issued license has been deprecated by Creative Commons. These changes
> > affect all versions of the REST API, excluding 1.0.
>
> This is a bit of a late reply, but -- it's *great* to see the 'deprecated'
> metadata showing up in the REST API. That's excellent.
>
> And the new Public Domain stuff Mark work been a long time coming. A lot
> of CC fans really appreciate the work CC is doing on revising that, and so
> it's a really welcome sign that it's stable enough to land in the API.
>
> -- Asheesh.
>
> --
> You will triumph over your enemy.
>
>
> ------------------------------
>
> _______________________________________________
> cc-devel mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/cc-devel
>
>
> End of cc-devel Digest, Vol 65, Issue 4
> ***************************************
>
_______________________________________________
cc-devel mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/cc-devel
