14:58:17 RRSAgent has joined #er 14:58:18 logging to http://www.w3.org/2007/03/07-er-irc 14:58:28 Zakim has joined #er 14:58:35 zakim, this will be ert 14:58:35 ok, shadi; I see WAI_ERTWG()10:00AM scheduled to start in 2 minutes 14:58:41 meeting: ERT WG 14:58:44 chair: Shadi 14:58:52 regrets: David 14:59:08 agenda: http://lists.w3.org/Archives/Public/public-wai-ert/2007Mar/0013.html 14:59:22 agenda+ Updated EARL 1.0 Schema Editor's Draft 14:59:35 JibberJim has joined #er 14:59:43 agenda+ Updated HTTP Vocabulary in RDF Editor's Draft 14:59:52 agenda+ Updated EARL Introduction page 15:00:03 agenda+ Check-in on Last Call publication schedule 15:00:46 WAI_ERTWG()10:00AM has now started 15:00:48 +Shadi 15:03:03 +[IPcaller] 15:03:07 -Shadi 15:03:09 +Shadi 15:04:00 CarlosI has joined #er 15:06:16 +berrueta 15:06:35 zakim, berrueta is really CarlosI 15:06:35 +CarlosI; got it 15:07:18 JohannesK has joined #er 15:07:27 CarlosV has joined #er 15:07:53 +Thomas 15:07:57 scribe: Jim 15:08:07 scribenick: JibberJim 15:08:24 zakim, thomas is really johannesK 15:08:24 +johannesK; got it 15:09:33 zakim, IPCaller is really Jim Ley 15:09:34 I don't understand 'IPCaller is really Jim Ley', JibberJim 15:09:57 zakim, ipcaller is really Jim 15:09:57 +Jim; got it 15:10:00 +johannesK.a 15:10:07 agenda? 15:10:28 zakim, take up agendum 1 15:10:28 agendum 1. "Updated EARL 1.0 Schema Editor's Draft" taken up [from shadi] 15:10:37 http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Schema-20070226 15:10:39 zakim, johannesK.a is really CarlosV 15:10:39 +CarlosV; got it 15:11:38 SZ: Some minor comments addressed in the Schema doc and now ready for review 15:12:01 SZ: Any additional comments on it? 15:12:40 CV: Namespace changed? 15:13:03 SZ: We're going to request the namespace change with the last call request to publish 15:13:32 http://www.w3.org/WAI/ER/EARL/nmg-strawman# 15:13:51 SZ: nmg-strawman in the current namespace 15:14:26 http://www.w3.org/2007/earl# 15:14:34 SZ: We said we'd stay with this until last call and then change to http://www.w3.org/2007/earl# 15:14:50 SZ: And we need directors approval for that namespace and we'll request that at LC time 15:16:03 http://www.w3.org/WAI/ER/EARL10/schema.rdf 15:19:23 CI: In Section 2.3 testSubject - should we clarify which date to use tested or identified 15:20:16 CI: e.g. if you tested something "it should be the date tested" or "if you fetched it but didn't test immediately use the fetch dated" 15:20:31 SZ: There's another, which is the creation of date of a web-resource 15:20:45 CI: For testing proposals, I think you need the date of the test 15:21:37 SZ: this is the testSubject class so it's "what was tested" not information about the test 15:22:48 CI: creation date of a resource is unreliable, you can't rely on it so for me the test date it was run is more reliable and useful 15:24:44 CI: We need to develop something in the date property so people should know what to expect here. 15:25:46 SZ: We should try to pick this up on mailing list - I agree more description on the dc:date would be good, and maybe add date to the test result too. 15:26:37 CI: Section 2.4 earl:Test Criterion - unclear language confusion between testable and test criterion, testable is the Class but we confuse with test criterion 15:27:33 SZ: This is just an editorial comment? 15:27:36 CI: Yes 15:29:24 CI: We should be clearer on references we use 15:29:58 SZ: We should increase the examples 15:30:33 CI: I'd like to add a note to encourage the use of WCAG public URI's 15:30:45 CV: We discussed that before - close to Test Description language 15:31:16 CI: I want to avoid an incompatibility problem, by encouraging the right URI's up front 15:31:22 CV: I don't think we can solve this problem here 15:31:46 SZ: I think we could do some things - e.g. instead of using example.org uri's use real ones from the HTML test-suite or something 15:33:03 SZ: Please send your comments to the list 15:35:40 zakim, take up next 15:35:40 agendum 2. "Updated HTTP Vocabulary in RDF Editor's Draft" taken up [from shadi] 15:35:56 http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20070301 15:37:22 SZ: Substantial changes out of the F2F 15:39:53 SZ: Next week want the decision on publish or not too publish 15:41:14 http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20070301#body 15:42:56 SZ: CV was it understandable? 15:43:09 CV: Yes it was clear 15:43:21 RFC for data URI scheme is RFC 2397 15:43:48 CV: although DATA URI's aren't well known 15:44:01 SZ: So we should probably have clearer link to the DATA RFC reference 15:45:02 ACTION: JK and SZ to add RFC 2397 to references, and link it from section 2.6 15:46:59 SZ: Should we have cardinality restrictions on some of the properties? 15:47:42 SZ: e.g. on parameters we require two things sometimes, but don't require people to record things like HTTP response codes - or with 10 response codes 15:48:15 SZ: so we could require at most 1 response code, or no exactly 1 15:49:00 SZ: JK had preference for exactly 1, I think you might want to report a broken HTTP response without a response code 15:49:32 JL: I like the idea of at most 1 15:50:12 JK: I favour exactly 1, as I don't think it's ocmplete but I could live with at most 1 15:50:31 JK: I feel a response without a response code would not be a response but an error 15:51:25 CI: I think there are several use cases where we require minimal information to make sense and responseCode should be one of those 15:51:50 SZ: Okay sounds like something for the mailing list 15:52:11 -Jim 15:52:20 scribe: JohannesK 15:53:06 CV: what's the use case for not having a response code? 15:53:51 SAZ: stand-alone, server sends incomplete response, you want to be able to describe this 15:54:57 ACTION: SAZ to send mail for discussing missing response code scenario to mailing list 15:55:02 http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20070301#example 15:56:35 SAZ: appendix D: realistic example, but only one request/response pair; should we have a second request/response pair (e.g. additional image to show data URI)? 15:57:24 JK: good to have more request/response pairs to show that more than one request is possible in connection 15:57:54 ACTION: JK to add another request/repsonse pair (image) to appendix D 15:59:04 SAZ: there's an issue with document type declaration in body, you cannot use it directly with parseType="Literal" 15:59:40 SAZ: keep it this way 15:59:42 zakim, take up next 15:59:43 agendum 3. "Updated EARL Introduction page" taken up [from shadi] 15:59:45 http://www.w3.org/WAI/intro/earl.php 16:00:54 SAZ: introduction page about EARL, updated to latest work 16:01:07 SAZ: send comments about it 16:01:38 CI: why is EARL Guide in Technical, not Educational section? 16:01:56 SAZ: EARL Guide will be published as technical document 16:02:17 SAZ: Educational is more like presentations, ... 16:02:56 CI: add information about status of EARL to encourage feedback 16:03:37 ACTION: SAZ to add text about encouraging feedback on EARL intro page 16:03:48 zakim, take up next 16:03:48 agendum 4. "Check-in on Last Call publication schedule" taken up [from shadi] 16:03:58 http://www.w3.org/WAI/intro/earl.php 16:04:10 http://lists.w3.org/Archives/Public/public-wai-ert/2007Feb/0068 16:04:12 http://lists.w3.org/Archives/Public/public-wai-ert/2007Feb/0068 16:05:07 I need to take off, see you next week 16:05:08 -CarlosV 16:05:19 SAZ: nearly in time 16:05:37 SAZ: Jim will be able to create a new pointers draft next week 16:06:30 SAZ: later tonight strawpoll will be open for publication of EARL schema draft as last call 16:07:04 SAZ: send comments also to list first, then vote later 16:07:26 -johannesK 16:07:29 -Shadi 16:07:35 -CarlosI 16:07:37 WAI_ERTWG()10:00AM has ended 16:07:38 Attendees were Shadi, CarlosI, johannesK, Jim, CarlosV 16:09:31 zakim, bye 16:09:31 Zakim has left #er 16:09:39 rrsagent, make logs world 16:09:43 rrsagent, make minutes 16:09:43 I have made the request to generate http://www.w3.org/2007/03/07-er-minutes.html shadi 16:09:45 rrsagent, make logs world 16:09:51 rrsagent, bye 16:09:51 I see 4 open action items saved in http://www.w3.org/2007/03/07-er-actions.rdf : 16:09:51 ACTION: JK and SZ to add RFC 2397 to references, and link it from section 2.6 [1] 16:09:51 recorded in http://www.w3.org/2007/03/07-er-irc#T15-45-02 16:09:51 ACTION: SAZ to send mail for discussing missing response code scenario to mailing list [2] 16:09:51 recorded in http://www.w3.org/2007/03/07-er-irc#T15-54-57 16:09:51 ACTION: JK to add another request/repsonse pair (image) to appendix D [3] 16:09:51 recorded in http://www.w3.org/2007/03/07-er-irc#T15-57-54 16:09:51 ACTION: SAZ to add text about encouraging feedback on EARL intro page [4] 16:09:51 recorded in http://www.w3.org/2007/03/07-er-irc#T16-03-37