How can we best serve you media XML?
We're just a few weeks into 2006 and already it's clear to most that one of this year's hot topics will be the maturation of services that deliver video over IP. Google's is surely just the first of many important announcements for this year.
2006 is of course also the year .
Meanwhile, in the backstage broom-cupboard, we've been thinking about how we can best serve you XML feeds of 91Èȱ¬ video content (well, feeds that link to and describe 91Èȱ¬ video content, to be pedantic).
91Èȱ¬ News already offers a set of RSS feeds for their 91Èȱ¬ New Player video service. However, these feeds contain links to pages that contain an embedded player, rather than links to the media assets themselves. Whilst this makes sense as a consumer-orientated service, clearly this does not help backstage developers who want to develop new propositions directly around these video items.
So we'd like to know how we can serve you developer-friendly XML feeds about our video. We're going to create some developer feeds which contain links directly to the media, but there are a number of format options floating about and we want to find out which option would work best for the backstage community.
Are you a big fan of the ? Or maybe you would just prefer ? Are there any other options we have missed?
At the moment, I'm personally persuaded by MediaRSS. In most instances, for each of our videos we need to reflect:
- Multiple encoding formats
- Multiple encoding bit-rates
- Whether they are available to all or just UK-based IP's
MediaRSS allows you to do all of that. But what I'd like to know is how easy it is for you to handle? Is there a MediaRSS parser available for your favourite language?
What if we offered enclosures instead? How would you like to see the above information represented within enclosure tagged RSS2.0 feeds?
So, please let me know what your thoughts are on the above - either by leaving your comment below or (do subscribe if you havn't already)!
Many thanks
Ben
Comments