Difference between revisions of "License Properties"
Line 1: | Line 1: | ||
In addition to the human readable license deeds and legal code, Creative Commons provides machine readable metadata for licenses. This page describes how to begin with a license URI and map it to license properties. | In addition to the human readable license deeds and legal code, Creative Commons provides machine readable metadata for licenses. This page describes how to begin with a license URI and map it to license properties. | ||
− | + | License Properties describe the permissions, prohibitions and requirements of a license. Permissions declare a permission given by the license, above and beyond what default copyright law allows. Prohibitions prohibit a particular use of the work, specifically affecting the scope of the permissions provided by a permission. Requirements describe actions required of user when making use of the permissions. | |
− | + | There are two ways to discover license properties given a license URI: | |
+ | * The "dumb" and easy way: [[inspect the URL|#Inspecting the URL]]. This can be done with regular expressions or even simple string searching, but requires your code to bake in a little knowledge about CC license URI conventions, and will not work with possible future license URIs that do not follow these conventions (e.g., non-CC licenses that use CC style metadata). But this downside should be of little concern if all you want to do is discover CC licensed material and be able to remember and filter on high level properties such as whether commercial use or derviative works are prohibited. | ||
+ | * The smart and hard way: [[#Using RDFa]]. This allows you to discover properties for any license URI, including properties that may not be encoded in URI conventions. However, use of this method requires your code to use a RDFa parser. | ||
− | + | = Inspecting the URL = | |
− | |||
− | |||
Creative Commons license deed URLs have the following format: | Creative Commons license deed URLs have the following format: | ||
Line 30: | Line 30: | ||
* '''sa''': Share-Alike: Derivative works are allowed, but must also be licensed under the same license. | * '''sa''': Share-Alike: Derivative works are allowed, but must also be licensed under the same license. | ||
− | == Using RDFa | + | === Special Cases === |
+ | |||
+ | http://creativecommons.org/licenses/publicdomain/ | ||
+ | |||
+ | For this URI, all of the properties above are false, but obviously the (implicit) properties of permitting distribution and derivative works are true. | ||
+ | |||
+ | |||
+ | = Using RDFa = | ||
[[RDFa]] is an editor's draft at W3 which describes a way to serialize [http://www.w3.org/RDF/ RDF] triples in HTML. Creative Commons includes the appropriate RDFa When selecting a license from http://creativecommons.org/license to indicate that a page is licensed. For example: | [[RDFa]] is an editor's draft at W3 which describes a way to serialize [http://www.w3.org/RDF/ RDF] triples in HTML. Creative Commons includes the appropriate RDFa When selecting a license from http://creativecommons.org/license to indicate that a page is licensed. For example: |
Revision as of 18:58, 10 September 2007
In addition to the human readable license deeds and legal code, Creative Commons provides machine readable metadata for licenses. This page describes how to begin with a license URI and map it to license properties.
License Properties describe the permissions, prohibitions and requirements of a license. Permissions declare a permission given by the license, above and beyond what default copyright law allows. Prohibitions prohibit a particular use of the work, specifically affecting the scope of the permissions provided by a permission. Requirements describe actions required of user when making use of the permissions.
There are two ways to discover license properties given a license URI:
- The "dumb" and easy way: #Inspecting the URL. This can be done with regular expressions or even simple string searching, but requires your code to bake in a little knowledge about CC license URI conventions, and will not work with possible future license URIs that do not follow these conventions (e.g., non-CC licenses that use CC style metadata). But this downside should be of little concern if all you want to do is discover CC licensed material and be able to remember and filter on high level properties such as whether commercial use or derviative works are prohibited.
- The smart and hard way: #Using RDFa. This allows you to discover properties for any license URI, including properties that may not be encoded in URI conventions. However, use of this method requires your code to use a RDFa parser.
Inspecting the URL
Creative Commons license deed URLs have the following format:
http://creativecommons.org/licenses/{license-properties}/{version}/{jurisdiction}/
The jurisdiction is optional. For example:
http://creativecommons.org/licenses/by/3.0/
Is the URL for the Attribution 3.0 (Unported) license. The license is Unported as there is no jurisdiction element present. The Attribution 2.0 (France) license has the following URL:
http://creativecommons.org/licenses/by/2.0/fr/
Mapping Individual Properties
The license properties portion of the URL is a sequence a two letter codes separated by dashes ("-"). These map to the following license properties:
- by: Attribution: Attribution is required with any reuse or redistribution, in the manner specified by the licensor.
- nc: Non-Commercial: Commercial use is prohibited.
- nd: No Derivatives: Only verbatim reproduction is permitted.
- sa: Share-Alike: Derivative works are allowed, but must also be licensed under the same license.
Special Cases
http://creativecommons.org/licenses/publicdomain/
For this URI, all of the properties above are false, but obviously the (implicit) properties of permitting distribution and derivative works are true.
Using RDFa
RDFa is an editor's draft at W3 which describes a way to serialize RDF triples in HTML. Creative Commons includes the appropriate RDFa When selecting a license from http://creativecommons.org/license to indicate that a page is licensed. For example:
<a href="http://creativecommons.org/licenses/by/3.0/" rel="license">Attribution 3.0</a>
The rel="license"
attribute indicates that the link specified (the license URL in this case) has special semantic meaning.
With the license URI, an RDFa parser may be used to extract license attributes from the human readable deed. RDFa parsers are available for many languages, including Python (RdfaDict, rdflib), Ruby (ruby-rdfa) and PHP (RDFa Monkey).
Passing the Attribution 3.0 Unported deed (http://creativecommons.org/licenses/by/3.0/) through an RDFa parser yields the following triples:
@prefix cc: <http://creativecommons.org/ns#> . http://creativecommons.org/licenses/by/3.0/ cc:requires cc:Attribution . http://creativecommons.org/licenses/by/3.0/ cc:requires cc:Notice . http://creativecommons.org/licenses/by/3.0/ cc:permits cc:Reproduction . http://creativecommons.org/licenses/by/3.0/ cc:permits cc:Distribution . http://creativecommons.org/licenses/by/3.0/ cc:permits cc:DerivativeWorks .
For a complete list of Permissions, Prohibitions and Requirements defined by Creative Commons see http://creativecommons.org/ns.