TSD TF

Next steps for current repository content. Waiting for update from WCAG WG.

CV: waiting for feedback from WCAG..

SAZ: ask WCAG for clarification on items?
... need to check what has changed since May WD..

<MichaelC> http://www.w3.org/WAI/GL/WCAG20/

MC: editor's draft URL.. fairly current
... almost all SC are stable except for 1.1 and ones relating to multimedia (maybe some others also?)

<shadi> http://www.w3.org/WAI/GL/WCAG20/Overview-diff.html

MC: no guarantee (just best guess..)
... no diff markings between WDs because of readability issues..
... maybe use CVS to track changes?

SAZ: lot of tests developed according to May 2007 draft - need to see what has changed
... need to mark what has changed and what has not changed

MC: compare May 17 2007 version to current version?

<shadi> http://www.w3.org/WAI/GL/WCAG20/Overview-diff.html

<shadi> May -> Dec -> now

SAZ: should go thru diffs or XMLSpec..which?

CV: can old XML files be sent?

<MichaelC> Current version of WCAG src: http://www.w3.org/WAI/GL/WCAG20/sources/wcag2-src.xml

<scribe> ACTION: CV to follow up with MC on generating WCAG diff from May 2007 to current internal draft [recorded in http://www.w3.org/2008/03/04-tsdtf-minutes.html#action01]

Review of test samples

<CarlosV> http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2008Jan/0009.html

TB: need more robust tracking/coordination mechanism between WCAG and tests for consistency

<shadi> http://www.w3.org/WAI/ER/tests/usingTCDL

<shadi> http://www.bentoweb.org/refs/TCDL2.0.html#edef-rules

<CarlosV> http://bentoweb.org/ts/XHTML1_TestSuite3/metadata/sc1.1.1_l1_001.xml

SAZ: test sample should match exactly one guideline

<shadi> <rule id="http://bentoweb.org/refs/rulesets.xml#WCAG2_20060427_1.1_text-equiv-all"

TB: should be goal that tests point to latest stable WCAG WD

SAZ: there is mechanism to identify which version tests are written for
... rulesets need to change to reflect new WCAG version..

<shadi> <rule id="http://bentoweb.org/refs/rulesets.xml#WCAG2_20071211_1.1_text-equiv-all"

SAZ: id would need to change..

<shadi> <guideline id="WCAG20-20060427_1.1" name="1.1" xlink:href="http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#text-equiv">

SAZ: id of guidelines should match id of rule (how versioning is done)..

TB: how easy to maintain?

SAZ: fragment name is different (possible issue?)
... possibly a checker (Schematron?)

<shadi> can schematron check if the rule ID really matches an existing rulesets guideline ID?

SAZ: should be able to check metadata (to prevent generating false metadata)

<shadi> http://www.w3.org/WAI/ER/tests/usingTCDL

<shadi> attribute xlink:href - required

CV: possible loss of information with updating?

<shadi> Suggestion: SAZ add brief note in the Using TCDL document on how the xlink attribute in the rule element works (that it points to the specific version of the guidelines within the rulesets.xml document)

<scribe> ACTION: SAZ to add brief note in the Using TCDL document on how the xlink attribute in the rule element works (that it points to the specific version of the guidelines within the rulesets.xml document) [recorded in http://www.w3.org/2008/03/04-tsdtf-minutes.html#action02]