- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Thu, 30 Jul 2015 18:01:41 +0200
- To: public-rww <public-rww@w3.org>, public-webid <public-webid@w3.org>
- Message-ID: <CAKaEYhK6+CBO75qwYoxwbs8c6D6YgeAQtrBRzDVb5W0inJC-ZQ@mail.gmail.com>
FYI: Google / Ryan Sleevi's comments on WebID ---------- Forwarded message ---------- From: Ryan Sleevi <rsleevi@chromium.org> Date: 30 July 2015 at 17:53 Subject: Re: (Pre-)Intent to Deprecate: <keygen> element and application/x-x509-*-cert MIME handling To: Melvin Carvalho <melvincarvalho@gmail.com> Cc: blink-dev <blink-dev@chromium.org> On Jul 30, 2015 7:42 AM, <melvincarvalho@gmail.com> wrote: > > > -1 KEYGEN is in use. > > This move will be severely detrimental several grass roots communities, such as the WebID community. > > [1] https://www.w3.org/community/webid/participants > This comment doesn't really address any of the technical concerns raised. WebID has repeatedly demonstrated a willingness to appropriate ill-suited technology, and has readily acknowledged that no browser implements the desired functionality for WebID to be successful. WebID is still nascent, and readily admits it won't work with Edge. An alternative would be for WebID to proceed with standards that are actually widely used and have a viable chance at being usable - such as WebCrypto. But it seems odd to hold a feature that was never fit to purpose nor working as desired hostage for experimental activity in a CG.
Received on Thursday, 30 July 2015 16:02:12 UTC