12:30:34 RRSAgent has joined #er 12:30:34 logging to http://www.w3.org/2014/09/17-er-irc 12:30:36 RRSAgent, make logs public 12:30:36 Zakim has joined #er 12:30:38 Zakim, this will be 3794 12:30:38 ok, trackbot; I see WAI_ERTWG()8:30AM scheduled to start now 12:30:39 Meeting: Evaluation and Repair Tools Working Group Teleconference 12:30:39 Date: 17 September 2014 12:31:09 zakim, call shadi-617 12:31:09 ok, shadi; the call is being made 12:31:15 samuelm has joined #er 12:31:44 carlos has joined #er 12:36:45 RESOLUTION: comments discussed last week are now resolved as proposed 12:38:15 Topic: Issue #12 https://github.com/w3c/w3c-waet/issues/12 12:43:39 https://w3c.github.io/w3c-waet/WAET.html#webdriver 12:49:33 SAZ: turn around the second to sentences in the second paragraph to say something like 12:50:58 [[There are [several?] tools that enable developers to write tests that automate the application's and the end-users' behaviour. There is an effort to standardize a common API for such tools, one of these APIs is the W3C WebDriver API [WebDriver]]] 12:52:21 Topic: Issue #24 https://github.com/w3c/w3c-waet/issues/24 12:53:15 https://w3c.github.io/w3c-waet/WAET.html#import 12:57:46 SM: import is different, if you consider merging and aggregating from different sources 13:03:27 SAZ: good point but not clear from current text 13:03:50 ...think need to keep 2.3.1 focus on "reporting formats" only 13:04:09 ...that is, move the first paragraph of 2.3.1 to 2.3.3 13:04:20 ...and reword 2.3.3 to make it more clear 13:04:45 ...also consider a heading like "exahnging results" or "combining test results" or so 13:05:12 RESOLUTION: change text according to suggestion 13:05:53 Topic: Issue #9 https://github.com/w3c/w3c-waet/issues/9 13:08:52 SAZ: odd to talk about group of people 13:10:11 ...if then you'd need to say something like "requirements for people with color blindness" 13:10:22 ...better to just drop or use a different *requirement* 13:10:33 RESOLUTION: change text according to suggestion 13:10:41 Topic: Issue #36 https://github.com/w3c/w3c-waet/issues/36 13:24:11 SAZ: think "testing before and after DOM" needs to be clearly highlighted 13:24:16 ...it is an important design decision that many developers miss 13:24:41 ...think need a new section in 2.2 13:24:53 ...needs to be very clear 13:25:07 CV: then too repetitive 13:25:20 SM: think want to recommend testing after DOM 13:27:54 CV 2.1.4 already says that 13:28:13 SAZ: but testing after DOM is not only applicable to RIA 13:28:38 ...could at least change 2.1.4 to be more clear 13:29:08 CV: will go for that 13:29:33 SAZ: also propose to add reference somewhere in 2.2 13:31:07 SAZ: defer to next week 13:31:38 trackbot, end meeting 13:31:38 Zakim, list attendees 13:31:38 sorry, trackbot, I don't know what conference this is 13:31:46 RRSAgent, please draft minutes 13:31:46 I have made the request to generate http://www.w3.org/2014/09/17-er-minutes.html trackbot 13:31:47 RRSAgent, bye 13:31:47 I see no action items