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: Wed, 27 May 2009 17:36:18 -0700
Cc: Larry Masinter <masinter@adobe.com>, HTML WG <public-html@w3.org>
Message-id: <F0394319-5BAF-42B9-A562-5490098E0B8E@apple.com>
To: Boris Zbarsky <bzbarsky@mit.edu>

On May 27, 2009, at 5:30 PM, Boris Zbarsky wrote:

> Larry Masinter wrote:
>> Specifying conservative authoring behavior at the same time  
>> encouraging
>> liberal reader behavior is the primary method by which standards  
>> writers
>> address those real concerns.
> This works well if the authors are sophisticated enough to be aware  
> of the specification.  In practice, that's not the case with HTML.
> That said, the current draft does in fact impose all sorts of  
> requirements on authors while defining what UAs should do if authors  
> violate those requirements.  So I'm not sure what we're actually  
> discussing here....

The spec has conformance requirements for markup, but generally not  
conformance requirements for use of scripting APIs. One reason for  
that is that we don't have good technology for validating a program's  
use of an API. In general, this kind of validation is equivalent to  
the halting problem and thus provably not computable. The best you  
could do is warn about violations at runtime, but that can't tell you  
about potential violations that can occur in different flows through  
the program.

Received on Thursday, 28 May 2009 00:36:58 UTC

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