- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Apr 2018 21:43:37 +0000
- To: public-webauthn@w3.org
@emlun > This seems to contradict itself, saying both that values are strings and that they are any JSON-able type. actually, [IIUC](https://en.wiktionary.org/wiki/IIUC), it is saying that [(collected) client data](https://w3c.github.io/webauthn/#sec-client-data) is a key-value mapping whose keys are string-valued. The _client data values_ associated with the latter string-valued keys can be any type that has a valid encoding in JSON. > Not all values are strings now that tokenBinding is a dictionary. I am thinking this is not a problem both because of the above disambiguation of the uses of the term "value" in the quoted spec text, and also because [IDL dictionary values can be converted to to ES objects](https://heycam.github.io/webidl/#es-dictionary). Perhaps we ought to clarify the quoted spec text like so... ``` The <dfn>client data</dfn> represents the contextual bindings of both the [=[RP]=] and the client platform. It is a key-value mapping whose keys are string-valued. The _client data values_ associated with the latter string-valued keys can be any type that has a valid encoding in JSON. Its structure is defined by the following Web IDL. ``` ..? -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/870#issuecomment-382539062 using your GitHub account
Received on Wednesday, 18 April 2018 21:43:41 UTC