19:19:15 RRSAgent has joined #ws-ra 19:19:15 logging to http://www.w3.org/2009/08/25-ws-ra-irc 19:19:17 RRSAgent, make logs public 19:19:17 Zakim has joined #ws-ra 19:19:19 Zakim, this will be WSRA 19:19:19 ok, trackbot; I see WS_WSRA()3:30PM scheduled to start in 11 minutes 19:19:20 Meeting: Web Services Resource Access Working Group Teleconference 19:19:20 Date: 25 August 2009 19:19:53 PaulN has joined #ws-ra 19:23:44 Bob has joined #ws-ra 19:23:59 trackbot, start telecon 19:24:01 RRSAgent, make logs public 19:24:03 Zakim, this will be WSRA 19:24:03 ok, trackbot; I see WS_WSRA()3:30PM scheduled to start in 6 minutes 19:24:04 Meeting: Web Services Resource Access Working Group Teleconference 19:24:04 Date: 25 August 2009 19:27:12 WS_WSRA()3:30PM has now started 19:27:19 +Bob_Freund 19:27:37 chair: Bob Freund 19:27:42 + +1.919.849.aaaa 19:28:03 + +1.207.827.aabb 19:28:04 zakim, aaaa is Sreed 19:28:05 +Sreed; got it 19:28:07 dug has joined #ws-ra 19:28:27 zakim, aabb is paulN 19:28:27 +paulN; got it 19:28:55 +Doug_Davis 19:29:27 Ram has joined #ws-ra 19:29:35
  • li has joined #ws-ra 19:30:16 +li 19:30:35 +??P11 19:31:20 Ashok has joined #ws-ra 19:31:35 fmaciel has joined #ws-ra 19:31:53 +Ashok_Malhotra 19:32:11 +[Microsoft] 19:32:12 +Vikas 19:32:25 +fmaciel 19:32:50 Vikas has joined #ws-ra 19:33:42 asir has joined #ws-ra 19:33:58 DaveS has joined #ws-ra 19:34:11 +Yves 19:34:11 +Tom_Rutt 19:34:25 hey bob 19:35:24 Tom_Rutt has joined #ws-ra 19:35:29 +gpilz 19:35:42 -li 19:35:43 fmaciel has joined #ws-ra 19:35:50 scribe: Li Li 19:35:57 scribenick: Li 19:35:57 +Mark_Little 19:36:03 gpilz has joined #ws-ra 19:36:09 +li 19:36:23 Sreed has joined #ws-ra 19:36:49
  • TOPIC: agenda 19:37:39 minutes link http://www.w3.org/2002/ws/ra/9/08/2009-08-18.html 19:37:54
  • TOPIC: approval of minutes 19:38:11
  • minutes accepted 19:38:45 Thank you Yves 19:39:55
  • TOPIC: snapshot of mex and rt 19:40:17
  • ram has some comments 19:40:58
  • dug and ram figure out which comments 19:41:22 http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0055.html 19:43:45
  • snapshots of mex and rt accepted 19:44:38
  • TOPIC: review action items 19:45:13 q+ 19:45:36
  • TOPIC: progress on ws-frag 19:45:40 q- 19:46:09
  • ram: needs a few more days to polish 19:47:10
  • bob: fpwd needs to be out by sept (next week) in order to hold out schedule 19:47:22
  • ram: that's acceptable 19:47:47
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365 19:49:16
  • bob: objection to proposal? 19:49:35
  • 7365 resolved as proposed 19:50:00
  • http://www.w3.org/Bugs/Public/show_bug.cgi?id=7235 19:50:11 http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0070.html 19:52:09
  • dug: explain issue and proposal 19:52:18 ** New dialect 19:52:20 definitions MUST include sufficient information for proper application. 19:52:21 For example, it would need to include the context (which data) over which 19:52:23 the filter operates. *** 19:53:34 -??P11 19:53:54 q+ to ask a question 19:54:14 +??P11 19:54:15
  • bob: append proposed text to spec? 19:54:19 ack asir 19:54:19 asir, you wanted to ask a question 19:54:52
  • asir: when does context change? 19:55:28
  • dug: context of xpath changes from envelope to event data 19:55:29 q+ to follow up 19:55:50
  • context may change for other uri too, like actionURI 19:55:51 ack asir 19:55:51 asir, you wanted to follow up 19:56:10 q+ 19:56:24
  • asir: i don't recall discussing change of context being discussed 19:56:37 ack gp 19:56:52 "... a new dialect might be defined to support filtering based on data not included in the notification message itself." 19:56:54 q+ 19:57:20
  • gil: generic use of xpath is insufficient as it doesn't tell the context 19:57:42
  • therefore, ws-e needs a new uri to convey the context 19:58:20
  • asir: it's new to me that uri indicates context 19:58:24 ack dug 19:58:59 q+ 19:59:27 q+ 19:59:30 ack tom 19:59:45
  • dug: filter always needs context 19:59:59
  • tom: do we need context to complicate thing? 20:00:17 ack asir 20:00:19 -Mark_Little 20:00:22
  • dug: yes, we have filter on action, topic, etc. beside just event data itself 20:00:28 q+ 20:00:51 ack dug 20:01:12
  • asir: uri needs to point to stable xpath 20:01:43
  • dug: maybe to separate flexibility to another issue 20:02:15 q+ 20:02:16
  • bob: we can define a uri for backward compability 20:02:25 ack asir 20:02:31 q+ 20:02:53 ack gp 20:03:13
  • asir: it's ok if this is a simple case 20:03:15 asir: if we were to define our own namespace name then this would be a unique case and not set any precedence 20:03:44
  • gil: we have to do it as gil explained the use cases 20:03:58
  • s/gil/dug/ 20:05:21
  • asir: it's not clear what is replaced 20:05:34 q+ 20:06:09
  • dug: two parts: one is to swap out uri; the other is the text 20:07:27 next text is in: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0070.html 20:07:37 s/next/new/ 20:08:36
  • figuring out the consolidated proposal... 20:09:35
  • asir: make uri to xpath 1.0? 20:09:55
  • daves: a different uri for xpath 2.0 then? 20:09:55 Here is the draft proposal 20:09:56 1. Append to Section '[Body]/wse:Subscribe/wse:Filter/@Dialect 20:09:56 ' 20:09:56 *** New dialect definitions MUST include sufficient information for proper application. For example, it would need to include the context (which data) over which the filter operates. *** 20:09:56 2. Replace http://www.w3.org/TR/1999/REC-xpath-19991116 with http://www.w3.org/2009/02/ws-evt/Dialects/XPath10 20:10:13 3. and similar for enum 20:10:29 Ram has joined #ws-ra 20:11:06
  • bob: any object to the above proposal to 7235? 20:11:21
  • bob: resolved with no objection 20:11:33
  • http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270 20:12:04 Unless otherwise noted, all URIs are absolute URIs and URI comparison MUST be performed according to [RFC 3986] section 6.2.1. 20:12:39 Ram has joined #ws-ra 20:13:20 test 20:13:44 q+ 20:13:48 q- 20:14:03 q- 20:14:10
  • yves: it's better to stay within uri instead of iri 20:14:30
  • object to the proposal? 20:14:31 q+ 20:14:38 ack ram 20:14:59 q+ 20:15:18
  • ram: any exception to the general rule? 20:15:28 q- 20:15:51
  • dug: i couldn't find any... 20:16:10 q+ 20:16:13
  • 7270 resolved as proposed 20:16:29
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7160 20:17:19 need format text :-) 20:17:22 s/format/formal/ 20:17:26
  • 7160 accepted 20:17:55
  • bob: 7426 accepted as new issue 20:18:16 q+ 20:18:19
  • bob: ban the use of iri where uri comparison is used 20:18:23 ack ram 20:18:44 can we see some text? 20:19:44
  • AI for yves to propose text for 7426 20:20:01 Action: Yves to propose text for issue 7426 20:20:01 Created ACTION-97 - Propose text for issue 7426 [on Yves Lafon - due 2009-09-01]. 20:20:36
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7196 20:20:55 Didn't you resolve it last week? 20:20:59 q+ 20:21:14 doubly resolved! 20:21:41 ack dug 20:22:02
  • bob: 7196 resolved 20:22:36 http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533 20:22:52
  • yves: explain the issue 20:22:58 q+ 20:23:57 ack dug 20:24:12
  • dug: why do we need this? 20:25:01
  • yves: we need to specify the property of that operation 20:25:20
  • dug: do we need to do the same for "getstatus"? 20:25:47 q+ 20:25:54
  • yves: we should spell out for all safe operations 20:26:02 ack asir 20:26:03 +1 20:26:07
  • dug: then we need to apply it to all specs 20:26:58
  • asir: why not idempotent? 20:27:13 Here is a link to Feb discussion ... http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0045.html 20:27:36 q+ 20:27:44 ack gp 20:27:46
  • yves: we could do that if people like it 20:28:09
  • gil: this is a constraint on implementations 20:28:43
  • ..we should do it for other specs as well 20:28:49 +1 obviously 20:29:14
  • gil: find all safe operations first 20:29:58
  • ACTION: yves to include all safe operations in all specs 20:29:58 Created ACTION-98 - Include all safe operations in all specs [on Yves Lafon - due 2009-09-01]. 20:30:15 http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/att-0057/wseventing_6401-6.html 20:30:41
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=6401 20:30:52 -Sreed 20:31:21
  • gil: explain the new proposal 6401 20:31:58 q+ 20:32:29 http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/att-0061/ws-eventing-6401-6-dug2.doc 20:32:51
  • looks ok to me 20:33:45 interesting - I'm missing the section header for appendix A when I look at the html version too - but the word doc is ok 20:38:21
  • dug: some editorial changes, remove duplicates about mex 20:38:24 Dug presents an amended proposal 20:38:33 I would like to understand this sentence in Dug's revision: "An Event Source there MUST NOT exist more than one EventDescription document." 20:38:55 q+ 20:38:58 q- 20:39:05 ack ram 20:39:25 q+ 20:39:37
  • ram: why that constraint? 20:40:04 ack gp 20:40:19
  • dug: it's in the original proposal 20:40:34 q+ 20:41:36
  • gil: more than ED document complicates relations to NW 20:41:52 ack asir 20:42:06 q+ 20:42:32
  • asir: i don't fully understand the requirement 20:42:48
  • ...to relate ED and NW 20:43:06 ack dug 20:44:26 q+ 20:44:45
  • dug: one ED doc should be returned, more than one adds complexity 20:45:20
  • ... one ED doc hides complexity 20:45:20 ack asir 20:45:36 q+ to ask a clarifying question 20:45:53
  • asir: multiple docs is supported by mex in multi sections 20:46:07 q+ 20:46:16 ack dug 20:46:16 dug, you wanted to ask a clarifying question 20:46:44
  • dug: what subscriber do with multii docs? 20:46:58
  • s/multii/multi/ 20:47:48
  • asir: client handles multi-docs according to the standards 20:47:48 ack gp 20:48:41
  • gil: we are profiling mex 20:48:59 +Doug_Davis.a 20:49:14
  • ...we make it clear how different parts are related 20:49:15 Gil - i was only trying to help you! Nothing more. 20:49:44 +Doug_Davis.aa 20:49:48 +JeffM 20:49:51 -Doug_Davis.a 20:50:11 dug has joined #ws-ra 20:50:27 sorry - power went out 20:50:28
  • ...if two ED docs and two NW docs are returned, then which goes which is not clear 20:51:08 q+ 20:51:14 q- 20:52:16 Vow .. are we closing 6401? 20:52:18
  • +q 20:52:22 never! :-) 20:52:43 ack li 20:53:54 I can send in a new rev with the typo that Ram noticed fixed 20:53:54 q+ 20:54:02 if people want 20:54:20 ack ram 20:54:43
  • li: would like to read it 20:55:18
  • ram: we would like to postpone it until next week 20:56:09 q+ 20:56:26
  • bob: review dug's proposal next week as basis of 6401 20:56:59 Goodnight 20:57:03 -Ashok_Malhotra 20:57:06 good job li! 20:57:07
  • bob: declare victory for today... 20:57:10 -fmaciel 20:57:11 -[Microsoft] 20:57:12 -Yves 20:57:13 -Vikas 20:57:15 -Bob_Freund 20:57:16 -Doug_Davis.aa 20:57:17 -Tom_Rutt 20:57:19 -??P11 20:57:20 I have made the request to generate http://www.w3.org/2009/08/25-ws-ra-minutes.html Yves 20:57:21 -li 20:57:27 gpilz has left #ws-ra 20:58:10 -paulN 20:58:18 -JeffM 20:58:48 -Doug_Davis 21:05:01 disconnecting the lone participant, gpilz, in WS_WSRA()3:30PM 21:05:02 WS_WSRA()3:30PM has ended 21:05:04 Attendees were Bob_Freund, +1.919.849.aaaa, +1.207.827.aabb, Sreed, paulN, Doug_Davis, li, Ashok_Malhotra, [Microsoft], Vikas, fmaciel, Yves, Tom_Rutt, gpilz, Mark_Little, JeffM