Difference between revisions of "OGG"
Jon Phillips (talk | contribs) m |
Jon Phillips (talk | contribs) |
||
| Line 1: | Line 1: | ||
[[Category:Developer]] | [[Category:Developer]] | ||
[[Category:technology]] | [[Category:technology]] | ||
| − | [[Category: | + | [[Category:Developer Challenges]] |
| − | [[Category: | + | [[Category:Developer Challenges Completed]] |
[[Category:OGG]] | [[Category:OGG]] | ||
{{incomplete}} | {{incomplete}} | ||
Revision as of 05:19, 1 May 2006
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 MP3s.
Ogg embedded metadata is placed in comment fields. One 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: 1995 Example Band. Licensed to the public under http://creativecommons.org/licenses/by/2.0/ verify at http://example.com/cclicenses.html
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 ".
Tools
Example code for embedding license claims in files and generating license claim RDF is available at the cctools project on sourceforge.
