19:57:50 RRSAgent has joined #ws-addr 19:57:50 logging to http://www.w3.org/2007/04/02-ws-addr-irc 19:58:25 WS_AddrWG()4:00PM has now started 19:58:32 +Bob_Freund 19:58:46 meeting: WS-Addressing WG Teleconference 19:58:53 chair: Bob Freund 20:00:32 +m2 20:00:46 TRutt_ has joined #ws-addr 20:01:24 +Gilbert_Pilz 20:01:37 gpilz has joined #ws-addr 20:01:46 zakim, +m2 is monica 20:01:46 sorry, bob, I do not recognize a party named '+m2' 20:01:47 TonyR has joined #ws-addr 20:01:58 zakim, m2 is monica 20:01:58 +monica; got it 20:02:02 anish has joined #ws-addr 20:02:15 +David_Illsley 20:02:41 +Anish_Karmarkar 20:02:56 +??P9 20:03:07 zakim, ??p9 is me 20:03:07 +TonyR; got it 20:03:12 monica has joined #ws-addr 20:03:25 +Tom_Rutt 20:03:27 rama will not be able to join today 20:06:52 +[Microsoft] 20:07:03 yinleng has joined #ws-addr 20:07:20 zakim, [microsoft] is ram 20:07:20 +ram; got it 20:07:49 PaulKnight has joined #ws-addr 20:07:55 zakim, who is on the phone? 20:07:55 On the phone I see Bob_Freund, monica, Gilbert_Pilz, David_Illsley, Anish_Karmarkar, TonyR, Tom_Rutt, ram 20:08:35 +Paul_Knight 20:08:48 +??P2 20:08:51 zakim, ??P2 is me 20:08:51 +yinleng; got it 20:10:20 +David_Hull 20:10:53 +[Microsoft] 20:11:06 MrGoodner has joined #ws-addr 20:11:13 zakim [microsoft is mrgoodner 20:11:32 zakim, [microsoft] is mrgoodner 20:11:32 +mrgoodner; got it 20:12:19 scribe: Paul 20:12:46 minutes of March 19 approved 20:12:50 MrGoodner1 has joined #ws-addr 20:13:20 Bob: Several new issues added to mail list 20:13:28 http://lists.w3.org/Archives/Public/public-ws-addressing-comments/2007Mar/0000.html 20:13:50 Bob: this one describes a pretty clear typo 20:14:51 Bob: This one is an editorial item, resolved as proposed. 20:14:59 http://lists.w3.org/Archives/Public/public-ws-addressing/2007Apr/0003.html 20:15:14 Bob: Next: attaching policy to an EPR. 20:16:08 TRutt: At WS-Policy, the feeling was that WS-Addressing should address it 20:16:19 q+ 20:16:32 TRutt: It should be pretty fast, about 3 pages 20:16:51 MrGoodner: Skeptical of how fast it will be 20:16:52 q+ 20:17:10 gpilz: Can it be in metadata spec? 20:17:20 ack gpi 20:17:27 ack david 20:18:10 David: Don't think it should be in metadata spec. 20:18:53 Bob: Earlier in WSA we did not feel we could address it well, and returned it to WS-Policy group 20:19:34 Bob: NOt sure we have enough domain knowledge in the group to do it. It is more in the purview of WS-Policy. 20:19:37 i would the ws-policy wg would review our spec 20:19:45 s/i would/i would hope/ 20:19:52 TRutt: It is not rocket science. 20:20:09 q+ 20:20:40 ack ani 20:20:41 TRutt: We just need to come up with a way to reference policy EPR. 20:21:38 Anish: It should be done either here or in WS-Policy. We could potentially do it if we have the expertise. Perhaps we could form a joint task force with WS-Policy. 20:21:56 Bob: record this as a new item 20:22:39 ACTION: Bob to coordinate with WS-Policy about some way to address it jointly. 20:22:48 http://lists.w3.org/Archives/Public/public-ws-addressing/2007Apr/0008.html 20:23:15 Bob: Next Item from Anish 20:24:08 Bob: We will accept this as a new issue. 20:24:29 Bob: Now for the main event: F vs. G 20:24:53 Bob: Consensus forming around G or G'; little support for F 20:25:14 TRutt: G is less verbose in most normal cases 20:25:41 Bob: Any objectin to using G as the base for further wordsmithing? 20:25:57 Bob: No objectin, we will use G going forward. 20:26:18 s/objectin/objection 20:26:40 TRutt: Monica had some important points 20:26:52 http://lists.w3.org/Archives/Public/public-ws-addressing/2007Apr/0007.html 20:28:27 Monica: Describes her items as addressed in her message. 20:29:03 i should point out that this ties in with one of my comments too 20:29:31 q+ 20:29:41 q+ 20:29:44 TRutt: How do we position these additional assertions? 20:30:17 TRutt: It's a matter of how we word it, to imply we are adding limitatins. 20:30:39 s/limitatins/limitations 20:31:14 David_Illsley_ has joined #ws-addr 20:31:35 +David_Hull.a 20:31:37 -David_Hull 20:31:57 Monica: When you have an empty policy, there is no claim. It does not infer behavior. 20:31:59 ack mrgo 20:32:15 dhull has joined #ws-addr 20:33:02 MrG: The nested addressing assertions imply further processing like the mixed mode. 20:34:22 TRutt: It is a user refinement of the capabilities. 20:34:53 Monica: Why not put a section in WSA that all these types are supported? 20:35:24 Tony: We have not written such a section yet. 20:35:32 ack ani 20:35:47 Monica: Would like to see such a section. 20:36:56 TRutt_ has joined #ws-addr 20:37:02 q+ 20:37:15 q- 20:37:41 q+ 20:37:42 Anish: It seems counter-intuitive that both anon and non-anon would be supported. 20:38:04 ack mrgo 20:38:30 q+ 20:39:05 TRutt_ has left #ws-addr 20:39:11 ack ani 20:39:16 MrGo: Don't see why you need to explicitly state the ability. 20:39:26 TRutt_ has joined #ws-addr 20:39:39 q+ 20:39:45 See: http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;%20charset=utf-8#rPolicy_Alternative 20:40:00 Explicitly: An alternative with zero assertions indicates no behaviors. An alternative with one or more assertions indicates behaviors implied by those, and only those assertions. 20:40:02 q+ 20:40:15 Can't infer from empty. 20:40:26 When an assertion whose type is part of the policy's vocabulary is not included in a policy alternative, the policy alternative without the assertion type indicates that the assertion will not be applied in the context of the attached policy subject. 20:40:43 Anish: Would ike to be able to state that you can have ReplyTo could be anon and FaultTo can be non-anon 20:40:51 s/ike/like 20:40:57 monica, the alternative would include an assertion, the wsam:Anonymous one for which we define the semantics 20:41:39 MrGo: Not sure what you want here. 20:41:41 q+ 20:42:04 ack gpilx 20:42:13 axk gp 20:42:17 ack gp 20:42:33 gpilz: Anish is talking about granularity. 20:42:46 i agree with gil, that this is tangential to the current discussion 20:43:14 that is what i was trying to estabilish, that split usecase is not supported by any of the proposal (including mine) 20:43:20 gpilz: It is tangential. 20:43:44 ack tru 20:43:50 anish, I agree with your statement that we don't need to support that detailed usecase 20:44:31 TRutt: It is one of our use cases we need to support. It's enough that the implementation supports either anon or non-anon. 20:44:45 q+ 20:44:58 ack monica 20:45:11 TRutt: Hope we can come up with wording to get around empty problem. 20:46:06 Monica: Empty does not tell you anything. See text pasted above. 20:46:10 q+ 20:47:09 Bob: Would an empty nested assertion satisfy the need? I've heard it described in various ways - asserts no influence, etc. 20:47:27 q+ 20:47:32 Bob: We're grappling with the nuances. 20:47:32 q+ 20:47:36 ack mrg 20:48:20 MrGo: The proposal I sent in was vetted with our (Microsoft) policy guys. 20:48:22 ack david 20:49:16 David: Wouldn't outer non-nested assertions indicate the behavior? 20:50:13 q? 20:50:31 Monica: If it's not there, you can't imply anything from it - null behavior. It is policy alternative vocabulary. 20:50:44 q+ ram 20:50:48 ack tru 20:52:09 ack ani 20:52:10 TRutt: The algorithm treats empty as having some implied restriction. If we can come up with some text to deal with it... 20:52:53 Anish: It is counterintuitive. I'd like an assertion that says "I support addressing." 20:53:21 Anish: If I don't put it in, it should not imply that I support all protocols. 20:53:39 s/find/finds/ 20:54:34 Anish: What if you make a WSA claim on an endpoint that only supports one-way operations? 20:54:47 q+ 20:54:53 Bob: Even one-way MEP has a way to support faults. 20:54:56 q- 20:54:59 ack ram 20:55:43 Ram: The absence of top-level or the absence of the nested assertion should be handled differently. 20:56:20 Monica: The primer does not address the nested assertion explicitly. 20:57:05 Ram: The nested assertions are to qualify the top-level assertion. 20:57:37 Bob: Should we construct a well-worded question to send to the WS-Policy group? 20:57:37 q+ 20:57:57 ack ani 20:58:47 Anish: The spec does not say that if you support WSA then you must support anon or non-anon. 20:59:34 q+ 21:00:17 Bob: the WSDL spec and now the Metadata spec elaborate on this. 21:00:40 ack ani 21:01:29 +1 to WSA is more than response endpoints 21:01:43 Anish: We are focusing on anon and non-anon, but there are other cases we need to consider. 21:01:55 q+ 21:02:16 Mrgo: This is a new use case we have not considered before. 21:02:31 q+ 21:02:42 Anish: We should have an assertion that simply expresses support for WSA. 21:03:07 MrGo: I thought that was what proposal G was for. 21:03:53 -ram 21:04:02 Anish: I suggest adding some explanation disclaiming support for either anon or non-anon. I think we actually agree. 21:04:48 q+ 21:04:54 TRutt: That capability was considered several proposals ago. F & G are simple use cases. 21:04:59 q- 21:05:27 TRutt: The intersection algorithm precludes some approaches. 21:06:18 Anish: If we go with the clarification I am suggesting, would a client wanting non-anon response EPRs, would it not find a match? 21:06:29 -yinleng 21:06:45 TRutt: We need to understand the use cases. 21:06:45 q+ 21:06:53 ack davi 21:07:02 q+ 21:07:33 ack monica 21:07:38 -TonyR 21:08:21 ack mrg 21:08:27 David: My concern is with letting the empty case imply support for specific response types. 21:10:05 MrGo: If you require mixed use case, you need nested policies to express it. 21:11:19 Monica: Is that domain-specific processing? 21:11:49 ack ani 21:12:02 MrGo: No, it doesn't have to introduce domain-specific processing. 21:12:19 q+ 21:13:13 ack gpil 21:13:15 Anish: The top-level assertion does not make claims, without the nested assertions. 21:13:33 gpilz: I'm confused by this discussion. 21:13:55 q? 21:14:01 q+ 21:14:23 q- 21:15:11 gpilz: WS-Policy defines vocabularies in the context of an assertion, which make it more complicated. 21:15:30 qa+ 21:15:36 q+ 21:15:41 Anish: yes, with nothing inside, it has different implications. 21:15:52 q+ 21:15:59 +1 to getting clarification from ws-policy wg 21:16:04 gpilz: Back to Bob's proposal to put pointed questions to WS-Policy. 21:16:06 ack tru 21:17:32 TRutt: The problem stems from Chris' inability to prevail on the meaining of empty in the WS-Policy group. That group is split on this issue. We should problably write what we want to support our use cases. 21:17:35 ack mrg 21:17:55 -David_Hull.a 21:18:15 q+ 21:18:16 q+ 21:18:42 ack ani 21:18:47 MrGO: We discussed the negation issue. We don't think it's an issue here. 21:19:24 ack monica 21:19:40 Anish: Somebody should work with WS-Policy on this. 21:20:08 Monica: Work is still going on in the Policy WG. 21:20:45 Bob: Can we package alternative "G" in a question for WS-Policy? Is that a reasonable thing to do now? 21:21:02 MrGo: Can we begin by adopting proposal G? 21:21:16 TRutt: G with my proposals? 21:21:32 Anish: No problem with that. 21:22:13 Bob: We seem to be resolved to incorporate G with Tom's subsequent wordsmithing. 21:22:14 does that include anish's comments? 21:22:26 q+ 21:22:35 TRutt: I think Tony can do the wordsmithing. 21:22:37 ping 21:22:57 ack ani 21:23:38 Bob: We have resolved to do what we just discussed, insert the text of G with Tom Rutt's additional text. 21:23:47 http://lists.w3.org/Archives/Public/public-ws-addressing/2007Apr/0010.html 21:24:13 Monica: that is a link to Anish's comments. 21:24:45 Anish: Why should we have this restriction described in my comments? 21:25:24 Bob: the WS-Policy group indicated it could not be done, due to the level of abstraction. It was in Chris Ferris' message to WSA. 21:25:55 Anish: I will look at that. 21:27:08 Anish: Not clear if we have defined this assertion closely enough. What about SOAP vs. non-SOAP binding? 21:27:09 chris' response http://lists.w3.org/Archives/Public/public-ws-addressing/2007Feb/0006.html 21:27:21 TRutt: This sounds like a new issue. 21:27:47 Bob: Anish, can you submit something on this topic? 21:28:41 Bob: Please extract the issue. 21:28:48 yes, that is the one 21:28:50 Anish: It is in comment number 1. 21:30:30 Bob: It is in point E in Chris's message. 21:30:54 Anish: It does not really explain why. 21:31:51 Anish: There were two issues in my comment... the second is what it is claiming conformance to. 21:32:23 Bob: I will take the contents of the email and make it two issues. 21:32:33 Anish: okay 21:33:00 ACTION: Bob split Anish's email to make two issues. 21:34:27 Bob: I hope we can preserve proposal G, with clarifications, to send back to WS-Policy. It should be ready before the next last call round. 21:34:50 q+ 21:35:15 ack tr 21:35:30 Bob: It would be good to finish before the last call , so we can get feedback early from WS-Policy instead of having it raised as an issue at last call. 21:36:28 Bob: Once we think we have a resolution, we should send it to WS-Policy, according to the W3C policy. 21:36:47 Trutt: We can send it as a reference to the new editor's draft. 21:37:03 Bob: Better to send it explicitly to WS-Policy. 21:37:23 q+ 21:37:42 ack ani 21:37:48 Bob: Tom, can you send me the wordsmithed text to modify G. 21:38:22 q+ 21:38:41 ack mrg 21:38:53 Anish: Gil's question about negation, with interpretation of the absence of a nested assertiion implying negation, is that resolved? 21:39:29 MrGo: Don't need to deal with that now, with WS-Policy. 21:39:52 Anish: That seems to take us back to proposal F, not G. 21:40:24 Bob: The nuance is the point at which the vocabulary is defined. 21:41:11 there is no negation in current ws-p 21:41:12 Bob: Maybe we should excise the assertions if they are so difficult to understand. 21:41:56 if we all agree that there is no negation, then i don't have a problem. But like Gil, I remember Chris ferris vehemently stating the negation part 21:42:10 which chair? 21:42:19 Bob: I have solicited one of the WS-Policy co-chairs' opinion on this, and it appeared that either F or G is possible; G was a bit better. 21:42:22 it would be easier if the policy wg resolved this issue once and for all 21:43:01 Bob: Suggest a call next Monday... It is a bank holiday in UK... ? 21:44:15 Bob: Aim for April 16th for next meeting. We need as much attendance as possible. 21:44:50 Bob: Meeting adjourned due to lack of linear arguments. 21:45:59 Bob: As of today, we have resolved on G. A through F are dead. There were no objections when the question was called. 21:47:22 Anish: Initiating circular discussion among WS-Policy members on the call. Minutes not taken. 21:48:20 -monica 21:48:22 -Tom_Rutt 21:48:23 -Gilbert_Pilz 21:48:23 -David_Illsley 21:48:25 -mrgoodner 21:48:27 -Anish_Karmarkar 21:48:28 -Bob_Freund 21:48:33 -Paul_Knight 21:48:34 WS_AddrWG()4:00PM has ended 21:48:36 Attendees were Bob_Freund, Gilbert_Pilz, monica, David_Illsley, Anish_Karmarkar, TonyR, Tom_Rutt, ram, Paul_Knight, yinleng, David_Hull, mrgoodner 21:48:36 TRutt_ has left #ws-addr 21:48:38 Paul, thanks for scribing 21:48:43 yinleng has left #ws-addr 21:48:55 rrsagent, make logs public 21:49:18 rrsagent, generate minutes 21:49:18 I have made the request to generate http://www.w3.org/2007/04/02-ws-addr-minutes.html bob 22:04:46 bob has left #ws-addr