Development of Creative Commons licenses

[Mike Linksvayer <ml AT creativecommons.org>]

On Sat, 2007-04-21 at 14:03 -0700, Lucas Gonze wrote:
> I am really frustrated by the labor involved in CC licensing for my
> own music.  It's not clear what I am supposed to do, and the tools are
> just a bummer to make work.  EG cli-tools doesn't do Ogg.
> 
> AFAIK this is the best current documentation --
> MP3: http://wiki.creativecommons.org/MP3
> Ogg: http://wiki.creativecommons.org/OGG
> FLAC: no spec exists

Well Ogg FLAC (I only just learned that there is a "Native FLAC"
container) of course falls under Ogg.  

> But is it possible that things have changed to the extent that I can
> live without any embedded metadata at all, per
> http://wiki.creativecommons.org/Nonweb_Tagging?

You can always live without metadata, period -- it is never required to
get metadata right to effectively license something.  Metadata only
helps tools (often only potentially helps tools) find and organize
works.

> The style defined at http://wiki.creativecommons.org/RDFa looks
> radically more convenient than embedded metadata:

Yes it is.  And entirely complementary. But I'd do web metadata before
embedded metadata if you do only one. 

> ...
> What about bar.jpg which is displayed in http://example.com/foo via a
> &tl;img src="/bar.jpg"> element?
> 
> To specify that bar.jpg is licensed, even under a different license,
> we can qualify the link with an about attribute:
> 
> <a about="/bar.jpg" rel="license"
> href="http://creativecommons.org/licenses/by-nc/2.5/";>cc</a>
> ...
> 
> I would then do the entire licensing process for
> http://example.com/foo.flacby publishing this statement:
> <a about="http://example.com/foo.flac"; rel="license"
> href="http://creativecommons.org/licenses/by-nc/2.5/";>cc</a>
> 
> Is there anything else I need to do aside from that?

No.

Currently the best document covering all of this is
http://wiki.creativecommons.org/Marking_Works_Technical


-- 
  http://wiki.creativecommons.org/User:Mike_Linksvayer