PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes from Ryan Sleevi on 2013-01-31 (public-webcrypto@w3.org from January 2013)

From: Ryan Sleevi <sleevi@google.com>
Date: Thu, 31 Jan 2013 11:06:33 -0800
To: public-webcrypto@w3.org
Message-ID: <CACvaWvZTn-JS_XnXpuUXE9TrZ86OeZJKyeB=XjbHO0ZO0PmBKA@mail.gmail.com>

http://www.w3.org/2012/webcrypto/track/issues/17

I would like to propose that ISSUE-17 be closed. The definition of
custom key attributes has been removed from the specification, on the
basis that this specification is not attempting to define a new web
storage mechanism. Attributes may instead be associated via the
storage mechanisms associated with Keys themselves (eg: IndexedDB).

The use of custom attributes, such as the Named Key discovery API, has
been addressed through separate specifications. As such, I believe we
have resolved this ISSUE.

Received on Thursday, 31 January 2013 19:07:00 UTC