WebPlatform Browser Support Info

Hi all,

A lot has been said over the past couple of emails, I've collected it 
all, and here are my reactions:

The data-exchange-format we use to transfer data is separated from the 
API that will be exposed in the end. I feel the data-exchange itself 
should be as accurate as possible, for, like Doug mentioned, it is 
possible to trim down layers, while we cannot add layers of accuracy.
This goes especially for test-results: A test is run on a specific 
build of a UA on a specific OS (or firmware). Even though we as humans 
might have the knowledge that that very test-result can be extrapolated 
to other builds of the browser, or the same build of the browser on a 
different OS or different platform, does not mean that that other build 
has been actually tested. Therefore, scientifically speaking, a 
test-result for that other build is non-existent, and thus should not be 
in the data-exchange.
Moreover: even though until now a test-result on build X means the 
feature will also work on build Y, doesn't mean this will hold true in 
the future. So, if the decision is made to collapse test-results in the 
data-exchange, you can never accommodate for such an event, unless you 
mark it up in a note with the test-result.
To conclude: I strongly feel that test-results should really be about 
the specific version/build of a UA, where parties displaying that 
information can choose for themselves whether or not to extrapolate that 
data to other builds/versions. We should not decide that for them.


I like the idea to use the URL's as opposed to UUID's. They are indeed 
more readable, plus the instantly provide a link to more information. 
However, we have to make sure the URL's stay the same. I noticed Doug 
was using the 'data'-subdomain on webplatform for this, a subdomain that 
doesn't currently exist. If everyone agrees, I think that could make for 
a good solution, since the URL's on data.webplatform.org could always 
stay the same, those URL's just redirect to the appropriate page, which 
could either be the latest spec of the feature at W3C, a description of 
the test at a test-source, or any other URL on the web. Those redirects 
are then allowed to change, but we can keep the URL's on 
data.webplatform.org the same, and thus provide a unique identifier.




For now the focus is on combining the data from several sources 
(quirksmode, html5test, mobilehtml5, caniuse) to provide as broad and 
accurate as possible test-results. Once that has been set-up, the intent 
has been to provide an interface for users of webplatform to add missing 
data. So yes, those plans have been made, they are just a different 
milestone.

I'll be making changes to the draft based on the ideas and remarks 
offered, and everything I said above. I will then put it up on github so 
you can fork and pull like there's no tomorrow ;)


Ronald

Received on Saturday, 19 October 2013 10:16:21 UTC