See also: IRC log
RESOLUTION: comments discussed last week are now resolved as proposed
https://w3c.github.io/w3c-waet/WAET.html#webdriver
SAZ: turn around the second to sentences in the second paragraph to say something like
[[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]]]
https://w3c.github.io/w3c-waet/WAET.html#import
SM: import is different, if you consider merging and aggregating from different sources
SAZ: good point but not clear from current
text
... th
ink need to keep 2.3.1 focus on "reporting formats" only
... that is, move the first paragraph of 2.3.1 to 2.3.3
... and reword 2.3.3 to make it more clear
... also consider a heading like "exahnging results" or "combining test
results" or so
RESOLUTION: change text according to suggestion
SAZ: odd to talk about group of people
... if then you'd need to say something like "requirements for people with
color blindness"
... better to just drop or use a different *requirement*
RESOLUTION: change text according to suggestion
SAZ: think "testing before and after DOM" needs
to be clearly highlighted
... it is an important design decision that many developers miss
... think need a new section in 2.2
... needs to be very clear
CV: then too repetitive
SM: think want to recommend testing after DOM
CV 2.1.4 already says that
SAZ: but testing after DOM is not only applicable
to RIA
... could at least change 2.1.4 to be more clear
CV: will go for that
SAZ: also propose to add reference somewhere in
2.2
... defer to next week
trackbot, end meeting