See also: IRC log
SAZ: problems with CVS account - if you want to use CVS frontend
need to use SSH tunnel if you want to communicate
CV: why do you need public SSH key?
SAZ: what is issue with public SSH key? Helps with identification?
CV: policy conflicts - hassle
SAZ: we use SSH for accesing our servers - more
secure
... ask for other possibilities
Daniela: also may be difficult for me
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2006Oct/0049.html
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2006Oct/0050.html
SAZ: need key from computer from which you will
access server
... put info about common clients documentation (Windows)
... who has issues with this? Has anybody use CVS/SSH tunnel before?
CR: Has done before, and worked fine (for test suite W3C site)..
Once set up, worked OK
SAZ: Lot of documentation on google
... Is CVS new to anybody? Everybody except for Tim seems experienced
Only new thing is using SSH tunnel
Daniela: possible issues with generating keys for local machines?
SAZ: puttygen - possible tool for generating keys?
keep private key private, only send public key on any computer
many frameworks available to use SSH - setting up will require research
SAZ: once set up, it should work
<scribe> ACTION: everybody to generate SSH public key and send to Shadi off-list [recorded in http://www.w3.org/2006/10/24-tsdtf-minutes.html#action01]
<shadi> http://www.w3.org/WAI/ER/tests/usingTCDL
CV: discussion on list on this document
SAZ: five-minute break to read document, since it was sent right before call
CV: Who is working on document - coordination?
SAZ: from me, for this round - specific comments?
CV: formatting issue - working group note?
SAZ: What is benefit of listing as working group note?
extensive mechanism to generate - format daunting - current format easier
to read - why do another specification?
CS: no issues with new format, but some issues
need to be cleaned up
... either form will work - what about people newer to it?
CI: prefer this format, creator and rights hard to read, maybe use
template, maybe link element to relevant part of spec
CR: looks fine to me - fairly easy to read
Daniela: insert also things not used - make explicit that not used in TF
SAZ: this would make document much longer? clarification needed?
form to input metadata (including files) provided, so what is benefit of
listing other elements?
Shane: would just be a list - worth the room to do it? not that helpful?
SAZ: listed up front - not clear enough?
CS: would be sufficient just to say these things aren't used - don't want to
draw too much attention to it
Shane: likes it, easy to read, looks good
maybe also same issue with creator and rights as CI
SAZ: supposed to be suite of four documents - still need to work on naming
Tim: looks good at first glance, will investigate more
SAZ: put in some editorial suggestions - maybe put in date info ?
How is date used in BentoWeb?
CS: inserted manually, once and don't change
any more
... already have version information, just creation date added
SAZ: change restriction to note - creation date of test sample - have
we agreed on format?
<scribe> ACTION: SAZ to change description of dc:date [recorded in http://www.w3.org/2006/10/24-tsdtf-minutes.html#action02]
CI: last modified date more interesting than creation date?
CS: always ask CVS for last change
CI: not always possible to see information
SAZ: revision number will change anyway - is it important to know when
last modified?
CI: last modified date is most important to know
SAZ: do we want both dates?
Shane: last modified date more important than creation date
CS: would need to change schema if kept both dates
RESOLUTION: dc:date is to reflect last modified date of the test sample
SAZ: help with generating example metadata file and template?
CS: shouldn't take long to do
<scribe> ACTION: CS and CV to create and send example metadata file and template [recorded in http://www.w3.org/2006/10/24-tsdtf-minutes.html#action03]
SAZ: have them as XML or HTML?
CS: create as XML anyway..
RESOLUTION: example metadata file and template will be in XML format
<CarlosV> example file: http://bentoweb.org/refs/sc3.1.1_l1_001.xml (to be modified)
SAZ: TCDL 2.0 will use "HTTP Vocabulary in RDF" or not?
CS: talked with Johannes Koch re: HTTP vocabulary in RDF, create XML
schema for those terms used in TCDL, and should work..
SAZ: monitor baseline discussion in WCAG WG
CV: required from schema or from task force? may lead to confusion
<scribe> ACTION: SAZ to clarify that required or optional refers to TF rather than to schema [recorded in http://www.w3.org/2006/10/24-tsdtf-minutes.html#action04]
CS: for EARL pointers in location need to create XML schema and import into TCDL