On 7/29/07, Andy <[EMAIL PROTECTED]> wrote: > That would actually be the same issue. No iPlayer client existed when > the BBC started the project. They created it. The BBC claim (possible > incorrectly) that there exists no cross platform DRM solution, and yet > they never considered creating it. If you find no adequate solution to > your problem then most people would _at least_ consider the 2 options > that all such projects have of coping with this problem. > 1. Develop it yourself (in house so to speak). > 2. Pay someone else to develop it for you.
Options 3, Buy an off the shelf solution and use it. Bonus points if the people whose content your licensing are happy with it and will endemnify you against someone cracking it. > > "At the time, the only two solutions deployed at scale on the internet > > were Microsoft's DRM, and Apple's Fairplay DRM. Fairplay did not > > include the ability to expire content, and therefore could not meet > > the minimum requirements for our rights at all." > > As above, if there is no adequate solution, you develop your own! > > Why is this _so_ difficult? > All you really need is a format for describing restrictions (how about > something based on XML) and some kind of cryptographic system. "If you think cryptography will solve your problem, you don't know anything about cryptography, and you don't understand your problem." Given we all know DRM's broken, yet is mandated by the people who own the content, what's better for the BBC to do? Write it's own and be responsible for fixing any breakages, or use one the content providers are happy with? Mike - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
