W3C home > Mailing lists > Public > www-tag@w3.org > July 2011

RE: [Bug 13100] TAG issue on HTML+RDFa and Microdata last call drafts

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Mon, 18 Jul 2011 22:27:34 +0000
To: Jeni Tennison <jeni@jenitennison.com>, "www-tag@w3.org List" <www-tag@w3.org>
CC: "Sam Ruby (rubys@intertwingly.net)" <rubys@intertwingly.net>, "Maciej Stachowiak (mjs@apple.com)" <mjs@apple.com>
Message-ID: <E3EACD022300B94D88613639CF4E25F8279B7127@TK5EX14MBXC134.redmond.corp.microsoft.com>
> Is there anything that we need to do, process-wise, during Last Call, to prevent that from happening, or can that be prevented at a later stage if it proves necessary?

Please review the WG's Last Call schedule that is documented at:
http://lists.w3.org/Archives/Public/public-html/2011Jun/0315.html 
and note the following date for the escalation of Last Call issues:

>- Jan 14, 2012 - cutoff for escalating bugs for Last Call consideration - all Tracker Issues in Tracker, calls for proposal issued by this date 
>    Consequences of missing this date: any further escalations will not be treated as a Last Call comment.

This effectively means that you have until Jan 14, 2012 to convert any Last Call bug into an Issue as per the WG's escalation path of its Decision Policy:
http://dev.w3.org/html5/decision-policy/decision-policy-v2.html#escalation 

Please let me know if this information is clear.

/paulc
HTML WG co-chair

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of Jeni Tennison
Sent: Monday, July 18, 2011 6:15 PM
To: www-tag@w3.org List
Subject: Re: [Bug 13100] TAG issue on HTML+RDFa and Microdata last call drafts

FWIW, I think this response is reasonable. We wanted to give the HTML WG a heads up about the formation of the task force, but there isn't anything specific for the editors to do until the W3C puts the task force together and it starts coming out with bug reports.

On the other hand, we do want to ensure that the specs don't become Recommendations before the task force has a chance to do its work. Is there anything that we need to do, process-wise, during Last Call, to prevent that from happening, or can that be prevented at a later stage if it proves necessary? (Noting that we're not anticipating the task force taking very long.)

Cheers,

Jeni

On 18 Jul 2011, at 22:39, Noah Mendelsohn wrote:

> The TAG needs to decide what, if anything, to do about the attached. Thank you.
> 
> Noah
> 
> -------- Original Message --------
> Subject:	[Bug 13100] TAG issue on HTML+RDFa and Microdata last call drafts
> Date:	Mon, 18 Jul 2011 18:41:38 +0000
> From:	bugzilla@jessica.w3.org
> To:	nrm@arcanedomain.com
> 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13100
> 
> 
> Aryeh Gregor
> <Simetrical+w3cbug@gmail.com>
>  changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|REOPENED                    |RESOLVED
>          Resolution|                            |WONTFIX
> 
> --- Comment #11 from Aryeh Gregor
> <Simetrical+w3cbug@gmail.com>
>  2011-07-18 18:41:37 UTC ---
> EDITOR'S RESPONSE: This is an Editor's Response to your comment. If 
> you are satisfied with this response, please change the state of this 
> bug to CLOSED. If you have additional information and would like the 
> Editor to reconsider, please reopen this bug. If you would like to 
> escalate the issue to the full HTML Working Group, please add the 
> TrackerRequest keyword to this bug, and suggest title and text for the 
> Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document:
> 
>    
> http://dev.w3.org/html5/decision-policy/decision-policy.html
> 
> 
> Status: Rejected
> Change Description: no spec change
> Rationale: As far as I can tell, nothing described in this bug is 
> specific enough to be actionable.  It does not request that any 
> specific changes be made to the microdata specification.  If the TAG 
> or any other party would like to set up a committee to make 
> recommendations, it is free to do so.  If a committee is eventually 
> formed and does develop specific recommendations, it can file them as individual bugs like any other feedback.
> 
> --
> Configure bugmail: 
> http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
> 
> ------- You are receiving this mail because: ------- You are on the CC 
> list for the bug.
> 
> 

--
Jeni Tennison
http://www.jenitennison.com
Received on Monday, 18 July 2011 22:28:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:39 GMT