See also: IRC log
<trackbot> Date: 07 February 2013
<scribe> scribe: LeonieWatson
JB: Status is that there are gaps, and we're aiming to have agreement about the changes needed by this coming Monday.
PC: Suggest one of the TF chairs send a note to the WG list, as last week on the WG call we were expecting this to be ready tomorrow.
SF: Ok.
SF: Status is that Janina needs
to respond to Robin about this.
... General message from Robin was to file bugs and we'll get
it moving.
JF: Are you still taking bugs on that document?
SF: Yes.
PC: John, it's Alt text in HTML that's blocked.
JF: Thanks, will follow up with Steve.
JS: I have a draft response to
Robin that's almost ready.
... I want to be sure we're clear about all the pieces before
we respond.
... I'm not sure we've evaluated everything.
PC: I'm a little flabbergasted. Several times on this call we've discussed solving specific problems. Why can't we just file bugs on the simple stuff?
JS: On the alt text in the spec, yes we can. The authoring guidance is the problem. If we could remove that guidance and replace it with Steve's document...
PC: Let's not delay filing bugs on the second part of the doc, let's get them filed and fixed.
JS: I don't see a problem, providing we understand that's only part of what we need to address.
JB: Agree with Paul, but we do need to address the authoring guidance too.
<MichaelC> Media bugs discussion from last week
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=11593
JF: We can let this one go.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=12545
SF: Silvia is happy to close thise one.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13692
<Stevef> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13692
<paulc> works for me
<Judy> --- Text bug processing background, update, and links ---
<Judy> Leonie's Dec 4 bug processing request to text subteam
<Judy> http://lists.w3.org/Archives/Public/public-html-a11y/2012Dec/0013.html
<Judy> List of text bugs to process
<Judy> <http://tinyurl.com/ckoq2cd>
<Judy> Minutes from initial processing round of 11 Dec 2012
<Judy> http://lists.w3.org/Archives/Public/public-html-a11y/2012Dec/0054.html
<Judy> which documented recommended actions on the following bugs
<Judy> 9216, 10642, 13461, 13727, 13728
<Judy> but also resulted in a request for additional bugzilla component to more clearly tag things to the TF
JB: Was a component added that would help us tag these bugs?
JS: We have an HTML A11y component now I think.
PC: My concern is that all other components are aligned to specs, and this one wouldn't be. I don't undertand why you'd have a component that doesn't relate to a specific spec.
TOC: I wonder if we could just assign to specific people?
PC: That's what the assignee field is for.
<Judy> http://lists.w3.org/Archives/Public/public-html-a11y/2012Dec/0054.html
<Judy> List of text bugs to process
<Judy> <http://tinyurl.com/ckoq2cd>
<Judy> Minutes from initial processing round of 11 Dec 2012
<Judy> http://lists.w3.org/Archives/Public/public-html-a11y/2012Dec/0054.html
<Judy> which documented recommended actions on the following bugs
<Judy> 9216, 10642, 13461, 13727, 13728
JB: 9215, suggested deferring this to 5.1.
<Judy> https://www.w3.org/Bugs/Public/show_bug.cgi?id=9215
PC: Choose HTML 5.0 for the 5.1 spec, and HTML CR for HTML 5.0.
<MichaelC> Bugs organization (view entire thread for full context)
JB: Reopend in HTML spec. That's ok.
PC: Seems this is related to alt techniques in HTML?
SF: The bug says these things are missing from the spec.
PC: Wonder if the alt spec should point to this bug?
SF: Ok.
JF: Poster alt.
JB: Status?
JF: The issue of poster and
short/long descriptions was escalated to an issue, and the
issue was deferred.
... Thinking was to resolve with ARIA. So think we can leave
this "as is".
JB: Can verify.
JF: Ok, done. Should we remove the tracker keyword?
PC: Looking it up, this is marked as postponed.
<Judy> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13461
JB: Thought this one needed a TF component, because it was the sort of thing tha would go into an extension and so wouldn't be tied to the schedules of other components.
PC: This bug is about longdesc, if you want to put it somewhere... As soon as you get longdesc out the component for this bug should be changed to longdesc.
JB: Text team is not meeting at the moment.
PC: Regrets for next week's call.
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: LeonieWatson Inferring ScribeNick: LeonieWatson WARNING: No "Present: ... " found! Possibly Present: Apple Cynthia_Shelly IPcaller JB JF JS Janina_Sajka John_Foliot Judy MichaelC Michael_Cooper Microsoft P12 P13 P15 P16 P2 PC SF Steve_Faulkner Stevef TOC chaals chaals1 hober html-a11y https inserted joined onie_Watson paulc trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 07 Feb 2013 Guessing minutes URL: http://www.w3.org/2013/02/07-html-a11y-minutes.html People with action items:[End of scribe.perl diagnostic output]