RE: CfC: Publish three heartbeat drafts as WDs

> has been open since March.

Bug 21341 is in the HTML 5.1 component and this thread is about the publication of an HTML 5.1 heartbeat.

But I have to wonder how Bug 21341 applies to the CR HTML 5.0 specification?  Will any changes to the HTML 5.1 spec also be made to the CR HTML 5.0 specification?

I want to point out that the current draft Long Description document normative references the CR HTML 5.0 spec [1] so I would have thought the A11Y TF would be more interested in having Bug 21341 applied to the CR HTML 5.0 spec or possibly to both the HTML 5.1 spec AND the CR HTML 5.0 spec.



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

-----Original Message-----
From: Janina Sajka [] 
Sent: Friday, May 24, 2013 2:04 PM
To: Robin Berjon
Cc: Charles McCathie Nevile; Sam Ruby; Maciej Stachowiak; Paul Cotton; Michael(tm) Smith (;; HTML Accessibility Task Force;; W3C WAI Protocols & Formats
Subject: Re: CfC: Publish three heartbeat drafts as WDs

Hi, Robin:

Robin Berjon writes:
> Hi Janina,
> On 24/05/2013 18:12 , Janina Sajka wrote:
> >I will withdraw my objection at this time in the interest of 
> >preserving and furthering the comity that has arisen among us since Plan 2014.
> Thank you.
Well, it's not my intent to throw a major monkey-wrench into the works.
Perhaps we should have inquired about prioritization and communicated our expected timelines before.

> >While I do not think anyone is intentionally delaying here, continued 
> >delay does exaserbate W3C accessibility messaging. Also, we're now 
> >quite likely to have a Last Call for HTMl Image Description published 
> >before another HTML heartbeat is published.
> What is your time frame for LC? We're not really constrained as to the 
> minimal amount of time between heartbeats.
We're expecting LC late June. We further expect to prepare our CR implementation report during LC, so that we may well go to PR late August/early September, skipping CR.

> >Is there any reason it's unreasonable to expect this bug to be 
> >resolved before the NEXT publication milestone?
> No, I wouldn't think so. As I said, it hasn't been handled either high 
> or low priority. I (and as far as I know, the other editors
> too) tend to proceed by fixing blocks of bugs that are on related 
> topics. We can certainly handle this bug soon.
Thanks, Robin. That would be helpful.


> --
> Robin Berjon - - @robinberjon


Janina Sajka,	Phone:	+1.443.300.2200

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats
	Indie UI

Received on Saturday, 25 May 2013 07:05:15 UTC