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

I'm happy for you to make the edits, Harry, so long as we get a chance to
review them.

...Mark

On Tue, Nov 25, 2014 at 8:00 AM, Harry Halpin <hhalpin@w3.org> wrote:

>
>
> On 11/25/2014 04:58 PM, Mark Watson wrote:
> > Sorry, I have not found time to look at this yesterday and will likely
> not
> > have time today. And then I am away for Thanksgiving, so we are in to
> next
> > week :-(
>
> If you guys give me permission, I'm happy to make the edits to close up
> the open issues that are "inline" in the spec myself.
>
> Otherwise, I can also wait till next week.
>
>    cheers,
>       harry
>
> >
> > ...Mark
> >
> > On Tue, Nov 25, 2014 at 4:12 AM, Harry Halpin <hhalpin@w3.org> wrote:
> >
> >>
> >>
> >> 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.
> >>>>
> >>>
> >>
> >>
> >
>