Open Video And Metadata Presentation

C Open Video & Metadata Fred Benenson Open Video Conference, June 20th 2009 fred@creativecommons.org Product Manager, Creative Commons Saturday, June 20, 2009

What is C? We’re a 501c3 corporation headquartered in San Francisco with 30 employees around the world. We’rea non-proﬁt. We do not offer legal services per se. We offer free legal and technology tools that allow creators to publish their works on more ﬂexible terms than standard copyright. Terms that allow public sharing, reuse, and remix. Saturday, June 20, 2009

Why do we do what we do? Saturday, June 20, 2009

Two Reasons Saturday, June 20, 2009

#1 Saturday, June 20, 2009

Analog Media Uses Implicating All © Law Possible Uses of a Work Fair Uses Saturday, June 20, 2009

Digital Media Uses Implicating © Law All Fair Uses Possible Uses of a Work* *Where every use is a copy. Saturday, June 20, 2009

#2 Saturday, June 20, 2009

The State of the Commons Prior to 2002 Public Domain Default Automatic © All Rights Reserved No Rights Reserved Orphan Works Pre-1923 works, Federal Everything from Dinsey ﬁlms Government Works, etc. to your notes, to most of the web. Saturday, June 20, 2009

Introducing: C No Rights Reserved Some Rights Reserved All Rights Reserved Orphan Works Pre-1923 works, Federal Government Works, etc. Everything from Dinsey ﬁlms c to your notes, to most of the web. Saturday, June 20, 2009

What does C actually do? Saturday, June 20, 2009

Saturday, June 20, 2009

Attribution Saturday, June 20, 2009

ShareAlike Saturday, June 20, 2009

NoDerivatives Saturday, June 20, 2009

NonCommercial Saturday, June 20, 2009

Three Different Formats Saturday, June 20, 2009

Some Considerations Public licenses are irrevocable and perpetual However works can be removed from public and their licenses can be changed CC licenses are non-exclusive Dual licensing Creative Commons licenses do not preclude fair uses, fair dealing, etc. Saturday, June 20, 2009

Semantic Web Metadata (RDF, RDFa) Saturday, June 20, 2009

“The Resource Description Framework (RDF) is a family of World Wide Web Consortium (W3C) speciﬁcations originally designed as a metadata data model. It has come to be used as a general method for conceptual description or modeling of information that is implemented in web resources; using a variety of syntax formats.” - Wikipedia Saturday, June 20, 2009

“[Simple] Wikipedia does not yet have an article with this name.” - Simple Wikipedia Saturday, June 20, 2009

RDF, Really “Triple” statements. <Fred> <is giving> <a talk on RDF>. <This work> <is licensed> <under CC BY>. Serialized XML ﬁle Like RSS, sort of. Vocabularies to describe anything Using URIs Some Microformats are RDF, but not all. Saturday, June 20, 2009

RDFa The “a” is for “attribute” Using XHTML meta and link attributes. A good compromise with the goals of Microformats Now a W3C Recommendation ccREL is expressed in RDFa Google, Yahoo, MySpace, Digg, etc. Saturday, June 20, 2009

<a rel="license" href="http://creativecommons.org/licenses/by/3.0/us/"> <img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by/3.0/us/88x31.png" /></a> RDFa FAQ by <a xmlns:cc="http://creativecommons.org/ns#" href="www.example.com" property="cc:attributionName" rel="cc:attributionURL">John Doe</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/3.0/us/">Creative Commons Attribution 3.0 United States License</a>. Based on a work at <a xmlns:dc="http://purl.org/dc/terms/1.1/" href="http:// wiki.creativecommons.org/RDFa" rel="dc:source">wiki.creativecommons.org</a>. Permissions beyond the scope of this license may be available at <a xmlns:cc="http://creativecommons.org/ns#" href="http://moreperms" rel="cc:morePermissions">http://moreperms</a>. Saturday, June 20, 2009

