W3C home > Mailing lists > Public > public-device-apis@w3.org > April 2010

Re: Interesting notes on designing Web standards

From: Ricardo Varela <phobeo@gmail.com>
Date: Fri, 16 Apr 2010 16:40:48 +0100
Message-ID: <y2sbfbd93661004160840m901ec082sb0cd2d73a59ddf86@mail.gmail.com>
To: Robin Berjon <robin@berjon.com>
Cc: public-device-apis@w3.org
Thanks for the notes, Robin! My favourite is "Implement First.
Standards created in a vacuum are usually bad"

But even more interesting is the note for "authors haven't read HTML4"

For me, API design goes hand in hand with testing. Most people are not
going to read the specs, ever. Most designs will never cover all
corner cases, ever. But forcing you to write tests to your API puts
you in the point of view of the implementer (good) and at the same
time provides something to the implementer that allows them to test if
they are done EVEN if they have never read the specs (double good)

I think we have to strengthen up the position of producing tests
alongside with the specifications, even in early phases. Now, I
realize it may be a question of getting people to help (if we don't
have editors, even less test writers) but for this specific item,
maybe we could leverage some help from the OEMs and other "early



On Fri, Apr 16, 2010 at 4:15 PM, Robin Berjon <robin@berjon.com> wrote:
> Hi,
> I thought that these notes were quite interesting, especially the slides:
>  http://weblogs.mozillazine.org/roc/archives/2010/04/api_design_for.html
>  http://weblogs.mozillazine.org/roc/images/APIDesignForTheMasses.pdf
> It's a good overview of how designing Web standards is not like designing APIs the old way.
> --
> Robin Berjon - http://berjon.com/

Ricardo Varela  -  http://phobeo.com  -  http://twitter.com/phobeo
"Though this be madness, yet there's method in 't"
Received on Sunday, 18 April 2010 21:38:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:19 UTC