20:27:18 RRSAgent has joined #ws-ra 20:27:18 logging to http://www.w3.org/2010/01/19-ws-ra-irc 20:27:20 RRSAgent, make logs public 20:27:20 Zakim has joined #ws-ra 20:27:22 Zakim, this will be WSRA 20:27:22 ok, trackbot, I see WS_WSRA()3:30PM already started 20:27:23 Meeting: Web Services Resource Access Working Group Teleconference 20:27:23 Date: 19 January 2010 20:27:27 +Wu_Chou 20:27:41 +Bob_Freund 20:28:28 + +984999aaaa 20:28:59 +Doug_Davis 20:29:00 Ashok has joined #ws-ra 20:29:05 zakim, aaaa is sreed 20:29:05 +sreed; got it 20:29:13 Vikas has joined #ws-ra 20:29:33 ah, never got the agenda email 20:30:04 + +1.571.262.aabb 20:30:22 zakim, aabb is vikas 20:30:22 +vikas; got it 20:30:25 + +1.408.642.aacc 20:30:49 +Ashok_Malhotra 20:30:57 zakim, aacc is Gilbert 20:30:57 +Gilbert; got it 20:31:10 +Yves 20:31:20 gpilz has joined #ws-ra 20:31:34 +Tom_Rutt 20:32:13 Sreed has joined #ws-ra 20:33:26 Katy has joined #ws-ra 20:33:35 +[Microsoft] 20:33:46 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0090.html 20:33:57 +??P22 20:34:07 + +03531803aadd 20:34:11 asir has joined #ws-ra 20:34:17 MartinC has joined #ws-ra 20:34:44 Ram has joined #ws-ra 20:36:07 scribe: Vikas 20:36:26 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0090.html 20:36:54 wow, 30! :-) 20:37:02 such the optimist 20:37:34 AGENDA: Agenda accepted without any objection in the working group. 20:38:13 RESOLUTION: The minutes from Dec 15 2009 meeting has been approved without objection 20:38:27 RESOLUTION: The minutes from Jan 05 2010 meeting has been approved without objection 20:38:46 do we have the logistic for the f2f? street address? times? 20:39:12 q+ 20:39:28 + +1.408.970.aaee 20:39:30 it appears that the W3C list archive is not (or slow in) pushing out mails to list subscribers 20:39:46 RESOLUTION: The minutes from Jan 12 2010 meeting has been approved without objection 20:39:55 fmaciel has joined #ws-ra 20:40:03 f2f logistics http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/0010.html 20:49:23 Proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0065.html 20:49:51 TOPIC: Issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068 20:50:10 Proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0065.html 20:51:13 RESOLUTION: Resloved as proposed above. 20:51:35 s/esloved/esolved/ 20:51:53 +JeffM 20:51:57 TOPIC: Issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180 20:52:25 q+ 20:52:45 ack gp 20:52:47 LOL the color throw me too 20:52:49 ack ram 20:54:09 q+ to ask a question 20:55:31 Vikas1 has joined #ws-ra 20:55:36 ack asir 20:55:36 asir, you wanted to ask a question 20:55:53 TOPIC: Issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283 20:56:05 Latest proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0086.html 20:56:12 what is the analogy of empty string there? do we ned at least an xml decl? 20:56:32 Ashok has joined #ws-ra 20:57:39 The term "generate" is used in relation to the various faults defined by this specification to imply that a fault is produced, no further processing SHOULD be performed, and the fault would normally be transmitted. 20:57:44 Bob, can you make Vikas1 as scribe 20:58:09 scribenick: Vikas1 20:58:18 s/would normally/SHOULD/ 20:58:32 q+ 20:58:38 ack ram 20:59:19 Vikas2 has joined #ws-ra 21:00:00 q+ 21:00:23 Bob, can you please mark Vikas2 as scribe. 21:00:24 ack gp 21:00:37 scribenick: Vikas2 21:01:09 ... no further processing SHOULD be performed. In these cases the fault SHOULD be transmitted. 21:02:11 Basic Profile says: "Both SOAP and this Profile use the term 'generate' to denote the creation of a SOAP Fault. It is important to realize that generation of a Fault is distinct from its transmission, which in some cases is not required. " 21:02:44 q+ 21:02:47 jeffm has joined #ws-ra 21:03:02 ack gp 21:04:07 The term "generate" is used in relation to the various faults defined by this specification to imply that a fault is produced and no futher processing SHOULD be performed. In these cases the fault SHOULD be transmitted. However, there might be when a compliant implementation might choose not to transmit the fault - for example, security concerns - in these situations the fault MAY NOT be... 21:04:09 ...transmitted. 21:04:16 Wu, better? 21:04:29 s/be when/be reasons when/ 21:04:41 Gil: There will be very few cases where fault is not propagated, if its generate the fault should be send back to the consumer. 21:05:30 The term "generate" is used in relation to the various faults defined by this specification to imply that a fault is produced and no futher processing SHOULD be performed. In these cases the fault SHOULD be transmitted. However, there might be reasons when a compliant implementation can choose not to transmit the fault - for example, security concerns - in these situations the fault MAY NOT... 21:05:32 ...be transmitted. 21:06:19 -sreed 21:06:20 RESOLUTION: Resolved 8283 with proposed text above. 21:06:33 +[IPcaller] 21:06:38 TOPIC: Issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286 21:06:50 proposal: The term "generate" is used in relation to the various faults defined by this specification to imply that a fault is produced and no futher processing SHOULD be performed. In these cases the fault SHOULD be transmitted. However, there might be when a compliant implementation might choose not to transmit the fault - for example, security concerns - in these situations the fault MAY NOT be 21:06:56 proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0084.html 21:08:47 someone needs to move their mic 21:08:49 RESOLUTION: 8286 resolved with above propsal, proposed in message nos. 84 21:09:12 proposal: http://www.w3.org/Bugs/Public/show_bug.cgi?id=8301#c1 21:09:14 Proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0091.html 21:09:28 TOPIC: Issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=8301 21:09:36 proposal: http://www.w3.org/Bugs/Public/show_bug.cgi?id=8301#c1 21:10:03 Proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0091.html 21:11:41 q+ 21:12:21 ack dug 21:13:13 q+ 21:14:21 FaultOnPutDenied: When present, this OPTIONAL parameter indicates that attempts to change portions of the representation that are read-only will generate a wst:PutDenied fault. If this parameter is not present, attempts to modify read-only portions of the resource representation will be ignored without any fault being generated. 21:15:07 q+ 21:15:48 ack gp 21:17:03 ack du 21:18:29 Vikas2 has joined #ws-ra 21:19:42 I would note that adding something to receive an error is a bit awkward, adding something to explicitely _ignore_ the error would make more sense 21:23:38 q+ 21:23:48 Vikas2 has joined #ws-ra 21:23:51 ack gp 21:23:53 RESOLUTION: 8301 resolved with comment#1 21:24:14 q+ 21:24:43 Topic: 8193 21:24:48 ok with fixing "it" :-) 21:24:49 ack ram 21:25:34 Vikas2 has joined #ws-ra 21:25:40 q+ 21:26:06 ack du 21:27:56 q+ 21:28:01 ack ram 21:28:38 Vikas2 has joined #ws-ra 21:29:19 scribe: gpilz 21:29:38 ram: need more time to consider this proposal 21:29:41 ... discuss at F2F 21:29:54 topic: issue 7774 21:30:10 http://www.w3.org/Bugs/Public/show_bug.cgi?id=7774 21:30:23 yves: last time I said this could wait for the F2F 21:30:47 ... during the previous F2F we discussed that is was not addressing something 21:31:01 q+ 21:31:09 ack dug 21:31:18 ... if WS-T Delete == WS-Frag Delete why does WS-T Put != WS-Frag Put 21:31:29 doug: Put is really an update of the resource rep 21:31:39 ... in the base case you get a whole new rep 21:32:01 ... in WS-Frag, Put with mode is an instruction, not a complete rep 21:32:28 ... WS-Frag Put is what you want, it's just not called "Patch" 21:32:57 (Yves & Doug): back and forth about semantics of "replace", "instructions", etc. 21:33:52 q+ 21:34:02 ack dug 21:34:58 Vikas has joined #ws-ra 21:35:05 action: doug - add clarifying text as a potential resolution to 7774 21:35:06 Created ACTION-136 - - add clarifying text as a potential resolution to 7774 [on Doug Davis - due 2010-01-26]. 21:35:19 topic: issue 8196 21:37:04 q+ 21:37:47 ack tom 21:37:57 +1 to Gil!!! 21:40:24 tom: would like to clarify this issue 21:41:01 I agree with Bob's statement 21:45:46 I'd like to defer 8292 21:46:09 its a big proposal - haven't had time to fully review it yet - sorry 21:48:04 bob: would like to have all issues have proposals by F2F 21:49:48 on the spot sounds good 21:50:16 +1 21:51:41 q+ 21:51:52 I think 8185 isn't really related 21:51:56 ack gpi 21:59:08 Bob - that would be lovely! 22:00:00 -Tom_Rutt 22:00:01 -Ashok_Malhotra 22:00:02 -Gilbert 22:00:03 -Wu_Chou 22:00:03 -vikas 22:00:04 -[Microsoft] 22:00:04 -[IPcaller] 22:00:05 -Yves 22:00:07 -Bob_Freund 22:00:09 - +1.408.970.aaee 22:00:11 -??P22 22:00:13 - +03531803aadd 22:00:15 -JeffM 22:00:17 -Doug_Davis 22:00:19 WS_WSRA()3:30PM has ended 22:00:21 Attendees were Wu_Chou, Bob_Freund, +984999aaaa, Doug_Davis, sreed, +1.571.262.aabb, vikas, +1.408.642.aacc, Ashok_Malhotra, Gilbert, Yves, Tom_Rutt, [Microsoft], +03531803aadd, 22:00:24 ... +1.408.970.aaee, JeffM, [IPcaller] 22:00:34 rrsagent, generate minutes 22:00:34 I have made the request to generate http://www.w3.org/2010/01/19-ws-ra-minutes.html Bob 22:02:09 MartinC has left #ws-ra 23:09:23 asir has joined #ws-ra