14:51:38 RRSAgent has joined #er 14:51:38 logging to http://www.w3.org/2006/11/22-er-irc 14:51:44 Zakim has joined #er 14:51:51 zakim, this will be ERT 14:51:51 ok, shadi; I see WAI_ERTWG()10:00AM scheduled to start in 9 minutes 14:51:56 meeting: ERT WG 14:52:00 chair: Shadi 14:52:27 agenda: http://lists.w3.org/Archives/Public/public-wai-ert/2006Nov/0020.html 14:52:42 agenda+ sequences in the HTTP vocabulary 14:52:55 agenda+ additional validity level values 14:53:07 agenda+ addressing security/privacy in EARL 14:57:06 JohannesK has joined #er 14:58:31 ChrisR has joined #er 14:58:33 davidr has joined #er 14:59:41 WAI_ERTWG()10:00AM has now started 14:59:43 +Shadi 14:59:56 +[IPcaller] 15:00:12 +??P5 15:00:30 zakim, ipcaller is really David 15:00:30 +David; got it 15:00:41 zakim, ? is really Johannes 15:00:41 +Johannes; got it 15:01:27 +[IPcaller] 15:01:37 zakim, ipcaller is really Chris 15:01:37 +Chris; got it 15:01:38 +Daniela 15:01:55 Daniela has joined #er 15:02:17 CarlosI has joined #er 15:02:36 regrets: CarlosV 15:03:00 scribe: David 15:03:08 scribenick: davidr 15:03:14 +berrueta 15:03:55 zakim, berrueta is really CarlosI 15:03:55 +CarlosI; got it 15:04:10 zakim, take up agendum 1 15:04:10 agendum 1. "sequences in the HTTP vocabulary" taken up [from shadi] 15:05:07 http://lists.w3.org/Archives/Public/public-wai-ert/2006Oct/0017 15:05:45 shadi: how to reconr sequences of headers that are sent and recoieved from the server 15:07:33 johannesk: summarises his email - http://lists.w3.org/Archives/Public/public-wai-ert/2006Oct/0017 15:11:42 shadi: the sequence of values is very important 15:13:23 shadi: not sure the importance of sequence in which headers occur 15:15:07 s/headers/headers of different types 15:15:32 action: saz add an editors note in the WD asking for feedback on potential conflict regarding sequence of *different* header types 15:18:27 probably sequence is not relevant for our use case in both cases but... 15:18:50 if we wont the HTTP in RDF vocabulary to be stand-alone... 15:19:09 I think both sequences could be relevant for other use cases 15:20:57 shadi: HTTP protocol makes no assumption on the order of headers 15:21:04 -Chris 15:22:04 +[IPcaller] 15:22:11 zakim, ipcaller is really Chris 15:22:11 +Chris; got it 15:23:27 "Header: Value1\nHeader: Value2" should result in "Header: Value1, Value2" 15:23:46 proposed resolution: in earl, sequence of values should be flattened out into comma seperated string 15:26:04 RESOLUTION: in earl, sequence of values within the same request/response should be flattened out into comma seperated string 15:27:51 shadi: the other scenario - sequence of multiple requests/responses between client and server 15:29:07 e.g. content negotiation 15:29:24 several request and response before getting any content 15:31:53 johannesK: record every piece of content seperately in a webcontent class and combine them together 15:34:15 but if you want to exactly reproduce the same conditions you need to record all the sequence 15:34:43 johannesK: redirects could be captured in individual webcontent classes 15:35:31 johannesK: e.g. redirect = a->b->c, we could capture a,b & c as individual webcontent classes 15:35:56 and what are the subjects? 15:39:04 ACTION: jk to write down some thoughts about his proposal of recording 1. simple request/response pair, 2. content negotiation, 3. redirect 15:39:56 zakim, close agendum 1 15:39:56 agendum 1, sequences in the HTTP vocabulary, closed 15:39:57 I see 2 items remaining on the agenda; the next one is 15:39:58 2. additional validity level values [from shadi] 15:40:00 zakim, take up agendum 2 15:40:00 agendum 2. "additional validity level values" taken up [from shadi] 15:41:17 shadi: summarizes discussion thus far 15:46:19 davidr: proposes the introduction of a warning property within the result class 15:50:30 f 15:50:52 have always thought warnings are QA bad practices in general 15:51:01 sorry, have to leave a bit earlier today ... 15:51:04 -Daniela 15:51:06 johannesK: chaals raised the point, what kind of warning it is? 15:51:06 not sure if we should support themm in EARL 15:51:19 they are a can of worms 15:51:38 almost each warning is unique 15:54:18 proposal: 15:54:35 use always one of the current values: pass, fail, etc. 15:54:38 then... 15:54:59 we can add a new warning class you can use 15:55:13 but not associated with any specific value 15:55:51 yes 15:56:05 you use alway one of the current values 15:56:40 -Chris 15:56:40 and you can additionally provide a warning 15:56:41 ChrisR has left #er 15:57:06 imposible to star working on it until next tuesday 15:57:40 ok 15:58:21 ACTION: CarlosI to summarize his proposal about warnings on the mailing list 15:59:34 -Johannes 15:59:37 bye 15:59:38 -David 15:59:42 -Shadi 15:59:46 -CarlosI 15:59:52 WAI_ERTWG()10:00AM has ended 15:59:54 Attendees were Shadi, David, Johannes, Chris, Daniela, CarlosI 16:01:17 davidr has left #er 16:01:37 zakim, bye 16:01:37 Zakim has left #er 16:01:49 rrsagent, make logs world 16:01:55 rrsagent, make minutes 16:01:55 I have made the request to generate http://www.w3.org/2006/11/22-er-minutes.html shadi 16:01:57 rrsagent, make logs world 16:02:01 rrsagent, bye 16:02:01 I see 3 open action items saved in http://www.w3.org/2006/11/22-er-actions.rdf : 16:02:01 ACTION: saz add an editors note in the WD asking for feedback on potential conflict regarding sequence of *different* header types [1] 16:02:01 recorded in http://www.w3.org/2006/11/22-er-irc#T15-15-32 16:02:01 ACTION: jk to write down some thoughts about his proposal of recording 1. simple request/response pair, 2. content negotiation, 3. redirect [2] 16:02:01 recorded in http://www.w3.org/2006/11/22-er-irc#T15-39-04 16:02:01 ACTION: CarlosI to summarize his proposal about warnings on the mailing list [3] 16:02:01 recorded in http://www.w3.org/2006/11/22-er-irc#T15-58-21