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

Re: algorithmic normative conformance requirements, design principles, etc.

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 25 May 2009 19:56:53 -0700
Cc: HTML WG <public-html@w3.org>
Message-id: <D4370B41-7936-4CB4-9863-9A6E60CB42F5@apple.com>
To: Larry Masinter <masinter@adobe.com>
Hi Larry,

On May 25, 2009, at 11:06 AM, Larry Masinter wrote:

> Sorry this is very long, but I'm trying to be precise.
> We've been talking "design principles" and "editorial
> style", so I thought I would deep dive on one little bit to
> see if we can get some clarity.
> Quick summary:
> The problems with the style of the document are
> not merely editorial, it's a technical difficulty
> with many of the conformance requirements in the
> document.
> Missing design principle: avoid MUST conformance
> requirements unless it is necessary for interoperability.
> Missing editorial policy: all technical terms must
> be defined precisely.
> Missing design principle: the temporal relationship
> between states must either be defined precisely
> or made explicitly flexible.

I hope you will forgive me for responding to a meta point. Your  
explanation here of what you think is wrong with the spec as written,  
and Sam's flagging of the feed sniffing issue as one that is important  
to him, are great progress. I find these much more conducive to  
improving the spec than arguments about the title. I especially like  
that you expanded on a concrete example in detail. I may respond  
further to your technical points once I have had a chance to think  
about it more.

Received on Tuesday, 26 May 2009 02:57:34 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:45 UTC