dc:title/dc:type RDFa FAQ  dc is Dublin Core  Title, Author, Type, etc.  The inner HTML of the tag is “RDFa FAQ” which is the title of the work.  This is a text document, so we point dc:type to the Dublin Core deﬁnition for "Text" using the rel tag.  Another document Type that could be speciﬁed with the href is http:// purl.org/dc/dcmitype/StillImage or http://purl.org/dc/dcmitype/Sound, depending on the medium being licensed. Saturday, June 20, 2009

cc:attributionName/cc:attributionURL <a xmlns:cc="http://creativecommons.org/ns#" href="http://www.example.com" property="cc:attributionName" rel="cc:attributionURL">John Doe</a>  CC is using its own XML namespace, abbreviated using cc:  The property is CC's AttributionName attribute, the value is the content inside the anchor tag (in this case, the ﬁctitious John Doe), and a relationship of cc:AttributionURL is deﬁned as being http:// www.example.com. Saturday, June 20, 2009

rel="license" <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/us/"> Creative Commons Attribution-Share Alike 3.0 United States License</a>.  Most basic and fundamental part of CC's usage of RDFa  Always included in the HTML offered, regardless of whether users ﬁll out the "Additional Information" section.  The rel speciﬁes the relationship of the href's URL. In this case, the relationship is "license" and the URL is a standard Creative Commons license. Saturday, June 20, 2009

dc:source Based on a work at <a xmlns:dc="http://purl.org/dc//" href="http://wiki.creativecommons.org/RDFa" rel="dc:source"> wiki.creativecommons.org</a>  Similar to dc:title, dc:source speciﬁes where the original source of the ﬁle is located.  Flickr does this and its awesome.  In this case it is pointing to http://wiki.creativecommons.org/RDFa  Saturday, June 20, 2009

cc:morePermissions Permissions beyond the scope of this license may be available at <a xmlns:cc="http://creativecommons.org/ns#" href="http://moreperms" rel="cc:morePermissions">http://moreperms</a>.  Part of the CC+ protocol, creators can specify a URL where re-users of CC licenses can obtain more rights to the work.  Here, the nonexistent URL of http://moreperms is used as a placeholder. Saturday, June 20, 2009

File Metadata (XMP, Ogg, etc.) Saturday, June 20, 2009

liblicense  Low-level license metadata integration for applications.  Features:  Extract and write license information for files  Supports enumeration of available licenses  Wraps internationalized license information for Creative Commons licenses  Bindings for dynamic languages (currently Python and Ruby)  Extensible support for file types using module system  No specific GUI library dependency allows applications to build the graphical chooser most appropriate for their platform.  FLAC, MP3, XMP, Ogg, GSF. Saturday, June 20, 2009

License Tagger Demo App Saturday, June 20, 2009

ffmpeg2theora $> ffmpeg2theora -a 3 -v 7 --pp de,tn:256:512:1024 --artist "Fred Benenson" --title "RDFa Video" --date "June 2009" --location "NY, NY" --organization "Creative Commons (http://www.creativecommons.org)" --copyright "Copyright 2009, Fred Benenson" --license "Creative Commons Attribution-ShareAlike 3.0" -o video.ogv video.dv  Ogg Theora supports a license ﬁeld as well as other metadata.  VLC can expose it. Saturday, June 20, 2009

Standardized Assets Saturday, June 20, 2009

Help?! Saturday, June 20, 2009

How C Uses Open Video & Metadata Saturday, June 20, 2009

Try Ogg Player Fall Back to Flash Player <video src="http://player.uncensoredinterview.com/e/11222.ogv" controls width="384" height="216"> <object type="application/x-shockwave-flash" width="384" height="216" data="http://player.uncensoredinterview.com/e/11222.swf"> <param name="movie" value="http://player.uncensoredinterview.com/e/ 11222.swf"></param><param name="allowfullscreen" value="true"></param> </object> </video>  Firefox 3.5, Chrome natively supports Ogg + <video> within HTML5  Safari, IE? Anyone?  Push to default YouTube to OGV instead of H.264  No good excuse from Google. Saturday, June 20, 2009

Open Video And Metadata Presentation

0 comments

Notes on slide 1

2 Favorites