I've taken a stab at this in https://github.com/w3c/webappsec/commit/58921e0254b0f46e1d0ac53a6fa84afe14397d0c. You can read the result more easily at https://w3c.github.io/webappsec/specs/powerfulfeatures/#terms.Thanks for the feedback! I hope things are clearer now.
Mike West <email@example.com>Google+: https://mkw.st/+, Twitter: @mikewest, Cell: +49 162 10 255 91Google Germany GmbH, Dienerstrasse 12, 80331 München, Germany
Registergericht und -nummer: Hamburg, HRB 86891Sitz der Gesellschaft: HamburgGeschäftsführer: Graham Law, Christine Elizabeth Flores(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)On Tue, Nov 25, 2014 at 1:06 PM, <firstname.lastname@example.org> wrote:At the moment the "definition" of sufficiently secure provides a random selection of detail from section 4. It only needs to say
"A Document or environment settings object is considered sufficiently secure to use powerful features if the algorithms defined in §4 return Sufficiently Secure when executed upon it."
If you want to add informative explanation here, you could make the prose more human-friendly - section 4 gives the gory details.
Charles McCathie Nevile - web standards - CTO Office, Yandex
email@example.com - - - Find more at http://yandex.com