19:22:09 RRSAgent has joined #ws-ra 19:22:09 logging to http://www.w3.org/2009/09/22-ws-ra-irc 19:22:11 RRSAgent, make logs public 19:22:11 Zakim has joined #ws-ra 19:22:13 Zakim, this will be WSRA 19:22:13 ok, trackbot; I see WS_WSRA()3:30PM scheduled to start in 8 minutes 19:22:14 Meeting: Web Services Resource Access Working Group Teleconference 19:22:14 Date: 22 September 2009 19:22:31 Agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/0072.html 19:24:53
  • li has joined #ws-ra 19:25:46 WS_WSRA()3:30PM has now started 19:25:53 +li 19:26:01 +[Microsoft] 19:26:49 Bob has joined #ws-ra 19:27:01 + +039331574aaaa 19:27:08 trackbot, start telecon 19:27:10 RRSAgent, make logs public 19:27:12 Zakim, this will be WSRA 19:27:12 ok, trackbot, I see WS_WSRA()3:30PM already started 19:27:13 Meeting: Web Services Resource Access Working Group Teleconference 19:27:13 Date: 22 September 2009 19:27:40 +Bob_Freund 19:29:02 dug has joined #ws-ra 19:29:10 +Doug_Davis 19:29:17 +gpilz 19:29:39 Hi there 19:30:17 Tom_Rutt has joined #ws-ra 19:30:33 chair: Bob Freund 19:30:45 +Tom_Rutt 19:31:09 +[Microsoft.a] 19:31:34 + +1.571.262.aabb 19:32:00 fmaciel has joined #ws-ra 19:32:02 Ram has joined #ws-ra 19:32:03 + +0208234aacc 19:32:12 Vikas has joined #ws-ra 19:32:37 + +1.408.970.aadd 19:32:44 zakim who is making noise? 19:32:57 Katy has joined #ws-ra 19:33:03 +Yves 19:33:15 zakim ses nobody making noise now that they have muted 19:33:55 zakim, who is making noise? 19:34:07 dug, listening for 11 seconds I heard sound from the following: Bob_Freund (59%), +1.571.262.aabb (46%) 19:34:26 tons of static Vikas 19:34:45 +??P11 19:34:47 Muted 19:36:01 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/0072.html 19:37:00 DaveS has joined #ws-ra 19:37:19 scribe: Li Li 19:37:29 scribenick: LI 19:37:50 yes, I'm here 19:38:17 Bob, I'm on the phone 19:38:27 Alessio, are you muted? 19:38:32 perhaps I'm muted, let me check 19:38:45 mary had a little lamb... 19:39:31 Alessio, there is an audio issue, we can't hear you 19:39:35 I tried 60# 19:39:40 but I think I'm still muted 19:39:48 039 is Italy, yes 19:39:49 sure 19:39:52 I can here you 19:40:24 zakim, umute asoldano 19:40:24 I don't understand 'umute asoldano', dug 19:40:29 asir has joined #ws-ra 19:40:33 zakim, unmute asoldano 19:40:33 sorry, dug, I do not know which phone connection belongs to asoldano 19:41:03 OK, let me try to redial 19:41:08 - +039331574aaaa 19:41:25 that's ok, most of us only communicate unidirectionally in any case 19:41:27
  • TOPIC: agenda 19:41:30 LOL 19:41:38
  • agenda agreed 19:41:40 + +039331574aaee 19:41:52
  • TOPIC: approval of minutes 19:42:18
  • bob: minutes approved 19:42:27
  • TOPIC: f2f next week 19:42:31 - +039331574aaee 19:42:47 http://www.w3.org/2002/09/wbs/43088/HursleyDinner/ 19:43:19
  • bob: complete it by tomorrow 19:43:41 q+ 19:43:56
  • bob: discuss next f2f in santa clara 19:44:06 ack ram 19:44:29 sorry, I've phone issues, joining again in few sec 19:44:46
  • ram: publishe fpwd by friday? 19:44:55
  • yves: will try 19:45:42
  • TOPIC: schedule 19:45:43 + +039331574aaff 19:46:44 q+ 19:46:49
  • TOPIC: AI reviews 19:46:57 ack dug 19:47:07
  • bob: anything can't be done by next f2f? 19:47:45 q+ 19:48:01 q+ 19:48:04 ack asir 19:48:38
  • asir: ask dug if it's possible to send out proposal this week 19:48:42
  • dug: i think so 19:49:16 + +0759029aagg 19:49:21 -??P11 19:49:32
  • asir: ai 94 is being worked on by me, we'll take over ai from geoff 19:49:36 ack katy 19:50:12
  • katy: 61 19:50:22
  • TOPIC: ws-frag 19:50:51 dug, mail sent (re AI on x-links) 19:50:57 thanks 19:51:18
  • ram: details not ready for f2f 19:51:48
  • ram: by the end of this week 19:52:07
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7698 19:53:07
  • issue opened 19:53:37
  • bob: any objection to the proposal in the issue? 19:54:07
  • ram: looks fine 19:54:13 fine to me 19:54:34
  • bob: no objection and resolved as proposed 19:54:56
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426 19:56:33
  • yves: iri is not used in xml namespace, as pointed out by asir 19:56:37 q+ 19:56:53 proposal is to use IRI for everything but namespaces 19:56:54
  • bob: use iri in everything except namespace? 19:57:03 ack dug 19:57:37
  • dug: ws-a bounced between IRI and URI 19:57:58
  • ...concrete strings are URI but generic ones are IRI 19:58:09
  • ...what is the pattern for us? 19:58:43
  • bob: use IRI for everything but namespace and literal strings 19:58:46 q+ 19:58:59 ack asir 19:59:24
  • asir: URI is also IRI, we can do a global replacement 19:59:33
  • dug: i'm still confused 19:59:57
  • dug: why the exception? 20:00:36 The working group intends to update the value of the Web Services Eventing namespace URI each... 20:00:51
  • bob: use IRI to permit localization 20:01:14
  • ...otherwise we stick to URI 20:02:03
  • dug: namespace URI -> URI, so it's not global change 20:02:48
  • asir: someone needs to make a line-by-line change 20:04:00
  • bob: we have to give either detail changes or instructions to editors 20:04:04 q+ 20:04:15
  • dug: i like line-by-line changes 20:04:16 I can do this on friday 20:04:20 ack gpil 20:05:16
  • bob: prefer line-by-line changes 20:05:41 ACTION: Yves to produce a line-by-line diff for issue 7426 20:05:41 Created ACTION-105 - Produce a line-by-line diff for issue 7426 [on Yves Lafon - due 2009-09-29]. 20:05:51
  • thanks 20:06:29
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7478 20:06:39 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/0027.html 20:06:52 zakim, who is making noise? 20:07:08 ah, sorry, didn't know it was you gil :-) 20:07:12 dug, listening for 17 seconds I heard sound from the following: Bob_Freund (2%), gpilz (97%) 20:07:20
  • gil: explain the proposal 20:09:34
  • ...it is about negotiating durations 20:09:41 q+ 20:09:50
  • ...it's simple and efficient 20:10:06 ack dave 20:10:37
  • daves: subcription is cut down to yes/no 20:11:02
  • ...more intelligent source can put hint in the response 20:11:27
  • ...how to make response clear 20:11:31 q+ 20:11:42 ack ram 20:12:18
  • ram: proposal is technical correct, but compatibility is an issue 20:12:48 q+ 20:13:03
  • ...developers should code against failures 20:13:59
  • ...subscriber should be able to negotiate in different situations 20:14:59 q+ 20:15:00 q+ 20:15:32
  • ...we need to provide right guidance to developers 20:15:50 ack gpi 20:15:55
  • ...this proposal doesn't help with practical issues 20:16:11 [Gil's voice is not clear on the phone 20:16:20 Gil: Your voice quality is not audible. 20:17:18 the same here unfortunately 20:17:28
  • gil: in system integration, event sink needs to count on event source 20:18:11 q- 20:18:26 ack dave 20:18:29
  • ...[not audible] 20:19:09
  • daves: incompatibilty 1: failure to provde feedback 20:19:21 q+ 20:19:47
  • incompatibilty 2: provide feedback in failure 20:20:14
  • ...3: complicated protocol and policy 20:20:37
  • ...gil's is in the middle ground 20:20:55 q+ 20:21:07
  • ...optional framework for policy later on? 20:21:15 ack ram 20:21:28 q+ 20:21:40
  • ram: need to deal with device comp. issue 20:22:31
  • ...feedback from users on back comp. issues 20:23:32
  • ram: is not back comp. issue, rather to avoid mistakes by developers 20:23:43
  • bob: specific changes? 20:24:18
  • ram: i sent some response today, event source should decide duration, 20:24:21 q+ 20:24:59 ack dug 20:25:01
  • ...i can live with subscriber having an option to indicate hint 20:25:16 q+ 20:25:34
  • dug: there are cases subscriber can indicate a hint or not a hint 20:26:10
  • ...can we have both, instead of just one? 20:26:44 bob I'd like to respond to what he just said 20:26:51 go ahead 20:26:57
  • ram: you are optimizing protocol to avoid unsubscribe 20:27:05 q- 20:27:17 ack ram 20:27:20
  • ...what is broken? 20:27:33
  • gil: yield to dug 20:28:19
  • dug: lightweight situation can create/delete subscription at will, 20:28:32
  • but other situation this is expensive 20:29:01
  • ...so we need to indicate "i really want" 20:29:01 ack gp 20:29:27
  • gil: device and enterprise people are talking across.. 20:29:40 q+ 20:30:12
  • ...we need to support both cases 20:30:14 ack dave 20:30:23 q+ 20:31:43
  • daves: gil's proposal covers ram's concern by not puting duration in request 20:31:59 ack ram 20:32:11 A Subscriber MAY indicate that it is willing to accept a Subscription with any expiration time by omitting this element from the Subscribe request. 20:32:20
  • ram: we're making leap of faith... 20:32:42 (the above is a part of the description of the optional /wse:Expirese element) 20:32:47 q+ 20:33:08 Ohh!? 20:33:31 Ooops I sat on the keyboard. 20:33:34 LOL 20:33:39
  • ...flexiblity is needed to interop 20:33:52
  • ...let's talk more usecases in the f2f 20:34:12 q+ 20:34:22
  • ...i'd like to know what is your use cases... 20:34:57
  • ..we shouldn't loose interop between device and enterprise worlds 20:35:22
  • ...what's wrong with current spec? 20:35:44 ack gpi 20:35:53 Asir, I hear hin well 20:36:28 there's also no guarantee that Renew will be accepted later on 20:36:29
  • gil: hint doesn't provide value to sink, if the time is cut off 20:36:33 we have difficulty hearing there is a lot of background noise 20:37:03 Dave agrees with Gil. A hint is the same as providing no duration at all. 20:37:29 ack gpi 20:37:29
  • ...[in audible mostly] 20:37:39 ack dug 20:38:08
  • dug: 2 issue with current spec: 1 cost of unsubscribe, 2 no guarantee on renew 20:38:40 q+ 20:38:46 katy what number do you use to dial into W3C? 20:38:56
  • ...why isn't your requirement not supported by proposal 20:39:11
  • ram: i have the same question to dug 20:39:28 q+ 20:40:17
  • ...current spec is not burdening event source. 20:40:30 Gil - number is +441173706152 20:40:40
  • ...current spec works in many different environments 20:40:46 ack dug 20:40:48 ack ram 20:41:02
  • dug: which use cases are not supported? 20:41:19
  • ram: i'm lost at what you try to solve 20:41:48
  • dug: what use case not supported 20:42:20
  • ram: not about technical content of proposal 20:42:38
  • ...but on what's goal of the proposal 20:42:54
  • bob: how would you modify it? 20:43:23
  • ram: i'll take another stab at it 20:43:43
  • bob: it's about deployment, correct? 20:43:47 q+ 20:43:59
  • bob: which line should be modified? 20:44:40
  • ram: though technically sound, but it doesn't help me 20:44:59
  • bob: what part cause you problem? 20:45:46
  • ram: client having two options is a problem 20:46:44 q+ 20:46:51
  • ram: having two parties making decision is difficult to code 20:47:12 ack dave 20:47:16
  • ram: i'm having problem with duality 20:47:53 + +01831332aahh 20:48:11 q+ 20:48:12
  • daves: proposal puts both subscriber and source in the driver seats 20:48:23 bob - ram can go first to answer dave 20:48:34 it might make my question moot 20:48:41 ack ram 20:49:43
  • ram: giving dualities is a problem for developers 20:50:30 q+ 20:51:12
  • ram: cause developers to misuse API instead of coding with interactions 20:51:42
  • dug: all elements in subscribe are optional 20:52:09
  • ...why this one expiry is different from the others? 20:52:26
  • ...while all others can fault when not satisfied 20:52:36 ack dug 20:53:00
  • ram: but there is negotiation between subscriber and source 20:53:23 Ram has joined #ws-ra 20:53:40
  • bob: why is it different from unsupported filter 20:53:45 q+ 20:53:56
  • ram: others are black and white, this one is not 20:54:39
  • dug: please explain why they are different 20:55:23
  • ram: something negotiable whereas other are not 20:55:36 q+ 20:55:50 q- 20:56:06 ack gp 20:56:12
  • ...current spec is flexible and interop 20:56:15 - +039331574aaff 20:56:44
  • gil: where can we go, if nothing can be modified? 20:57:24
  • bob: strong objection? 20:57:29 -gpilz 20:57:32
  • ram: need more time 20:57:46
  • bob: it's long enough 20:58:12
  • asir: we should not close it now 20:58:54
  • bob: i asked many different ways 20:59:08
  • asir: we need to work with oracle 20:59:24
  • bob: what's wrong? 20:59:40
  • bob: we're not progressing 20:59:46 I really would like specfics before allowing more time. 20:59:59 I agree with Bob - I'm still confused as to what's wrong with the proposal 21:00:01
  • ram: let's spend time in f2f 21:00:19 What is broken and I am happy to see more time. 21:00:45
  • bob: let's focuses on specifics 21:00:57
  • s/focuses/focus/ 21:01:21
  • bob: objection or acceptance 21:01:31
  • ram: will work on it 21:02:04
  • bob: action to ram to work on the proposals 21:02:42
  • ACTION: ram to work on proposal for the issue 21:02:42 Created ACTION-106 - Work on proposal for the issue [on Ram Jeyaraman - due 2009-09-29]. 21:03:04 - +0759029aagg 21:03:14 - +1.408.970.aadd 21:03:15 -[Microsoft] 21:03:15 - +1.571.262.aabb 21:03:16 -Yves 21:03:16 -[Microsoft.a] 21:03:16 -Bob_Freund 21:03:17 -Doug_Davis 21:03:20 -li 21:03:25 -Tom_Rutt 21:03:30 I have made the request to generate http://www.w3.org/2009/09/22-ws-ra-minutes.html Yves 21:07:32 gpilz has left #ws-ra 21:07:41 - +01831332aahh 21:08:07 - +0208234aacc 21:08:09 WS_WSRA()3:30PM has ended 21:08:10 Attendees were li, [Microsoft], +039331574aaaa, Bob_Freund, Doug_Davis, gpilz, Tom_Rutt, +1.571.262.aabb, +0208234aacc, +1.408.970.aadd, Yves, +039331574aaee, +039331574aaff, 21:08:13 ... +0759029aagg, +01831332aahh 21:37:54 dug has joined #ws-ra 21:37:58 yves? 23:26:12 Zakim has left #ws-ra