15:49:02 RRSAgent has joined #pf 15:49:02 logging to http://www.w3.org/2015/05/20-pf-irc 15:49:04 RRSAgent, make logs public 15:49:04 Zakim has joined #pf 15:49:06 Zakim, this will be WAI_PF 15:49:06 ok, trackbot; I see WAI_PF()12:00PM scheduled to start in 11 minutes 15:49:07 Meeting: Protocols and Formats Working Group Teleconference 15:49:07 Date: 20 May 2015 15:49:29 agenda? 15:50:22 Chair: Janina 15:50:22 agenda: this 15:50:22 agenda+ preview agenda with items from two minutes; Webex continued 15:50:22 agenda+ Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open 15:50:23 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html#tr_LCWD 15:50:24 agenda+ Community Groups http://www.w3.org/community/groups/ 15:50:27 agenda+ ARIA.Next Items--Extension Mechanism [See Below] 15:50:29 agenda+ Rechartering Continued 15:50:32 agenda+ Other Task Force Updates; COGA; HTML-A11Y; SVG 15:50:34 agenda+ Other Business 15:50:37 agenda+ next and future meetings http://www.w3.org/Guide/1998/08/teleconference-calendar#s_273 15:50:40 agenda+ be done 15:52:53 agenda? 15:56:25 present+ Janina 15:56:36 zakim, next item 15:56:36 agendum 1. "preview agenda with items from two minutes; Webex continued" taken up [from janina] 16:01:24 Yes, James and I are chatting 16:05:07 present+ Joanmarie_Diggs 16:09:07 Gottfried has joined #pf 16:09:27 Gottfried has left #pf 16:11:29 richardschwerdtfeger has joined #pf 16:11:35 WAI_PF()12:00PM has now started 16:11:42 +??P0 16:11:56 Rich, we're on Webex! 16:12:04 Webex 647 857 439# 16:13:08 -??P0 16:13:10 WAI_PF()12:00PM has ended 16:13:10 Attendees were 16:14:03 fesch has joined #pf 16:14:20 present+ fesch 16:14:33 present+ Michael_Cooper 16:14:40 scribe: joanie 16:14:55 present+ JamesN 16:15:28 zakim, next item 16:15:28 agendum 2. "Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open" taken up [from janina] 16:15:34 Gottfried has joined #pf 16:15:56 Janina: I'm in the middle of media. It's a long spec. 16:16:07 Janina: I need to tell them that I'm working on it still. I'll do that today. 16:16:13 MC: That would be a good idea. 16:16:22 action-1615 16:16:22 action-1615 -- Janina Sajka to Review media capture and streams http://www.w3.org/tr/mediacapture-streams/ -- due 2015-05-06 -- OPEN 16:16:22 https://www.w3.org/WAI/PF/Group/track/actions/1615 16:16:35 MC: There's a bunch of actions that are not due yet. 16:16:51 MC: Aside from media capture streams, there's nothing else under spec review. 16:16:58 zakim, next item 16:16:58 agendum 3. "new on TR http://www.w3.org/TR/tr-status-drafts.html#tr_LCWD" taken up [from janina] 16:16:59 MC: Everything else is due 27th or 29th 16:18:14 MC: Canvas 2D context is in last call. 16:18:26 Janina: We're famailiar with that via HTML A11y task force. 16:18:31 Janina: Rich is on top of that. 16:18:34 -> http://www.w3.org/TR/2dcontext/ HTML Canvas 2D Context 16:18:52 Janina: We were expecting this publication. We had some language changes last minute. 16:19:02 Janina: I'm not sure if those changes made it into last call. 16:19:14 Janina: We'll continue debugging the two implementations. 16:19:24 Janina: Then we'll have full support, including hit regions. 16:19:37 MC: About the CR, this is under the old process where it cannot easily change. 16:19:51 MC: That means we need to do things in last call. 16:20:03 FE: Rich told me hit regions was implemented in Chrome and Firefox. 16:20:13 Janina: I think both are amenable to bug reports. 16:20:28 Janina: And we'll continue to manage this in the HTML A11y task force. 16:20:34 MC: So we don't need an action in PF? 16:20:38 Janina: No 16:20:46 MC: They do not provide a last call due date. 16:20:46 Gottfried has left #pf 16:20:55 MC: That means we don't know when they'll go to CR. 16:21:06 Janina: I'll remind Paul to state that. 16:21:24 Janina: I don't think we want the spec to change in CR, but do want it to be long enough to catch bugs. 16:21:40 MC: It cannot exit CR unless it passes. 16:21:55 Janina: I'm talking about bugs in implementation; not the spec. 16:22:01 MC: CSS flexbox is up for last call. 16:22:17 MC: I believe we've reviewed it before. I know we've had concerns. 16:22:27 -> http://www.w3.org/TR/css-flexbox-1/ CSS Flexible Box Layout Module Level 1 16:22:32 MC: I'm not sure if we have anything to comment upon at this time. 16:22:45 MC: Candidate recommendations. 16:23:38 RS: Bo is participating with the CSS group and is on top of this. 16:24:10 Gottfried has joined #pf 16:24:37 -> http://www.w3.org/TR/ttml-imsc1/ TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0 16:25:01 MC: I think we took a look at this at the last CR. 16:25:22 MC: If they're in CR, there are presumably substantial changes. 16:25:29 MC: But I don't see a list of what they are. 16:25:41 WAI_PF()12:00PM has now started 16:25:48 +??P0 16:25:54 s/at this/at TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0/ 16:26:05 Janina: Would we be out of line to request a list of changes? 16:26:14 MC: It wouldn't impact this publication. 16:26:30 MC: In general, I'd like to establish some best practices for review. 16:26:38 -??P0 16:26:39 WAI_PF()12:00PM has ended 16:26:39 Attendees were 16:26:45 WAI_PF()12:00PM has now started 16:26:47 MC: They've made some changes with respect to frame rate synchronization. 16:26:52 +??P0 16:26:57 MC: There's some editorial edits here and there. 16:27:06 I am trying to get in. But it says i am the first participant on the conference. 16:27:19 Gottfried: We're on Webex: 647 857 439# 16:27:30 MC: The initial value of text align should be center; before it didn't have a default value. 16:27:30 What URL? 16:27:37 MC: Everything else looks like clarifications. 16:27:48 -??P0 16:27:49 WAI_PF()12:00PM has ended 16:27:49 Attendees were 16:28:02 https://mit.webex.com/mit/j.php?MTID=m6e3f82ceee1b44268fd496d928c40001 16:28:22 MC: Agreed that we don't need to review this? 16:28:28 Janina: I don't think we need to review it. 16:28:32 MC: Web Notifications 16:28:35 -> http://www.w3.org/TR/notifications/ Web Notifications 16:28:47 MC: This one is under the new process. 16:29:00 MC: I have the sense we've looked at this before. I don't recall if we had concerns. 16:29:07 Janina: We did, concerns about an icon. 16:29:15 Janina: But I think we backed off. 16:29:26 MC: Reads from spec. 16:29:35 Janina: I think that was the result of our comments. 16:29:49 MC: There's no obvious ChangeLog. 16:30:33 MC: Three specs from us and two from HTML which use "ARIA" in their titles. 16:30:55 Janina: We got review on the Notes on using ARIA in HTML. 16:31:12 MC: The names of the two documents confuses me. 16:31:19 Janina: Both are Steve's. 16:31:31 Janina: The Notes document is basically best practice. 16:32:08 Janina: There was quite a lot of discussion on list. Everyone approved publication. 16:32:27 Janina: We need to be sure Notes and the ARIA Authoring Practices remain in sync. 16:32:37 MC: I see this is REC track. Is that correct? 16:32:43 Janina: No. 16:33:13 Janina: Action me to point this out. 16:33:54 action: janina to file comment on Notes on Using ARIA in HTML http://www.w3.org/TR/aria-in-html/ that it should not be on the Rec track 16:33:54 Created ACTION-1641 - File comment on notes on using aria in html http://www.w3.org/tr/aria-in-html/ that it should not be on the rec track [on Janina Sajka - due 2015-05-27]. 16:34:44 MC: There is now a means to publish more frequently via a new automated tool. 16:35:06 MC: The current version of this tool doesn't yet support non-REC-track documents. 16:35:43 MC: The tool should allow NOTE-track documents to also be published. 16:35:49 Janina: Did they even think about it? 16:36:02 MC: Yes, there's documentation stating that you cannot publishing NOTE-track stuff. 16:36:14 MC: Which is why I haven't moved us to that process yet. 16:36:29 Janina: ARIA in HTML is the breakout of the section that talks about ARIA conformance. 16:36:50 Janina: We had a lot of discussion about not having joint ownership of this document. 16:37:06 Janina: And that document is on the automated process, and it is REC-track. 16:37:20 Janina: We need to proactively review it from time to time now as a result. 16:37:47 Janina: This is a coordination question we haven't talked about yet. 16:38:13 Janina: If the group splits, the review working group would need to stay on top of things remaining in sync. 16:38:31 Janina: And it will be up to the ARIA group to decide about joint ownership or not. 16:38:59 MC: There are two other docs that are working drafts. 16:39:04 Zakim, next item 16:39:04 agendum 4. "Community Groups http://www.w3.org/community/groups/" taken up [from janina] 16:39:19 present+ Gottfried 16:39:36 jamesn has joined #pf 16:39:53 MC: I had gotten a month ahead of our three-month advance. 16:40:05 MC: So we don't have any new community groups to look at as a result. 16:40:14 Zakim, next item 16:40:14 agendum 5. "ARIA.Next Items--Extension Mechanism" taken up [from See Below] 16:40:29 Janina: Rich, we have an extension definition. 16:40:37 Janina: And we want a formal consensus? 16:41:08 https://www.w3.org/WAI/PF/wiki/ARIAExtensions 16:41:13 RS: We ran into an issue with Digital Publishing. 16:41:42 RS: We need to be able to extend ARIA without impacting ARIA core. 16:42:03 RS: So the Extensions proposal allows other groups to write an extension module. 16:42:13 https://www.w3.org/WAI/PF/wiki/ARIAExtensions 16:42:20 RS: Shane and I worked on this (link above) 16:42:28 RS: Anyone can start working on an extension. 16:42:42 RS: This is for 1.x. We don't yet know what we're going to do about ARIA 2.x. 16:42:56 RS: (Reads from document linked above) 16:43:46 RS: I don't know what will happen after the chartering. 16:44:50 RS: We may have one in development like ARIA 1.1, which is maybe in draft form. We need to be sure it's published on the TR list. 16:45:12 RS: (More reading from document) 16:46:12 RS: The ARIA group might want to incorporate some roles into the main spec, like Chapter. 16:46:30 RS: The other thing that will be required is a REC-track mapping specification. 16:46:49 RS: The important part is your extension cannot break ATs or interfere with other mappings. 16:47:01 RS: Are there any concerns about this? 16:47:16 CS: I still need to write up the non-role-related extensions. 16:47:30 RS: We're going to present this to the HTML A11y group tomorrow. 16:47:41 RS: I wouldn't worry too much about this now. 16:47:50 Janina: We want to formally adopt this. 16:48:01 Janina: This is version 1.0. We can always make a 1.1. 16:48:15 CS: My concern is that 2.0 is going to be done as a set of modules. 16:48:28 RS: If we have to tweak the process at some point, I don't think that's a problem. 16:48:43 Janina: And this is for ARIA 1.x. 16:48:57 s/A11y group/Working Group/ 16:49:12 CS: So you added the bit about it being for 1.x? 16:49:14 RS: Yes. 16:49:25 CS: I'll give it a quick read and send any concerns to the mailing list. 16:49:34 Janina: Should I wait for this call to complete for a CFC? 16:49:44 (hand-wave about versions and synchronization - TBD). 16:49:56 RS: There's a statement from Shane about "hand wave" (text above) 16:50:21 MC: What's to be determined is how we implement that. 16:50:31 MC: Does the ARIA spec say how to make extensions noramtive? 16:50:44 MC: Does the ARIA spec gets published with the extension incorporated into it? 16:50:48 RS: I think that depends. 16:51:01 Janina: It already says you could go either way with that. 16:51:39 Janina: We don't have a mechanism on the engine end to implement only parts of things. 16:51:51 CS: Not every browser is going to do every extension. 16:52:20 CS: For instance, if DPUB becomes a recommendation, why would browsers implement that? 16:52:33 CS: And it seems weird that failure to implement DPUB would make you non-compliant. 16:52:43 RS: All DPUB readers are based on web engines. 16:53:27 CS: If someone does an extension spec for scientific equations, would that mean your browser is not compliant? 16:53:34 RS: Ah, no. 16:53:47 RS: You have to define a mapping, and have two implementations. 16:53:54 RS: A host language might not implement a module. 16:54:05 RS: For instance I don't think SVG would implement DPUB. 16:54:14 MC: I do think the wording of item 4 is problematic. 16:54:26 MC: I read it to mean conformance equals ARIA plus all modules. 16:54:30 CS: Yes. 16:54:39 RS: Do you have suggested wording? 16:54:45 MC: I don't have a single sentence. 16:55:30 MC: I think we need to make it clear that you can still conform to ARIA core. 16:55:42 RS: Things that are not in ARIA core would be considered optional. 16:55:58 MC: We say all roles are normative. 16:56:20 CS: Conformance needs to be separate. 16:56:41 RS: That's what I mean by optional. Browsers don't have to implement it. But you need two implementations. 16:57:02 MC: What's not called out in this wording is if the extensions are in the REC track, their conformance is non-optional. 16:57:35 CS: ARIA DPUB, for example, should be optional with respect to conformance to ARIA core. 16:57:58 Janina: I think we'll be happiest if implementation of extensions is optional. 16:58:08 MC: We need to be sure to include stakeholders. 16:58:24 MC: For instance, we'd be unhappy if longdesc were viewed as extensions. 16:58:39 CS: I'm not worried about REC; I'm asking about my browser being compliant. 16:58:55 Janina: Since this is not hammered out, it's not ready for CFC. 17:00:15 RS: If the browser vendors don't implement the mappings, that's going to be a problem. 17:00:32 CS: The concern is the never-ending addition of new things to ARIA. 17:00:42 RS: Maybe I can word this differently. 17:01:06 RS: I think what Cynthia is saying is I've got a project schedule and now there's a new module. 17:01:18 CS: Right. 17:01:42 MC: And the ability to say IE is not a DPUB reader. 17:02:37 CS: If there were ARIA molecular browser, I wouldn't expect everyone to implement it. 17:03:30 CS: We don't have molecular biology in the accessibility APIs. 17:04:11 Janina: We may have lots of specialized extensions. 17:04:24 CS: I agree that a path for specialized applications is an important thing. 17:04:37 RS: So we need to tweak that bullet. 17:04:59 CS: Yes, I want to say compliance to each extension is a separate thing. 17:05:12 RS: I will figure out how to word this. 17:05:29 Janina: Maybe things that are prefixed are optional and non-prefixed items are required. 17:05:46 RS: So we're going to probably need another round of this. 17:05:59 RS: I hope it won't take too long because DPUB is waiting for this. 17:06:19 RS: Maybe we get what people agree to in this version. 17:06:34 CS: Maybe an editorial note regarding things we're still discussing. 17:06:51 RS: I'll note that on the bullet. 17:07:06 Janina: I think we're ready for tomorrow's meeting. 17:07:23 Janina: I've invited everyone from PF, DPUB, and HTML. 17:08:03 Zakim, part 17:08:03 Zakim has left #pf 17:08:09 RRSAgent, make minutes 17:08:09 I have made the request to generate http://www.w3.org/2015/05/20-pf-minutes.html joanie 17:11:06 present+ Rich_Schwerdtfeger 17:11:13 present+ Cynthia_Shelly 17:11:22 RRSAgent, make minutes 17:11:22 I have made the request to generate http://www.w3.org/2015/05/20-pf-minutes.html joanie 17:11:43 jcraig has joined #pf 17:29:05 richardschwerdtfeger has left #pf 17:31:53 Gottfried has left #pf