- From: Martin Thomson via GitHub <noreply@w3.org>
- Date: Tue, 13 Jan 2026 04:30:50 +0000
- To: public-patwg@w3.org
My view on these: 1. DAP might assume that the verification key is fixed for the lifetime of a task, but it doesn't need to be. I realize that the validation key needs to be agreed, but it could be agreed across an aggregation job instead. Because it isn't specified, that would seem to be possible without changing specifications (though integrating the change in a specification might be an improvement). 2. Understood. That's why slide 12 asks that question. The cost would be that we'd need to define an (optional) parameter in the API for it. -- GitHub Notification of comment by martinthomson Please view or discuss this issue at https://github.com/w3c/patwg/issues/76#issuecomment-3741873287 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 January 2026 04:30:51 UTC