W3C home > Mailing lists > Public > public-webappsec@w3.org > February 2015

BIKESHED: Rename "Powerful features"?

From: Mike West <mkwst@google.com>
Date: Wed, 18 Feb 2015 16:19:26 +0100
Message-ID: <CAKXHy=eKTkNAQJjaBuB2buVKbV_65H2GJWL+A5LE034hfMi_nQ@mail.gmail.com>
To: "public-webappsec@w3.org" <public-webappsec@w3.org>
Cc: Yan Zhu <yzhu@yahoo-inc.com>, Mark Watson <watsonm@netflix.com>, Crispin Cowan <crispin@microsoft.com>, Brian Smith <brian@briansmith.org>
Brian, Crispin, and Mark have all expressed various degrees of displeasure
with the "powerful features" name, arguing that it invites debate about the
word "powerful" rather than the content of the spec (I'm paraphrasing: see
https://lists.w3.org/Archives/Public/public-webappsec/2015Feb/0304.html for
a more detailed description).

Mark suggested "HTTP-unsafe" to get the conversation started. I'm not a
huge fan of that formulation, as it seems equally question-begging.

If the normative focus of the specification is going to be the details in
https://w3c.github.io/webappsec/specs/powerfulfeatures/#algorithms, and not
the discussion in
https://w3c.github.io/webappsec/specs/powerfulfeatures/#is-feature-powerful,
then renaming the spec "Sufficiently Secure Contexts" might make sense. We
could then drop the term "powerful" entirely in
https://w3c.github.io/webappsec/specs/powerfulfeatures/#is-feature-powerful,
and land on the verbose-but-tautologically-correct "Features which are only
available in sufficiently secure contexts"?

WDYT?

--
Mike West <mkwst@google.com>, @mikewest

Google Germany GmbH, Dienerstrasse 12, 80331 München,
Germany, Registergericht und -nummer: Hamburg, HRB 86891, Sitz der
Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine Elizabeth
Flores
(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)
Received on Wednesday, 18 February 2015 15:20:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:10 UTC