[Bug 24827] Be clearer about the distinction between operations and methods

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24827

--- Comment #5 from Ryan Sleevi <sleevi@google.com> ---
(In reply to Mark Watson from comment #4)
> This is a continuing source of confusion.
> 
> For example, there is no longer a derive key operation. The deriveKey
> *method* procedures say "call the derive bits operation for the derivation
> algorithm then feed the result into import key for the target key algorithm".
> 
> In fact it only makes sense for the derivation algorithm to go as far as
> deriving the raw bits. The process of importing raw bits into a key object
> for *another algorithm* is a function of that other algorithm.

I'm sorry, but I find this paragraph vastly more confusing than the one you
have issue with.

> 
> But when looking at the supported operation tables, the fact that derive Key
> is missing for things like DH generates confusion because this distinction
> between methods and operations is not properly described.
> 
> Any opinions on this ?
> 
> Should I make a more concrete proposal to resolve this ?

I'm already working on resolving this as part of the TAG feedback, with respect
to how algorithms are defined, their extensibility points, and the conceptual
framework for interacting with them.

I hope to have a concrete proposal up soon. However, because much of the
feedback results in changes through multiple layers, I haven't pushed a change
because it's not clear when viewed in piece-meal, and because I'm trying to
ensure the spec is holistically updated, rather than in the bits and pieces
that have led to the linguistic, stylistic, and functional inconsistency of the
present spec.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 14 May 2014 20:14:15 UTC