16:51:59 RRSAgent has joined #pf 16:51:59 logging to http://www.w3.org/2015/12/16-pf-irc 16:52:01 RRSAgent, make logs public 16:52:03 Zakim, this will be WAI_PF 16:52:03 I do not see a conference matching that name scheduled within the next hour, trackbot 16:52:04 Meeting: Protocols and Formats Working Group Teleconference 16:52:04 Date: 16 December 2015 16:53:11 agenda? 16:53:16 zakim, clear agenda 16:53:16 agenda cleared 16:55:04 genda+ preview agenda with items from two minutes 16:55:04 agenda+ APA Housekeeping Reminders http://www.w3.org/2015/10/apa-charter.html 16:55:04 agenda+ Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open 16:55:04 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 16:55:06 agenda+ Community Groups http://www.w3.org/community/groups/ 16:55:06 agenda+ Tracker Migration 16:55:09 agenda+ Other Business 16:55:11 agenda+ next and future meetings http://www.w3.org/Guide/1998/08/teleconference-calendar#s_273 16:55:14 agenda+ Adjourn sine die 16:56:07 present+ janina 16:56:13 zakim, next item 16:56:13 agendum 1. "APA Housekeeping Reminders http://www.w3.org/2015/10/apa-charter.html" taken up [from janina] 16:56:28 zakim, clear agenda 16:56:28 agenda cleared 16:57:12 agenda+ preview agenda with items from two minutes 16:57:12 agenda+ APA Housekeeping Reminders http://www.w3.org/2015/10/apa-charter.html 16:57:12 agenda+ Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open 16:57:12 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 16:57:14 agenda+ Community Groups http://www.w3.org/community/groups/ 16:57:14 agenda+ Tracker Migration 16:57:17 agenda+ Other Business 16:57:19 agenda+ next and future meetings http://www.w3.org/Guide/1998/08/teleconference-calendar#s_273 16:57:22 agenda+ Adjourn sine die 16:57:31 zakim, next item 16:57:31 agendum 2. "APA Housekeeping Reminders http://www.w3.org/2015/10/apa-charter.html" taken up [from janina] 16:57:35 present+ Janina 16:57:39 chair: Janina 16:58:51 LJWatson has joined #pf 17:00:10 cyns has joined #pf 17:01:56 present+ LJWatson 17:03:04 fesch has joined #pf 17:03:14 present+ fesch 17:03:16 present+ Joanmarie_Diggs 17:03:29 scribe: fesch 17:03:43 richardschwerdtfeger has joined #pf 17:04:46 present+ 17:05:15 JF has joined #PF 17:05:23 present+ JF 17:05:36 js: this is the last meeting of PF! When we come back in January we will be APA. 17:06:06 jn: csun in march, anyone planning on a face-to-face? 17:06:42 rs: it is up in the air whether ARIA will meet at CSUN. 17:07:27 jf: I have heard someone is trying to organize something on the Saturday (hackathon), so any f-f should be before 17:07:40 jemma_ku has joined #pf 17:07:52 jongund has joined #pf 17:07:56 js: we need 60 days in advance to arrange a face-to-face... unlikely 17:08:32 Gottfried has joined #pf 17:09:04 present+ JaeunJemmaKu 17:09:45 zakim, next item 17:09:47 agendum 3. "Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open" taken up [from janina] 17:09:59 zakim, take up item 2 17:09:59 agendum 2. "APA Housekeeping Reminders http://www.w3.org/2015/10/apa-charter.html" taken up [from janina] 17:10:50 cs: jn: in process to join 17:11:04 js: still 3 weeks... 17:12:22 mc: will be new mailing lists, at some point pf mailing list will end (posts), tracker is being migrated (new year) 17:12:37 mc: issues will start with a large number (2000) or something 17:13:12 mc: go to the new home pages... look for new infrastructure on new home pages 17:14:49 js: will have a CFC for a new decision policy, list policy will mirror for ARIA, unless someone has an problem with that... hearing no problems, we will mirror ARIA policy 17:15:27 js: HTML task force will do minimum changes... 17:16:07 mc: HTML a11y task force - confusing now in media WG, was in HTML WG... 17:16:23 lw: HTML WG -> media WG 17:16:37 COGA moved to APA... 17:17:33 js: HTML TK needed to update docs... I thought we would be changing it to APA 17:17:54 lw: will have to find out 17:19:01 mc: in terms of changing work statements and should get formal approval for WG, wonder if we could get a joint template, were under WAI.... 17:19:54 mc: need to do that for all task forces... 17:20:42 mc: discusses names of task forces (whether to have WAI... in the name) 17:21:28 zakim, next item 17:21:28 agendum 3. "Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open" taken up [from janina] 17:22:11 action-1751 17:22:11 action-1751 -- Léonie Watson to Review push api http://www.w3.org/tr/push-api/ -- due 2015-12-16 -- OPEN 17:22:11 https://www.w3.org/WAI/PF/Group/track/actions/1751 17:22:48 action-1751 due 13 Jan 2016 17:22:48 Set action-1751 Review push api http://www.w3.org/tr/push-api/ due date to 2016-01-13. 17:23:35 mc: janina, james has actions 17:23:53 zakim, nest item 17:23:53 I don't understand 'nest item', fesch 17:24:00 zakim, next item 17:24:00 agendum 4. "new on TR http://www.w3.org/TR/tr-status-drafts.html" taken up [from janina] 17:24:33 -> http://www.w3.org/TR/css-writing-modes-3/ CSS Writing Modes Level 3 17:25:25 mc: do we need to review this? 17:27:07 mc: taking notes in the wiki 17:28:21 js: wonder if we need someone to walk us through each spec... and another to scribe in wiki... plus normal scribe 17:28:37 -> http://www.w3.org/TR/csp-embedded-enforcement/ Content Security Policy: Embedded Enforcement 17:29:29 jf: seems to be really low level... 17:30:12 -> http://www.w3.org/TR/csp-cookies/ Content Security Policy: Cookie Controls 17:31:13 rs: cookies are a privacy issues wrt accessibility 17:31:58 mc: wonder if we should look at it... 17:32:21 jf: not sure how important cookies are for work Greg is doing... 17:32:37 jn: app would need to support those cookies... 17:33:07 From the Draft Spec: 17:33:10 4. Security Considerations 4.1. Existing Cookies Note that the mechanisms defined here do not protect against cookies that already exist in a user’s cookie store. Those cookies are delivered along with the HTTP request, before Content Security Policy can be delivered and applied. It is possible that future work like [CSP-PINNING] might enable these kinds of a priori restrictions, but, even then, CSP should be seen as a mitigation strategy, layered on top of filter 17:33:32 rs: if they use local data storage may have used a flow manager... may not be using cookies any more 17:34:27 mc: we should review it 17:34:58 jf: may be a question to the spec author 17:35:24 js: may only have potential... I wouldn't ask them if there is an accessibility issue or not 17:35:46 js: could ask Katie 17:36:38 mc: lets give Katie an action, just so someone has an action 17:36:58 js: can reassign if need be 17:36:59 action: Katie to review http://www.w3.org/TR/csp-cookies/ Content Security Policy: Cookie Controls to see if a11y issues or not - due 20 Jan 2016 17:36:59 Created ACTION-1762 - Review http://www.w3.org/tr/csp-cookies/ content security policy: cookie controls to see if a11y issues or not [on Katie Haritos-Shea - due 2016-01-20]. 17:37:16 action-1762? 17:37:16 action-1762 -- Katie Haritos-Shea to Review http://www.w3.org/tr/csp-cookies/ content security policy: cookie controls to see if a11y issues or not -- due 2016-01-20 -- OPEN 17:37:16 https://www.w3.org/WAI/PF/Group/track/actions/1762 17:39:14 zakim, next item 17:39:14 agendum 5. "Community Groups http://www.w3.org/community/groups/" taken up [from janina] 17:39:22 zakim, close item 17:39:22 I don't understand 'close item', fesch 17:39:29 zakim, close this item 17:39:29 agendum 5 closed 17:39:30 I see 4 items remaining on the agenda; the next one is 17:39:30 6. Tracker Migration [from janina] 17:39:34 zakim, next item 17:39:34 agendum 6. "Tracker Migration" taken up [from janina] 17:41:00 mc: after migration PF tracker will become editable, you will have to look in APA tracker, will update IRC associations... 17:41:10 mc: that should be transparent 17:42:12 js: we kept some items in our tracker - a lot of OLD actions, some we never closed, but at least a couple dozen to return to when we can - wondering whether MC and I should take a first pass or do it as a group? 17:42:26 mc: I was only going to migrate open actions 17:42:48 mc: would be good to cleanup but by default open actions will migrate 17:43:03 js: I will take a pass.... 17:43:49 mc: would have to be cleaned up after migration if not before... 17:44:15 cs: is that for PF and ARIA actions? 17:44:31 mc: yes - some will migrate to APA others to ARIA.... 17:44:53 cs: sticking with tracker? not going to github or...? 17:45:20 mc: yes, good integration with IRC, too useful to abandon 17:45:40 mc: we use github and moved away from bugzilla... 17:45:57 cs: OK just wanted to know where they are going 17:46:21 js: IRC integration is really useful... 17:46:42 zakim, next item 17:46:42 agendum 7. "Other Business" taken up [from janina] 17:46:52 s/will become editable/will become uneditable/ 17:47:47 js: we have an open CFC for MFC extensions, discussed them at TF 17:48:18 js: some folks wanted to bring up longdesc again 17:48:42 q+ 17:49:05 js: please respond either positive or negative 17:49:12 ack l 17:49:35 lw: which working group is owned by? 17:49:57 js: media... was traditionally joint with HTML TF 17:51:23 js: our comments are not particularly technical, we asked for a longdesc or possibly use accessible SVG... some folks want a more generic statement 17:51:39 js: but a11y folks are the folks that give advice how to do that 17:51:48 js: first diagram is a png 17:52:01 Q+ 17:52:16 js: we have API's being defined but not much plain text (prose) to introduce the sections... 17:53:05 js: issue raised whether this is the place for suggesting alternative media... no not in this spec 17:53:43 js: would be useful to have an overview of how W3C spec fit together... 17:53:49 ack jf 17:54:42 jf: I weighted in on longdesc, has a complex graphic, needs a description how it does it, I don't care how it does it. Needs a description. 17:55:14 q+ 17:55:45 js: I don't think using a CFC to complain about longdesc gets in the way, they can ask to have the issues re raised... 17:56:43 jf: what we should have said is the image needs a long description (not longdesc)... 17:56:58 js: we are offering to help solve the compliant 17:57:24 lw: we should have described every possible approach how to solve the problem 17:57:37 q? 17:57:46 lw: John's approach probably wouldn't raise a complaint 17:57:48 ack lw 17:57:54 ack me 17:58:42 ShaneM has joined #pf 17:58:50 s/we should have described every possible approach how to solve the problem/If we described one solution we should have described multiple solutions for achieving the goal/ 17:59:06 js: if people feel that we should take that approach that is fine, then a +1 with the change... would be fine... right now I have to rely on the silence 17:59:40 jf: I will take an action to write a long description of the image... 18:00:24 js: do we have a consensus? need more +1s or -1s on record 18:00:38 rrs agent, make minutes 18:00:40 ACTION: JF to write up the longer text description for the MSE spec Due January 16, 2016 18:00:40 Created ACTION-1763 - Write up the longer text description for the mse spec due january 16, 2016 [on John Foliot - due 2015-12-23]. 18:00:57 zakim, next item 18:00:57 agendum 8. "next and future meetings http://www.w3.org/Guide/1998/08/teleconference-calendar#s_273" taken up [from janina] 18:01:30 PF is now adjourned! 18:02:19 rrsagent, make minutes 18:02:19 I have made the request to generate http://www.w3.org/2015/12/16-pf-minutes.html fesch 18:10:26 fesch has left #pf