Ok, not a good situation. Like I said before, all it really takes to
get something started here is enough interest from a community of folks
willing to do the work and implement support. Assuming we have that, we
need to start documenting some requirements.
Grouping:
The ability to group alternative representations of the same content.
For instance, video may be encoded as wmv, mov, mpg, etc. We need
the ability to specify a single default representation
Generic content metadata:
Every piece of content has general metadata applicable to all
alternate representations. These include title, description,
rating, keywords, categorization, copyright, license, credits,
captioning, lyrics, distribution restrictions, etc.
Media specific metadata:
Each media resource has metadata specific to the media type. We need
the ability to express the appropriate metadata for each resource.
This metadata may vary across alternative representations of the same
content.
These include things like the url, file size, type, medium, bit rate,
frame rate, sampling rate, channels, duration, display dimensions,
language, hash, software,
Previews:
The ability to specify a content preview such as a thumbnail, a
shortened video snippet, a transcript, etc. Previews may be offered
in multiple formats.
If there's anything missing from this, please respond and help fill in
the gaps.
Once we have the requirements documented, we might as well start
knocking around a straw man...
<feed xmlns="http://www.w3.org/2005/Atom";>
...
<entry>
<id>tag:example.org,2008:/shows</id>
<title>My Dog's Wedding</title>
<updated>2008-12-12T12:12:12Z</updated>
<published>2008-12-12T12:12:12Z</published>
<x:expires>2007-12-13T12:12:12Z</x:expires>
<author>
<name>James</name>
</author>
<summary>My dog got married the other day</summary>
<category scheme="http://example.org/rating/simple";
term="nonadult" />
<category scheme="http://example.org/rating/mpaa";
term="pg" />
<category scheme="http://example.org/keywords";
term="dog" />
<category scheme="http://example.org/keywords";
term="wedding" />
<category scheme="http://example.org/category";
term="videos/personal/events/weddings/dog" />
<category scheme="http://example.org/restriction/country/allow";
term="au us" />
<category scheme="http://example.org/restriction/country/deny";
term="ca fr" />
<rights>Copyright (c) 2008 James</right>
<link rel="license"
href="http://www.creativecommons.org/licenses/by-nc/1.0"; />
<x:person scheme="http://example.org/roles"; term="director">
<name>Linda</name>
</x:person>
<x:person scheme="http://example.org/roles"; term="cameraoperator"
<name>Joe</name>
</x:person>
<x:person scheme="http://example.org/roles"; term="actor">
<name>The Dog</name>
</x:person>
<x:text type="html"
start="00:00:02.000"
end="00:00:10.000"><i>...</i></x:text>
<x:text type="html"
start="00:00:15.000"
end="00:01:00.000"><i>...</i></x:text>
<content src="#mpeg type="video/quicktime" />
<link x:id="mov"
rel="enclosure"
type="video/quicktime"
title="Dog's Wedding (quicktime)"
size="1234567890"
href="dogwedding.mov">
<x:hash algorithm="http://www.w3.org/2001/04/xmldsig-more#md5";>
...
</x:hash>
<x:bitrate>...</x:bitrate>
<x:framerate>...</x:framerate>
...
</link>
<link x:id="mpeg"
rel="enclosure"
type="video/mp4"
title="Dog's Wedding (mpeg)"
size="1234567890"
href="dogwedding.mpeg">
<x:hash algorithm="http://www.w3.org/2001/04/xmldsig-more#md5";>
...
</x:hash>
<x:bitrate>...</x:bitrate>
<x:framerate>...</x:framerate>
...
</link>
<link rel="http://example.org/preview";
type="video/mp4"
title="Preview of the Dog's Wedding (mpeg)"
size="12345"
href="dogwedding_preview.mpeg">
<x:hash algorithm="http://www.w3.org/2001/04/xmldsig-more#md5";>
...
</x:hash>
<x:bitrate>...</x:bitrate>
<x:framerate>...</x:framerate>
...
</link>
<link rel="http://example.org/preview";
type="image/jpg"
title="Screencap from the wedding"
size="12345"
href="dogwedding1.jpg">
<x:hash algorithm="http://www.w3.org/2001/04/xmldsig-more#md5";>
...
</x:hash>
</link>
<link rel="http://example.org/preview";
type="image/jpg"
title="Screencap from the wedding"
size="12345"
href="dogwedding2.jpg">
<x:hash algorithm="http://www.w3.org/2001/04/xmldsig-more#md5";>
...
</x:hash>
</link>
</entry>
</feed>
Is this better or worse than the yahoo/itunes approaches? Why? Does it
make more sense to use a more iterative approach building from either
the yahoo or itunes schemas? What are the other possible approaches?
- James
Ryan Parman wrote:
Correct. David Hall is no longer with Yahoo, and charge over the spec
has fallen to Jeremy Zadowny. Unfortunately, Jeremy has pretty much
ignored all requests to fix the spec, so we've got past and present
versions of the spec with different namespaces.
Yay.
=========================================
Ryan Parman
Creator and Co-Developer
SimplePie
http://simplepie.org
On Jan 23, 2008, at 1:15 PM, James Holderness wrote:
Karl Dubost wrote:
* Apple - Last Change: no date :/
http://www.apple.com/itunes/store/podcaststechspecs.html#rss
<rss xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd";
version="2.0">
I believe that is correct.
* Yahoo - Last Change: 2005-10-22 ?
http://search.yahoo.com/mrss
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss";>
That is what the current spec says, but that's not correct. There's an
official acknowledgement of the mistake here:
http://tech.groups.yahoo.com/group/rss-media/message/1008
Regards
James
