Samuel Weiler
Samuel Weiler
The FPWD at https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/ Seems near empty, with a table of contents pointing at a different document: https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/intro/introduction.html And those two documents have conflicting sections. e.g. the latter, in section...
Please replace the individual doc links with a link to https://www.w3.org/wiki/DocumentReview#How_to_get_horizontal_review That way, we reduce the maintenance burden when we update these docs.
collapsing the five pairs of horizontal labels will help make this doc more usable. for -tracker: "Applied by WGs to bring an issue to the attention of a horizontal group....
During TPAC, we observed that SPC-capable credentials can also be used for login. I speculated about the possibility of not-payment sites attempting to create SPC-capable credentials for the purpose of...
Add an in-line informative reference to: https://www.w3.org/2017/12/formal-objections.html (Alternatively, deprecate that document.)
it needs a line for the present rechartering, showing the new deliverable.
Charter draft is not using the most up-to-date template, as evidenced by the security and privacy line. I think the IPR policy text todo's would also be fixed by that...
Rather than duck by pointing at others' suggestions ("The [TOUCHSIGNATURES] and [ACCESSORY] research papers propose that implementations can ..."), define normative privacy mitigations in this spec. Here are some of...
Section 4 is a little short on analysis and explanation of the risks of exposing this API. At the very least, since the mitigations it defines (well, see https://github.com/w3c/battery/issues/27...) seem...
First, it's not quite clear what "the user permission requirement" refers to in > The user agent MAY ask the user for battery status information access, or alternatively, enforce the...