- From: Larry Masinter <masinter@adobe.com>
- Date: Tue, 24 Apr 2012 15:10:29 -0700
- To: Noah Mendelsohn <nrm@arcanedomain.com>, "www-tag@w3.org" <www-tag@w3.org>
I think it was this: There's a normative reference from a W3C recommendation to an Internet Draft which has now expired and for which progress is uncertain (MIME sniffing). * Use of normative references to in-progress documents with no persistence guarantees seems in contradiction to the W3C QA recommendation. Is there a process issue that would have required checking references _before_ entering CR, and at least pointing out the dependency and requiring explicit agreement of reviewers that dangling references can be tolerated? * The cause of mime-sniffing being in the HTML working group originally seemed to be an unanticipated scope creep. -----Original Message----- From: Noah Mendelsohn [mailto:nrm@arcanedomain.com] Sent: Tuesday, April 24, 2012 2:27 PM To: www-tag@w3.org Subject: ACTION-687: Please help me remember what this one is about At the end of the 3 April 2012 discussion [1] of XML-ER, I was given: ACTION-687: on - Noah Mendelsohn - Look for opportunities to discuss putting forward something to the AB about the Process and the failed reference from REC drafts to expired RFCs as a side-effect of scope creep etc. - Due: 2012-04-24 - OPEN At the time this was assigned, the discussion had begun to focus on issues relating to sniffing, and Robin had just been given ACTION-686: on - Robin Berjon - try to find who is in charge of the current browser content sniffing clustermess, and see if there is a way of moving out of the quagmire - Due: 2012-05-01 - OPEN ACTION-686 makes sense to me; I confess that ACTION-687 doesn't. I'd be grateful if someone could remind me what it's trying to ask, and how (if at all) it relates to the XML-ER and sniffing discussions that we were having? Thank you. Noah [1] http://www.w3.org/2001/tag/2012/04/03-minutes#item04
Received on Tuesday, 24 April 2012 22:16:11 UTC