20:50:31 RRSAgent has joined #ws-addr 20:50:31 logging to http://www.w3.org/2006/11/06-ws-addr-irc 20:50:46 zakim, this will be ws_addrwg 20:50:46 ok, bob; I see WS_AddrWG()4:00PM scheduled to start in 10 minutes 20:51:13 Meeting: Web Services Addressing WG Teleconference 20:51:24 Chair: Bob Freund 20:53:03 Agenda: http://lists.w3.org/Archives/Public/public-ws-addressing/2006Nov/0015.html 20:53:47 rrsagent, make logs public 20:58:08 WS_AddrWG()4:00PM has now started 20:58:15 +Tom_Rutt 20:58:42 +Bob_Freund 20:58:43 +Gilbert_Pilz 20:59:04 gpilz has joined #ws-addr 20:59:55 plh has joined #ws-addr 21:00:07 +Plh 21:00:07 dhull has joined #ws-addr 21:00:14 pauld has joined #ws-addr 21:00:46 TonyR has joined #ws-addr 21:00:51 +Marc_Hadley 21:01:22 marc has joined #ws-addr 21:01:29 +??P6 21:01:36 zakim, ??p6 is me 21:01:36 +TonyR; got it 21:01:50 zakim, who is on the phone 21:01:50 I don't understand 'who is on the phone', marc 21:01:58 zakim, who is on the phone ? 21:01:58 On the phone I see Tom_Rutt, Bob_Freund, Gilbert_Pilz, Plh, Marc_Hadley, TonyR 21:02:11 PaulKnight has joined #ws-addr 21:02:50 +Paul_Knight 21:03:02 Katy has joined #ws-addr 21:03:50 MrGoodner has joined #ws-addr 21:04:26 +David_Hull 21:04:30 +David_Hull.a 21:05:00 zakim, mute david_hull.a 21:05:00 David_Hull.a should now be muted 21:05:07 +Paul_Downey 21:05:11 zakim, unmute david_hull.a 21:05:11 David_Hull.a should no longer be muted 21:05:26 zakim, mute david_hull 21:05:26 David_Hull should now be muted 21:05:38 zakim, drop david_hull 21:05:38 David_Hull is being disconnected 21:05:40 -David_Hull 21:06:21 Paco has joined #ws-addr 21:06:26 +[IBM] 21:06:27 +[Microsoft] 21:07:00 +[IPcaller] 21:07:20 zakim, IPcaller contains Katy 21:07:20 +Katy; got it 21:08:24 scribe: marc 21:08:24 scribe: marc 21:09:20 minutes of last meeting approved 21:09:33 TOPIC: cr33 21:10:40 bob: section 5.2.1 of SOAP binding allows for other URIs as anon. did we mean that ? 21:11:36 bob: brief discussion and will then vote of this question 21:11:47 q? to ask a question 21:11:58 q+ to ask a question 21:12:25 marc: might be better phrased as "do we still mean it" 21:12:34 ack dhull 21:12:34 dhull, you wanted to ask a question 21:13:12 dhull: do we have a specific textual change to vote on 21:13:41 bob: will rip out 5.2.1 21:14:23 tom: looked for source of the text - not clear that text was explicit in discussion 21:14:50 +GlenD 21:15:21 editors can't recall where text originated 21:16:08 it's in our spec and went through CR-PR-REC 21:16:52 so nit-picking on the scribing seems a little mute 21:18:21 paco: what will be the gain by doing anything 21:18:29 q 21:18:32 q+ 21:19:19 marcgoodner: last sentence of 5.2.1 and 5.2.2 is the text in question 21:21:43 q+ 21:21:58 guilty == remove text allowing other anon URIs 21:22:03 q- 21:22:08 not-guilty == keep that text 21:22:17 ack mrg 21:22:47 pauld: errate, version 1.1, ? 21:23:17 It's not like the text has much force to begin with. Wouldn't an erratum be enough? 21:23:52 bob: how we do it is not relevant, will do minimum necessary 21:23:57 I think errata is enough 21:24:21 it doesn't seem to impact the wsa namespace 21:24:23 formal vote: 21:24:28 IBM - not guilty 21:24:37 BT - guilty 21:24:46 Microsoft: guilty 21:24:55 Sun - guilty 21:25:09 tibco - not guilty 21:25:21 Nortel - guilty 21:25:34 W3C - guilty 21:25:44 BEA - not guilty 21:25:54 CA - guilty 21:26:06 GlenD has joined #ws-addr 21:26:17 Fujitsu - guilty 21:26:34 Hitachi - guilty 21:26:50 8 guilty, 3 not guilty 21:28:28 http://www.w3.org/2005/10/Process-20051014/tr.html#rec-modify 21:28:31 q+ 21:29:20 plh: the change might affect conformance 21:29:52 +1 to Paco 21:29:54 q- 21:30:22 q+ 21:31:06 ack marc 21:31:18 q+ 21:31:58 ack ipcaller 21:32:07 marc: agree with paco, change put other uri out-of-scope for WS-A spec but doesn't preclude it 21:32:10 ack [IPcaller] 21:32:15 ack dhull 21:32:36 so the lack of a MUST means a change doesn't impact conformance, and could fall into "3. Corrections that MAY affect conformance, but add no new features" 21:32:52 dhull: saw text as guidance, doesn't affect conformance 21:33:30 2. Corrections that do not affect conformance 21:33:30 Editorial changes or clarifications that do not change the technical content of the specification. 21:33:32 +1 21:33:53 bob: does WG feel change is not related to conformance 21:34:03 s/3. Corrections that MAY affect conformance, but add no new features/Corrections that do not affect conformance/ 21:34:03 WG: assents 21:35:17 bob: part 2 deals with failure of WSDL binding to support usage promoted by text we have voted to remove 21:35:43 bob: close 33 without action ? 21:36:24 paco: what about the proposals 21:36:57 bob: do we all agree that we need to do something to compose better with policy ? 21:37:05 WG assents 21:37:43 bob: deal with cr33 on its basis and then look at proposals to better support policy 21:39:45 q+ 21:40:02 ack mrg 21:40:07 paco: don't want to close cr33 until we have dealt with policy proposals 21:40:35 mrg: only anon marker needs to be fixed 21:41:37 paco: do we have a specific proposal ? 21:42:29 http://www.w3.org/2002/ws/addr/cr-issues/Overview.html#cr33 21:44:02 q+ 21:45:19 ack dhull 21:45:21 bob review the issue text 21:46:48 q+ 21:46:50 dhull: anon=optional seems to leave the door open to using RM anon but really it just pertains to WS-A anon 21:47:29 ack paco 21:47:40 actually, it's anon=required that just pertains to WS-A anon. Optional leaves things open. 21:48:18 q+ 21:48:28 paco: markers as designed not useful, issue is not with text in soap binding 21:48:31 ack katy 21:48:45 katy: have lost track of rx requirement 21:48:48 A&P proposal speaks to a different issue 21:49:44 RX requirement is actually already satisfied 21:50:01 q+ 21:50:42 Doesn't think WSA anon definition is restrictive at all 21:50:51 ack gpil 21:51:03 katy: when soap binding came out it was possible for rx to use their anon uri but with wsdl binding we restrict that 21:53:01 gill: is it possible to define a policy that restricts to anon only and then expand that to allow rx anon ? 21:53:06 glen: yes 21:53:33 q+ 21:54:29 ack gil 21:54:51 q+ 21:54:52 paco: such usage would contravene policy usage recommendations 21:55:03 glen: no it wouldn't 21:55:15 paco: yes it would 21:55:19 repeat 21:56:11 ack dhull 21:56:17 paco: going to have to ignore the marker because it is badly designed 21:56:24 q+ 21:57:05 q+ 21:57:06 -Tom_Rutt 21:57:18 q- 21:57:34 q+ 21:57:43 +Tom_Rutt 21:57:49 ack [IPcaller] 21:58:09 zakim, IPcaller is marc 21:58:09 +marc; got it 21:59:41 ack paco 21:59:51 q+ 22:00:33 marc: unclear which marker are badly designed - i think everyone agrees that the original formulation doesn;t work with policy but several options have been proposed - some by paco - are any of these ok in paco's opinion 22:01:17 paco: some are ok, disagreeing with glen proposal for rx to create an assertion that overrides the ws-a one 22:01:46 q+ 22:03:06 ack gpil 22:03:25 dhull: composability not limited to rx 22:05:10 so that means we're going back to LC? 22:05:10 ack mrg 22:05:32 quick poll confirms that everyone agrees that current syntax is broken wrt policy 22:05:41 q+ 22:05:44 q+ 22:05:59 mrg: we just need to fix it wrt ws-a anon 22:06:09 ack dhull 22:06:42 ack paco 22:07:10 dhull: use case is indicating haw async response can be sent 22:07:21 paco: having same discussion as last week 22:07:30 q+ to propose a way forward 22:09:53 ack dhull 22:09:53 dhull, you wanted to propose a way forward 22:10:17 bob: don't think ws-a has exclusive on back-channel, we need to find a way to get out of the way of future specs 22:10:34 q+ 22:11:47 q+ 22:13:46 dhull: need a way to say stuff like: "can use mail addresses in reply to" 22:14:27 q+ 22:15:11 q+ 22:15:35 ack [IPcaller] 22:16:55 but it's useful to say "I can't do anythng *but* anon" (or "I can't do anything *but* email") 22:16:59 ack paco 22:17:08 ack mrg 22:17:54 marc: going over ground we covered in Japan F2F. think we need a way to state "i can do ws-a anon" and "I can't do ws-a anon" but not have assertions that shut out others 22:18:04 q- 22:18:08 q+ to talk about going over ground covered 22:18:36 mrg: not worried if our assertion shuts out others 22:21:30 ack dhul 22:21:30 dhull, you wanted to talk about going over ground covered 22:22:22 q+ 22:22:58 dhull: think we have new information now that requires revisiting Japan decision 22:23:42 ack [IPcaller 22:24:18 +1 on relevance of policy 22:24:41 TomRutt has joined #ws-addr 22:26:09 q+ 22:26:36 marc: use of policy brings level of expressiveness that a WSDL marker doesn't have, the two marker proposed are all we need to define, other specs can define others 22:26:43 ack dhull 22:27:39 Katy calls in from Moon Base 1 :-) 22:28:42 q+ 22:29:08 ack mrg 22:29:43 q+ 22:29:52 ack dhull 22:31:21 dhull: in what way is our current markup policy unfriendly ? does policy have a "this and this but not that" 22:31:26 q+ 22:32:25 q- 22:32:50 paco: second is an open issue with policy WG, first is that assertion qname should capture meaning not attribute value or content 22:35:47 -[IBM] 22:36:34 +1 22:37:22 marc: volunteers to propose a solution 22:37:30 gill: volunteers to help 22:38:38 -[Microsoft] 22:38:40 -Paul_Downey 22:38:41 -Gilbert_Pilz 22:38:43 -Tom_Rutt 22:38:45 -TonyR 22:38:49 -Bob_Freund 22:38:50 -Marc_Hadley 22:38:51 -David_Hull.a 22:38:52 -Paul_Knight 22:38:52 Katy has left #ws-addr 22:38:53 gpilz has left #ws-addr 22:38:53 -GlenD 22:38:55 -Plh 22:38:57 TonyR has left #ws-addr 22:38:58 pauld has left #ws-addr 22:39:00 thanks for scribing, Marc 22:39:07 I have made the request to generate http://www.w3.org/2006/11/06-ws-addr-minutes.html plh 22:39:07 -marc 22:39:08 WS_AddrWG()4:00PM has ended 22:39:10 Attendees were Tom_Rutt, Bob_Freund, Gilbert_Pilz, Plh, Marc_Hadley, TonyR, Paul_Knight, David_Hull, Paul_Downey, [IBM], [Microsoft], Katy, GlenD, marc 22:40:40 zakim, bye 22:40:40 Zakim has left #ws-addr 22:42:37 TomRutt has left #ws-addr 22:51:49 bob has left #ws-addr