mjs: expecting this to be short meeting
... next 2 or 3 weeks will be more busy

Action Items Pending Review

mjs: none

ACTION items due by Thu Mar 18

mjs: none

Call For Consensus that close by Mar 18

mjs: none

Call for Proposals that close by Thu Mar 18

mjs: none

Items that close next week

ISSUE-31?

<trackbot> ISSUE-31 -- What to do when a reasonable text equivalent is unknown/unavailable? -- OPEN

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

<pimpbot> Title: ISSUE-31 - HTML Weekly Tracker (at www.w3.org)

mjs: number of proposals already - closes Mar 23
... questions?

ISSUE-41?

<trackbot> ISSUE-41 -- Decentralized extensibility -- OPEN

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

<pimpbot> Title: ISSUE-41 - HTML Weekly Tracker (at www.w3.org)

mjs: again closes on tuesday
... received at least 3 different proposals from 2 people
... holding open in case anyone wants to submit another or volunteer
... discussion ongoing on the mailing list
... questions?

rob: discusssion may generate alternative

ISSUE-80?

<trackbot> ISSUE-80 -- document conformance and device dependent display of title attribute content -- OPEN

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

<pimpbot> Title: ISSUE-80 - HTML Weekly Tracker (at www.w3.org)

mjs: also closes Mar 23 - related to issue 31
... only one of issue 31 proposals tackles this

<MikeSmith> issue-31

<MikeSmith> issue-31?

<trackbot> ISSUE-31 -- What to do when a reasonable text equivalent is unknown/unavailable? -- OPEN

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

<pimpbot> Title: ISSUE-31 - HTML Weekly Tracker (at www.w3.org)

ISSUE-86?

<trackbot> ISSUE-86 -- HTML5 relaxes Atom requirement on atom:id stability -- OPEN

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

<pimpbot> Title: ISSUE-86 - HTML Weekly Tracker (at www.w3.org)

mjs: think we have a volunteer
... due next tuesday

ISSUE-88?

<trackbot> ISSUE-88 -- Should meta/@content allow a list of languages instead of just a single language? -- OPEN

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

<pimpbot> Title: ISSUE-88 - HTML Weekly Tracker (at www.w3.org)

mjs: call for counter proposals on this one
... change proposal submitted and ongoing discussion
... waiting to see if we have counters to the proposal
... remaining 2 items are due mar 25

ISSUE-32?

<trackbot> ISSUE-32 -- how to provide a summary of a table, e.g. for unsighted navigation? -- OPEN

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

<pimpbot> Title: ISSUE-32 - HTML Weekly Tracker (at www.w3.org)

mjs: expecting revised change proposal

<richardschwerdtfe> please add me on agenda for issue-74

mjs: a11y tf may not be able to deliver by the due date
... will ask for new due date if necessary

<mjs> richardschwerdtfe, will do (after official agenda)

<richardschwerdtfe> thanks

ISSUE-82?

<trackbot> ISSUE-82 -- Suggested replacement for head/@profile does not provide for disambiguation -- OPEN

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

<pimpbot> Title: ISSUE-82 - HTML Weekly Tracker (at www.w3.org)

mjs: change proposal due thur mar 25

New Calls for Proposals/Consensus this Week

ISSUE-78?

<trackbot> ISSUE-78 -- Spec should use a term other than "URL" for Web Addresses -- RAISED

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

<pimpbot> Title: ISSUE-78 - HTML Weekly Tracker (at www.w3.org)

mjs: only issue not yet asked for proposals
... all issues now in pipeline

New Issues This Week

mjs: none

julian: wanted to note that closed issue-79 with resolution for editor to update spec
... do we need some tracking for pending review issues

mjs: in accordance with decision policy we reopened the bug
... tagged with WGDECISION keyword
... it is being tracked via bugzilla

julian: ok

mjs: richard - issue 74

issue-74?

<trackbot> ISSUE-74 -- How accessibility works for <canvas> is unclear. -- OPEN

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

<pimpbot> Title: ISSUE-74 - HTML Weekly Tracker (at www.w3.org)

richard: a11y tf come to decision for canvas to have new attribue
... by default content in canvas is in keyb nav order
... provides opportunity to turn off if desired
... still need to address focus and caret navigation for magnifier

<richardschwerdtfe> http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibilitynonav

<pimpbot> Title: ChangeProposals/canvasaccessibilitynonav - HTML WG Wiki (at www.w3.org)

richard: this is the proposal for people to look at

mjs: would appreciate if someone could sent to public-html when TF ready

<MikeSmith> issue-74?

<trackbot> ISSUE-74 -- How accessibility works for <canvas> is unclear. -- OPEN

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

<pimpbot> Title: ISSUE-74 - HTML Weekly Tracker (at www.w3.org)

mjs: can then record as change proposal for issue 74
... we do already have proposal submitted for caret nav and focus issue

<MikeSmith> issue-74: see change proposal - http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibilitynonav

<trackbot> ISSUE-74 How accessibility works for <canvas> is unclear. notes added

<pimpbot> Title: ChangeProposals/canvasaccessibilitynonav - HTML WG Wiki (at www.w3.org)

mjs: has been some discussion of details

richard: good to have this important discussion
... will submit to public-html after call

mjs: thanks

verifying resolved bugs

mjs: sent mail to the list about this process

<mjs> http://bit.ly/da3rUe

<pimpbot> Title: Bug List (at bit.ly)

mjs: this is list of bugs now in verified state
... need people to review
... any that don't get response by april 12 will be considered comments with no reply from commenter on decision
... if you are interested in any of these, either move to close if accept decision
... or reopen if you want fresh consideration
... or tracker keyword if want to escalate to issue tracker
... prefer as many as possible get reply from original commenter
... hope people will do that
... if in the process you find any other bugs you can close or escalate
... that would be appreciated
... any other business?

<rubys1> scribe?

Scribe for next meeting

mjs: any volunteers?

julian: might be good to remind people that ietf meeting is next week

<paulc> Either Sam or Paul will chair next week

julian: might be several meetings including cookie, hybi, iri, http that could be interesting

<paulc> If Sam chairs then Paul will volunteer to scribe.

julian: can use xmpp or listed to audio stream

<MikeSmith> cookie = http-state , right?

<Julian> yes

<Julian> See: http://greenbytes.de/tech/webdav/

<pimpbot> Title: greenbytes WebDAV resources (at greenbytes.de)

mjs: thanks, definitely wg with cross interest

<Julian> actually http://greenbytes.de/tech/webdav/#news

<pimpbot> Title: greenbytes WebDAV resources (at greenbytes.de)

mjs: encourage participation if interested
... next week w3c ac and tag are meeting

<paulc> Can Julian provide links to the remote participation techniques?

mjs: sam and paul will be there
... will update us after
... ECMA TC-39 meeting also

<Julian> paulc, they are in the news item I posted

mjs: paul willing to scribe if sam chairs
... if paul chairs, maciej will scribe

<paulc> Adjourn at :23 after the hour.

<cardona507> thanks everyone