RE: [webauthn] TAG review feedback: Align Credential interface with Credential Management?

Another piece of feedback I received – putting dots in the names of the extensions is confusing because it implies an object hierarchy where there is none. Could we just remove the dots or turn them into underscores or something?

From: J.C. Jones [mailto:jc@mozilla.com]
Sent: Wednesday, July 06, 2016 12:27 AM
To: Vijay Bharadwaj via GitHub <sysbot+gh@w3.org>
Cc: W3C WebAuthn WG <public-webauthn@w3.org>
Subject: Re: [webauthn] TAG review feedback: Align Credential interface with Credential Management?

Completely agreed. I've actually started some of that last week but haven't written it up. [1]
J.C.

1) https://github.com/w3c/webauthn/compare/master...jcjones:api-aesthetics


On Wed, Jul 6, 2016 at 8:59 AM, Vijay Bharadwaj via GitHub <sysbot+gh@w3.org<mailto:sysbot+gh@w3.org>> wrote:
My understanding of the current consensus on this one is that we
believe this alignment no longer makes sense. So I propose to:
- Move this interface from the global window namespace to the
navigator namespace to reduce pollution of the global namespace
- Rename interface Credential to ScopedCredential to fix the name
collision with Credential Management.
- Possibly rename CredentialType to version to make it clearer what
this field signifies (since ScopedCredential is itself arguably a
credential type and ScopedCredentialType is unwieldy)

Feedback welcome.

--
GitHub Notification of comment by vijaybh
Please view or discuss this issue at
https://github.com/w3c/webauthn/issues/60#issuecomment-230693738 using
 your GitHub account