My slides from a presentation I gave to the GNU/Linux NYC Meetup on June 24th

1. c
Fred Benenson
Culture Program Associate
Tuesday, June 24 2008
fred@creativecommons.org

3. What is c?
 We’re a 501c3
 Non-profit
 Non-legal
 We offer free legal and technology tools
that allow creators to publish their works on
more flexible terms
 Terms that allow public sharing, reuse, and
remix.

4. Why?

5. To resolve a tension.

7. Terms May Permit Less

8. The Tension in Digital Media
 Technology has changed the way
creative works are made, distributed,
and used.
 Thenature of digital computer implicates
the right to copy.
 Cheap easy software further implicates
the right to make derivative works.

9. What If?

10. You want to:
 Share?
 Remix?
 Build Upon?
 Comment?
 Translate?

11. Then You Have To
ASK
(and hire a lawyer)

12. What if?

13. You could give permission
before to say

14. Enter …

20. Attribution

21. ShareAlike

22. NoDerivatives

23. NonCommercial

27. Three Different Formats

33. RDFa
 Allowsbuilding metadata into XHTML
and other XML documents with attributes.
 <arel=quot;licensequot; href=quot;http://
creativecommons.org/licenses/by/
3.0/quot;>cc</a>
 <a about=quot;/bar.jpgquot; rel=quot;licensequot;
href=quot;http://creativecommons.org/
licenses/by-nc/3.0/quot;>cc</a>

34. ccREL
 ccRELis described in ccREL: The
Creative Commons Rights Expression
Language (pdf), published March 3,
2008.
 ccREL a specification describing how
license information may be described
using RDF and how license information
may be attached to works.

35. XMP
 XMP (Extensible Metadata Platform)
facilitates embedding metadata in files
using a subset of RDF.
 XMP supports embedding metadata in
PDF and many image formats, though
it is designed to support nearly any file
type.

36. Liblicense
 liblicense
provides a straight-forward
way for developers to build license-
aware applications.
 Reads license metadata
 If possible, writes license metadata
 GUI independent

42. Ported Around The World

52. C+

57. Cø