13:19:02 RRSAgent has joined #er 13:19:02 logging to http://www.w3.org/2011/11/09-er-irc 13:19:04 RRSAgent, make logs public 13:19:04 Zakim has joined #er 13:19:06 Zakim, this will be 3794 13:19:06 ok, trackbot; I see WAI_ERTWG()8:30AM scheduled to start in 11 minutes 13:19:07 Meeting: Evaluation and Repair Tools Working Group Teleconference 13:19:07 Date: 09 November 2011 13:25:20 cstrobbe has joined #er 13:26:32 philipA has joined #er 13:30:41 WAI_ERTWG()8:30AM has now started 13:30:48 +??P7 13:30:51 zakim, call shadi-617 13:30:51 ok, shadi; the call is being made 13:30:52 +Shadi 13:30:58 Zakim, ??P7 is philipA 13:30:58 +philipA; got it 13:31:35 +Christophe_Strobbe 13:32:27 Zakim, have you gotten any smarter since the last call? 13:32:27 I don't understand your question, cstrobbe. 13:33:08 regrets: Kostas, Emmanuelle, Samuel 13:34:29 carlosV has joined #er 13:35:06 scribe: philip 13:35:14 scribenick: philipA 13:35:19 +??P14 13:35:32 agenda: http://lists.w3.org/Archives/Public/public-wai-ert/2011Nov/0003.html 13:35:40 zakim, ??p14 is carlosV 13:35:40 +carlosV; got it 13:35:52 Topic: Candidate Recommendation exit criteria 13:37:34 +??P15 13:37:39 Zakim, ??P15 is philipA 13:37:39 +philipA; got it 13:38:29 Shadi: there are already some tool implementations of EARL 13:38:59 Shadi: like imergo or AccessODF 13:41:58 Shadi: need to document these implementations, the features 13:42:52 Shadi: test suites: how could they look like 13:43:50 Shadi: to enter candidate recommendation, we need implementations and test suites 13:45:05 Shadi: what is sufficient for tools, output earl or input earl as well 13:45:35 Shadi: two tools that output each feature, two tools that input each feature 13:46:18 Christophe: AccessODF both produces and consumes EARL 13:47:00 Christophe: generates EARL and displays the EARL results 13:49:33 PhilipA: imergo has a server side component that generates EARL and a client that processes and displays those EARL results 13:50:19 CarlosV: when do you need the full documentation? 13:50:43 Shadi: I would like to enter candidate recommendation in December 13:50:56 Shadi: documentations ready until end of February 13:51:04 Shadi: thats feasible? 13:51:41 CarlosV: if we concentrate first on the schema? and then on the guide? 13:52:24 Shadi: documentation needs to come from the developers 13:52:36 Shadi: same for the test suites 13:52:39 -Christophe_Strobbe 13:53:29 +Christophe_Strobbe 13:54:03 Shadi: documentation as some kind of table, listing each feature and tool 13:54:13 Shadi: half page description of the tool 13:54:22 CarlosV: thats ok 13:55:12 Shadi: tool needs not to be public 13:55:23 Shadi: only documentation of its functionality 13:55:41 Christophe: we have some test files 13:55:52 Christophe: odf files 13:56:35 kostas has joined #er 13:56:36 + +30231125aaaa 13:56:53 zakim, aaaa is kostas 13:56:53 +kostas; got it 14:01:24 kostas: yes, we can provide some tests 14:02:33 CarlosV: yes, we have for example html test files 14:03:28 Shadi: EARL report has most likely to be part of the test suite 14:04:07 Shadi: so that second tools could compare their results with those 14:04:59 Shadi: we need EARL that conform to the conformance section 14:05:10 Shadi: and EARL reports that don't conform to the conformance section 14:05:16 Shadi: what do you think? 14:05:58 kostas: we have followed EARL but we also created new attributes, that would be still conform? 14:06:09 Shadi: yes, creating new attributes is ok 14:06:40 Shadi: for example extending the outcome values is allowed 14:07:35 Shadi: testsuites will look like: 14:07:44 Shadi: 1.) sample EARL files that conform 14:08:13 Shadi: 2.) tool developers would compare their output to those to check that the EARL graphs matches 14:08:34 Shadi: 3.) plus EARL files that do not conform 14:08:55 CarlosV: sounds good 14:09:20 CarlosV: Johannes started an EARL checker once 14:10:29 Shadi: EARL checker would tell you if an EARL file conforms to the conformance sections 14:10:40 http://www.w3.org/TR/EARL10-Guide/#conformance 14:12:00 Topic: Conformance Requirements 14:13:45 Shadi: moved from schema to guide 14:14:09 Shadi: how other w3 specs handle conformance requirements 14:15:45 E.g. Mobile SVG Profiles: SVG Tiny and SVG Basic: http://www.w3.org/TR/SVGMobile/ 14:16:12 Mobile SVG Profiles: conformance criteria: http://www.w3.org/TR/SVGMobile/#sec-conformance 14:17:33 Perhaps see also OWL 2 Web Ontology Language Profiles: http://www.w3.org/TR/owl2-profiles/ 14:17:37 Conforming EARL 1.0 reports adhere to the requirements listed in 4.1 Conforming EARL 1.0 Reports 14:17:37 Software tools that produce conforming EARL 1.0 reports can provide them in valid RDF/XML notation 14:17:37 Software tools that process conforming EARL 1.0 reports can accept them in valid RDF/XML notation 14:20:01 Shadi: 1.) EARL report as meta data 14:20:06 Shadi: 1.) EARL report as output 14:20:13 Shadi: 3.) EARL report as input 14:20:28 Shadi: different rules apply 14:21:31 Shadi: continue discussion next week 14:21:48 Topic: Next Meeting 14:22:18 16 November 2011 14:22:28 i am available 14:22:38 s/1.) EARL report as output/2.) EARL report as output 14:24:09 -kostas 14:24:10 -Christophe_Strobbe 14:24:12 -philipA.a 14:24:14 -Shadi 14:24:17 -carlosV 14:24:29 philipA has left #er 14:25:13 zakim, who is on the phone? 14:25:13 On the phone I see philipA 14:25:19 zakim, drop p 14:25:19 philipA is being disconnected 14:25:20 WAI_ERTWG()8:30AM has ended 14:25:22 Attendees were Shadi, philipA, Christophe_Strobbe, carlosV, +30231125aaaa, kostas 14:25:25 trackbot, end meeting 14:25:25 Zakim, list attendees 14:25:25 sorry, trackbot, I don't know what conference this is 14:25:26 RRSAgent, please draft minutes 14:25:26 I have made the request to generate http://www.w3.org/2011/11/09-er-minutes.html trackbot 14:25:27 RRSAgent, bye 14:25:27 I see no action items