This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
With the removal of RSAES-PKCS1-v1_5, the dictionary RsaKeyAlgorithm disappeared as well. So RsaHashedKeyAlgorithm needs to inherit directly from KeyAlgorithm, not from RsaKeyAlgorithm.
This seems straightforward.
https://dvcs.w3.org/hg/webcrypto-api/rev/06d1b5781e13
Reopening. The resolution introduced two dictionaries that are unused, except for inheritance purposes. With the removal of RSAES-PKCS1-v1_5, these dictionaries should be folded as members of RsaHashedKeyGenParams / RsaHashedKeyAlgorithm.
Well, inheritance is a form os use, so they are not unused. I left these separate because it seemed like it might be useful to have the base definitions available for algorithms that use RSA keys without parameterization with a hash. If the removed RSA-ES is the only such algorithm that will ever exist, then indeed these dictionaries would never be used. This is entirely editorial anyway.
(In reply to Mark Watson from comment #4) > Well, inheritance is a form os use, so they are not unused. > > I left these separate because it seemed like it might be useful to have the > base definitions available for algorithms that use RSA keys without > parameterization with a hash. If the removed RSA-ES is the only such > algorithm that will ever exist, then indeed these dictionaries would never > be used. > > This is entirely editorial anyway. We had great discussions with the TAG and Boris on the non-idiomatic approach to inheritance, with multiple vendors expressing concerns over the "C++ style" API. I think we can and should nuke the inheritance, as it's visible (as has been noted before)
Dictionary inheritance is just a spec artifact; it's not visible in any way that I'm aware of...
As per comment#6 there is no visible difference between the current specification and combining the dictionary definitions.