Difference between revisions of "Embedded Metadata"
m (→Embedding the metadata) |
(→The advantage of the verification link) |
||
| Line 16: | Line 16: | ||
</rdf:RDF> --> | </rdf:RDF> --> | ||
| − | |||
| − | |||
| − | |||
<!-- <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#"> | <!-- <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#"> | ||
| − | <Work rdf:about="urn:sha1: | + | <Work rdf:about="urn:sha1:7LTEBYH2MA7XHJXGFHHHLJUC2ST4C5YW"><dc:date>2008</dc:date><dc:title>DjEmmetMasterson Vs DjJoeP</dc:title><dc:description>Sick track!</dc:description><dc:rights><Agent><dc:title>http://creativecommons.org/technology/embedding#2</dc:title></Agent></dc:rights><dc:type rdf:resource="http://purl.org/dc/dcmitype/Sound" /><license rdf:resource="http://creativecommons.org/licenses/by-sa/2.5/" /></Work> |
| − | + | <License rdf:about="http://creativecommons.org/licenses/by-sa/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/ShareAlike" /><requires rdf:resource="http://web.resource.org/cc/Notice" /></License> | |
| − | |||
| − | |||
| − | |||
| − | <License rdf:about="http://creativecommons.org/licenses/by- | ||
| − | |||
| − | |||
| − | |||
| − | |||
</rdf:RDF> --> | </rdf:RDF> --> | ||
Revision as of 23:38, 14 April 2008
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).
Verification Link: Engine
Also a Traffic An added benefit of the verification link is that licensors, or the companies who do their hosting, can use them to draw traffic to their websites.
Example:
Ravi is an amateur photographer. He hosts his photos at SNAP, a website devoted to photography. Each time Ravi uploads his photos to the SNAP website, the SNAP software offers Ravi an opportunity to use Creative Commons licenses, and the tools to embed his webpage on SNAP with the appropriate RDF. Next, SNAP's software automatically inserts the verification link into his photo files' copyright fields.
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).
