You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
There was interest in having companies sign onto the threat model once it's stable, as something of a pledge not to try to circumvent it.
Even though most of the document is aimed at UA and specification conformance, I could imagine some parts aimed at websites something like HTML's notion of document conformance.
I'm hesitant to do this for a couple reasons:
I think it has proven to be confusing in HTML.
I don't want to help companies declare their love of motherhood and apple pie unless we can find ways to enforce that they back that up with action. In this context, that enforcement probably consists of "MUST"-level statements in this document, combined with some regulator who can impose penalties for breaking those rules. I'm not confident we can get either one.
However, I'm happy to listen to the rest of the group to discover I'm wrong.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There was interest in having companies sign onto the threat model once it's stable, as something of a pledge not to try to circumvent it.
Even though most of the document is aimed at UA and specification conformance, I could imagine some parts aimed at websites something like HTML's notion of document conformance.
I'm hesitant to do this for a couple reasons:
However, I'm happy to listen to the rest of the group to discover I'm wrong.
The text was updated successfully, but these errors were encountered: