[Fwd: [W3C Blog] New Comment Added to 'Web Compatibility Test strikes back']

Hi,

Someone commented on the blog that they would like more details on why
we picked some technologies rather than others in the new Web
Compatibility Test; we had some explanations in the manifesto of the
previous test, so having a similar document for the new one would be
useful.

Is anyone interested in taking a first stab at documenting this?

Dom

-------- Message transféré --------
From: dret@...
> À: dom@w3.org
> Sujet: [W3C Blog] New Comment Added to 'Web Compatibility Test strikes
> back'
> Date: Tue, 23 Feb 2010 18:40:06 +0000
> 
> A comment has been posted on your blog W3C Blog, for entry #8726 (Web Compatibility Test strikes back).
> 
> who is deciding what goes into those test suites and what doesn't? i
> don't want to criticize this test's utility as a tool, but i am
> definitely curious to understand why this specific set of tests made it
> into the test. there is an infinite number of ways how you could choose
> and combine tests to come up with a some score in a "browser test", and
> unless there is some explanation as to why the test is doing what it is
> doing now, it seems a bit random to me. the blog entry itself says "the
> choice of the tested technologies is somewhat arbitrary", but i sure
> hope it's not completely random, so explaining at least a bit why the
> test has been designed this way would be very useful.

Received on Wednesday, 24 February 2010 08:11:54 UTC