19:31:04 RRSAgent has joined #ws-ra 19:31:04 logging to http://www.w3.org/2010/03/30-ws-ra-irc 19:31:06 RRSAgent, make logs public 19:31:06 Zakim has joined #ws-ra 19:31:08 Zakim, this will be WSRA 19:31:08 ok, trackbot, I see WS_WSRA()3:30PM already started 19:31:09 Meeting: Web Services Resource Access Working Group Teleconference 19:31:09 Date: 30 March 2010 19:31:13 zakim, who is on the phone? 19:31:13 On the phone I see ??P3, +984999aaaa, Doug_Davis, Bob_Freund, [Microsoft], Tom_Rutt, +1.703.860.aabb 19:31:15 Vikas has joined #ws-ra 19:31:41 +Wu_Chou 19:31:59 + +39.331.574.aacc 19:32:05 + +1.831.713.aadd 19:32:15 zakim, aacc is asoldano 19:32:15 +asoldano; got it 19:32:21 Wu has joined #ws-ra 19:32:23 +??P13 19:33:14 gpilz has joined #ws-ra 19:33:39 http://www.w3.org/2002/ws/ra/chair-tools/scribelist.html 19:34:32 scribe: Wu 19:34:48 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Mar/0045.html 19:35:40 + +1.408.970.aaee 19:35:54 Ashok has joined #ws-ra 19:36:26 Minutes of March 16 is approved. 19:36:29 +Ashok_Malhotra 19:37:09 +Yves 19:38:03 Bob: last call WD will happen today or tomorrow depending web master. 19:38:23 Yves: it should happen quite soon 19:39:08 Bob: F2F schedule logistic information 19:39:18 Ram: it should come out very soon. 19:40:01 Bob: new issues 19:41:25 Topic: 9266 19:41:29 http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Mar/att-0039/WS-Eventing-Section_9_marked_LC-dug.doc 19:41:34 issue 9266 19:42:04 Bob: issue 9266 is accepted 19:42:36 Doug: it is a fairly minor edit to spec 19:44:39 Topic: 9320 19:44:42 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320 19:45:04 This specification does not mandate how events are serialized into 19:45:05 Decision: issue 9266 is solved as proposed. 19:45:05 notification messages. Rather, within the Subscribe request message 19:45:07 a subscriber can specify a "Format" that indicates the set of rules 19:45:08 that MUST be followed when constructing notification messages. 19:45:17 RESOLUTION: Issue 9266 resolved with the proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Mar/att-0039/WS-Eventing-Section_9_marked_LC-dug.doc 19:45:55 Bob: Issue 9266 is accepted as a new proposal 19:46:11 RESOLUTION: Issue 9320 resolved as proposed 19:46:21 Topic: 9321 19:46:23 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321 19:48:33 9321 accepted as a new issue 19:48:33 Bob: the issue is accepted as a new issue 9321 19:48:36 Topic: 9031 19:48:47 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031-Davis 19:48:51 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031 19:49:28 q+ 19:49:40 ack ram 19:50:00 Ram: did some research on it, and I am fine with Dug's proposal 19:50:17 RESOLUTION: issue 9031 resolved as proposed 19:51:07 Bob: issue 9095 19:51:21 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9095 19:51:38 q+ 19:52:01 q- 19:52:14 Ram: I am fine with Dug proposed 19:52:26 Ram: comment #1 is fine 19:52:51 RESOLUTION: issue 9096 resolve with comment #1 19:53:06 s/9096/9095 19:53:27 RESOLUTION: issue 9095 resolve with comment #1 19:54:24 q+ 19:54:38 ack dug 19:56:02 eves, why not? 19:56:13 Issue 8832: it will need more time and discuss in next meeting 19:56:25 lol 19:56:35 exactly 19:56:46 Issue 8284 on WSDL version 19:57:13 Bob: need time frame to resolve this issue 19:58:54 Ram: we are expecting in mid May to get down to this issue 20:00:01 Bob: how long for the WG to wait? 20:00:29 Ram: it is about three month. 20:01:07 Bob: Dependency on BP might affect our progress. 20:01:39 q+ 20:01:39 Gil: let's see what happens until what we progress 20:01:48 q- 20:02:41 q+ 20:02:49 q- 20:02:55 Bob: we discuss at F2F to find out which feature will be at risk 20:03:12 Bob: there is plenty things to do at F2F 20:04:32 Bob: There is a remaining issue 9250 20:05:12 Bob: anybody needs more time to talk issue 9321 20:05:25 Bob: there is a proposal for issue 9321 20:06:04 q+ 20:06:30 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321 20:06:54 acl gp 20:06:57 ack gp 20:07:42 q+ 20:07:56 Gil: that does not particular bother me. If both are optional, then it is unclear. 20:08:20 Gil: want to take a look of Dug's propoal 20:09:35 Dug: we need to address this issue from Format 20:11:42 Action: discuss over the mailing list and progress it to resolution 20:11:42 Sorry, couldn't find user - discuss 20:11:56 Issue 9250 20:12:20 zakim, who is noisy? 20:12:31 gpilz, listening for 10 seconds I heard sound from the following: Doug_Davis (73%), [Microsoft] (44%) 20:12:40 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250 20:13:10 q+ 20:13:13 q- 20:13:18 Dug: I have slight preference to put things in MEX and well comments 20:13:40 ack ram 20:13:43 Ram: I am still researching this issue. 20:14:29 q+ 20:14:57 Ram: SOAP version is part of binding 20:15:33 ack dug 20:16:15 Dug: it is more for the case that wsdl is not available 20:16:50 q+ 20:16:58 q- 20:17:05 Yves: if no wsdl availabe, then server decides 20:17:11 zakim, who is noisy? 20:17:24 gpilz, listening for 12 seconds I heard sound from the following: Doug_Davis (52%), ??P13 (4%), Yves (76%) 20:17:56 Ram: I need more time to make progress on this issue 20:18:13 Action: discuss this issue in the next call 20:18:13 Sorry, couldn't find user - discuss 20:19:52 Ram: issue 9087 is a reasonable question raised. 20:20:46 Ram: we can say xml resouce with an xml representation 20:22:08 Bob: if you have an empty resource, what will be the return of "GET" 20:23:39 http://www.w3.org/2002/ws/ra/edcopies/wst.html#InvalidRepresentation 20:23:40 Bob: If the encoding and xml format is not acceptable, we define a fault. 20:23:56 If an implementation detects that the presented representation is invalid for the target resource, then the implementation MUST generate a wst:InvalidRepresentation fault. 20:25:01 so "is invalid" -> "is invalid or incompatible" 20:25:05 ? 20:27:20 Bob: resource defined in xml infoset, any thought about that? 20:29:20 q+ 20:30:14 q+ 20:30:21 ack gp 20:30:25 ack ram 20:30:42 Bob: what is a better approach: constrain the def of resource, or we manipulate, ... 20:30:42 - +984999aaaa 20:30:49 on the comment thing, people may just be forced to pass in the parent in some cases - not idea but it can work. 20:30:58 s/idea/ideal/ 20:31:30 Topic: 8273 20:31:34 http://www.w3.org/Bugs/Public/show_bug.cgi?id=8273 20:32:07 Gil: issue 8273 can touch all specs. 20:32:09 propasal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Mar/0046.html 20:34:59 Gil: WS-E can discuss notification. You may check security at the subscription time, or check at per-notificaion basis. 20:35:57 q+ 20:36:11 ack katy 20:36:11 Ram: I will take a look at it. 20:37:23 Katy: Event source integrity is important 20:37:53 Gil: In addition, it needs authentication, etc. as well. 20:42:00 Gil: endpoint verification - event sink also needs to be protected. 20:42:28 the concept of a useful security section is mind blowing! 20:43:33 Bob: what is the plan? 20:44:35 bye 20:44:36 -[Microsoft] 20:44:39 -Wu_Chou 20:44:40 -Ashok_Malhotra 20:44:41 -Tom_Rutt 20:44:42 - +1.408.970.aaee 20:44:43 - +1.831.713.aadd 20:44:44 -Yves 20:44:46 -??P13 20:44:50 -??P3 20:44:51 -Bob_Freund 20:44:51 -asoldano 20:45:00 -Doug_Davis 20:45:38 rrsagent, generate minutes 20:45:38 I have made the request to generate http://www.w3.org/2010/03/30-ws-ra-minutes.html Bob 20:47:04 - +1.703.860.aabb 20:47:05 WS_WSRA()3:30PM has ended 20:47:07 Attendees were +984999aaaa, Doug_Davis, Bob_Freund, [Microsoft], Tom_Rutt, +1.703.860.aabb, Wu_Chou, +39.331.574.aacc, +1.831.713.aadd, asoldano, +1.408.970.aaee, Ashok_Malhotra, 20:47:10 ... Yves 21:18:17 gpilz has left #ws-ra