License Properties - Revision history

CCID-timidrobot: Updated URLs to use HTTPS, where appropropriate

2020-05-27T15:40:33Z

Updated URLs to use HTTPS, where appropropriate

Mike Linksvayer: Reverted edits by Deyong (talk) to last revision by Nathan Yergler

2013-07-22T03:57:37Z

Reverted edits by Deyong (talk) to last revision by Nathan Yergler

Deyong at 04:07, 4 July 2013

2013-07-04T04:07:52Z

Nathan Yergler at 20:37, 10 September 2007

2007-09-10T20:37:05Z

Nathan Yergler at 20:29, 10 September 2007

2007-09-10T20:29:12Z

Nathan Yergler at 20:13, 10 September 2007

2007-09-10T20:13:46Z

Mike Linksvayer at 18:59, 10 September 2007

2007-09-10T18:59:35Z

Mike Linksvayer at 18:58, 10 September 2007

2007-09-10T18:58:16Z

Nathan Yergler at 16:07, 10 September 2007

2007-09-10T16:07:28Z

Nathan Yergler at 15:46, 10 September 2007

2007-09-10T15:46:47Z

@@ Line 9: / Line 9: @@
 = Inspecting the URL =
-Creative Commons license deed URLs have the following format:
+Creative Commons license deed URLs, for version 4.0, have the following format:
-   http://creativecommons.org/licenses/{license-properties}/{version}/{jurisdiction}/
+   https://creativecommons.org/licenses/{license-properties}/{version}/
-The jurisdiction is optional.  For example:
+Creative Commons license deed URLs, prior to version 4.0, have the following format:
-   http://creativecommons.org/licenses/by/3.0/
+   https://creativecommons.org/licenses/{license-properties}/{version}/{jurisdiction}/
 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/
+   https://creativecommons.org/licenses/by/2.0/fr/
 === Mapping Individual Properties ===
@@ Line 41: / Line 45: @@
 Example usage:
-$ python extract_simple.py http://creativecommons.org/licenses/by/3.0/
+$ python extract_simple.py https://creativecommons.org/licenses/by/3.0/
 Attribution
-$ python extract_simply.py http://creativecommons.org/licenses/by-nc/3.0/
+$ python extract_simply.py https://creativecommons.org/licenses/by-nc/3.0/
 Attribution
 Non-Commercial
@@ Line 86: / Line 90: @@
 ==== Public Domain ====
-   http://creativecommons.org/licenses/publicdomain/
+   https://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.
-==== Sampling ====
+==== Sampling (retired) ====
 The [http://creativecommons.org/license/sampling Sampling Licenses] define specific permissions with respect to sampling a work.  The license URLs are
-   http://creativecommons.org/licenses/sampling/1.0/ (retired)
+   https://creativecommons.org/licenses/sampling/1.0/ (retired)
-   http://creativecommons.org/licenses/sampling+/1.0/
+   https://creativecommons.org/licenses/sampling+/1.0/ (retired)
-   http://creativecommons.org/licenses/nc-sampling+/1.0/
+   https://creativecommons.org/licenses/nc-sampling+/1.0/ (retired)
 Many simple implementations may ignore these.
@@ Line 104: / Line 108: @@
 Creative Commons provides metadata "wrappers" for some source code licenses.  These URLs are:
-   http://creativecommons.org/licenses/MIT/
+   https://creativecommons.org/licenses/MIT/
-   http://creativecommons.org/licenses/BSD/
+   https://creativecommons.org/licenses/BSD/
-   http://creativecommons.org/licenses/GPL/2.0/
+   https://creativecommons.org/licenses/GPL/2.0/
-   http://creativecommons.org/licenses/LGPL/2.1/
+   https://creativecommons.org/licenses/LGPL/2.1/
 = Using RDFa =

@@ 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.
-[http://goo.gl/vGpQ8 contoh cv]  and  [http://goo.gl/MLwzP kata kata galau]  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.
+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:

@@ 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.
-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.
+[http://goo.gl/vGpQ8 contoh cv]  and  [http://goo.gl/MLwzP kata kata galau]  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:

@@ Line 129: / Line 129: @@
 For a complete list of Permissions, Prohibitions and Requirements defined by Creative Commons see http://creativecommons.org/ns.
 [[Category:Developer]]
 [[Category:Metadata]]

@@ Line 32: / Line 32: @@
 === Sample Code ===
-{{incomplete}}
+<pre><nowiki>
 === Special Cases ===

@@ Line 23: / Line 23: @@
 === 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:
+The license properties portion of the URL is a sequence a 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.
@@ Line 29: / Line 29: @@
 * '''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/
@@ Line 36: / Line 42: @@
 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 =

@@ Line 4: / Line 4: @@
 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 "dumb" and easy way: [[#Inspecting the URL|Inspect 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.
+* The smart and hard way: [[#Using RDFa|Use 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 =

@@ 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.
@@ Line 34: / Line 32: @@
 == Using RDFa ==
-[http://www.w3.org/2006/07/SWD/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:
+[[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:
    &lt;a href="http://creativecommons.org/licenses/by/3.0/" '''rel="license"'''>Attribution 3.0</a>
@@ Line 40: / Line 38: @@
 The <code>rel="license"</code> 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.
+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]], [http://rdflib.net rdflib]), Ruby ([http://code.google.com/p/ruby-rdfa/ ruby-rdfa]) and PHP ([http://www.avthasselt.sohosted.com/rdfamonkey/ RDFa Monkey]).
-=== Additional Resources ===
+  @prefix cc: <http://creativecommons.org/ns#> .
 [[Category:Developer]]
 [[Category:Metadata]]