W3C home > Mailing lists > Public > public-html@w3.org > June 2009

Re: Why Design Principles?

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 3 Jun 2009 19:38:37 -0700
Message-ID: <63df84f0906031938l4e0b1e65g95fc9273ba40c7ec@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: HTML WG <public-html@w3.org>
On Wed, Jun 3, 2009 at 7:34 PM, Jonas Sicking <jonas@sicking.cc> wrote:
> On Tue, Jun 2, 2009 at 2:54 PM, Maciej Stachowiak <mjs@apple.com> wrote:
>>
>> Ian and Anne both suggested that I should add most of this justification to
>> the Design Principles document itself. I will likely replace the current
>> abstract and introduction with something based on this email. I suggest that
>> those with an interest in the Design Principles should voice their
>> objections to this plan.
>>
>> There are also some suggested additions and removals of principles at the
>> end.
>
> I would love it if we had a design principle that described the fact
> that we're writing the spec to support the authors that tests their
> pages by running them in a browser, rather than by checking that they
> comply with the spec.
>
> See a more detailed description in [1], but the short of it is that we
> are generally avoiding leaving things explicitly or implicitly
> undefined and hoping that authors won't rely on it. Instead we are
> trying to define things in great detail to increase the chances that a
> HTML document that works in one complying HTML UA, will also work in
> another.

Doh! Just realized that this is exactly what principle 4.1 is. I'll
see if I can come up with wording to make it stronger.

/ Jonas
Received on Thursday, 4 June 2009 02:39:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:38 GMT