Re: how goes the capability stuff?
Raoul Duke <[email protected]>
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <CAJ7XQb6E_1Y69sc3Y+N4n_T3fohqL3ihgEwnrpkf25oZrwYROw@mail.gmail.com> |
Please send such good, insightful comments along to the working group, it would be great for them to get more feedback! Email [email protected] On Fri, Oct 10, 2014 at 7:55 AM, Jonathan Rees <[email protected]> wrote: > 5.1 'reasons to use capability URLs' doesn't mention CSRF defense as a reason. That seems odd given how on this list it's often given as the #1 reason to use capabilities. > > Jonathan > > On Oct 10, 2014, at 4:03 AM, Raoul Duke <[email protected]> wrote: > >> ---------- Forwarded message ---------- >> From: Daniel Appelquist >> Date: Fri, Oct 10, 2014 at 12:04 AM >> Subject: Re: how goes the capability stuff? >> >> Well - we had a discussion on this at last week’s face-to-face TAG >> meeting, minuted here: >> >> https://github.com/w3ctag/meetings/blob/gh-pages/2014/sept29-oct1/09-29-f2f-minutes.md#capability >> >> Those minutes contain links to the latest drafts. Jeni Tennison is >> busy putting together a final draft based on some additional >> suggestions… That draft will appear here: >> http://w3ctag.github.io/capability-urls/ and can be tracked here >> https://github.com/w3ctag/capability-urls. >> >> Basically I think we are done and ready to publish this document - and >> as I recall, part of that process was incorporating lots of feedback >> including from the community you highlighted - but always open for >> more feedback. >> >> _______________________________________________ >> cap-talk mailing list >> [email protected] >> http://www.eros-os.org/mailman/listinfo/cap-talk > > > _______________________________________________ > cap-talk mailing list > [email protected] > http://www.eros-os.org/mailman/listinfo/cap-talk _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk