- From: Edward O'Connor <eoconnor@apple.com>
- Date: Thu, 13 Dec 2012 09:28:50 -0800
- To: public-html-wg-announce@w3.org
Hi Maciej, You wrote: > The HTML Working Group will have its usual weekly teleconference on > 2012-12-13 for up to 60 minutes from 17:00Z to 18:00Z. The minutes are available in HTML at http://www.w3.org/2012/12/13-html-wg-minutes.html or in plain text below. [1]W3C [1] http://www.w3.org/ - DRAFT - SV_MEETING_TITLE 13 Dec 2012 Attendees Present Regrets Chair mjs Scribe hober Contents * [2]Topics 1. [3]Action items due by Thursday, December 13 2. [4]New Issues This Week 3. [5]Status of WG documents 4. [6]Other Business 5. [7]Other other business 6. [8]Scribe for next meeting 7. [9]Adjournment * [10]Summary of Action Items __________________________________________________________ <gitbot> 01[13html01] 15rubys pushed 2 new commits to 06feature/whatwg: 02[11]https://github.com/w3c/html/compare/d5bd64200791...91afdc 7c9859 [11] https://github.com/w3c/html/compare/d5bd64200791...91afdc7c9859 <gitbot> 13html/06feature/whatwg 1405ffac7 15ianh: [e] (0) More ruby examples.... <gitbot> 13html/06feature/whatwg 1491afdc7 15ianh: [e] (0) Clarify that these use cases aren't exclusive.... <mjs> hi everyone <mjs> is anyone willing to scribe this week? <scribe> ScribeNick: hober Action items due by Thursday, December 13 mjs: there are none New Issues This Week mjs: also none, but there are 8 tracker requests [12]http://w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywo rds=TrackerRequest [12] http://w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywords=TrackerRequest Status of WG documents mjs: status of HTML5 ... we've put in a CR transition request to the director ... along with the formal objections ... no update to report ... HTML Canvas 2D Context ... in same state as HTML5 ... HTML Microdata ... we will soon have a note v. rec survey ... otherwise it's pretty much ready for cr ... Polyglot Markup: HTML-Compatible XHTML Documents ... also about ready for note v. rec survey ... we have rationale statements both ways ... needs some additional work if it is to proceed to CR ... needs to meet the CR template, and needs CR exit criteria ... since it has no UA conformance requirements ... HTML5: Techniques for providing useful text alternatives ... also pending a survey, there is active discussion ... also needs to meet the CR template, and needs CR exit criteria ... next several documents have been published as WD by the WG but have never gone to LC ... HTML to Platform Accessibility APIs Implementation Guide ... HTML5 differences from HTML4 ... HTML5: Edition for Web Authors ... HTML: The Markup Language (an HTML language reference) ... as some point we should look to see if any of these document should proceed to LC and beyond ... there are several extension specifications ... they have EDs, most have not gone to FPWD ... with the exception of the <main> element spec ... some of the others may have been dropped by their editor ... and others will be proposed FPWD soon, when their editors are ready ... HTML 5.1 series <jaymunro> It's currently being called : HTML Canvas 2D Context, Level 2 mjs: now that HTML5 and the Canvas 2D Context API are moving along, preparing FPWD documents of the next versions plh: is fpwd request the next step? mjs: i believe so plh: will you be doing this, or one of the other chairs? mjs: unsure at this time, will discuss with my co-chairs ... ARIA in HTML ... a proposed non-normative set of guidelines ... currently being discussed by the a11y tf ... likely to be proposed to the wg soon janina: i think the longdesc extension spec will be ready for a fpwd cfc soon ... tf is organizing the feedback it's received ... request to publish probably a week or two away Other Business mjs: we've had a suggestion to require a CFC to add features to HTML 5.1 and perhaps other specs ... the chairs are somewhat receptive to this, but there are many details that would need to be worked out ... first, which deliverables ... 5.1 likely, new extension specs unlikely, canvas a grey area ... important to define what happens if the CfC passes ... does that mean that no one gets to object to the feature in the future ... if fails, could someone use the decision process to get it in anyway ... these are some of the things we'd have to define in order to have such a policy janina: it's not clear how issues get reopened for 5.1 (that were resolved in 5.0) ... we want to clearly mark in bugs that things are open for 5.1 but resolved for 5.0 Other other business Scribe for next meeting hober: when is the next meeting? holiday cancellations, etc. mjs: dec 20 and 27 will be cancelled ... next meeting is jan 3 janina: a11y tf will meet next week, then not until jan 10 Adjournment mjs: we are adjourned Summary of Action Items
Received on Thursday, 13 December 2012 17:45:06 UTC