5 Dec 2006


See also: IRC log


Shadi, Michael, Christophe, Vangelis, Chris, CarlosI, CarlosV, Tim
CarlosV, Christophe


Linking location and techniques in TCDL 2.0


cv: concerns expressed about mapping locations and techniques
... proposal from Christophe

cs: prefer option A
... most robust, minimal duplication

saz: question on A - is techref IDREF?

cs: is IDREFS
... would like to be able to use space-separated refs

saz: was only one not liking it on list

cv: problem with non-valid ID attribute on techinque

cs: schema updated, technique has ID

cv: Option A most error-prone, but cleaner

mc: validating processor can ensure avoidance of errors

cv: discussed with CS; scendario with techniques / locations wouldn't be caught
... by validating processor

vk: A more processor-friendly; B more user-friendly; can live with A

cr: prefer A or B to C

ci: agree with analysis; no preference between A & B, lean towards B, don't like C

saz: point of being more machine testable compelling
... should be able to extract IDs out of WCAG source XML
... may be able to do a bunch of stuff with that

ci: can live with A

<CarlosV> chris, can you live with option A?

mc: prefer A

cr: can live with A

RESOLUTION: accept model A from Christophe's proposal http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2006Nov/0044.html

Final review of evaluation process


saz: no feedback received

cv: were some issues raised last week

cs: Shadi clarified some issues on list

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2006Nov/0046.html

saz: <summarizes responses at http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2006Nov/0046.html>

<shadi> http://www.w3.org/WAI/ER/2005/tools

cv: concern about how people contribute to lists

cs: suggest wiki

saz: wiki is available if we want
... could also use CVS to edit a common document

mc: wiki easier for multiple contributions

saz: not concerned about concurrency but want it to be easy for people to track

cv: where would wiki be hosted?

saz: service from W3C, need to explore details

cs: weren't there ease of use issues with W3C wiki?

mc: some of the issues may be resolved because it's now supported, but not familiar with the specific software

<scribe> ACTION: Shadi to explore wiki option [recorded in http://www.w3.org/2006/12/05-tsdtf-minutes.html#action01]

saz: question about reviews at steps 2 and 3

cv: perhaps steps are same

saz: might do things asynchronously, better not to combine

cv: prefer same person to do the steps

saz: we could prefer same user, but not combine

cv: need way to store results

saz: results need to be publicly visible; wiki option
... WBS form can be publicly viewable, but it doesn't keep history like wiki does
... <WBS is W3C's Web-Based Survey system>
... appropriate for straw poll (step 4) but recording evaluation results better in wiki

cs: agree

ci: discussed bug-tracking system earlier
... but not user-friendly

saz: Bugzilla is an option

ci: could store history and store who's working on what, more consistenly than wiki
... use JIRA instead of Bugzilla

<CarlosV> JIRA: http://www.atlassian.com/software/jira/

saz: wouldn't be supported by W3C systems team, so we'd be on our own

ci: if Bugzlilla supported by W3C, why WCAG use external?

mc: may not have been supported at time, and needed to customize

saz: issues with externally-hosted tools
... prefer to go with internally-supported, low-rent tools

ci: can ask to support JIRA?

saz: asked a while ago, no plans to support anything else
... there is effort to analyze WG needs, but won't be complete for a while

cv: prefer Bugzilla still, but may be better to use just one tool e.g. wiki
... issue tracking in bug tracker more flexible than wiki
... author can get automatic feedback from system about changes in status in bug tracker

saz: issue of who configures

mc: bug tracker still has its limitations

saz: will use WBS in step 4 anyway
... we have discomfort either with configuring bug tracker, or sending emails to each author

cv: prefer bug tracker

ci: any bug tracker will have difficulties, but should choose what meets our needs, as simply as possible
... that may be wiki
... if that doesn't meet needs, than Bugzilla best next option

saz: hear support for bug tracking, but usability an issue

cv: JIRA runs in Tomcat

<scribe> ACTION: Carlos V to send question to list about software [recorded in http://www.w3.org/2006/12/05-tsdtf-minutes.html#action02]

saz: request people review his responses to see if other open questions

Summary of Action Items

[NEW] ACTION: Carlos V to send question to list about software [recorded in http://www.w3.org/2006/12/05-tsdtf-minutes.html#action02]
[NEW] ACTION: Shadi to explore wiki option [recorded in http://www.w3.org/2006/12/05-tsdtf-minutes.html#action01]
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/12/05 14:37:27 $