Difference between revisions of "Embedding Specifications"

From Creative Commons
Jump to: navigation, search
(Filetypes)
Line 8: Line 8:
 
== Filetypes ==
 
== Filetypes ==
  
=== [[MP3]] ===
+
=== [[MP3]] - audio format ===
  
=== [[OGG]] ===
+
=== [[OGG]] - audio format ===
  
=== [[Quicktime]] ===
+
=== [[Quicktime]] - Video and Multimedia format ===
  
=== [[Windows Media]] ===
+
=== [[Windows Media]] - Video format ===
  
=== [[PDF]] ===
+
=== [[PDF]] - document (and multimedia) format ===
  
=== [[XML]] ===
+
=== [[XML]] - W3C document format ===
  
=== [[SVG]] ===
+
=== [[SVG]] - W3C Graphics format ===
  
=== [[SMIL]] ===
+
=== [[SMIL]] - W3C Multimedia format ===
  
=== [[OpenDocument Format]] - ODF (ODT, ODP, ODS, ODG)
+
=== [[OpenDocument Format]] - ODF (ODT, ODP, ODS, ODG) ===
  
 
=== [[Microsoft Office Document Formats]] - the legacy Microsoft Office formats ===
 
=== [[Microsoft Office Document Formats]] - the legacy Microsoft Office formats ===

Revision as of 02:10, 6 July 2006


We currently publish license claim embedding recommendations for MP3 and OGG files. We want to publish similar recommendations for every popular "media" file format including Quicktime, Windows Media, PDF, GIF, JPEG, PNG, Flash... Can you research a file format and suggest a specification? We also need people to provide implementations of our recommendations in various languages, e.g., a Java library that embeds, reads, and verifies license claims. See the cctools project for existing implementations.

Filetypes

MP3 - audio format

OGG - audio format

Quicktime - Video and Multimedia format

Windows Media - Video format

PDF - document (and multimedia) format

XML - W3C document format

SVG - W3C Graphics format

SMIL - W3C Multimedia format

OpenDocument Format - ODF (ODT, ODP, ODS, ODG)

Microsoft Office Document Formats - the legacy Microsoft Office formats

[[[Microsoft XML Format]] - the new Microsoft XML format

Please add your own file type

Examples

TODO

  • (DONE) Make specs/implementations a top-level category, with each format it's own challenge.
  • Upon completion of a spec, issue a challenge for implementations in different languages and addition of support to existing libraries.