Extend Metadata - Revision history

Edsu: fixed link to schema

2013-04-25T08:11:23Z

fixed link to schema

Hdworak: /* Conclusions */ Improved the accessibility of the code

2008-08-18T10:56:38Z

‎Conclusions: Improved the accessibility of the code

Hdworak: An RDFa example (available under public domain)

2008-06-28T19:41:19Z

An RDFa example (available under public domain)

Nathan Yergler at 17:26, 24 June 2008

2008-06-24T17:26:26Z

Hdworak: /* As an element attribute */

2008-06-03T19:46:18Z

‎As an element attribute

Nathan Yergler at 22:44, 15 February 2008

2008-02-15T22:44:44Z

Jon Phillips: /* LINKing to a data: URL */

2006-05-24T03:36:11Z

‎LINKing to a data: URL

Nathan Yergler at 20:03, 23 May 2006

2006-05-23T20:03:09Z

Evan: data:

2006-05-23T19:45:26Z

data:

Jon Phillips at 23:06, 17 April 2006

2006-04-17T23:06:41Z

@@ Line 8: / Line 8: @@
 Familiar with RDF and want to know how this fits in with the larger picture?
-* View our [http://creativecommons/schema.rdf RDF schema] for information about [http://creativecommons.org/ns our model] in a machine-processable form.
+* View our [http://creativecommons.org/schema.rdf RDF schema] for information about [http://creativecommons.org/ns our model] in a machine-processable form.
 * Read our report on how to use [[#Defining dc:rights|dc:rights]].
 * Take a look at [[#Embedding RDF in HTML|our conclusions on using RDF in HTML]].

@@ Line 152: / Line 152: @@
      <span property="dc:date" content="1842">foo</span>
      <span property="dc:format" content="audio/mpeg">foo</span>
-     <a rel="dc:type" href="http://purl.org/dc/dcmitype/Sound">foo</a>
+     <a rel="dc:type" href="http://purl.org/dc/dcmitype/Sound">foo</a>,
-     <a rel="dc:source" href="http://example.net/gnomovision.mov">foo</a>
+     <a rel="dc:source" href="http://example.net/gnomovision.mov">foo</a>,
-     <a rel="cc:license" href="http://creativecommons.org/licenses/by-nc-nd/2.0/">foo</a>
+     <a rel="cc:license" href="http://creativecommons.org/licenses/by-nc-nd/2.0/">foo</a>,
-     <a rel="cc:license" href="http://artlibre.org/licence/lal/en/">foo</a>
+     <a rel="cc:license" href="http://artlibre.org/licence/lal/en/">foo</a>,
    </div>
    <div about="http://creativecommons.org/licenses/by-nc-nd/2.0/" typeof="cc:License">
-     <a rel="cc:permits" href="http://web.resource.org/cc/Reproduction">foo</a>
+     <a rel="cc:permits" href="http://web.resource.org/cc/Reproduction">foo</a>,
-     <a rel="cc:permits" href="http://web.resource.org/cc/Distribution">foo</a>
+     <a rel="cc:permits" href="http://web.resource.org/cc/Distribution">foo</a>,
-     <a rel="cc:requires" href="http://web.resource.org/cc/Notice">foo</a>
+     <a rel="cc:requires" href="http://web.resource.org/cc/Notice">foo</a>,
-     <a rel="cc:requires" href="http://web.resource.org/cc/Attribution">foo</a>
+     <a rel="cc:requires" href="http://web.resource.org/cc/Attribution">foo</a>,
-     <a rel="cc:prohibits" href="http://web.resource.org/cc/CommercialUse">foo</a>
+     <a rel="cc:prohibits" href="http://web.resource.org/cc/CommercialUse">foo</a>,
    </div>
 </div></source>
 Further reading: [http://esw.w3.org/topic/EmbeddingRDFinHTML Embedding RDF in HTML]

@@ Line 22: / Line 22: @@
 We've decided to use dc:rights to hold a more structured description of the copyright holder. Here's an example:
-<pre>
+<source lang="XML">
 <dc:rights>
    <Agent rdf:about="http://me.yoyo.dyne.name/">
@@ Line 30: / Line 30: @@
 </dc:rights>
-</pre>
+</source>
 As you can see the copyright holder is a person with a URL, a name and a date (of birth).
@@ Line 46: / Line 46: @@
 becomes this chunk of RDF:
-<pre>
+<source lang="XML">
 <rdf:Description>
    <dc:date>2002</dc:date>
@@ Line 54: / Line 54: @@
    </Agent></dc:rights>
 </rdf:Description>
-</pre>
+</source>
 '''Note:''' The actual text and description of the license ("...place up to three (3) copies...") is not included in this RDF, but would presumably be available at the URL given for the license.
@@ Line 73: / Line 73: @@
 A data: URL (see [http://www.ietf.org/rfc/rfc2397.txt RFC 2397]) encapsulates data into the URL itself. If used as the <code>href</code> attribute of a <code><link></code> element, it can include an RDF document verbatim.
-  <link rel="meta" type="application/rdf+xml" href="data:application/rdf+xml,%3Crdf%3ARDF%20xmlns%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2F%22%0D%0A%20%20%20%20xmlns%3Adc%3D%22http%3A%2F%2Fpurl.org%2Fdc%2Felements%2F1.1%2F%22%0D%0A%20%20%20%20xmlns%3Ardf%3D%22http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23%22%3E%0D%0A%3CWork%20rdf%3Aabout%3D%22http%3A%2F%2Fexample.org%2Fgnomophone.mp3%22%3E%0D%0A%20%20%3Cdc%3Atitle%3ECompilers%20in%20the%20Key%20of%20C%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3Cdc%3Adescription%3EA%20lovely%20classical%20work%20on%20compiling%20code.%3C%2Fdc%3Adescription%3E%0D%0A%20%20%3Cdc%3Acreator%3E%3CAgent%3E%0D%0A%20%20%20%20%3Cdc%3Atitle%3EYo-Yo%20Dyne%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3C%2FAgent%3E%3C%2Fdc%3Acreator%3E%0D%0A%20%20%3Cdc%3Arights%3E%3CAgent%3E%0D%0A%20%20%20%20%3Cdc%3Atitle%3EGnomophone%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3C%2FAgent%3E%3C%2Fdc%3Arights%3E%0D%0A%20%20%3Cdc%3Adate%3E1842%3C%2Fdc%3Adate%3E%0D%0A%20%20%3Cdc%3Aformat%3Eaudio%2Fmpeg%3C%2Fdc%3Aformat%3E%0D%0A%20%20%3Cdc%3Atype%20rdf%3Aresource%3D%22http%3A%2F%2Fpurl.org%2Fdc%2Fdcmitype%2FSound%22%20%2F%3E%0D%0A%20%20%3Cdc%3Asource%20rdf%3Aresource%3D%22http%3A%2F%2Fexample.net%2Fgnomovision.mov%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%3Aresource%3D%22http%3A%2F%2Fcreativecommons.org%2Flicenses%2Fby-nc-nd%2F2.0%2F%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%3Aresource%3D%22http%3A%2F%2Fwww.eff.org%2FIP%2FOpen_licenses%2Feff_oal.html%22%20%2F%3E%0D%0A%0D%0A%3C%2FWork%3E%0D%0A%0D%0A%3CLicense%20rdf%3Aabout%3D%22http%3A%2F%2Fcreativecommons.org%2Flicenses%2Fby-nc-nd%2F2.0%2F%22%3E%0D%0A%20%20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FReproduction%22%20%2F%3E%0D%0A%20%20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FDistribution%22%20%2F%3E%0D%0A%20%20%3Crequires%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FNotice%22%20%2F%3E%0D%0A%20%20%3Crequires%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FAttribution%22%20%2F%3E%0D%0A%20%20%3Cprohibits%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FCommercialUse%22%20%2F%3E%0D%0A%0D%0A%3C%2FLicense%3E%0D%0A%3C%2Frdf%3ARDF%3E" />
+<source lang="XML"><link rel="meta" type="application/rdf+xml" href="data:application/rdf+xml,%3Crdf%3ARDF%20xmlns%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2F%22%0D%0A%20%20%20%20xmlns%3Adc%3D%22http%3A%2F%2Fpurl.org%2Fdc%2Felements%2F1.1%2F%22%0D%0A%20%20%20%20xmlns%3Ardf%3D%22http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23%22%3E%0D%0A%3CWork%20rdf%3Aabout%3D%22http%3A%2F%2Fexample.org%2Fgnomophone.mp3%22%3E%0D%0A%20%20%3Cdc%3Atitle%3ECompilers%20in%20the%20Key%20of%20C%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3Cdc%3Adescription%3EA%20lovely%20classical%20work%20on%20compiling%20code.%3C%2Fdc%3Adescription%3E%0D%0A%20%20%3Cdc%3Acreator%3E%3CAgent%3E%0D%0A%20%20%20%20%3Cdc%3Atitle%3EYo-Yo%20Dyne%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3C%2FAgent%3E%3C%2Fdc%3Acreator%3E%0D%0A%20%20%3Cdc%3Arights%3E%3CAgent%3E%0D%0A%20%20%20%20%3Cdc%3Atitle%3EGnomophone%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3C%2FAgent%3E%3C%2Fdc%3Arights%3E%0D%0A%20%20%3Cdc%3Adate%3E1842%3C%2Fdc%3Adate%3E%0D%0A%20%20%3Cdc%3Aformat%3Eaudio%2Fmpeg%3C%2Fdc%3Aformat%3E%0D%0A%20%20%3Cdc%3Atype%20rdf%3Aresource%3D%22http%3A%2F%2Fpurl.org%2Fdc%2Fdcmitype%2FSound%22%20%2F%3E%0D%0A%20%20%3Cdc%3Asource%20rdf%3Aresource%3D%22http%3A%2F%2Fexample.net%2Fgnomovision.mov%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%3Aresource%3D%22http%3A%2F%2Fcreativecommons.org%2Flicenses%2Fby-nc-nd%2F2.0%2F%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%3Aresource%3D%22http%3A%2F%2Fwww.eff.org%2FIP%2FOpen_licenses%2Feff_oal.html%22%20%2F%3E%0D%0A%0D%0A%3C%2FWork%3E%0D%0A%0D%0A%3CLicense%20rdf%3Aabout%3D%22http%3A%2F%2Fcreativecommons.org%2Flicenses%2Fby-nc-nd%2F2.0%2F%22%3E%0D%0A%20%20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FReproduction%22%20%2F%3E%0D%0A%20%20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FDistribution%22%20%2F%3E%0D%0A%20%20%3Crequires%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FNotice%22%20%2F%3E%0D%0A%20%20%3Crequires%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FAttribution%22%20%2F%3E%0D%0A%20%20%3Cprohibits%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%2FCommercialUse%22%20%2F%3E%0D%0A%0D%0A%3C%2FLicense%3E%0D%0A%3C%2Frdf%3ARDF%3E" /></source>
 * '''Pro:''' It includes the data in the HTML document; it doesn't break old browsers; it's standard-compliant; it uses the proper element (link) for associating metadata
@@ Line 100: / Line 100: @@
 Example:
-<pre>
+<source lang="XML">
 <meta name="DC.rights"
        scheme="DCTERMS.URI"
@@ Line 106: / Line 106: @@
 <meta name="DC.rights"
        content="(c) 2002 Gnomovision Records" />
-</pre>
+</source>
 * '''Pro:''' Won't break anything.
@@ Line 126: / Line 126: @@
 [[RDFa]] allows RDF to be expressed using a small set of attributes.  The simple case of asserting a license only needs <code>rel="license"</code> added to the license link.  Example:
-<pre>
+<source lang="XML">
 This work is licensed under the <a rel="license"
      href="http://creativecommons.org/licenses/by/2.0/">Creative
      Commons Attribution License</a>.
-</pre>
+</source>
 * '''Pro:''' Super simple, extensible, [http://rdfa.info/wiki/How-to-validate validates].
@@ Line 142: / Line 142: @@
 We use and recommend [[RDFa]] since it's easy, straight forward, powerful and doesn't break existing web clients (browsers).  Our previous recommendation, including the RDF in an HTML comment, is no longer recommended.  For more information on our use of RDFa and metadata strategy generally, see information on the [[ccREL|CC Rights Expression Language]].
 Further reading: [http://esw.w3.org/topic/EmbeddingRDFinHTML Embedding RDF in HTML]

@@ Line 60: / Line 60: @@
 == Embedding RDF in HTML ==
-There may be lots of RDF out there, but it's no good if no one can find it. Since almost everything on the Web is HTML, we need a good way to hook RDF into the HTML Web. Here are the best ways to do so:
+There may be lots of RDF out there, but it's no good if no one can find it. Since almost everything on the Web is HTML, we need a good way to hook RDF into the HTML Web. Here are some ways to do so:
 === LINKing to an external file ===
@@ Line 76: / Line 76: @@
 * '''Pro:''' It includes the data in the HTML document; it doesn't break old browsers; it's standard-compliant; it uses the proper element (link) for associating metadata
-* '''Con:''' It requires the RDF to be URL-encoded; it's hard to read; not all URL libraries can recognize or decode a data: URL; Creative Commons tools ([[MozCC]], [[CcLookup]], etc) don't support it, likely browsers don't/won't support it; not a preferred method
+* '''Con:''' It requires the RDF to be URL-encoded; it's hard to read; not all URL libraries can recognize or decode a data: URL; Creative Commons tools ([[MozCC]], [[CcLookup]], etc) don't support it, likely browsers don't/won't support it; not a preferred method.
-See also: [http://software.hixie.ch/utilities/cgi/data/data data: URI kitchen] (tool for making data: URLs), [http://www.mozilla.org/quality/networking/docs/aboutdata.html about data: URLs] (from Mozilla)
+See also: [http://software.hixie.ch/utilities/cgi/data/data data: URI kitchen] (tool for making <code>data:</code> URLs), [http://www.mozilla.org/quality/networking/docs/aboutdata.html about data: URLs] (from Mozilla)
 === In the HEAD ===
@@ Line 85: / Line 85: @@
 * '''Pro:''' Should be ignored by browsers.
-* '''Con:''' Not all users may be able to. Doesn't validate.
+* '''Con:''' Not all users may be able to insert content into the HEAD of their documents. Doesn't validate. Not a preferred method.
 === In the BODY ===
@@ Line 92: / Line 92: @@
 * '''Pro:''' Super simple.
-* '''Con:''' RDF needs to be formatted as attributes. May cause problems with some browsers. Doesn't validate.
+* '''Con:''' RDF needs to be formatted as attributes. May cause problems with some browsers. Doesn't validate.  Not a preferred method.
 === In META ===
@@ Line 109: / Line 109: @@
 * '''Pro:''' Won't break anything.
-* '''Con:''' Not all users may be able to. '''Not RDF''' (included in this list due to obviousness). Limited to statements about the current page.
+* '''Con:''' Not all users may be able to. '''Not RDF''' (included in this list due to obviousness). Limited to statements about the current page. Not a preferred method.
 Further reading: [http://dublincore.org/documents/dcq-html/ Expressing Dublin Core in HTML/XHTML meta and link elements]
-=== As an element attribute ===
+=== In a comment ===
-A <code>rel="license"</code> attribute may be added to an "<code>a</code>" anchor element in HTML/XHTML. Example:
+[[RDFa]] allows RDF to be expressed using a small set of attributes.  The simple case of asserting a license only needs <code>rel="license"</code> added to the license link.  Example:
 <pre>
@@ Line 123: / Line 132: @@
 </pre>
-* '''Pro:''' Super simple, validates.
+* '''Pro:''' Super simple, extensible, [http://rdfa.info/wiki/How-to-validate validates].
-* '''Con:''' '''Not RDF''' (however may be used to generate RDF in a GRDDL fashion). Limited to statements about the current page.
+* '''Con:''' Validation requires modifying the DOCTYPE which some users may be unable to do.
-=== In a comment ===
+See also: [[ccREL|Creative Commons Rights Expression Language]]
 === Conclusions ===
@@ Line 141: / Line 141: @@
 RDF readers should support all of these methods.
-We use and recommend the "in the comment" method, since it's easy and won't break anything. Hopefully tools that don't yet support it will be upgraded to do so. Two examples: [http://www.yergler.net/projects/ccvalidator/ ccValidator] and [http://www.yergler.net/projects/mozcc/ mozCC].
+We use and recommend [[RDFa]] since it's easy, straight forward, powerful and doesn't break existing web clients (browsers).  Our previous recommendation, including the RDF in an HTML comment, is no longer recommended.  For more information on our use of RDFa and metadata strategy generally, see information on the [[ccREL|CC Rights Expression Language]].
 Further reading: [http://esw.w3.org/topic/EmbeddingRDFinHTML Embedding RDF in HTML]

@@ Line 115: / Line 115: @@
 === As an element attribute ===
-A <code>rel="license"</code> attribute may be added to an "<code>a</code>" anchor element in HTML/XMTML. Example:
+A <code>rel="license"</code> attribute may be added to an "<code>a</code>" anchor element in HTML/XHTML. Example:
 <pre>

@@ Line 62: / Line 62: @@
 There may be lots of RDF out there, but it's no good if no one can find it. Since almost everything on the Web is HTML, we need a good way to hook RDF into the HTML Web. Here are the best ways to do so:
-=== LINKing to it ===
+=== LINKing to an external file ===
 RDF can be kept in a separate file (<code>filename.rdf</code>) and linked to using <code><link rel="meta" type="application/rdf+xml" ... /></code> or an equivalent a href tag.
@@ Line 68: / Line 68: @@
 * '''Pro:''' Doesn't break anything.
 * '''Con:''' Requires users to make files. Not supported by all readers.
 === In the HEAD ===

← Older revision		Revision as of 23:06, 17 April 2006
Line 1:		Line 1:
−	= Extending Creative Commons Metadata =	+	[[Category:Developer]]
		+	[[Category:Technology]]
		+	[[Category:metadata]]
		+	[[Category:guide]]
		+
		+	== Extending Creative Commons Metadata ==

	Familiar with RDF and want to know how this fits in with the larger picture?		Familiar with RDF and want to know how this fits in with the larger picture?