Re: [webauthn] mmiller-improve-terminology-and-progression (#1615)

On 2-Jun-2021 call: 
@equalsJeffH observed that the underlying "issue" with the webauthn spec is that it caters to at least three audiences: browser implementors, RP implementors, and authenticator implementors.  And that rather than doing non-trivial surgery to the spec in order to cater to a particular one of those audiences, we could have an audience-specific "introduction to the spec" document that does so.  @nicksteele suggested that this was something that could be attempted in the context of the [WebAuthn Adoption CG](https://www.w3.org/community/webauthn-adoption/).

-- 
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1615#issuecomment-853392257 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 2 June 2021 21:24:09 UTC