>> An example: >> 1. An MP3 codec will not be part of the core components of MeeGo (not >> open-source, licensing...) (correct?). >> 2. All commercial devices out there will have an MP3 codec pre-installed, >> even though MP3 is not a required MeeGo package. >> 3. The compliancy-requirement thus requires a software developer that needs >> MP3 functionality to licence an MP3 codec, even though it is already on all >> target systems? >> This is a huge cost for a small ISV...
>applications tend to want "audio playback" capability , not Mp3 specific. >if it's for media that comes with the app, the app is better off using >ogg anyway Sure, but not in 100% of the cases. Listening to Internet based radio station is one example. Almost all of them are MP3 based and you can't choose your codec. Anyway, this was just an example. There might be other similar things with other vital closed source components. Do every application that depends on Air need to licence/redistribute Air (if you need to licence this to redistribute it)? Potentially the same with Silverlight? I don't expect these two to be part of the compliancy stack either.... Just some examples, Im sure there are more examples out there. We should just be aware of the potential effects. Thanks, /Jonas ---------------------------------------------------------------------- Intel Sweden AB Registered Office: Knarrarnasgatan 15, 164 40 Kista, Stockholm, Sweden Registration Number: 556189-6027 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
