13:51:00 RRSAgent has joined #er 13:51:00 logging to http://www.w3.org/2007/05/23-er-irc 13:51:05 Zakim has joined #er 13:51:12 zakim, this will be ert 13:51:12 ok, shadi; I see WAI_ERTWG()10:00AM scheduled to start in 9 minutes 13:51:19 meeting: ERT WG 13:51:24 chair: Shadi 13:51:32 regrets: CarlosI, CarlosV 13:51:55 agenda: http://lists.w3.org/Archives/Public/public-wai-ert/2007May/0014.html 13:52:06 agenda+ HTTP Vocabulary in RDF comments 13:52:18 agenda+ EARL 1.0 Schema comments 13:55:38 JohannesK has joined #er 13:55:52 regrets: CarlosI, CarlosV, Charles 13:58:33 WAI_ERTWG()10:00AM has now started 13:58:41 +JohannesK 14:00:28 +Shadi 14:05:27 Reinhard has joined #er 14:06:15 + +43.702.468.aaaa 14:07:03 drooks has joined #er 14:08:39 zakim, +43.702.468.aaaa is really Reinhard 14:08:40 +Reinhard; got it 14:09:32 agenda? 14:09:46 zakim, please take up agendum 1 14:09:46 agendum 1. "HTTP Vocabulary in RDF comments" taken up [from shadi] 14:10:07 scribe: Reinhard 14:13:44 JK: discusses issue 001 - incomplete response should be noted, when connection failed no response note can be taken, 14:14:06 JK: item was discussed in last conference 14:16:55 JK: talks about an incomplete HTTP-response 14:18:17 SAZ: possible scenario: client sends request, which is incomplete. Then a client might also recieve an incomplete response 14:20:57 SAZ: How does EARL handle incomplete responses (eg because of a server timeout)? 14:22:46 JK: Issue 003 was closed as NO during last conference. 14:23:13 i think last week we said that issue 001 could be represented in HTTP RDF through the absence of an expected response class 14:24:04 JK: It is out of scope of the vocabulary 14:24:25 SAZ: Thinks it is META-Information on requests and responses 14:25:05 SAZ: would recommend it at least as optional information 14:28:08 JK: If we would take up response times - which element to take (eg from DC) 14:33:42 SAZ: There could be use cases where recording of timestamps might be useful in HTTP in RDF 14:35:11 ACTION: SAZ: get feedback from working group on timestamp issues 14:35:51 SAZ: takes up Issue-017 14:39:11 JK: if default character encoding cannot be used, we wanted to use DATA URI 14:41:07 JK: inclusion of DTD can be solved through combination of seperate properties, which are combined 14:41:51 SAZ: We need a different concept for the body 14:42:12 SAZ: Maybe different classes according to different content types 14:49:08 ACTION: JK: draft a concept for the solution of problem with body property (Issue 14,15 & 17) 14:53:23 SAZ: we should try to get message headers as literal values 14:54:55 JK: we record the response code, but some persons might want to know the actual meaning 14:59:14 SAZ: Literal vs. predifined value consideration is also an performace issue 15:00:22 SAZ: keep on discussing the advantages/disadvantages of literal values and predifined values on the mailing list 15:05:07 http://lists.w3.org/Archives/Public/public-wai-ert/2007May/0015.html 15:06:51 JK: Thinks this approach is valuable, maybe also for other properties 15:08:15 RESOLUTION: tentativly accepted solution provided by SAZ 15:13:31 -JohannesK 15:13:34 -Reinhard 15:13:38 -Shadi 15:13:39 WAI_ERTWG()10:00AM has ended 15:13:41 Attendees were JohannesK, Shadi, Reinhard 15:16:19 zakim, bye 15:16:19 Zakim has left #er 15:16:27 rrsagent, make logs world 15:16:32 rrsagent, make minutes 15:16:32 I have made the request to generate http://www.w3.org/2007/05/23-er-minutes.html shadi 15:16:33 rrsagent, make logs world 15:16:37 rrsagent, bye 15:16:37 I see 2 open action items saved in http://www.w3.org/2007/05/23-er-actions.rdf : 15:16:37 ACTION: SAZ: get feedback from working group on timestamp issues [1] 15:16:37 recorded in http://www.w3.org/2007/05/23-er-irc#T14-35-11 15:16:37 ACTION: JK: draft a concept for the solution of problem with body property (Issue 14,15 & 17) [2] 15:16:37 recorded in http://www.w3.org/2007/05/23-er-irc#T14-49-08