See also: IRC log
cs: We didn't finish discussion of naming convention; no further discussion online
mc: taking a lot of time to discuss, will take more to implement, let's just move forward
cv: worried some test cases will end up in wrong SC
mc: trust in metadata
... if that's wrong, then we need to make change
... has been months of discussion though
saz: ask for summary of issue
cs: Bentoweb planned to have test suites for
different technologies
... needed way to distinguish test suites in ids
... at moment we only have one so it's not really relevant
... but there's nothing scripts can act on
<shadi> http://www.w3.org/2008/04/08-tsdtf-minutes.html#item02
saz: reviewing previous discussion (above link)
<shadi> xhtml1_text-equiv-all_002
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2008Apr/0002.html
saz: ID like above sample was proposal
... we agreed it was beneficial, but didn't close on how much work it would
be to migrate
cs: bulk of work is moving from numbers to ids
mc: is it the task of making the change, or making the mapping from number to id mapping?
cs: it's the renaming of files
cv: not sure about resources for making change
saz: cs and cv should work out whether we have resources to make change and make it, or decide we can live with it
<scribe> ACTION: cs and cv to work out whether we have resources to make change and make it, or decide we can live with it [recorded in http://www.w3.org/2008/04/29-tsdtf-minutes.html#action01]
cs: tb has finished review
... status for ci?
ci: were responses to Tim's comments
cs: will summarize changes made and send to list
saz: issue with test samples that have video or audio format
<Christophe> Resolution from 8 april was to ignore the files that have been uploaded in the wrong directory and follow the process for future uploads
saz: should migrate from focus on what files in CVS, to using an interface that doesn't worry about structure underneath
cv: there are other W3C test suites that are purely CVS based
saz: W3C persistency policy is about any Web
resource, not just HTML
... CVS Web front end is not recommended, is resource intensive
... suggest we focus on HTML view of test suite
... don't think we can break persistency policy and remove just because it
ended up somewhere wrong
... if we rename test samples, we will have a whole slew of tests that are
obsolete
mc: can set up redirects, but that might not be the easiest path
tb: how determine how a test is obsolete?
saz: mostly the renaming
cs: test samples for audio and video don't list
all the technologies used in the metadata
... need volunteers to scrub
mc: can help in a week or two
cs: will send instructions to list
... we have one that uses wmv
... there are 3 ways of identifying; should make them more consistent
mc: not just using MIME type?
cs: metadata uses more than MIME
... recommendations?
mc: people should get to it when they get to it on a scrubbing pass
tb: are there standardized identification mechanisms for media we're using?
cs: W3C formats have stable mechanisms, but not
sure for external formats
... Wikipedia entry perhaps our best bet
cv: suggest supplement with MIME type in case URL of recommendation disappears
cs: where should it go?
cv: new attribute
<shadi> http://www.w3.org/WAI/ER/tests/usingTCDL
<Christophe> MIME Media Types: http://www.iana.org/assignments/media-types/
<scribe> ACTION: Christophe to add MIME type to TCDL schema [recorded in http://www.w3.org/2008/04/29-tsdtf-minutes.html#action02]
cs: question whether to update test samples to
new draft
... wanted to identify which SC are stable
saz: should focus on doing a diff
mc: when CR comes out, anything not listed as "at risk" is stable because can't change without bouncing back to WD
saz: reviewing action, CV was to look at diffs
cv: pending, have documents, need to do comparison
cs: reviews probably have to wait until migrate to new draft
saz: and new naming convention
NEXT MEETING: 13 May 2008