16:33:13 RRSAgent has joined #ua 16:33:13 logging to http://www.w3.org/2012/08/02-ua-irc 16:33:15 RRSAgent, make logs public 16:33:15 Zakim has joined #ua 16:33:17 Zakim, this will be WAI_UAWG 16:33:18 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:33:18 Date: 02 August 2012 16:33:19 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 27 minutes 16:34:39 Agenda+ New 1.1.3 incorporating and adding to Jan's suggestions. from 16:34:40 Hakkinen, Mark - Note Mark was going to update one more time from last meeting http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JulSep/0004.html 16:34:42 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JulSep/0005.html 16:34:43 Agenda+ 1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing 16:34:45 Agenda+ Structure" (Jan) 16:34:47 Agenda+ Action-740 Changes to 2.8 Provide toolbar configuration (Mark & 16:34:48 Agenda+ Jaime) 16:34:50 agenda+ 2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim 16:34:52 agenda+ Name, Role, State Proposal Action-649, Action-651 16:34:56 rrsagent, make minutes 16:34:56 I have made the request to generate http://www.w3.org/2012/08/02-ua-minutes.html kford 16:37:01 JAllan has joined #ua 16:37:22 zakim, agenda? 16:37:22 I see 7 items remaining on the agenda: 16:37:24 1. New 1.1.3 incorporating and adding to Jan's suggestions. from [from kford] 16:37:24 2. 1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing [from kford] 16:37:24 3. Structure" (Jan) [from kford] 16:37:24 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 16:37:24 5. Jaime) [from kford] 16:37:24 6. 2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim [from kford] 16:37:26 7. Name, Role, State Proposal Action-649, Action-651 [from kford] 16:39:30 regrets: Jaime, Mark 16:57:21 WAI_UAWG()1:00PM has now started 16:57:28 +[Microsoft] 16:57:39 zakim, microsoft is kford 16:57:39 +kford; got it 16:58:18 +Jim_Allan 16:59:10 Greg has joined #ua 17:01:16 Jan has joined #ua 17:01:23 zakim, code? 17:01:23 the conference code is 82941 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Jan 17:01:24 jeanne has joined #ua 17:01:53 +Jeanne 17:02:14 +??P10 17:02:16 JAllan has joined #ua 17:02:18 +Greg_Lowney 17:05:14 zakim, ??P10 is really Jan 17:05:14 +Jan; got it 17:05:39 scribe: Jan 17:06:13 rrsagent, make minutes 17:06:13 I have made the request to generate http://www.w3.org/2012/08/02-ua-minutes.html kford 17:06:24 zakim, agenda? 17:06:25 I see 7 items remaining on the agenda: 17:06:25 1. New 1.1.3 incorporating and adding to Jan's suggestions. from [from kford] 17:06:25 2. 1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing [from kford] 17:06:25 3. Structure" (Jan) [from kford] 17:06:25 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 17:06:27 5. Jaime) [from kford] 17:06:28 6. 2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim [from kford] 17:06:30 7. Name, Role, State Proposal Action-649, Action-651 [from kford] 17:07:00 Scribe: Jan 17:07:00 +Kim_Patch 17:10:04 Chair: Kelly Ford 17:10:32 agenda+ WAI Mobile Strategy 17:10:38 JS: Just came out of a WAI meeting regarding mobile.... 17:10:42 zakim, take up item 8 17:10:42 agendum 8. "WAI Mobile Strategy" taken up [from kford] 17:11:05 JS: Idea that we might have a opportunity to address mobile in uaag 17:11:16 JS summarizes WI strategy meeting on mobile. 17:11:24 JS: Strategy would be to publish to TR soon.... 17:11:39 JS: Then to look at any gaps in mobile... 17:11:56 JS: And to see about working them in. 17:12:07 JS: But I don't have all the details 17:12:25 JS: We'll also be discussing in CG 17:12:47 KP: Maybe could beef things up by going through and making sure we have mobile examples. 17:13:09 JA: Also the other WG....if they find something they should let us know. 17:13:36 KP: Maybe that can be a way to get people to read uaag 17:13:55 JS: There is a Mobile Accessibility community group 17:14:32 JS: Also I need to turn the wiki page we made into a note etc 17:14:51 KP: On mobile speech, most voice rec engines are server based 17:15:01 KP: So can get stranded... 17:15:22 KP: So I've been talking to developers 17:16:01 KP: Apparently there is no technical reason preventing it being on phone 17:16:27 KP: Big issue is that when they control servers they can improve the speech 17:16:50 KP: Just wanted people to know its not technical, but is business issue 17:17:19 Greg: like the IBM-Siri issue 17:18:20 JS: Certainly could be problem on simpler platforms. 17:18:37 JA: Remarkable that mobiles have the HP to do that. 17:18:39 zakim, close item 8 17:18:39 agendum 8, WAI Mobile Strategy, closed 17:18:40 I see 7 items remaining on the agenda; the next one is 17:18:40 1. New 1.1.3 incorporating and adding to Jan's suggestions. from [from kford] 17:18:48 zakim, take up item 1 17:18:48 agendum 1. "New 1.1.3 incorporating and adding to Jan's suggestions. from" taken up [from kford] 17:19:43 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JulSep/0029.html 17:19:46 KimPatch has joined #ua 17:20:19 1.1.3 Display of Time-Based Media Alternatives: For recognized on-screen alternatives for time-based media (e.g. captions, sign language video), the following are all true: (Level AA) 17:20:20 (a) Do Not Obscure Primary Media: The user can specify that the display of media alternatives does not obscure the primary time-based media; and 17:20:22 (b) Do Not Obscure Controls: The user can specify that the display of media alternatives does not obscure recognized controls for the primary time-based media; and 17:20:23 (c) Configurable Text: Text within media alternatives (e.g. captions) can be configured in conformance with 1.4.1; and 17:20:25 Note: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement. 17:21:36 1.1.X Size and Position of Time-Based Media Alternatives: The user can configure recognized on-screen alternatives for time-based media (e.g. captions, sign language video) as follows: (Level AAA) 17:21:38 (a) Resize: The user can resize the media alternatives up to at least the size of the primary time-based media. 17:21:39 (b) Reposition: The user can reposition the media alternatives to at least the top, bottom, left and right of the primary time-based media. 17:21:41 Note 1: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement. 17:21:42 Note 2: Implementation may involve displaying media alternatives in a separate window, but this is not required. 17:22:04 JAllan_ has joined #ua 17:23:00 Does "the user can specify" imply a setting that affects automatic placement, rather than manual placement, when both are acceptable? 17:23:41 Perhaps "The user can have". 17:24:02 As in "The user can have media alternatives not obscure..." 17:26:34 Perhaps change "text within media alternatives" to "Recognized text within media alternatives" so that text appearing, for example, in the sign language video is not counted. 17:28:24 1.1.3 Display of Time-Based Media Alternatives: For recognized on-screen alternatives for time-based media (e.g. captions, sign language video), the following are all true: (Level AA) 17:28:26 (a) Do Not Obscure Primary Media: The user can specify that the display of media alternatives does not obscure the primary time-based media; and 17:28:28 (b) Do Not Obscure Controls: The user can specify that the display of media alternatives does not obscure recognized controls for the primary time-based media; and 17:28:29 (c) Configurable Text: Recognized text within media alternatives (e.g. captions) can be configured in conformance with 1.4.1. 17:28:31 Note: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement. 17:29:08 http://www.w3.org/2007/10/htmldiff?doc1=http%3A%2F%2Fwww.w3.org%2FWAI%2FUA%2F2012%2FED-UAAG20-20120731%2FMasterUAAG20120731.html&doc2=http%3A%2F%2Fwww.w3.org%2FWAI%2FUA%2F2012%2FED-UAAG20-20120731%2FMasterUAAG20120802.html#def-recognize 17:30:01 Resolved: All accept new wording for 1.1.3 (see above) with clarification around how user can specify placement, etc. in the IER 17:30:22 1.1.X Size and Position of Time-Based Media Alternatives: The user can configure recognized on-screen alternatives for time-based media (e.g. captions, sign language video) as follows: (Level AAA) 17:30:24 (a) Resize: The user can resize the media alternatives up to at least the size of the primary time-based media. 17:30:25 (b) Reposition: The user can reposition the media alternatives to at least the top, bottom, left and right of the primary time-based media. 17:30:27 Note 1: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement. 17:30:28 Note 2: Implementation may involve displaying media alternatives in a separate window, but this is not required. 17:30:55 Why limit it to the size of the primary time-based media? Why not the size of the display? If the primary media is small, this would be useless. 17:33:53 (a) Resize: The user can resize the media alternatives up to at least the maximum size of the primary time-based media. 17:35:03 (a) Resize: The user can resize the media alternatives up to at least the size of the user agent's viewport. 17:35:15 (a) Resize: The user can resize the media alternatives up to the size of the user agent's viewport. 17:36:12 As long as it's AAA, why not also include positioning the alternative to overlap the primary media? 17:37:31 (b) Reposition: The user can reposition the media alternatives to at least the top, bottom, left, and right of the primary time-based media as well as overlaying the primary time-based media. 17:39:10 (b) Reposition: The user can reposition the media alternatives to at least the top, bottom, left, and right of the primary time-based media (either overlaying or not the primary time-based media). 17:39:17 "The user can reposition the media alternatives to at least above, below, to the right, to the left, and overlapping the primary time-based media."? 17:39:52 (b) Reposition: The user can reposition the media alternatives to at least above, below, to the right, to the left, and overlapping the primary time-based media. 17:40:17 1.1.X Size and Position of Time-Based Media Alternatives: The user can configure recognized on-screen alternatives for time-based media (e.g. captions, sign language video) as follows: (Level AAA) 17:40:19 (a) Resize: The user can resize the media alternatives up to the size of the user agent's viewport. 17:40:20 (b) Reposition: The user can reposition the media alternatives to at least above, below, to the right, to the left, and overlapping the primary time-based media. 17:40:22 Note 1: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement. 17:40:23 Note 2: Implementation may involve displaying media alternatives in a separate window, but this is not required. 17:40:35 Resolved: All accept new wording for 1.1.X (see above) 17:42:27 rrsagent, make minutes 17:42:27 I have made the request to generate http://www.w3.org/2012/08/02-ua-minutes.html kford 17:44:22 KF: Who wants to write the IER? 17:46:37 Note: we need to get IERs for these partly based off of Mark's original text. 17:46:56 zakim, agenda? 17:46:56 I see 7 items remaining on the agenda: 17:46:57 1. New 1.1.3 incorporating and adding to Jan's suggestions. from [from kford] 17:46:57 2. 1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing [from kford] 17:46:57 3. Structure" (Jan) [from kford] 17:46:57 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 17:46:57 5. Jaime) [from kford] 17:46:59 6. 2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim [from kford] 17:47:01 7. Name, Role, State Proposal Action-649, Action-651 [from kford] 17:47:20 zakim, close item 1 17:47:20 I see a speaker queue remaining and respectfully decline to close this agendum, kford 17:47:32 ack greg 17:47:42 q? 17:47:45 Zakim, close this item 1 17:47:45 I don't understand 'close this item 1', Jan 17:47:52 Zakim, close this item 17:47:52 agendum 1 closed 17:47:53 I see 6 items remaining on the agenda; the next one is 17:47:53 2. 1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing [from kford] 17:47:54 zakim, close item 1 17:47:55 agendum 1, New 1.1.3 incorporating and adding to Jan's suggestions. from, closed 17:47:55 I see 6 items remaining on the agenda; the next one is 17:47:55 2. 1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing [from kford] 17:48:01 Zakim, take up next item 17:48:01 agendum 2. "1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing" taken up [from kford] 17:48:07 zakim, take up item 2 17:48:07 agendum 2. "1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing" taken up [from kford] 17:48:38 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JulSep/0034.html 17:48:52 Intent of Success Criterion 1.2.2: 17:48:54 When an author has neglected to provide labels and/or headers as necessary for accessibility, the user agent can, in some cases, use heuristics to determine potential labels and/or headers from presentation attributes. Once potential headings and/or labels have been identified, the user agent can proceed (e.g. with communication via platform accessibility services) as if the relationship was... 17:48:55 ...defined in the markup. The user must have the option to specify whether the heuristics should be applied because some users will need to experience the content as the author provided it, for example to perform evaluations. 17:52:07 When an author has neglected to provide labels and/or headers as necessary for accessibility, the user agent can, in some cases, use heuristics to determine potential labels and/or headers from presentation attributes. Once potential headings and/or labels have been identified, the user agent can proceed (e.g. with communication via platform accessibility services) as if the relationship was... 17:52:07 I think turning off heuristics because they're wrong is a more prominent accessibility issue than the need to turn it off for testing. 17:52:08 ...defined in the markup. The user must have the option to specify whether the heuristics should be applied because some users will want to experience the content as the author provided it, for example to perform evaluations or they may find that heuristics occasionally fail. 17:53:00 "or when they find"? 17:54:16 When an author has neglected to provide labels and/or headers as necessary for accessibility, the user agent can, in some cases, use heuristics to determine potential labels and/or headers from presentation attributes. Once potential headings and/or labels have been identified, the user agent can proceed (e.g. with communication via platform accessibility services) as if the relationship was... 17:54:17 ...defined in the markup. The user must have the option to specify whether the heuristics should be applied because some users will want to experience the content as the author provided it, for example to perform evaluations or when they find that heuristics occasionally fail. 17:54:44 Resolved: All accept intent text (above) for 1.2.2 17:54:58 Examples of Success Criterion 1.2.2: 17:54:59 - content markup includes a checkbox without a specified label, but the user agent detects that a static text component is positioned immediately to the right of the checkbox and no other static text components are nearby. The nearby text is treated as the label. 17:55:01 - content markup includes a table with no header row. The user agent detects that top row contains textual entries while the other rows contain numeric entries. The top row of the table is treated as table headers. 17:55:02 - content markup (in English) includes instances of static text that differ from surrounding text due to being styled sentence fragments and being styled with a larger font, bold weight and additional spacing. The instances are treated as headings. 17:56:52 Examples of Success Criterion 1.2.2: 17:56:53 - content markup includes a checkbox without a specified label, but the user agent detects that a static text component is positioned immediately to the right of the checkbox and no other static text components are nearby. The nearby text is treated as the label. 17:56:55 - content markup includes a table with no header row. The user agent detects that the top row contains textual entries while the other rows contain numeric entries. The top row of the table is treated as the table header row. 17:56:56 - content markup (in English) includes instances of static text that differ from surrounding text due to being sentence fragments and being styled with a larger font, bold weight and additional spacing. The instances are treated as headings. 17:57:16 JAllan has joined #ua 17:57:50 Could acknowledge in the examples that there are different approaches to implementation, e.g. right now all are are default actions by the user agent, could have one be at user request. 17:58:33 Examples of Success Criterion 1.2.2: 17:58:35 - content markup includes a checkbox without a specified label, but the user agent detects that a static text component is positioned immediately to the right of the checkbox and no other static text components are nearby. The nearby text is treated as the label. 17:58:36 - Maria sets her user agent to automatically assume that when tables lack marked up header rows, the first row should be treated as the table header row. 17:58:38 - content markup (in English) includes instances of static text that differ from surrounding text due to being sentence fragments and being styled with a larger font, bold weight and additional spacing. The instances are treated as headings. 18:06:54 Examples of Success Criterion 1.2.2: 18:06:56 - George uses speech input. When content markup includes a checkbox without a specified label, the user agent detects that a static text component is positioned immediately to the right of the checkbox and no other static text components are nearby. The nearby text is treated as the label. This enables George to toggle the checkbox by speaking its name. 18:06:58 - Maria uses a screen reader. When a table lacks marked up header rows, the user agent gives her the option to have the first row treated as the table header row. 18:06:59 - Li uses a scanning keyboard and makes use of the user agent's outline view to more efficiently navigate web pages. The content markup (in English) includes instances of static text that differ from surrounding text due to (a) being sentence fragments and (b) being styled with a larger font, bold weight and additional spacing. The instances are treated as headings as therefore appear in the... 18:07:01 ...outline view, enabling Li to more efficiently navigate to them. 18:07:33 Resolved: All accept examples (above) for 1.2.2 18:08:17 Related Resources for Success Criterion 1.2.2: 18:08:19 - Understanding WCAG 2.0: Heading and Labels: http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-descriptive.html 18:08:36 Resolved: All accept related resource (above) for 1.2.2 18:08:49 zakim, close item 2 18:08:49 agendum 2, 1.2.2 Action-725 - Write IER for "1.2.2 Repair Missing, closed 18:08:51 I see 5 items remaining on the agenda; the next one is 18:08:51 3. Structure" (Jan) [from kford] 18:09:01 zakim, take up item 3 18:09:01 agendum 3. "Structure" (Jan)" taken up [from kford] 18:09:29 zakim, close item 3 18:09:29 agendum 3, Structure" (Jan), closed 18:09:30 I see 4 items remaining on the agenda; the next one is 18:09:30 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 18:09:33 close action-725 18:09:33 ACTION-725 Write IER for the new "1.2.2 Repair Missing Structure" closed 18:09:40 zakim, agenda? 18:09:40 I see 4 items remaining on the agenda: 18:09:42 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 18:09:42 5. Jaime) [from kford] 18:09:42 6. 2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim [from kford] 18:09:42 7. Name, Role, State Proposal Action-649, Action-651 [from kford] 18:10:51 JA: Jaime still working on it, so will have it next week. 18:10:54 zakim, take up item 6 18:10:54 agendum 6. "2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim" taken up [from kford] 18:11:16 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JulSep/0033.html 18:11:50 2.1.9 is better with modifier keys, but worse with "help" and lacking saving. And vice versa. 18:12:16 +1 to progress not perfection 18:13:34 (If F1 can't be remapped then almost anything could be considered reserved.) 18:15:51 I think the 2.3.5 was supposed to replace 2.1.9, but the confusion stems from the fact that "author supplied...and user interface controls" is ambiguous as to whether it means user supplied UI controls or UA supplied UI controls. We could clarify by changing "user interface controls" to "user agent user interface controls" and then delete 2.1.9. 18:16:16 We can either incorporate the sentence about modifier keys from 2.1.9 or leave it out. 18:16:59 2.3.5 Customize Keyboard Commands: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user agent user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). The user must be able to save these settings beyond the current session. (Level AA) 18:17:39 Do we want to add back in "The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment." ? 18:19:27 KP: Better if that extra text in 18:19:32 JR: Agreed 18:19:49 KP: One handed keyboard is already in as examples in 2.3.5 18:20:08 2.3.5 Customize Keyboard Commands: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user agent user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). The rebinding options must include single-key and key-plus-modifier keys if available in the... 18:20:09 ...operating environment. The user must be able to save these settings beyond the current session. (Level AA) 18:20:21 brb 18:21:57 Resolved: Delete 2.1.9 and modify 2.3.5 with wording immediately above. 18:22:12 rrsagent, make minutes 18:22:12 I have made the request to generate http://www.w3.org/2012/08/02-ua-minutes.html kford 18:23:15 zakim, remote item 5 18:23:15 I don't understand 'remote item 5', kford 18:23:26 zakim, remove item 5 18:23:26 agendum 5, Jaime), dropped 18:23:36 zakim, remove item 3 18:23:36 agendum 3, Structure" (Jan), dropped 18:23:48 zakim, agenda? 18:23:48 I see 3 items remaining on the agenda: 18:23:50 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 18:23:50 6. 2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim [from kford] 18:23:50 7. Name, Role, State Proposal Action-649, Action-651 [from kford] 18:25:11 Action kford look at IER from 2.3.5 and 2.1.9 and ensure the new 2.3.5 covers what was important from the now deleted 2.1.9 18:25:11 Created ACTION-750 - Look at IER from 2.3.5 and 2.1.9 and ensure the new 2.3.5 covers what was important from the now deleted 2.1.9 [on Kelly Ford - due 2012-08-09]. 18:25:36 zakim, close item 6 18:25:37 agendum 6, 2.1.9 appears to overlap with 2.3.5 [2.3.5 looks better] Jim, closed 18:25:39 I see 2 items remaining on the agenda; the next one is 18:25:39 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 18:25:55 zakim, agenda 18:25:55 I don't understand 'agenda', kford 18:26:03 zakim, agend? 18:26:03 I don't understand your question, kford. 18:26:09 zakim, agenda? 18:26:09 I see 2 items remaining on the agenda: 18:26:11 4. Action-740 Changes to 2.8 Provide toolbar configuration (Mark & [from kford] 18:26:11 7. Name, Role, State Proposal Action-649, Action-651 [from kford] 18:27:03 zakim, take up item 7 18:27:03 agendum 7. "Name, Role, State Proposal Action-649, Action-651" taken up [from kford] 18:27:16 JAllan has joined #ua 18:27:52 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JulSep/0030.html 18:28:09 From Jim's mail: 18:28:12 close items related to 4.1.2 Name, Role, State, Value, Description: 18:28:14 leave SC and Intent as is because: 18:28:16 --if we genericize terms no one will know what we are talking about. 18:28:17 --we have added the descriptions of Name, Role, State, etc. in the Intent, so the terms could be used with other technologies... 18:28:19 Name (component name) 18:28:21 Role (purpose, such as alert, button, checkbox, etc) State (current status, such as busy, disabled, hidden, etc) Value (information associated with the component such as, the data in a text box, the position number of a slider, the date in a calendar 18:28:23 widget) 18:28:25 Description (user instructions about the component). 18:28:27 remove example 1 "A browser is developing a component..." it is incomplete and need lots more work. Jeanne says it lame. 18:30:57 Resolved: Close action 649 and 651 without change except to delete example 1 18:31:09 -Jan 18:31:16 JAllan has joined #ua 18:31:18 close action-649 18:31:18 ACTION-649 Rewrite in modern terms (genericize) 4.1.2 with greg closed 18:31:21 zakim, close action 649 18:31:21 I don't understand 'close action 649', kford 18:31:33 close action-651 18:31:33 ACTION-651 Combine 412 and 416, with Mark closed 18:31:50 rrsagent, make minutes 18:31:50 I have made the request to generate http://www.w3.org/2012/08/02-ua-minutes.html kford 18:33:14 REsolved: the group agrees to publish a new working draft. 18:33:30 rrsagent, make minutes 18:33:30 I have made the request to generate http://www.w3.org/2012/08/02-ua-minutes.html jeanne 18:33:37 rrsagent, make logs public 18:33:48 -Kim_Patch 18:33:49 -Jim_Allan 18:34:16 -kford 18:34:17 zakim, bye 18:34:17 Zakim has left #ua 18:34:18 leaving. As of this point the attendees were kford, Jim_Allan, Jeanne, Greg_Lowney, Jan, Kim_Patch 18:34:34 rrsagent, make minutes 18:34:34 I have made the request to generate http://www.w3.org/2012/08/02-ua-minutes.html jeanne