SM: agree with proposal from yesterday
RESOLUTION: separate "character encoding" from "language support"
<scribe> ACTION: shadi to check issue #52 before publication
<trackbot> Created ACTION-148 - Check issue #52 before publication [on Shadi Abou-Zahra - due 2014-10-09].
SAZ: provide very brief (~1 sentence) description
of any resources you reference
... so that readers can determine whether they want to follow the link or not
http://www.w3.org/TR/WAET/#overview
http://www.w3.org/TR/WCAG-EM/#step1
"Step 2: Explore the Target Website"
SAZ: can reuse same style
... for internal links
CV: adopt throughout the document?
SAZ: yes
CV: also for references?
SAZ: no, these are fairly short acronyms
https://w3c.github.io/w3c-waet/WAET.html#StdRep
http://www.w3.org/2014/09/24-er-minutes.html#item03
<scribe> ACTION: ymartin to check issue #66 before publication
<trackbot> Created ACTION-149 - Check issue #66 before publication [on Yod Samuel Martin - due 2014-10-09].
http://www.w3.org/TR/WCAG20/#media-equiv
http://www.w3.org/TR/WCAG20/#alt-time-based-mediadef
http://www.w3.org/TR/WCAG20/#audiodescdef
http://www.w3.org/TR/WCAG20/#captionsdef
RESOLUTION: adopt WCAG 2.0 terminology and refer people to Guideline 1.2 for specific accessibility considerations
<samuelm> http://www.w3.org/2014/10/01-er-minutes.html#item05
<Zakim> samuelm, you wanted to comment on https://github.com/w3c/w3c-waet/issues/46
[explain discussion from yesteday - agreement]
SAZ: main target audience is developers, but not
only audience
... for example, we say that it is useful in procurement setting
CV: concerned that people may then land on this document, and are then disappointed that it is not the right one for them
http://www.w3.org/WAI/eval/selectingtools
http://www.w3.org/WAI/eval/selectingtools#features
SAZ: should cross-reference between the two
documents
... one is the more basic introduction, and the other more techy
... should be clearly cross-referenced at the start
... so people can be directed to the document that is more correct for them
SM: need to update selecting tools
... especially the features list
SAZ: propose to drop the features list
SM: rather than drop, better to exlain how to use
the features
... for example in procurement setting
... or add that explanation to a different section
SAZ: ok to drop the list of features but keep an explanation of how to use the features?
CV: think yes but need to see it
SAZ: publication moratorium 24 october - 3 november
CV: will get updated draft by next Tuesday EOB
SM: will review wednesday morning
SAZ: aim is to have complete document that
addresses all comments
... will do editorial clean-up later on
... but need to check with each comments that they agree with how their
comments have been addressed