In Mark Wood's last message, he stated that > We need to examine the different codec bundles > provided by the browsers that implement these elements at all. (Do we > provide multiple encodings, or point to add-on codec packages, or some > of each, or...?) This stuff will affect and be affected by our sites' > acceptable-formats policies.
I think the point about multiple encodings is especially important to discuss. At this point that both Firefox 3.5 and Google Chrome support the Theora codec natively, but no one knows what Opera, Apple, and Microsoft will eventually do with their browsers. One current framework that's helping extend the use of the video tag is Video for Everybody! (http://camendesign.com/code/video_for_everybody). The usability approach taken by the framework's programmers relies on having two bitstreams, one created using the patent-encumbered H.264 codec, and another created using the open video codec, theora. On a side note, use of the H.264 codec could become really pricey by 2011, when the MPEG LA begins enforcing licensing fees. Personally, I hate the idea of having multiple encodings for accessibility purposes, primarily because video is already a space hog. But I also think we need to save the time of the reader (in this case, watcher), and if multiple encodings can help that cause, it's worth considering. Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary3 jfow...@sbts.edu ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
