In our strive to make it utmost convenient for our customers to use Web Playlists, we are considering another feature. In my last post I discussed the option of being able to configure the output format for Web Playlists and use open standards like ATOM as possible output in addition to ASX today. We are actually thinking of allowing you to add a XSLT and then be able to configure the output format of your choice that way.
Continuing on the same lines I wanted to explore the option of a standard input format this time. Today we use POX. While this works, it has the problems of not being understood by other media servers and honestly you have to learn a new format. The idea we have now is to use SMIL as an input format. Windows Media Services already understands the SMIL input for Server-side Playlists and so do many other media server platforms. For this release, we are exploring supporting only a sub-set of SMIL modules- SMIL Structure, Media Object (audio,video and ref) and Metainformation modules.
Here is an example of the SMIL playlist would look like. We haven't closed on this yet and would love to hear any inputs you might have here (the example uses SMIL 2.1 but it would really work with SMIL 2.0 or SMIL 3.0 too)
<!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 2.1//EN" "http://www.w3.org/2005/SMIL21/SMIL21.dtd"> <smil xmlns="http://www.w3.org/2005/SMIL21/Language"> <head> <meta name="title" content="Web Playlists Sample"/> <meta name="author" content="IIS.net"/> <meta name="copyright" content="(c)2008 Microsoft Corporation"/> <meta name="timeToLive" content="1440"/> <meta name="inactivityTimeout" content="120"/> </head> <body> <ref src="a.wmv" > <param name="canSkipForward" value="true" /> <param name="canSkipBack" value="true" /> <param name="canSeek" value="true" /> </ref> </body> </smil>
How do you feel about this change? We would love to hear from you.