Difference between revisions of "OGG"

From Creative Commons
Jump to: navigation, search
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
[[Category:Developer]]
 
[[Category:Developer]]
[[Category:technology]]
+
[[Category:Technology]]
[[Category:Developer Challenges]]
+
{{Filetype|
[[Category:Developer Challenges Completed]]
+
    license_url=True|
[[Category:OGG]]
+
    web_statement=True|
{{incomplete}}
+
    more_permissions=False
 +
}}
 +
= Using Creative Commons Metadata in OGG Files =
  
 
<div style="float: right">
 
<div style="float: right">
Line 11: Line 13:
 
</div>
 
</div>
  
'''This is a developer-oriented document.  Read our [http://creativecommons.org/technology/embedding non-technical account with explanatory comics] first.'''
+
'''This is a developer-oriented document.  Read our [[Embedded Metadata|non-technical account with explanatory comics]] first.'''
  
This document describes how to apply [[Nonweb Tagging|our non-web content guidelines]] to MP3s.
+
This document describes how to apply [[Nonweb Tagging|our non-web content guidelines]] to OGG files.
  
Ogg embedded metadata is placed in [http://www.xiph.org/ogg/vorbis/doc/v-comment.html comment fields]. One of these will be used for embedding Creative Commons license claim metadata:
+
OGG embedded metadata is placed in []. Two of these will be used for embedding Creative Commons license claim metadata:
  
The '''LICENSE''' comment should include a human-readable license and license claim information. The contents of this frame are displayed by some programs in a "file info" window. Example value: <code>1995 Example Band. Licensed to the public under http://creativecommons.org/licenses/by/2.0/ verify at http://example.com/cclicenses.html</code>
+
'''LICENSE''' (Copyright/Legal information) should include the license URL. For example, http://creativecommons.org/licenses/by/2.5/.
  
If "verify at " exists in LICENSE, everything after it must be the license claim URL, and if there is a license claim URL then it must be preceded by "verify at ".
+
'''CONTACT''' (Contact information for track creators) should include the URL where the work metadata, including verification information, may be found. See [[Nonweb Tagging]] for information on verification metadata.
 
 
== Tools ==
 
 
 
Example code for embedding license claims in files and generating license claim RDF is available at the [http://cctools.sourceforge.net/ cctools project on sourceforge].
 

Latest revision as of 17:56, 10 October 2007


File Type Information
Supports embedding license URL: supports_license_url::True
Supports embedding web statement: supports_web_statement::True
Supports embedding more permissions: supports_more_permissions::False
Metadata Location: [[Metadata location::{{{metadata_location}}}]] | (unknown) }}
Metadata Format: [[Metadata format::{{{metadata_format}}}]] | (unknown) }}


Using Creative Commons Metadata in OGG Files

http://creativecommons.org/images/metadata/mp3-small.gif
Click to See Full Image

This is a developer-oriented document. Read our non-technical account with explanatory comics first.

This document describes how to apply our non-web content guidelines to OGG files.

OGG embedded metadata is placed in []. Two of these will be used for embedding Creative Commons license claim metadata:

LICENSE (Copyright/Legal information) should include the license URL. For example, http://creativecommons.org/licenses/by/2.5/.

CONTACT (Contact information for track creators) should include the URL where the work metadata, including verification information, may be found. See Nonweb Tagging for information on verification metadata.