Manu Sporny

@brucelawson The HTML9 development process requires us to use an "always-reject" model. We've found that this leads to consistent, equitable, rapid progress. If you have an issue with this policy,...

> @philarcher @msporny @pchampin - anything to add here? Thanks for the ping @danbri, yes, quite a bit to add. Some data points for this thread to consider: * Educational/Occupational...

> I think the most feasible path forward for this is to: Awesome, thanks for the concrete suggestion @rhiaro -- we'll pass this plan by the W3C DID WG on...

@jyasskin wrote: > I suspect there's no way to resolve this concern short of actually specifying the allowed ZKP methods and where they put their data, which y'all have I-think-rightly...

> There's currently no specification for timestamps in VPs, meaning that presenters can't mitigate the risk of replay attack by limiting their presentation validity to a short window during which...

@marcoscaceres raised some questions that are helpful wrt. requirements for this feature: > * where should we gather the list of candidate corrections/additions? There seem to be four classes of...

This PR needs to be rebased before we merge it. I believe the same problem might apply to the `proof` property, but I haven't had the time to check to...

@iherman wrote: > is it a vocabulary that ought to be taken over by the WG? Yes, it should be taken over by the WG.

Hrm, having looked at all the SVG diagrams in the latest version of Chromium... all the diagrams are busted in ways that make the images look bad now. Misaligned text...

> We're going to be blocked publishing the v1.1 spec until this is fixed... or we revert to the old graphics. I fixed a number of the issues, very minor...