Re: (Pre-)Intent to Deprecate: <keygen> element and application/x-x509-*-cert MIME handling

Being that WebID is a URI, that would afford us a good deal of flexibility
in what we can utilize, wouldn't it? So, some work could be conducted in
coupling WebID with things such as WebCrypto.

On Fri, Jul 31, 2015 at 7:45 AM, Timothy Holborn <timothy.holborn@gmail.com>
wrote:

> WebID is a URI
>
> On 02:02, Fri, 31/07/2015 Melvin Carvalho <melvincarvalho@gmail.com>
> wrote:
>
>> 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.
>>
>>


-- 
Regards,

-Cory Sabol
cssabol@uncg.edu