Re: [W3C Web Crypto WG] status of web crypto api

On 11/25/2014 10:59 AM, Ryan Sleevi wrote:
> I am as uncertain as you are, as it's unclear which of Harry's requests
> require action and which are already addressed by other means.

The only request that requires action is getting rid of the "open"
editorial issues referenced in the spec.

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

Can either Mark or Ryan do those edits quickly?

I've closed all the open issues in the tracker, as it seemed that were
out of date. The Bugzilla is fine, with all objections being addressed.
However, having what appears to be an open issues (ISSUE-35)  referenced
in the spec will definitely cause a problem when we transition to CR.
See bug above and previous email (which have same text).

If any of these editorial notes cannot be resolved now, just add a quick
note to the effect that "Due to the implementation-driven nature of the
issue, the WG will resolve this during CR."

   cheers,
      harry


> 
> On Tue, Nov 25, 2014 at 1:41 AM, GALINDO Virginie <
> Virginie.Galindo@gemalto.com> wrote:
> 
>> Hi Mark, Ryan and Harry,
>> can you clarify where we are on the web crypto API publication side ?
>> Thanks,
>> Virginie
>> ________________________________
>>  This message and any attachments are intended solely for the addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>> E-mails are susceptible to alteration. Our company shall not be liable for
>> the message if altered, changed or falsified. If you are not the intended
>> recipient of this message, please delete it and notify the sender.
>> Although all reasonable efforts have been made to keep this transmission
>> free from viruses, the sender will not be liable for damages caused by a
>> transmitted virus.
>>
>

Received on Tuesday, 25 November 2014 12:12:59 UTC