Home > All Posts > Individual Post
Post #512

Re: [videoblogging] Re: New Video Blog post from the DNC

By Ryan Shaw | Ryan Shaw <ryanshaw@...> | ryan_b_shaw
August 2, 2004 | Post #512 | Topic #449

Lucas Gonze wrote: > On Mon, 2 Aug 2004, The Dane wrote: > >>--- In videoblogging@yahoogroups.com, Adrian Miles >><adrian.miles@r...> wrote: >> >>> no, the metadata is standard metadata that >>> is in the html page. things like movable >>> type write this automagically, on my site i >>> added a pile of dublin core metadata to >>> boot. google doesn't read qt metadata... >> >> So then, really, there doesn't need to be any media standard so long >> as the surrounding HTML is properly informatory? I hope this is the >> case, because really, I think this is how The Net should be - we >> don't want to artificially stagnate progress on the web by forcing >> an unnatural standard (i.e., one that isn't a de facto standard). > > But once you move the metadata from the QT object to the HTML, you're > using the standard. I just wanted to point out that multimedia search engines do more than look at the surrounding HTML--they also parse the media objects themselves for embedded metadata and do some content analysis. Some formats (WMV for instance) have hundreds of embedded metadata fields defined. Others (Real) have hardly any. Content analysis (things like extracting keyframes, looking at color distributions, etc.) can be very difficult with things like Flash, because instead of a standalone movie file to be analyzed you now have an application in which video is embedded in some non-standard way. Trying to determine where the video is involves decompiling the Flash application and parsing through the source... yuck. I agree that forcing a standard is a bad way to go, *but* there are things to think about beyond image quality and download size. As Lucas has pointed out, the situation now with multimedia on the web is like the text web circa 1995--everyone is concerned with looking slick and isn't really considering things like accessibility, searchability, etc. Anyway, these really *shouldn't* be issues for end-users and content creators to worry about, but until tool-builders get their acts together and worry more about quality of experience and less about things like DRM, they'll have to be in the backs of people's minds. Ryan