rsleevi: maybe this should be an
issue?
... i believe we have a consensus, but should put it to the
group
... depends on whether we have a generic key-value store or
something else

hhalpin: can test for consensus
on calls if you like

<hhalpin> yes, its an
ISSUE

virginie: will transform to
issue, seems like rsleevi has a clear view

rsleevi: don't think attributes
have to be stored
... in the same location as the keys

<rsleevi> +q

<hhalpin> vgb: there will
always be times like smartcards

<hhalpin> ... where you can't
just add arbitrary attributes

<hhalpin> ... maybe the
difference is between secure and non-secure custom
attributes

rsleevi: threw out a hypothetical
strawman of a user with multiple browsers - maybe if both use
OS key store the browsers should be able to share/agree on
these

<hhalpin> +1 coupling them
together, but not sure how

rsleevi: but in practice it may
not be possible in all cases. Maybe browsers should make a best
effort but it shouldn't be scoped or speced.

wtc: for example start and end
date attributes are not supported natively by all underlying
libraries, so we will have to do something specific to the
platform and maybe different browsers will reach different
solutions

markw: understand that we don't
want to create new key-value stores, but we should still have
room for attributes that are associated with the key but are
not set by app

rsleevi: not proposing a both-and
solution, proposing either-or
... if you want to pre-provision then you can also
pre-provision an indexDB set of values
... if we use an existing key-value store then the key should
not have its own attribute store

markw: asking about other
specific things like whether the key is exportable

rsleevi: existing draft provides
a model for the key object, and those are exposed. the other
attributes not listed here may not be supported
... in a key store

hhalpin: everyone needs to
complete open actions this week
... then editor proposes moving to FPWD
... each member of WG then needs to read and provide
comments
... mark comments as major or minor
... in ~2 weeks we will do informal consensus and then get it
published

<hhalpin> next week: New
Version of editors draft, complete all open actions