W3C home > Mailing lists > Public > public-wsc-wg@w3.org > June 2008

ACTION-481: Conformance model (and testing) in section 7

From: Thomas Roessler <tlr@w3.org>
Date: Fri, 6 Jun 2008 18:33:11 +0200
To: public-wsc-wg@w3.org
Message-ID: <20080606163311.GP553@iCoaster.does-not-exist.org>

Section 7, Robustness, [1] was a section where we got confused about
conformance models and testing.

Reading through it again, I would suggest that our use of RFC 2119
keywords mostly makes sense:

7.1.1 (shared secrets) is a purely optional feature that might end
up as "at risk" in CR (my guess); we'll probably only know what
conformance with this one really means when we've seen an example or
two.  Till then, I suggest we just leave this section alone, and
treat 7.1.1 as an optional feature.

7.1.2 (keep chrome visible) mostly suffers from one of our confusing
"MAY NOT" clauses; I've changed that one for clarity.

7.2, 7.3, and 7.4 sound like they are mostly fine with respect to an
RFC 2119 conformance model.

7.4.1 [2] is about preventing content from controlling chrome too
much.  Each of the techniques there is, again, a perfectly fine MUST
or MUST NOT; I suspect that most of the confusion here comes from
these bullet items being denoted as techniques.

I've therefore removed the "Techniques" phrase and the bulleting,
but left the text in place.

1. http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#Robustness
2. http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#robustness-apis-obscure-security-ui
Thomas Roessler, W3C  <tlr@w3.org>
Received on Friday, 6 June 2008 16:33:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:21 UTC