Skip to Content.
Sympa Menu

cc-metadata - Re: draft document on CC metadata in SMIL

cc-metadata AT lists.ibiblio.org

Subject: discussion of the Creative Commons Metadata work

List archive

Chronological Thread  
  • From: Mike Linksvayer <ml AT creativecommons.org>
  • To: cc-metadata AT lists.ibiblio.org
  • Subject: Re: draft document on CC metadata in SMIL
  • Date: Wed, 29 Oct 2003 13:14:11 -0800

Lucas Gonze wrote:
> <smil>
> <head>
> <metadata id="meta-rdf">

I guess you didn't need the skip-over attribute because you put <metadata> as a child of <head>?

xmlns:rdfs = "http://www.w3.org/TR/1999/PR-rdf-schema-19990303#";

http://www.w3.org/2000/01/rdf-schema#

xmlns:dc = "http://purl.org/metadata/dublin_core#";

http://purl.org/dc/elements/1.1/

(the smil2.0 metadata example is a bit outdated)

<!-- Question: what is this namespace URL? Shouldn't the
namespace URL for SMIL metadata be something real? -->
xmlns:smilmetadata = "http://www.example.org/AudioVideo/.../smil-ns#"; >

I'd say chuck it. It is only used in the smil2.0 metadata example, nowhere else AFAIK, CC has no requirement for it, and the use in the example is kind of silly -- for the most part it duplicates information in the actual SMIL directives.

<!-- Value of rdf:about attribute should be the URI of your playlist -->
<Work rdf:about="http://www.example.com/smil-cc.smil";>

<!-- The name of your playlist. --->
<dc:title>SMIL CC</dc:title>
<dc:description>An example of how to apply Creative Commons metadata to SMIL resources.</dc:description>

<dc:creator>
<Agent>
<dc:title>Yo-Yo Dyne</dc:title>
</Agent>
</dc:creator>

<dc:rights>
<Agent>
<dc:title>Gnomophone</dc:title>
</Agent>
</dc:rights>

<dc:date>1842</dc:date>

<!-- Mime type of SMIL is application/smil, not text/smil as given in the SMIL recommendation! -->
<dc:format>application/smil</dc:format>

<!-- If your playlist is derived from any others, put the
URL here. Please preserve dc:source elements from
source SMIL files. Put additions at the top of the
list of dc:source elements, so that they are ordered
from newest to oldest. -->
<dc:source>http://example.com/a_prior_smil_resource.smil</dc:source>
<dc:source>http://example.com/value_of_dc:source_in_the_above.smil</ dc:source>

<license rdf:resource="http://creativecommons.org/licenses/by-nd-nc/1.0/"; />
</Work>

One person commented to me along the lines of "what's the point of licensing a playlist/can a list of tracks even be copyrighted". I think it is key to point out as a motivating factor someplace in the document that SMIL can do much more than simple playlists. The first term that comes to me is client-side remixing, but maybe someone can think of a cooler phrase.

However, the individual components of a SMIL playlist most certainly are copyrightable, and the example needs to demonstrate how SMIL metadata can denote the license each component is under, e.g.,

<Work rdf:about="http://example.com/mp3/first.mp3";>
<license rdf:resource="http://creativecommons.org/licenses/publicdomain/";>
</Work>

Otherwise it looks great.

--
Mike Linksvayer
http://creativecommons.org/learn/aboutus/people#21





Archive powered by MHonArc 2.6.24.

Top of Page