Kosso's podcast.com seems to get away with plain old OPML...
http://my.podcast.com/kosso/opml/

He's a friend of this list[1] so may be happy to help.

Other options are the emerging RDF programme ontology (ask Michael
Smethurst whether he's willing to announce the URL yet, I'm not going to
spoil his fun!), or even Media RSS itself might be able to do it

Or perhaps we could make one of these formats work with a custom
extension element or two? As you all know, when it comes to XML schemas,
wheel reinventing is highly frowned upon...

Brendan.
[1] Well maybe he's sort of the list's strange uncle who tells odd
stories at Christmas, but we love him anyway :-)

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Philip
Miller
Sent: 04 December 2007 16:11
To: [email protected]
Subject: RE: [backstage-developer] BBC Podcasts (sorry no OGG)

Schema is here: http://downloads.bbc.co.uk/podcasts/ppg.xsd

Some background: we use this format to move data around internally
within the podcast publishing application. We examined other available
formats - OPML/TV-A/etc, but none seem to fit our requirements.

You can see that this is designed as a program guide sort of thing and
includes a lot of BBC-specific information. You could use it to build an
iTunes-style feed browser for BBC content.

Is it a useful data set? Is it just XML soup? As Carlos said, feedback
is appreciated.


--
Phil Miller
Technical Lead, Media Services
BBC News Interactive
[EMAIL PROTECTED]
+44 7799 894180



> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Carlos Roman
> Sent: 04 December 2007 14:56
> To: [email protected]
> Subject: [backstage-developer] BBC Podcasts (sorry no OGG)
> 
> 
> Figured rather than using the other list this might be the 
> best place to ask/show a Podcast feed. Figured it might get 
> derailed like the last discussion on Podcasts.
> 
> Anyway, at the moment got a very early version of a directory 
> listing for all BBC Podcasts, which can be found here:
> http://downloads.bbc.co.uk/podcasts/ppg.xml
> 
> What am looking for is some feed back on this really, and 
> possibly what people would like to see included in here.
> 
> The current version on live is missing an "rssenc" element 
> which would give information about the files in a Podcast. 
> This is element would work as follows:
> <rssenc 
>  
> type="audio/mpeg|audio/x-m4a|video/mp4|video/x-m4v|video/quick
> time|appli
> cation/pdf"
>     medium="image|audio|video|document|executable" 
>     stream="true|false"
>     audioEnc="mp3|wma|acc"
>     audioProfile="ABR|CBR|VBR"
>     videoEnc="x264|mpeg4|mpg2|mpg1|wvc1|..."
>     videoProfile="ABR|CBR|VBR"
> />
> 
> So, for a typical MP3 Podcast it would be:
> <rssenc type="audio/mpeg" medium="audio" stream="false" audioEnc="mp3"
> audioProfile="CBR" />
> 
> For AAC Enhanced Podcast:
> <rssenc type="audio/x-m4a" medium="audio" stream="false" 
> audioEnc="aac"
> audioProfile="VBR" />
> 
> What I would like to also add for the next version (apart 
> from the "rssenc" element) is information on the current 
> episode in the Podcast (if there is one). This would mean you 
> wouldn't have to parse every RSS feed to find those with an 
> episode (or to find the current episode). The original idea 
> was to just use the "link" element I already have but extend 
> it so that it has optional elements "title", "description" 
> and "pubDate". This would produce something like this:
> 
> <link target="currentEpisode"
> url="http://downloads.bbc.co.uk/podcasts/radio4/archers/archer
> s_20071018
> -1920.mp3">
>       <title>Archers: Thursday 18 Oct 07</title>
>       <description>Jazzer gives Ed some words of advice, and 
> Lynda receives a surprise visitor at Ambridge Hall.</description>
>       <pubDate>Thu, 18 Oct 2007 19:20:00 +0000</pubDate> </link>
> 
> Only thing I don't like about this (hence part of the reason for this
> post) is that it doesn't seem (to me) to appear to be in the 
> correct place. The good thing about this is that it keeps 
> everything consistent with the schema we have. The bad/ugly 
> is that the information about the encoded file is not 
> included in the "link" element. Personally think it should be 
> moved inside the "rssenc" element, but wondering if there is 
> any opinions about this and where it should probably be found?
> 
> Again, feed back on this feed would be most appreciated. 
> Also, please remember this is a first version and so there is 
> a good chance that it will change as it evolves.
> 
> 
> - Carlos Roman
> 
> P.S.
> 
> Sorry if this arrives twice, thought I had signed up to this 
> list but turns I hadn't so re-subscribed and sent this again.
> 
> -
> Sent via the backstage.bbc.co.uk developer discussion group.  
> To unsubscribe, please send an email to 
> [EMAIL PROTECTED] with  unsubscribe 
> backstage-developer [your email] as the message.
> 

-
Sent via the backstage.bbc.co.uk developer discussion group.  To
unsubscribe, please send an email to [EMAIL PROTECTED] with
unsubscribe backstage-developer [your email] as the message.

-
Sent via the backstage.bbc.co.uk developer discussion group.  To unsubscribe, 
please send an email to [EMAIL PROTECTED] with  unsubscribe backstage-developer 
[your email] as the message.

Reply via email to