Skip to Content.
Sympa Menu

cc-devel - Re: [cc-devel] Querying All License and Versions

cc-devel AT lists.ibiblio.org

Subject: Developer discussion for Creative Commons technology and tools

List archive

Chronological Thread  
  • From: Nathan Yergler <nathan AT yergler.net>
  • To: Maarten Zeinstra <mz AT kl.nl>
  • Cc: cc-devel AT lists.ibiblio.org
  • Subject: Re: [cc-devel] Querying All License and Versions
  • Date: Fri, 7 Dec 2012 11:35:13 -0500

You can imagine that if you're building a service that allows people
to upload/archive existing works (as opposed to new works), you'd want
to capture the specific license the work was offered under, as opposed
to requiring license upgrade or limiting yourself to 3.0 Unported
works.

NRY

On Thu, Dec 6, 2012 at 5:33 PM, Maarten Zeinstra <mz AT kl.nl> wrote:
> Hi Alex,
>
> Yes that would be the RDF file.
>
> Incidentally I abstracted all valid license URLs out of that file just the
> other day. I've included that file here. You might be surprised that that
> list contains 600 different licenses. This is because we have 3 major
> versions of our licenses ported to many different jurisdiction. There are
> also a lot of licenses that still exist but are not actively promoted
> anymore like earlier versions of a license and some other license
> constructions.
>
> Also could you please tell us why you would need a list of all the
> licenses. If I would offer license options for a website or service I would
> just use the six unported 3.0 licenses:
>
> http://creativecommons.org/licenses/by/3.0/
> http://creativecommons.org/licenses/by-sa/3.0/
> http://creativecommons.org/licenses/by-nc/3.0/
> http://creativecommons.org/licenses/by-nd/3.0/
> http://creativecommons.org/licenses/by-nc-nd/3.0/
> http://creativecommons.org/licenses/by-nc-sa/3.0/
>
> I would copy the explanation from http://creativecommons.org/licenses/ and
> provide proper attribution (of course). Which makes your software far more
> maintainable.
>
> Again we are happy to think with you on your project.
>
> Cheers and good luck,
>
> Maarten Zeinstra
>
> --
> Kennisland | www.kennisland.nl | t +31205756720 | m +31643053919 |
> @mzeinstra
>
>
>
>
>
> On Dec 6, 2012, at 19:38 , Mike Linksvayer <ml AT gondwanaland.com> wrote:
>
>> On Thu, Dec 6, 2012 at 10:24 AM, Thomas, Alexander <athom09 AT emory.edu>
>> wrote:
>>> Nathan,
>>>
>>> Is This the RDF you are referring to
>>> https://creativecommons.org/licenses/index.rdf (link provided by Mike)?
>>
>> Probably. :)
>>
>>> If so I can sees how to get the URI and Name and image but don't see how
>>> to get the Description.
>>
>> If you mean by "Description" a brief text like those at
>> https://creativecommons.org/licenses/#licenses there is no
>> programmatic way; those are just translated in
>> https://www.transifex.com/projects/p/CC with no lookup by license, but
>> maybe that is something that ought be done by a CC programmer (none
>> exist at this moment).
>>
>> Probably the closest existing thing to a description useful for
>> programs other than the license name is the content found at a license
>> URI, ie, the deed. Another approach would be to construct your own
>> description by pretty-printing permits/requires/prohibits statements
>> you find.
>>
>> Mike
>> _______________________________________________
>> cc-devel mailing list
>> cc-devel AT lists.ibiblio.org
>> http://lists.ibiblio.org/mailman/listinfo/cc-devel
>
>
> _______________________________________________
> cc-devel mailing list
> cc-devel AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/cc-devel
>




Archive powered by MHonArc 2.6.24.

Top of Page