See also: IRC log
SAZ: suggest we split these into two
... we accept the first, except that we will add these descriptions to section
"reporting" rather than "workflow"
... for the second, we need to assess if and how many of the ATAG mockups can
be reused in our document
... principally think we can accept the comment, but keep to the end to
determine if we can integrate in this next revision or a later one
<scribe> ACTION: cvelasco to check issue #37 before publication [recorded in http://www.w3.org/2014/10/01-er-minutes.html#action03]
<trackbot> Created ACTION-144 - Check issue #37 before publication [on Carlos A. Velasco - due 2014-10-08].
CV: same as mockups -- principally yes but need to check if we can do in this revision or the next
<scribe> ACTION: cvelasco to check if can add example proposed by comment #37 before publication [recorded in http://www.w3.org/2014/10/01-er-minutes.html#action06]
<trackbot> Created ACTION-145 - Check if can add example proposed by comment #37 before publication [on Carlos A. Velasco - due 2014-10-08].
<scribe> ACTION: cvelasco to check if we can include mockups from ATAG before publication [recorded in http://www.w3.org/2014/10/01-er-minutes.html#action07]
<trackbot> Created ACTION-146 - Check if we can include mockups from atag before publication [on Carlos A. Velasco - due 2014-10-08].
CV: content encoding is dangerous because relates to HTTP aspect
SAZ: separate "character encoding" or alternate
name from "language"
... in the first, the function is tool support for different character sets
... for example, can the tool process UTF-8
... the other function, if the tool can check accessibility (like reading
level) of different languages
CV: agree with these two separate features
<scribe> ACTION: ymartin to check agreement with separating "character encoding" and "language" as different features [recorded in http://www.w3.org/2014/10/01-er-minutes.html#action10]
<trackbot> Created ACTION-147 - Check agreement with separating "character encoding" and "language" as different features [on Yod Samuel Martin - due 2014-10-08].
SAZ: suggest expanding section on DOM fragments
to talk about evaluating parts of content more generally
... with DOM fragments being one technique
... could also mention that using protocls like HTTP enables tools to be more
versatile and independent of particular CMSs
CV: can also mention elsewhere in the document
RESOLUTION: expand section on DOM fragments as discussed above
SAZ: relates to previous comments
CV: can't give quantities
SAZ: samuel asks for a feature, that developers document how they address each Success Criterion
CV: can do that
RESOLUTION: add feature on developers documenting how they address each Success Criterion