Originally posted by d000hg
View Post
As CUK is a commercial operation those Ts and Cs don't apply (unless expressly permitted in writing, etc.)
On to the technical stuff:
That's pretty much the code the YouTube embedding produces on CUK, but YouTube has straightforward identifiers in its URLs; the BBC's setup doesn't make it so easy as yet, though not for want of wanting to.
I haven't really looked into the vB video embedding code too much (although I'm keen on the idea of getting HTML5 video working, if only for my own sake) but it is in principle possible to use a BBC page URL to establish the necessary identifier for the iPlayer content and embed it; there's the fact that (I think) the Beeb sometimes have more than one video on a page to contend with, but if we're just talking video pages then in principle the UI could cope with that. It might even be possible to hook into the existing video embed code and accept pasted stuff like that above and make something useful of it. If admin thinks it's worthwhile, I can dig deeper and see what might be possible
About the BBC using iPlayer more: that's really to do with the transition from their old and unbelievably wretched RealPlayer/WMP embedded (or usually popup) player to the Flash based one that also powers iPlayer online and the Adobe AIR app (a wrapper around Flash) that is iPlayer Desktop. It's the same technology, but different uses thereof have different branding and licensing: you can embed a BBC News clip with a decent expectation of it staying there, but if you embed last week's Doctor Who it'll vanish shortly. I'm not sure how this might complicate (or even simplify) things without looking into it further.
FWIW, the BBC took a lot of flak over sticking with the RealPlayer garbage for so long, but I know some people on the iPlayer dev team, and it wasn't really the Beeb's fault. One of the fundamental problems they face is the way BBC expenditure is controlled in relation to Government decisions about the licence fee. When they see the need to switch to a new and better technology for an existing service (such as news clips) they often aren't allowed to do so because the terms of some previous agreement with the Government require them to continue to use the technology in place at the time. This even went to the level of basic HTML templating: they used unbelievably recondite SSI (server-side include) techniques that the rest of the world abandoned in the late 90s until very recently, because Government rules wouldn't allow them to do so much as stick something totally free like PHP on a server and use that instead, even though there would have been a massive cost saving in terms of developer effort. Investment in new technology, even free-as-in-beer technology, was simply forbidden by terms drafted by civil servants in the days before anybody had ever even seen a URL on a TV ad. Meanwhile, newer services were able to do useful stuff with XSLT and such, but even when they created something awesome it could only be used for things that were totally new, not to improve stuff that already existed, even if the people doing it all worked in the same office. It's crazy, and it's not the BBC's fault: it's the rules imposed by civil servants who have probably only just recovered from the shock of seeing their secretary's typewriter replaced with a new-fangled thing that looks like a television.
<nostalgia>I remember the first time something I'd done had its URL on both a telly advert and a poster campaign in 1997...</nostalgia>
Leave a comment: