See also: IRC log
<trackbot> Date: 12 November 2014
<janina> agenda: this
<scribe> scribenick: joanie
JS: Two minutes around the table.
Any news?
... TPAC followup? Anything?
JS: TPAC minutes were all done in
public space.
... So we don't need to approve those.
... We do need to approve the Wednesday meeting before
TPAC.
... Any additions, changes, or other edits?
... Objects to posting the minutes as submitted?
<janina> /Objects/Objections/
RESOLUTION: The minutes from the Wednesday meeting before TPAC will be published as submitted.
JS: We're coming up on the end of
the year.
... That means quite a few holidays for many people.
... Traditionally, this group doesn't meet the last two weeks
at the end of the year.
... Sometimes we also don't meet the day before
Thanksgiving.
... Christmas Eve and New Years Eve we will not meet.
... No meeting on the 26th of November.
... Resume January 7th.
... Each of our subteams is welcome to make their own
schedules.
... I'm quite confident that most of our groups will take time
off at the end of the year.
... On the Monday call, many people indicated they'd be
there.
... The Americans can do what they see fit. :)
... Comments or questions re planned holiday schedule?
JS: Michael?
action-1522
<trackbot> action-1522 -- James Nurthen to Try to find an example where user style sheet cannot override author intent -- due 2014-11-07 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1522
MC: [Reads issue]
<MichaelC> action-1522 due 1 week
<trackbot> Set action-1522 Try to find an example where user style sheet cannot override author intent due date to 2014-11-19.
JN: Another week.
action-1518
<trackbot> action-1518 -- Joanmarie Diggs to Draft comment on selection api http://www.w3.org/tr/2014/wd-selection-api-20141007/ -- due 2014-10-22 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1518
<janina> scribe: janina
jd:
<MichaelC> jd: discussed at TPAC
No need for comments at this point, excellent and thorough discussion during TPAC
<MichaelC> filed stuff in their issue tracker
<MichaelC> am following so will catch new issues
jd: Expect will have some questons
<joanie> scribenick: joanie
action-1517
<trackbot> action-1517 -- Janina Sajka to Figure out why canvas 2d hit region testing wasn´t put in the spec -- due 2014-10-08 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1517
<MichaelC> close action-1517
<trackbot> Closed action-1517.
MC: I thought we were going to close this.
JS: confirmed.
action-1503
<trackbot> action-1503 -- Lisa Seeman to Review css counter styles level 3 http://www.w3.org/tr/2014/wd-css-counter-styles-3-20140826/ -- due 2014-09-10 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1503
LS: Put me down for another
week.
... We wrote a response and we're not sure if they reacted to
it.
MC: This was a due diligence
review.
... We commented on their list and just wanted to make sure
everything was still OK.
... I'm wondering if we feel this is priority enough to file
comments.
JS: We really should have looked, but it's rather late.
<MichaelC> close action-1503
<trackbot> Closed action-1503.
JS: Let's just close it.
MC: There's a whole bunch of
xquery, xpath, xslt, ....
... There's like six of them
... [Reads titles]
... It's all 3.1 versions.
... I think we've typically been skipping these.
JS: Agreed.
JS: I think as far as us and the
SVG WG we are done.
... All i's dotted and t's crossed.
... There is a completed work statement.
... It's almost the same as the CfC approved one.
... The differences are not things that are up to us.
... I don't recall if there was a wording change around the
mailing list we were setting up.
... There was a question about what "public" means: Readable or
also Writable.
... SVG is RW so we're going with that.
MC: Comments will go straight to
the mailing list.
... This is not reflected in the work statement.
<MichaelC> SVG A11Y TF mailing list
MC: Subscribing to the list is
also not limited to group membership.
... Nominally to join the task force, you should join one of
the working groups.
... I don't think Doug wants that infrastructure.
... If you go to the URL I put in, you can subscribe to the
mailing list.
... Which means we don't know if you're a member of PF or
SVG.
... But Philippe said Doug will deal with that.
... I don't know if there will be a formal joining
procedure?
JS: I think Rich's last comment was to get the group started after Thanksgiving.
JS: We have a quarterly task to
review new community groups.
... We have about a dozen groups to look at.
MC: There's only 3 CGs older than 3 months.
<MichaelC> Web Bluetooth Community Group
MC: The first of them is Web
Bluetooth CG (link above)
... [Reads description of the group]
<fesch> got to drop
MC: 32 participants, no
chairs.
... 51 messages in the early days. Now just a few messages a
month.
JS: You said something about interface?
MC: [Reads and sees nothing describing that]
JS: That alone means we need to do due diligence.
MC: Looks like they attempted to
have a meeting in August, but it didn't happen.
... Put it on the "look at later" list?
JS: I think so.
LS: It's potentially extremely
useful to make sure it's integrated into IndieUI.
... See if this is relevant to ARIA 1.1.
JS: Remember this is a CG. They
cannot write specs.
... But you're otherwise correct.
<MichaelC> Open and Transparent W3C Community Group
MC: Second CG is [the
above]
... [Reads their description]
... Looking at the mailing list, it seems to be functioning as
a push list for Art to say "this is what is going on."
... I think that since this isn't defining UI we don't need to
track it.
... However, process issues do impact us.
JS: I don't think this is
something we need to track.
... We get pushed on the point of being public or not from time
to time.
... We give the smae explanations, but it doesn't really go
anywhere.
... There's nothing really new from our perspective. And that's
probably the best we can say.
MC: There's a lot of w3c teams following this.
JS: The trick is how to make all the pieces work together well.
SM: And also how do you keep the lights on.
MC: The third is credentials CG
<MichaelC> Credentials Community Group
MC: [Reads from above]
... So... I'm not sure how to summarize all of that.
... No chair. 36 participants.
SM: It's a big deal, and I'm monitoring it.
MC: Do we want to actively track it?
SM: Yes.
... This fell out of the web payments activity. Which I also
monitor.
MC: I guess we're set.
JS: On the ones that are more
than three months old.
... Did we say how often we'd review, prune our list, etc.?
MC: I don't think we decided
that.
... Maybe every six months at most; every year at least.
JS: So our next review would be around January-March or July-Sept.
MC: New Year and Mid Year is memorable.
JS: Thoughts?
... I propose we look at this again, I guess until we find out
we can be looser, let's aim at twice a year.
... So the first quarter of 2015.
... Any objections?
SM: I don't object. I assume that if something comes up before then, I should just raise it.
JS: Absolutely.
... The purpose of the occasional review is to be sure we're
covered.
JS: Rich is not here.
... Not sure what to say around this topic other than an
enormous amount of activity seems to have resulted from TPAC
work.
... This is wonderful.
... Probably there is more coming because there's another task
force that is finishing its formation, namely DPub.
... We did agree to try to get some heartbeats out before year
end.
... Anything else?
JS: Both HTML WG and us (PF)
approved to move longdesc to PR status.
... WG approvals are finished.
... We are negotiating for a time to have a Director's
meeting.
... The Director will look to verify we've fulfilled all our
requirements.
... We hope this will happen next Monday.
... We do not anticipate any problems.
... What follows is 30 days of voting to move this
forward.
... We do not know if there will be any more controversy in the
AC.
... Re Media, we're trying to close a number of comments from
EO on MAUR.
... hopefully we can resume meetings of that subteam
soon.
... Publications moratorium is 19 December.
... We might be able to publish this content as a note.
... At TPAC we took a decision to do work beyong publishing a
note.
... Because members of the Japanese government, NHK, etc.
came.
... Best practices were proposed.
... Starting with clean audio. I think that's useful.
... Regarding HTML, we have new editors for Useful Text
Alternatives document.
... Some additional edits are called for, including
longdesc.
... Then there is lot of discussion in the HTML WG regarding
what the operational expectations are moving forward.
... 5.1, 5.2, 6.0, modularization, etc.
... COGA, you guys are still doing your background work,
right?
LS: We're starting to put
techniques together.
... Moving them out of the background document.
... Jan is writing about issues around security and
CAPTCHA.
... Michael and I need to work on getting that background
document out
... But the rest of the group needs to move forward on
foreground issues.
MC: What are issue papers?
LS: Like CAPTCHA.
... These pose challenges for individuals with cognitive
issues.
... Another example is two-step verification.
... This is hard for individuals with mild dementia.
... These topics would be addressed in an Issue Paper.
... Web Payments, voice email systems, voice activation
systems. These are all things we'd need to look at.
MC: So this is a precursor to techniques?
LS: Yes, and also a means to promote discussion.
JS: And a way to get to a gap
analysis.
... You could extract from the issue papers a list.
LS: And maybe even once we have
these issues discussed and fleshed out, if other people wanted
to provide input, including developers.
... They're not necessarily going to want to choose a security
issue that makes things hard for a lot of their users.
JS: I got a little worried when you said "techniques" but then you said "issues"
LS: One of the things of gaps is,
are there techniques?
... If there is a technique that addresses it, then is it
really a gap?
JS: If the techniques are not
implemented, and if the issue is a stumbling block, then this
may be a gap.
... We also need to analyze where we have a technique and where
we do not.
... Other comments, questions?
Jason: When do you anticipate having this done?
LS: I am hoping we'll have a
working draft in approximately in a month.
... Ready for review, I mean.
... Does that sound about right?
JS: Publications moratorium
starts 19 December.
... Anyone else?
... We are task-force heavy.
... And getting people to populate them, which is a very good
thing.
JS: If there is not other
business, we can adjourn for today.
... Next meeting will be next week.