Difference between revisions of "Embedded Metadata"
(Undo revision 114280 by CCID-jeremyhardin (talk)) |
|||
| (21 intermediate revisions by 15 users not shown) | |||
| Line 16: | Line 16: | ||
<div style="text-align:center"> | <div style="text-align:center"> | ||
| − | http:// | + | http://creativecommons.org/images/comics/mp3/1.gif |
</div> | </div> | ||
| − | First, Anita would put a "Some Rights Reserved" button on the | + | First, Anita would put a "Some Rights Reserved" button on the page displaying here work where her song could be downloaded — along with a link to a license, some RDF metadata, and an assertion about the copyright status of the work. Nothing new here: this is what Creative Commons licensors do now. |
<div style="text-align:center"> | <div style="text-align:center"> | ||
| − | http:// | + | http://creativecommons.org/images/comics/mp3/2.gif |
</div> | </div> | ||
| Line 28: | Line 28: | ||
<div style="text-align:center"> | <div style="text-align:center"> | ||
| − | http:// | + | http://creativecommons.org/images/comics/mp3/4.gif |
</div> | </div> | ||
| Line 51: | Line 51: | ||
</rdf:RDF> --> | </rdf:RDF> --> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | < | + | Ravi circulates the photos among his schoolmates, whose photo-viewing software reads the copyright fields and takes them to the SNAP website, where they can see Ravi's whole catalog of photography and links to other SNAP services.<!-- <rdf:RDF xmlns="http://web.resource.org/cc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> |
| − | http:// | + | <Work rdf:about="urn:sha1:55QRQ2ZQXJQGK6D6ZEYERTA3QRDFCE2M"><dc:date>2008</dc:date><dc:title>Number one sex</dc:title><dc:description></dc:description><dc:rights><Agent><dc:title>R. Kelly & Keri Hilson</dc:title></Agent></dc:rights><dc:type rdf:resource="http://purl.org/dc/dcmitype/Sound" /><license rdf:resource="http://creativecommons.org/licenses/by/2.5/" /></Work> |
| − | </ | + | <License rdf:about="http://creativecommons.org/licenses/by/2.5/"><requires rdf:resource="http://web.resource.org/cc/Attribution" /><permits rdf:resource="http://web.resource.org/cc/Reproduction" /><permits rdf:resource="http://web.resource.org/cc/Distribution" /><permits rdf:resource="http://web.resource.org/cc/DerivativeWorks" /><requires rdf:resource="http://web.resource.org/cc/Notice" /></License> |
| − | + | </rdf:RDF> --> | |
| − | |||
| − | |||
| − | < | ||
| − | http:// | ||
| − | </ | ||
| − | |||
| − | |||
== Technical Explanation == | == Technical Explanation == | ||
See [[Nonweb Tagging]], and for specific formats, see [[MP3]] and [[XMP]] (PDF, JPEG, video). | See [[Nonweb Tagging]], and for specific formats, see [[MP3]] and [[XMP]] (PDF, JPEG, video). | ||
Latest revision as of 20:46, 23 September 2015
Creative Commons licenses are attached to Web pages. But we also want our licenses to be useful for materials distributed in file formats around the Net. The protocol described here works for many filetypes.
If your software does not transparently support embedding CC license metadata (you should only have to select a license), do not attempt to do it yourself (it will be a frustrating experience).
Embedding the metadata
Let's say Anita wants to license her song, "Volcano Love," with a Creative Commons license, and release it as an MP3. Here's what she'd do:
First, Anita would put a "Some Rights Reserved" button on the page displaying here work where her song could be downloaded — along with a link to a license, some RDF metadata, and an assertion about the copyright status of the work. Nothing new here: this is what Creative Commons licensors do now.
With file embedding, though, this page will now serve the added function of verification. Here's how: Anita would insert the URL to that webpage in the copyright field of the MP3 file, along with a short, plain description of the work's license status. We call this the license verification link because it points back to a page that Anita herself controls.
Next, imagine Anita puts the MP3 on a file-sharing network. A user comes across her MP3 and can follow the verification link to Anita's page. In the future, we hope that file-sharing networks, media players, and other applications will build tools that read the verification link automatically and inform users of the copyright assertions like Anita's.
The advantage of the verification link
Embedding this kind of "verification link" in MP3s, as opposed to merely the license metadata, is a measure of protection for artists against the incorrect or fraudulent labeling and sharing of their work.
Ravi circulates the photos among his schoolmates, whose photo-viewing software reads the copyright fields and takes them to the SNAP website, where they can see Ravi's whole catalog of photography and links to other SNAP services.
Technical Explanation
See Nonweb Tagging, and for specific formats, see MP3 and XMP (PDF, JPEG, video).
