- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Nov 2024 12:36:02 +0000
- To: public-webauthn@w3.org
While I somewhat agree in principle, I'm not sure that using [parse JSON bytes to an Infra value](https://infra.spec.whatwg.org/#parse-json-bytes-to-an-infra-value) is better. It indirectly references invoking [%JSON.parse%](https://tc39.es/ecma262/#sec-json.parse) from ECMAScript, which may be appropriate if this verification step happens to be running in a browser, but these steps often run on a backend server that's not JavaScript, so it seems awkward to (indirectly) refer to ECMAScript procedures in those cases. While yes, describing these RP operations as operating on JavaScript values is a bit of a fantasy as they've most likely been transformed to and from network representations along the way, I'm not sure that using Infra values really adds much. I would leave this as is for L3 and maybe reconsider for L4. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2207#issuecomment-2503767969 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 November 2024 12:36:04 UTC