12:32:23 RRSAgent has joined #tsdtf 12:32:23 logging to http://www.w3.org/2008/07/01-tsdtf-irc 12:32:29 Zakim has joined #tsdtf 12:32:35 zakim, this will bbe tsd 12:32:35 I don't understand 'this will bbe tsd', shadi 12:32:40 zakim, this will be tsd 12:32:40 ok, shadi; I see WAI_TSDTF()8:30AM scheduled to start 2 minutes ago 12:32:57 zakim, code? 12:32:57 the conference code is 8783 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), shadi 12:33:06 zakim, who is on the phone? 12:33:06 WAI_TSDTF()8:30AM has not yet started, shadi 12:33:07 On IRC I see RRSAgent, Christophe, shadi, carlosI 12:33:18 WAI_TSDTF()8:30AM has now started 12:33:25 +Christophe_Strobbe 12:33:41 +shadi 12:33:53 +CarlosI 12:35:40 Agenda: http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2008Jun/0024.html 12:35:48 Chair: Christophe 12:36:19 regrets: CarlosV, Tim 12:36:55 Agenda+ Reviewing remapped test samples 12:37:05 Agenda+ Schedule for meetings during July-August(-September) 12:37:06 scribe: Shadi 12:37:55 CS: a few things that need clarification 12:39:41 ...testElement, elementName, and specReference are child nodes of testElements 12:40:07 CI: testElements was designed according to the WCAG 2.0 Baseline approach 12:40:19 ...we kept it until we see what happens with WCAG 2.0 12:40:27 ...still a pending decision 12:41:03 ...time to move on, now that we have a clear view of how the WCAG 2.0 concept looks like 12:41:25 ...need to take a decision and update the metadata accordingly 12:41:49 CS: the test elements are very useful for filtering the test sample 12:42:15 ...WCAG WG looking at creating data to define Accessibility Supported Technologies 12:42:37 ...if we drop this, we may drop data that WCAG WG may be interested in 12:45:07 SAZ: seems to be a real issue, we have not revisted this concept since the change of Baseline 12:45:27 ...however, AST still under discussion in WCAG WG 12:45:46 ...may be best to wait for PR stage of the guidelines until the approach is more stable 12:45:53 ...and we understand the requirements 12:46:11 ...we can drop this data at anytime, it is not hindering our work right now 12:47:27 SAZ: maybe we should add the sub-nodes of testElements in the metadata 12:47:45 ...knowing that it is under discussion and could be dropped at any time 12:48:09 action: CS update the metadata document to reflect the subnodes under testElements 12:49:40 CS: added some notes in the metadata to help me keep track of the updated test samples 12:50:11 ...between what is uploaded and what is on the BenToWeb site 12:51:37 SAZ: ok to keep these internal notes for now, but should clarify that it is an internal note 12:51:49 ...knowing that they will be dropped when our work is finalized 12:52:33 CI: agree that internal notes are fine, but think we are setting a bad example to misuse elements for a different purpose than it was intended for 12:55:03 SAZ: could we drop this information in the description element? 12:55:24 CI: maybe better to add a specific element for this purpose 12:55:43 ...this could be shown or hidden depending on the audience or usage 12:55:54 ...but keep that information separate 12:58:46 zakim, pick a victim 12:58:46 Not knowing who is chairing or who scribed recently, I propose CarlosI 12:59:17 SAZ: how much additional work is this? 12:59:25 CS: not much work 12:59:35 SAZ: should give a heads-up to the group first 12:59:56 action: CI send a heads-up to the group about adding a new element for internal/development comments 13:01:54 CS: comment on pointers in test sample 18 13:03:40 CI: seems to be inconsistent usage of pointers, need a minimum set of rules on how to use them 13:04:22 CS: would be good to have some rules 13:05:28 CI: could write some 13:05:43 SAZ: doesn't this relate to the Pointers-in-RDF document? 13:06:00 CI: it does, and might be good to address this somewhere 13:09:04 action: SAZ bring this discussion into the ERT WG discussion on Pointers-in-RDF document, to see if these type of rules belong in there 13:12:00 CS: comment on relative vs absolute URI's in test sample 30 13:12:15 SAZ: understand that relative ones are easier for portability 13:12:35 ...but absolute ones are easier to work with for people not logged on the server 13:12:53 CS: can we keep until we have the HTML interface on W3 servers? 13:13:13 [no objections] 13:16:03 CS: question on validity in test sample 2 13:16:14 SAZ: might be best to check offline 13:18:12 zakim, take up next 13:18:12 agendum 1. "Reviewing remapped test samples" taken up [from Christophe] 13:18:19 zakim, take up agendum 2 13:18:19 agendum 2. "Schedule for meetings during July-August(-September)" taken up [from Christophe] 13:18:30 SAZ: confirmed is July 15 13:20:11 SAZ: seem we have low availability from 21 july until end august 13:20:23 ...let's figure out week by week 13:21:14 -shadi 13:21:18 -Christophe_Strobbe 13:21:22 -CarlosI 13:21:23 WAI_TSDTF()8:30AM has ended 13:21:24 Attendees were Christophe_Strobbe, shadi, CarlosI 14:06:36 zakim, bye 14:06:36 Zakim has left #tsdtf 14:06:44 rrsagent, make logs world 14:06:48 rrsagent, make minutes 14:06:48 I have made the request to generate http://www.w3.org/2008/07/01-tsdtf-minutes.html shadi 14:06:49 rrsagent, make logs world 14:06:53 rrsagent, bye 14:06:53 I see 3 open action items saved in http://www.w3.org/2008/07/01-tsdtf-actions.rdf : 14:06:53 ACTION: CS update the metadata document to reflect the subnodes under testElements [1] 14:06:53 recorded in http://www.w3.org/2008/07/01-tsdtf-irc#T12-48-09 14:06:53 ACTION: CI send a heads-up to the group about adding a new element for internal/development comments [2] 14:06:53 recorded in http://www.w3.org/2008/07/01-tsdtf-irc#T12-59-56 14:06:53 ACTION: SAZ bring this discussion into the ERT WG discussion on Pointers-in-RDF document, to see if these type of rules belong in there [3] 14:06:53 recorded in http://www.w3.org/2008/07/01-tsdtf-irc#T13-09-04