See also: IRC log
CV: shall we continue updating test cases or wait?
SAZ: are you talking about internal tests or those that are already at CVS?
CV: internal
CS: there are a few SC that has been renamed
... what to do with those that are already at CVS?
SAZ: have to live with some outdated and so on
content
... due to persistence policies
MC: are the test cases associated by ID or SC
number?
... the ID shouldn't change
... mainly minor clarifications with no major impact are expected
... should be safe to proceed
... no major impact on test suite expected
SAZ: expected timeline from BTW for the update?
CV: early August, maybe the second week
SAZ: something by the 31st July possible?
CV: don't think so, too close
SAZ: maybe then we may postpone next meeting
CS: maybe some of them could be ready for next meeting
SAZ: let's take this up again at the end of the call
<shadi> http://www.w3.org/2005/MWI/Tests/Open/submit
<shadi> http://www.w3.org/2005/MWI/Tests/Open/review
SAZ: this is very early work in MWI
... a lot of potential to reuse
... with some adaptation and customization
... early stage, open to comments and suggestions
... is time to give them feedback or a sort of wish list
... there's a license grant required by our legal staff
... my hope is to get the form generate the metadata in the background
... would be very easy to add whatever else we need
... using a new BBDD and just adding the new fields reusing existing
technology
<shadi> http://www.w3.org/WAI/ER/tests/usingTCDL
SAZ: some of the metadata we need could be
generated automatically
... CS, not sure about your comment on titles
CS: people could have different ways to provide
titles
... some could be more generic others more specific
SAZ: a title as a handle would be useful
... talk with DOM about how they manage technologies and suggest we use
URIs
... rules are really specific
... would be the tough part
... there's no pointer to the related test
... we can point this out and see how they plan to solve it
CI: we may have problems with the current file submission
SAZ: could use a multiple step submission
... let's see also the review template
CS: status is missing
... in our case URI points to the metadata file not the test itself
SAZ: would like to have some way to export the
system metadata
... could use the machine processable argument
... add links to the comments each time we create a new one
... we may have a different way to create IDs
... we may use the title as a handle instead of description
... links to the comments
... author's email
... links to the file and the metadata
... trying to get everything as generic as possible
... bulleted list of comments in notes with the different reviews and
issues
TB: we may need to add timestamps to the comments
SAZ: we also may need to associate each comment
with the owner
... all the comments seems useful and hope DOM will implement them
<scribe> ACTION: to write up the comments and send them to the list [recorded in http://www.w3.org/2007/07/17-tsdtf-minutes.html#action01]
SAZ: back to the tests update
CV: 31st not possible
... may be 7th August or 15th
SAZ: 15th holiday in several countries
... let's try with August the 7th