12:32:43 RRSAgent has joined #er 12:32:43 logging to http://www.w3.org/2009/04/22-er-irc 12:32:45 RRSAgent, make logs public 12:32:45 Zakim has joined #er 12:32:47 Zakim, this will be 3794 12:32:47 ok, trackbot; I see WAI_ERTWG()8:30AM scheduled to start 2 minutes ago 12:32:48 Meeting: Evaluation and Repair Tools Working Group Teleconference 12:32:48 Date: 22 April 2009 12:33:06 zakim, call shadi-617 12:33:07 ok, shadi; the call is being made 12:33:25 zakim, who is on the phone? 12:33:25 WAI_ERTWG()8:30AM has not yet started, shadi 12:33:26 On IRC I see RRSAgent, JohannesK, carlosI, MikeS, shadi, trackbot 12:34:35 present: Mike, Johannes, CarlosI, Shadi, CarlosV 12:35:57 agenda: http://lists.w3.org/Archives/Public/public-wai-ert/2009Apr/0025.html 12:36:07 scribe: MikeS 12:36:16 agenda+ Requirements Document 12:36:23 agenda+ Pointer Comments 12:36:35 agenda+ EARL 1.0 Guide Document 12:36:44 agenda+ Next meetings 12:37:02 zakim, take up agendum 1 12:37:02 agendum 1. "Requirements Document" taken up [from shadi] 12:37:12 http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Requirements-20090421.html 12:37:52 Topic: requirements document 12:38:01 http://lists.w3.org/Archives/Public/public-wai-ert/2009Apr/0026.html 12:38:11 ah, ok 12:38:52 points from MS on requirements document 12:39:37 0 is requirement doc for entire EARL document suite or just schema? 12:40:08 SAZ: assumption seems to be applies to the EARL Schema only but not called out explicitly 12:41:34 CI: it seems implicit that these are reqiurements for the schema 12:41:49 ...but still, ambiguity between EARL - Schema vs. entire suite of documents 12:42:15 SAZ: document is dated, developed in 2005 prior to splitting EARL into modules or parts 12:43:05 ...good place to define EARL and its related components or vocabularies 12:43:17 ...return to overview doc and adapt accordingly 12:43:34 CI: requirements doc is not the place to define relationships between vocabularies 12:44:26 SAZ: requirements doc does not need to spell out in detail but is there a problem with pointing out or specifying each vocabulary/component? 12:44:32 cvelasco has joined #er 12:45:36 CI: entire thrust of document must change - title, for example, should be something like "Requirements for EARL Framework" 12:47:44 SAZ: if 'EARL 1.0' is spelled out as a framework with many parts, then thrust of requirements doc is clear 12:48:32 CI: agreed - specify as a framework but specifics about components should not be a requirement (e.g. number of vocabularies, relationship between them) 12:49:52 JK: agree with CI - requirements document (RD) should be a document pertaining to the entire suite 12:50:37 ...what is the purpose of the requirements document? 12:50:54 SAZ: 1) internally, for the group, keeps us on track in temrs of what we're trying to do 12:51:03 ...2) people do read to understand the goals 12:51:24 ...3) demonstrate that we've satisified our requirements to W3C community 12:51:49 JK: a bit odd, though, to write/tinker the RD after the suite is nearly complete 12:52:47 ...could have RD for each vocabulary 12:53:41 ...overall framework RD and specific RDs for each vocabulary (Pointers in RDF, Representing Content in RDF, etc.) 12:54:44 SAZ: clearly an iterative process, started in 2005 12:55:03 ...adjust and adapt as we move ahead 12:55:34 ...requirements is not as stringent as, say, in a software development context 12:56:35 ...good example of need in external context is points made by XML group about Pointers in RDF; might ahve been answered by a solid RD 12:59:31 SAZ: conclusion seems to be that RD is for entire EARL suite 12:59:59 RESOLUTION: Requirements Document has scope of entire EARL Document Suite, not just Schema and should be spelled out explicitly in RD 13:00:40 SAZ: resolution may have implications for title, structure, and other aspects of the RD 13:02:56 SAZ: MS should edit abstract according to more generic use of EARL to non-accessibility realms 13:04:36 ...restriction to web is necessary given area of expertees but want to remain open to toher ocntexts 13:04:44 ...avoid scope creep and entering into 13:08:39 MS: Removed "computational" from D03 but do we need to have "in a reasonable time?" 13:09:06 SAZ: need some sor tof formulation about reasonable performance for EARL consumers and producers based on complexity of the specification 13:09:38 ...persistence in F03 refers to repeatability given, say, http exchange 13:10:28 ...F04 is supported via extensibility; somewhat handled by the guide 13:11:57 http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Schema-20090410#TestSubject 13:13:03 JK: aggregation seems to mean colection or assimilation 13:13:08 ...if not the meaning, change the word 13:15:05 ...one interpretation is when a test subject is tested against different test criteria (e.g. WCAG2, Sec 508) 13:15:43 CV: combine test results from testing same resource 13:17:58 SAZ: recall discussion of a truth table for aggregation (e.g. what happens if one test result against a test subject is PASS and another result of same resource is FAIL) 13:18:00 ok 13:19:40 SAZ: Question is how do we "support aggregation? 13:20:45 "...no guidance on resolving conflicting results 13:21:13 ...MS should start a thread on this 13:22:45 JK: logical combination of composition of test results is out of scope for EARL 13:24:02 zakim, take up next 13:24:02 agendum 2. "Pointer Comments" taken up [from shadi] 13:24:40 http://lists.w3.org/Archives/Public/public-wai-ert/2009Apr/0028.html 13:25:44 SAZ: propose to find a different name for ptr:XMLNamespace given that terms prefixed with 'xml' are reserved 13:26:57 ...look at introduction and abstract for more clear description of text-orientedpointers 13:27:03 rememeber that we have also the XML names problem in other documents like "Representing Content in RDF" 13:27:27 ...remove examples that refer to abstract or generic classes 13:30:03 zakim, take up next 13:30:03 agendum 3. "EARL 1.0 Guide Document" taken up [from shadi] 13:30:25 http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Guide-20090422.html 13:32:31 zakim, take up next 13:32:31 agendum 4. "Next meetings" taken up [from shadi] 14:01:21 trackbot, end meeting 14:01:21 Zakim, list attendees 14:01:21 sorry, trackbot, I don't know what conference this is 14:01:22 RRSAgent, please draft minutes 14:01:22 I have made the request to generate http://www.w3.org/2009/04/22-er-minutes.html trackbot 14:01:23 RRSAgent, bye 14:01:23 I see no action items