- From: <bugzilla@jessica.w3.org>
- Date: Mon, 29 Sep 2014 21:43:18 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25198 --- Comment #13 from Mark Watson <watsonm@netflix.com> --- This is more relevant to the overall extensibility story for WebCrypto. It was argued that we needed to provide explicit extensibility points exactly to enable future extension of the specification without either modifying the base specification itself or modifying it "from afar" (monkey-patching). If, on the other hand, extension of the base always requires modification of the base specification itself, then I don't see the advantage of defining extension points a priori: they can be provided in future versions when then are needed. I'm fine either way, but it seems the only value in explicitly defining and constraining extension points now is that what you're constraining is what can and can't be done from other future specifications, without modification of the base. You can always do whatever you want by modifying the base itself. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 29 September 2014 21:43:19 UTC