- From: Michael[tm] Smith <mike@w3.org>
- Date: Mon, 20 Oct 2014 11:02:08 +0900
- To: Arthur Barstow <art.barstow@gmail.com>, Hallvord Steen <hsteen@mozilla.com>
- Cc: public-webapps <public-webapps@w3.org>
Received on Monday, 20 October 2014 02:02:10 UTC
Arthur Barstow <art.barstow@gmail.com>, 2014-10-19 09:59 -0400: ... > >c) Ship a TR based on the newest WHATWG version, reference WHATWG's Fetch spec throughout. > > The staff does indeed permit normative references to WHATWG specs in > WD and CR publications so that wouldn't be an issue for those types > of snapshots. However, although the Normative Reference Policy [NRP] > _appears_ to permit a Proposed REC and final REC to include a > normative reference to a WHATWG spec, in my experience, in practice, > it actually is _not_ permitted. There's no prohibition against referencing WHATWG specs in RECs. > (If someone can show me a PR and/or REC that includes a normative > reference to a WHATWG spec, please let me know.) If it's your goal to ensure that we actually do never have a PR or REC with a normative reference to a WHATWG spec, the line of logic implied by that statement would be a great way to help achieve that. If Hallvord and the other editors of the W3C XHR spec want to reference the Fetch spec, then they should reference the Fetch spec. > As such, we could do c) but with respect to helping to set realistic > expectations for spec that references such a version of XHR, I think > the XHR spec should be clear (think "Warning!"), that because of the > Fetch reference, the XHR spec might never get published beyond CR. That's not necessary. Nor would it be helpful. --Mike -- Michael[tm] Smith http://people.w3.org/mike
Received on Monday, 20 October 2014 02:02:10 UTC