Meeting minutes
https://
mmiller: getting use to terms, want to get spec out to newcomers
… normalize the terms. go through core content, then recommendation, privacy, etc.
tony: we have some people looking at this
jeffH: we could have intro. doc for certain participants, like RPs
mmiller: W3C doesn't feel like it is for devs
… part of issue is it tries to be all things to all people.
jeffH: primary customer is a browser developer
… can't solve all of this on the call. it has been a struggle from the first draft.
jbradley: have to throw in authenticator dev.
https://
agl: close this.
tony: any objection
https://
tony: leave this one another week for a response.
https://
jeffH: is this better suited for IETF?
… likely not for us
https://
elundberg: started to write a PR for this.
… can add some clarification.
https://
nSteele: this being baked in would be great, but not doing this in the CG
mmiller: devs will have to deal with this issue.
elundberg: there are arguments against doing this
sweeden: lot of this dev comes out of browser side
elundberg: crazy idea, what if we extend JSON
selfissue: modifying JSON is way out of scope. and creates other issues.
https://
jeffH: proposing to add a little more explanation for RPs and cred IDs
bradley: put stake in the ground at 512 bytes
<selfissued> Can someone add a comment to PR #1615 containing a URL at which I can view a rendered version of the PR? When sweeping changes are made, it's often useful to be able to view the rendered result alongside of the diffs. Thanks.
akshay: what do we do with any future features?
… we should check with other people
jeffH: we have more experience so maybe we can be more reasonable
tony: jeffH, you will follow up?
jeffH: yes.
elundberg: anymore on multiple keys?
jeffH: will talk about that in FIDO.
tony: adjourn