- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jul 2020 01:10:52 +0000
- To: public-device-apis-log@w3.org
> In other words, "there aren't enough implementors for the WG to take it on" is a silly complaint, It's not. It's completely valid. A single implementer spec is not a standard. > but "based on previous experience, we don't think this should be part of the web platform" seems like a totally valid (procedurally and on the substance) reason to remove items from the group's charter / scope of work. I disagree. And this one provable. @pes10k, stop avoiding my direct question: is Brave going to do the work to actually enable `SecureContext` and Permission Policy for Battery or not? It's a yes or no question. Intel and Google are not going to do it, so will you or Brave step up and actually do the work? Additionally, if Intel and Google are not going to do the actual work. They we should remove `SecureContext` and Permission Policy from the spec. Having fictitious privacy claims in the spec discredits the work on this working group and w3c. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/98#issuecomment-666854467 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 July 2020 01:10:54 UTC