Re: What is the "open web" ?

On 6/3/2013 4:47 PM, Karl Dubost wrote:
> Le 4 juin 2013 à 00:17, Mark Watson a écrit :
>> I think it's clear that the W3C specifications have to be implementable RF. I am talking about the case where those APIs rely (explicitly or effectively) on underlying system capabilities that are not part of the W3C specification.
> Understood. Let's see.
>
> For example the <video> element is used to play a video. The video format is orthogonal to the functionality. People may use things such as H264, ogg/theora, etc. It is an issue because for some developers (opensource and non open), they would not have the money to implement the support for some of the formats, but let's say manageable. W3C is looking for an encumbered format (difficult task).
>
> In the past, the main formats for images were GIF and JPEG. GIF has been an issue when Compuserve started to claim its patent rights. The consequences led small developers (opensource and non open) to abandon the development of their software because they could not pay the license fees. It also led to the creation of PNG (the first W3C spec ever published) to be able to have a format with similar features (non destructive compression, transparency, etc.)
>
> In the system which is being discussing, currently, will it be **usable** by itself and/or in a combination with at least one open counterpart.
>
>
> PS: I will repeat it once again. We spend far too much time debating a system with no consensus, instead of trying to create something that would be compatible with an open Web platform. I usually prefer a choice which enables activities (in the respect of every members of the communities) than something which restricts the majority of the community.
>
+1 to your PS.  In my blog post responses, I heard several people assert 
that they had solutions that did not involve DRM.  Are any of these 
solutions being formally proposed or evaluated?

Received on Monday, 3 June 2013 23:44:00 UTC