- From: Mike Jones via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Mar 2017 23:56:36 +0000
- To: public-webauthn@w3.org
As we discussed in the F2F, it's a business decision which extensions to support. They're extensions because supporting them is optional. Also, for context, the working group made a decision very early on to merge all the technical specifications into a single document, both to make it easier to keep the content in sync, and so that we're not having to go for W3C approvals for multiple documents, with risk of delays and getting things out of sync that that entails. All the content, including the initially defined extensions, are in the same document for good reasons. FYI, https://github.com/w3c/webauthn/pull/386 should make it a lot clearer how to define and register new extensions. It makes it clear that the initially defined ones are not somehow "special". -- GitHub Notification of comment by selfissued Please view or discuss this issue at https://github.com/w3c/webauthn/issues/290#issuecomment-288256425 using your GitHub account
Received on Tuesday, 21 March 2017 23:56:42 UTC