21:01:59 RRSAgent has joined #ws-addr 21:01:59 logging to http://www.w3.org/2005/12/05-ws-addr-irc 21:02:05 zakim, who is on the phone? 21:02:05 sorry, TonyR, I don't know what conference this is 21:02:06 On IRC I see RRSAgent, Zakim, mnot, Katy, bob, vikas, prasad, uyalcina, Tony, Nilo, David_Illsley, TonyR, Jonathan_Marsh, pauld, hugo 21:02:07 zakim, this is ws_addr 21:02:07 ok, mnot; that matches WS_AddrWG()4:00PM 21:02:17 Meeting: Web Services Addressing Working Group Teleconference 21:02:20 +??P14 21:02:22 Chair: Mark Nottingham 21:02:25 dhull has joined #ws-addr 21:02:30 zakim, who is on the phone? 21:02:30 On the phone I see ??P0, David_Illsley, gpilz, Steve_Vinoski, Bob_Freund, Mark_Little, Nilo_Mitra, +1.408.748.aaaa, +1.781.444.aabb, Umit_Yalcinalp, [Microsoft], Dave_Hull, ??P14 21:02:34 ... (muted) 21:02:37 Agenda: http://www.w3.org/mid/0E8FBB36-5818-4A11-9607-3373FB7E8B82@bea.com 21:02:42 zakim, I am ??p0 21:02:42 +TonyR; got it 21:02:48 +Prasad_Yendluri 21:03:03 That 748.aaaa is Vikas 21:03:04 +Mark_Peel/Katy_Warr 21:03:07 gpilz has joined #ws-addr 21:03:11 +MarkN 21:03:26 zakim, aaaa is Vikas 21:03:26 +Vikas; got it 21:03:32 zakim, +1.781.444.aabb is me 21:03:32 +Tony; got it 21:03:33 +pauld 21:03:51 +Marc_Hadley 21:03:58 Zakim, call hugo-617 21:03:58 ok, hugo; the call is being made 21:04:00 +Anish 21:04:12 Zakim, call hugo-617 21:04:13 ok, hugo; the call is being made 21:04:14 +Hugo 21:04:19 marc has joined #ws-addr 21:04:27 -Anish 21:04:30 +??P18 21:04:33 swinkler has joined #ws-addr 21:04:40 +Steve_Winkler 21:04:45 anish has joined #ws-addr 21:05:02 Paco has joined #ws-addr 21:05:11 +Anish 21:05:14 zakim, who is on the phone? 21:05:14 On the phone I see TonyR, David_Illsley, gpilz, Steve_Vinoski, Bob_Freund, Mark_Little, Nilo_Mitra, Vikas, Tony, Umit_Yalcinalp, [Microsoft], Dave_Hull, ??P14 (muted), 21:05:17 ... Prasad_Yendluri, Mark_Peel/Katy_Warr, MarkN, pauld, Marc_Hadley, Hugo, ??P18, Steve_Winkler, Anish 21:05:24 + +1.408.219.aacc 21:05:41 +[IBM] 21:05:52 +Jonathan_Marsh 21:06:21 zakim, IBM contains Paco 21:06:21 +Paco; got it 21:06:39 ./mr oops http://www.ctrl-c.liu.se/ftp/images/aviation/military/warbirds/p40-warhawk-1.gif 21:06:50 vinoski has joined #ws-addr 21:07:06 scribe: marc 21:07:13 +Pete_Wenzel 21:07:53 2. Agenda review, AOB 21:07:55 dorchard has joined #ws-addr 21:07:59 no ob 21:08:11 3. Call for corrections to the minutes 21:08:46 2005-11-21: approved 21:09:05 2005-11-28: corrections pending 21:09:16 4. Review action items 21:09:23 Umit - done 21:09:33 Jonathan - open 21:09:50 5. Co-ordination 21:09:59 * TAG request for help 21:09:59 21:11:26 q+ 21:12:17 Mark reviews note from TAG 21:13:50 ack dhull 21:14:14 Mark: does WG feel the need for formal response ? 21:14:28 q+ 21:15:10 +[Fujitsu] 21:15:13 wonders what we can do, or care about how other people use our specs 21:15:16 - +1.408.219.aacc 21:16:39 + +1.407.503.aadd 21:17:23 TonyC has joined #ws-addr 21:17:31 dhull: wonders if we need something to explain migration from submission 21:17:34 ack bob 21:17:41 zakim, aadd is Glen 21:17:41 +Glen; got it 21:18:04 Yeah. Tony just got dropped and reconnected as TonyC 21:18:21 WG is OK with informal response to TAG 21:18:31 other 5. Proposed and New Issues 21:18:49 zakim, +1.781.444.aabb is me 21:18:49 sorry, TonyC, I do not recognize a party named '+1.781.444.aabb' 21:19:12 zakim, +1.781.444.0202 is me 21:19:13 sorry, TonyC, I do not recognize a party named '+1.781.444.0202' 21:20:03 Jonathan reviews the issue 21:21:14 q+ 21:21:15 q+ 21:21:54 GlenD has joined #ws-addr 21:21:57 q? 21:22:45 Nothing prevents anyone from using as a policy assertion element under , does it? 21:22:51 Exactly 21:23:00 this is what I wrote on my email 21:23:14 +1 on extensibility 21:23:52 Mark: such a policy assertion would need to be compatible with WS-Policy ? 21:23:58 Jonathan: yes 21:24:21 +1 21:24:25 -MarkN 21:24:35 -Glen 21:24:39 dammit! 21:24:39 Mark: havediscussed with several people, feedback indicates that charter changes might be required 21:24:42 that wasn't the mute button 21:24:44 mark, we lost you 21:24:48 brb 21:25:23 ring ring 21:25:29 +Glen 21:25:33 ha beat him back! 21:25:39 +MarkN 21:27:06 q+ 21:27:32 Jonathan: charter requires us to define a mechanism for indicating use - policy is one way of doing that. can be done without normative reference to WS-Policy. 21:27:38 q+ 21:27:44 q? 21:27:56 scribe: mnot 21:28:34 march: know of people developing policy constraints; would like to use that instead of a specific policy language. 21:29:19 ... Would like to speak against domain-specific policy langauge; want to use something domain-independant one (which is usable with WS-Policy). 21:29:31 ... Urge WG to look at WS-PolicyConstraints. 21:29:36 scribe: marc 21:29:39 q? 21:29:42 ack marc 21:30:25 ack uyal 21:31:06 +1 21:31:16 +1 21:31:24 AIUI Anne's OASIS dipal working group is based upon XACML: http://research.sun.com/projects/xacml/ 21:31:30 +Tom_Rutt 21:31:49 and it is looking very interesting 21:32:41 ack Paco 21:33:16 umit: can use existing extension elements in WS-Policy, good enough, lets move on 21:33:50 +1 21:34:02 ack hugo 21:34:10 Paco: in favor of defining policy assertions 21:34:37 ack anish 21:34:45 Paco: existing elements can be r-used in policy language when that gets standardized 21:35:12 anish: can't see any need to say anything about policy right now 21:37:03 q+ 21:37:07 ack bob 21:38:36 q+ 21:38:42 ack Paco 21:38:46 Bo has joined #ws-addr 21:38:54 q+ 21:39:00 q+ 21:40:15 ack Jonath 21:42:17 jonathan: need a policy assertion, I can either talk to paco and IBM and MS can define it or we can do it in the WG. Former is not that unattractive as bilaterally we can define waht we want and twiddle it whenever we want. Doing it in the WG is a low cost way to get this on a standards track. 21:42:22 ack uyal 21:42:29 -MarkN 21:43:34 umit: don't want to see another policy assertion document elsewhere, lets do this in the WG 21:43:44 +MarkN 21:44:57 umit: just need an indication that the elements we define can be used in policy and leave it at that 21:45:20 ack hugo 21:45:20 hugo, you wanted to answer the question: should we open the issue? 21:45:38 q+ 21:45:40 hugo: don't think we need to open an issue for this 21:46:01 q+ quick question 21:46:09 hugo: from charter pov, we have defined WSDL extensions 21:46:19 q- quick question 21:46:26 q+ to ask a quick question 21:46:27 ack anish 21:46:59 anish: thinks jonathans suggestion re MS and IBM defining this is the best way to go 21:47:02 ack dhull 21:47:02 dhull, you wanted to ask a quick question 21:47:04 why are we abstracting concrete QNames, Anish? 21:47:33 dhull: nothing prevents our elements being re-used - right ? 21:48:01 jonathan: nothing structural, but thinks such use would be viewed as abuse 21:49:08 umit: (to hugo) thinks if we don't open this issue then we are asking for it to happen elsewhere 21:50:55 glen: doesn't think use of our elements elsewhere would be viewed as abuse 21:52:47 mark: if we open this to use with policy then we would need to track usage quite closely 21:53:15 +1 to marc 21:54:10 +1 to Marc 21:54:28 +1 to Marc too 21:54:52 marc: either do the job and define use in each framework or don't do it, making some vague statement will do nobody any favours 21:55:05 mark: what is your preference ? 21:55:12 +1 21:55:30 note that you are now requiring a very high bar... 21:55:40 marc: would like a standardized policy framework to do the work against, in absence of such don't see what we can do 21:55:43 q+ 21:56:22 tony: policy not in a state where we can reliably define something for use in it 21:56:50 pauld: would like to see some concrete proposals 21:57:09 -Mark_Little 21:59:47 Mark: could accept this as an issue and explore solutions that are not specific to any policy framework 22:00:11 -MarkN 22:00:43 hugo: there was quite a bit of opposition, can we poll to see level of interest 22:01:07 gpilz has joined #ws-addr 22:01:44 +MarkN 22:02:52 mark: if we open the issue then ill be tightly scoped to a couple of generic sentences saying elements can be used elsewhere 22:03:30 jonathan: that's acceptable 22:03:41 paco seconds the issue 22:04:03 ACTION: Jonathan to make concrete, non-referencing proposal for new issue WRT policy. 22:04:05 -Tom_Rutt 22:05:02 TOPIC: 6. Working Draft Issues 22:05:17 * i059 - Support for asynchronous / multi-MEP usage of web services 22:05:35 +DOrchard 22:05:47 umit presents her proposal 22:06:13 -MarkN 22:07:00 +Mark_Nottingham 22:08:05 mark: lots of discussion on email 22:08:33 umit: lets agree to incorporate the proposal and then work on the comments as separate issues 22:08:56 q+ 22:09:06 jonathan: q re prohibited value, is that really a common requirement ? 22:09:19 umit: voted at F2F 22:09:39 ack dhull 22:09:42 ack, pauld 22:09:50 q- 22:10:04 dhull: seems that WS-AT requires this 22:10:29 q+ 22:10:36 q+ 22:11:27 q+ 22:11:54 jonathan: any other cases ? 22:12:44 umit: application level requirements 22:13:02 ack uyal 22:13:49 anish: nice indication at binding that responses will not come back on back channel, good to know beforehand rather than find out at runtime 22:14:29 +1 to app level requirements 22:14:49 ack anish 22:15:31 what I am saying is that application level requirements may require async bindings. In this case, this marker will be useful even it is at the binding level 22:16:39 ack gpilz 22:16:47 of course, you can build async applications on top of sync protocols too, but if we had a long running request response at the app level, it will REQUIRE an async binding. 22:17:35 q+ 22:18:32 q+ to add a bit to gil's point about ws-rx. 22:19:25 -Mark_Peel/Katy_Warr 22:19:27 ack dhull 22:19:49 gil: thinks there are cases where this is important and that it would be odd if that was not possible in WSDL 22:20:42 q+ 22:20:50 q+ to ask a q to Anish 22:20:54 ack dorch 22:20:54 dorchard, you wanted to add a bit to gil's point about ws-rx. 22:21:20 TonyC has joined #ws-addr 22:22:02 +Mark_Peel/Katy_Warr 22:23:23 dorchard cites WS-RX case where WS-Addr capability can be used to indicate support for anon/non-anon RX replies 22:24:20 q? 22:25:58 ack Paco 22:26:37 paco: doesn't understand RX use case well enough but looks like partitioning of functionality isn't the most appropriate way to do it 22:26:58 -Glen 22:27:56 q? 22:28:00 ack uyal 22:28:00 uyalcina, you wanted to ask a q to Anish 22:28:18 umit: same use case as anish, long running request response 22:29:32 umit: the markup enables applications, think we should keep it 22:30:30 q? 22:30:33 anish: WSDL 1.1 abstract isn't that abstract so use of this markup isn't that counter 22:31:01 umit: make a high level decision on whether to incorporate this or not 22:31:04 q+ 22:31:22 ack marc 22:32:47 marc: don't want to incorporate a lot of text that is open to change, don't think the proposal is ready yet 22:33:45 http://www.w3.org/mid/239DAF7F-6BAE-47D6-A2FC-5B06F55575E5@Sun.COM 22:35:33 working through point raised in above referenced email 22:35:48 (i) agree this is an issue 22:36:05 (ii) similar to wsaw:Action seems appropriate 22:36:57 + to MarcH 22:37:05 +1 to MarcH 22:37:16 +1 to not cramming everything into the WSDL binding document 22:37:31 (iii) agreed 22:41:43 Jonathan_Marsh has joined #ws-addr 22:43:07 (iv) and (v) generated a lot of discussion wrt to whether new bindings are being defined or required 22:43:54 q+ 22:45:42 q- 22:51:39 http://www.w3.org/mid/54E8F43C-242F-48FF-A099-C7AC17980AD6@Sun.COM 22:52:05 jonathan: in wsdl 2.0 we always include an explicit way of saying the same thing as the default 22:52:14 marc: ok with leaving it in 22:52:26 http://www.w3.org/mid/43949EE5.6020106@oracle.com 22:53:59 umit: didn't think too deeply on this one, wanted to keep BP semantic but also thought there were cases where a reply envelope would be required 22:54:30 jonathan: related to the RM question of sending ack back ? 22:55:03 -TonyR 22:55:19 umit: yes 22:55:39 +??P0 22:55:47 zakim, ??p0 is me 22:55:48 +TonyR; got it 22:56:20 this "open door" is just "request with optional response" by another name 22:56:26 not that that is a bad thing 22:57:06 not convinced 22:57:10 (either way) 22:57:11 anish: so 202 SHOULD NOT include a SOAP envelope and we can revisit 22:57:19 umit: yes 22:57:40 WS-RX has problems if there is no SOAP envelope 22:57:54 How about SHOULD follow BP, as opposed to SHOULD NOT not follow it? 23:03:24 Hard to imagine w3c spec normatively referring to ws-i spec. Pretty much flies in the face of "we just do profiles"... 23:04:03 where is the WS-I 'one-way' binding, is there a URI? 23:04:20 -TonyC 23:04:28 TonyC has left #ws-addr 23:04:42 look for 202 in BP 23:04:46 -Steve_Winkler 23:05:10 -DOrchard 23:05:31 -Anish 23:05:33 -Steve_Vinoski 23:05:34 -[IBM] 23:05:34 -Umit_Yalcinalp 23:05:35 -Hugo 23:05:36 -Mark_Peel/Katy_Warr 23:05:37 vinoski has left #ws-addr 23:05:37 -Vikas 23:05:39 -pauld 23:05:40 -Marc_Hadley 23:05:41 -Jonathan_Marsh 23:05:42 -David_Illsley 23:05:44 -Mark_Nottingham 23:05:46 -Dave_Hull 23:05:48 -Prasad_Yendluri 23:05:50 -TonyR 23:05:54 TonyR has left #ws-addr 23:06:01 I'm logging. I don't understand 'generate log', anish. Try /msg RRSAgent help 23:06:04 -gpilz 23:06:15 -??P18 23:07:26 -Nilo_Mitra 23:07:35 -Bob_Freund 23:08:00 bob has left #ws-addr 23:09:33 -Pete_Wenzel 23:12:01 I have made the request to generate http://www.w3.org/2005/12/05-ws-addr-minutes.html anish 23:16:05 -[Fujitsu] 23:18:19 -[Microsoft] 23:20:19 -??P14 23:20:20 WS_AddrWG()4:00PM has ended 23:20:21 Attendees were David_Illsley, gpilz, Steve_Vinoski, Bob_Freund, Mark_Little, Nilo_Mitra, +1.408.748.aaaa, Umit_Yalcinalp, [Microsoft], Dave_Hull, TonyR, Prasad_Yendluri, 23:20:24 ... Mark_Peel/Katy_Warr, MarkN, Vikas, pauld, Marc_Hadley, Anish, Hugo, Steve_Winkler, +1.408.219.aacc, Jonathan_Marsh, Paco, Pete_Wenzel, [Fujitsu], +1.407.503.aadd, Glen, TonyC, 23:20:26 ... Tom_Rutt, DOrchard, Mark_Nottingham 23:40:42 rrsagent, make minutes public 23:40:42 I'm logging. I don't understand 'make minutes public', mnot. Try /msg RRSAgent help 23:40:53 rrsagent, make logs public 23:41:02 rrsagent, generate minutes 23:41:02 I have made the request to generate http://www.w3.org/2005/12/05-ws-addr-minutes.html mnot