<trackbot> Date: 21 July 2011

<pimpbot> Title: {agenda} HTML WG telecon 2011-07-21: Task Force reports, Last Call change control, Decision Policy from Maciej Stachowiak on 2011-07-20 (public-html-wg-announce@w3.org from July to September 2011) (at lists.w3.org)

<rubys> ...Maciej should be here momentarily...

ACTION items due by Thursday, July 21

mjs: there are none

New Issues This Week:

mjs: there are none

Items Closed Last Week

mjs: there are none

Items Closing This Week

mjs: there are none

Items Closing Next Week

ISSUE-153?

<trackbot> ISSUE-153 -- link type "external" either not useful or underspecified -- open

<trackbot> http://www.w3.org/html/wg/tracker/issues/153

<pimpbot> Title: ISSUE-153: link type "external" either not useful or underspecified - HTML Weekly Tracker (at www.w3.org)

mjs: Call for Counter-Proposals closes Jul 28

ISSUE-154?

<trackbot> ISSUE-154 -- "sidebar" might not be a proper use of a link relation -- open

<trackbot> http://www.w3.org/html/wg/tracker/issues/154

<pimpbot> Title: ISSUE-154: "sidebar" might not be a proper use of a link relation - HTML Weekly Tracker (at www.w3.org)

mjs: Call for Counter-Proposals closes Jul 28
... both issues about link relations

ISSUE-166?

<trackbot> ISSUE-166 -- text/html-sandboxed does not always fail closed -- raised

<trackbot> http://www.w3.org/html/wg/tracker/issues/166

<pimpbot> Title: ISSUE-166: text/html-sandboxed does not always fail closed - HTML Weekly Tracker (at www.w3.org)

mjs: Change Proposals due Jul 28

ISSUE-167?

<trackbot> ISSUE-167 -- Remove the crossorigin attribute and CORS normative dependency -- raised

<trackbot> http://www.w3.org/html/wg/tracker/issues/167

<pimpbot> Title: ISSUE-167: Remove the crossorigin attribute and CORS normative dependency - HTML Weekly Tracker (at www.w3.org)

mjs: Change Proposals due Jul 28

New Calls this week

mjs: there are none

New Surveys this week

mjs: there are none
... will not start any more surveys until the end of the LC comment period on 8/4

Decisions this week

mjs: there are none

Task Force Reports

Testing Task Force report

krisk: met last week

<krisk> Here notes http://lists.w3.org/Archives/Public/public-html-testsuite/2011Jul/0004.html

<pimpbot> Title: RE: HTML Testing Task Force Conf Call Agenda 7/12/2011 from Kris Krueger on 2011-07-21 (public-html-testsuite@w3.org from July 2011) (at lists.w3.org)

krisk: group agreed to use html5lib test format going forward
... new tests from mozilla
... there are authoring guidelines available

<krisk> http://www.w3.org/html/wg/wiki/Testing/Authoring

krisk: microsoft has submitted some structured clone algorithm tests
... opera has also submitted tests
... TF meets on 7/26

Accessibility Task Force report

janina: not much to report
... have asked people to read through the spec to look for a11y issues
... long call next thursday to process those reports
... media subgroup have 3 unresolved issues, waiting on PoCs
... text subgroup will make some comments on longdesc, canvas a11y, etc.
... asking tf participants to focus on bugs

Other Business

ISSUE-134?

<trackbot> ISSUE-134 -- Provide tablist and tab states for menu and command elements respectively -- open

<trackbot> http://www.w3.org/html/wg/tracker/issues/134

<pimpbot> Title: ISSUE-134: Provide tablist and tab states for menu and command elements respectively - HTML Weekly Tracker (at www.w3.org)

CP on ISSUE-134: http://lists.w3.org/Archives/Public/public-html/2011Jul/0235.html

<pimpbot> Title: Re: CfC: Close ISSUE-134 tab-states by Amicable Resolution from Tab Atkins Jr. on 2011-07-14 (public-html@w3.org from July 2011) (at lists.w3.org)

mjs: in the future, we will be stricter about the CfC deadline
... this is a one-time exception
... have filed bug on decision policy to clarify this going forward
... Last Call change control and non-bugzilla changes http://lists.w3.org/Archives/Public/public-html/2011Jul/0286.html

<pimpbot> Title: Thoughts on restricting non-bugzilla-driven spec changes during Last Call from Maciej Stachowiak on 2011-07-20 (public-html@w3.org from July 2011) (at lists.w3.org)

mjs: looking at what sort of change control should be applied, email is quite detailed
... strongly encourage wg participants to read that email
... there are 3 key process requirements affected by spec changes happening during LC
... 1) formal requirement to address all issues received during LC
... 2) must have documentation of all changes since the previous step (entering last call)
... there's a Process distinction between minor and substantive changes
... substantive changes are changes that invalidate previous review or impl report
... minor changes only require reporting diff
... Process requires us to provide meaningful summary of substantive changes
... substantive changes made after entering LC require issuing another WD, can't proceed straight to CR
... we knew going into this LC that there woulud be substantive changes in certain areas etc.
... must fulfill documentation requirement
... we will have to have an LC period in which we don't make substantive changes
... there are a number of changes made to the spec that are from comments not at the w3c
... also rdfa-in-html spec has changes made due to comments in the rdfa wg, not just an issue with the html5 spec

janina: should people be commenting on the may 25th LCWD or a july ED? (question came up in a11y tf)

mjs: up to the reviewer
... May 25th draft is frozen, so it won't change during review
... the EDs have ongoing changes, including LC comments
... issues may already have been fixed, there may be new problems
... ED probably tracks what will be in a future LC

paulc: it's always possible to get the static version by following the dated links
... we'll always process LC comments on the LCWD
... it's also valid as an LC comment to request revert of changes happening in the ED

mjs: Decision Policy update plans http://lists.w3.org/Archives/Public/public-html/2011Jul/0287.html

<pimpbot> Title: Decision Policy update plans from Maciej Stachowiak on 2011-07-20 (public-html@w3.org from July 2011) (at lists.w3.org)

mjs: have been working on the Decision Policy 'v2' draft
... will be presenting a CfC to the WG to adopt the v2 Decision Policy
... please review v2 draft and file bugs
... Any other business?

Scribe for next meeting

<adrianba> i can scribe next week

Adjournment

<paulc> rssagent, generate minutes

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/chris/krisk/
No ScribeNick specified.  Guessing ScribeNick: hober
Inferring Scribes: hober

WARNING: No "Present: ... " found!
Possibly Present: Apple Cynthia_Shelly MarkF_ Microsoft Mike MikeSmith Norm P32 Radhika_Roy Sam Title aaaa aabb aacc aadd adrianba dpenkler eliot hober html-wg janina joined konaya krisk mjs paulc pimpbot rubys trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Agenda: http://lists.w3.org/Archives/Public/public-html-wg-announce/2011JulSep/0004.html

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 21 Jul 2011
Guessing minutes URL: http://www.w3.org/2011/07/21-html-wg-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.