Also see these: syndication | resource discovery | formats | Syndication and metadata | Using media rss to syndicate and share media | Media rss media group element | Overview of images in rss | Category:Syndication
In our workflow, we've now uploaded a piece of media, which has been archived, and various multimedia formats have been generated, that now sit on a server. How do I now make this media available through the web?
If my website runs of the same server, then I could just run the website of (say) the same database table that holds the optimised video information. But suppose my website sits on a different server.
The most basic approach is obviously to copy and paste urls by hand, but this clearly isn't sustainable. The rightmost part of the diagram on Multimedia Encoding Workflow concerns making video available via web pages. There are many interesting ways of doing this, including OAIPMH, etc. However, a simple way of getting this done, is RSS. Syndication via RSS and aggregation of RSS is a common way of shuffling information around, and with 'enclosures', media can be attached. An interesting feature of RSS is the possibility for including extra namespaces, and this is how the iTunes additions to RSS with enclosures work. A much less known extra namespace in RSS is media:rss.
Media:rss allows for different versions of the same media file, i.e. multiple enclosures, as well as 'media groups'. However, the basic feed is just an rss feed with extra enclosures. The MediaPlayer project works like this: The MediaPlayer doesn't actually host any video or audio, but simply draws on information made available through a media:rss feed, generated from a central 'media:rss server'. Other websites draw on feeds from the same server to generate their listings. For instance, look at the video elsewhere tab on the mediaplayer site: http://mediaplayer.group.cam.ac.uk/main/Mini-Sites.html
For further discussion of this, see some of my podcasts.