W3C home > Mailing lists > Public > public-webappsec@w3.org > April 2016

Re: webappsec-ACTION-216: Examine fetch refs for stability

From: Brad Hill <hillbrad@gmail.com>
Date: Wed, 20 Apr 2016 20:02:55 +0000
Message-ID: <CAEeYn8jibnwoWPU5it4eAFxo5ym=x4m38_+B_R0+YuSsnts33Q@mail.gmail.com>
To: Frederik Braun <fbraun@mozilla.com>, Anne van Kesteren <annevk@annevk.nl>
Cc: Web Application Security Working Group <public-webappsec@w3.org>
So Wendy is going to see if the specific parts of Fetch our specs refer to
are stable enough to be OK, even if the entire spec will never be stable.

On Wed, Apr 20, 2016 at 12:07 PM Frederik Braun <fbraun@mozilla.com> wrote:

> See draft notes for today's call:
> http://www.w3.org/2016/04/20-webappsec-minutes.html#item04
>
> My attempt to summarize is as follows (and, folks, please correct me
> if I'm wrong):
>
> Some specifications that are currently waiting to transition (e.g.,
> SRI towards Proposed Recommendations) have normative references to
> fetch. The main problem here seems that a living standard by
> definition can't be considered stable. But stability seems to be a
> requirement according to
> https://www.w3.org/2013/09/normative-references
>
>
> On Wed, Apr 20, 2016 at 7:29 PM, Anne van Kesteren <annevk@annevk.nl>
> wrote:
> > On Wed, Apr 20, 2016 at 6:19 PM, Web Application Security Working
> > Group Issue Tracker <sysbot+tracker@w3.org> wrote:
> >> webappsec-ACTION-216: Examine fetch refs for stability
> >>
> >> http://www.w3.org/2011/webappsec/track/actions/216
> >
> > Context?
> >
> >
> > --
> > https://annevankesteren.nl/
> >
>
>
Received on Wednesday, 20 April 2016 20:03:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:19 UTC