19:56:23 RRSAgent has joined #ws-addr 19:56:24 logging to http://www.w3.org/2007/04/30-ws-addr-irc 19:56:26 Ram has joined #ws-addr 19:56:38 Zakim has joined #ws-addr 19:56:57 zakim, this will be #ws_addrwg 19:56:57 I do not see a conference matching that name scheduled within the next hour, bob 19:57:11 David_Illsley has joined #ws-addr 19:58:11 Katy has joined #ws-addr 19:58:11 TonyR has joined #ws-addr 19:58:39 zakim, who is on the phone? 19:58:39 sorry, TonyR, I don't know what conference this is 19:58:40 On IRC I see TonyR, Katy, David_Illsley, Zakim, Ram, RRSAgent, bob 19:58:52 zakim, this will be addr 19:58:52 ok, TonyR, I see WS_AddrWG()4:00PM already started 19:58:53 PaulKnight has joined #ws-addr 19:59:09 zakim, who is on the phone? 19:59:09 On the phone I see [IPcaller], Bob_Freund 19:59:17 +David_Illsley 19:59:20 meeting: WS-Addressing WG Teleconference 19:59:28 chair: Bob Freund 19:59:39 +Gilbert_Pilz 19:59:55 +Paul_Knight 20:00:52 anish has joined #ws-addr 20:01:01 +[Microsoft] 20:01:05 -Gilbert_Pilz 20:01:09 +m2 20:01:12 Rama has joined #ws-addr 20:01:21 +Anish_Karmarkar 20:01:26 zakim, m2 is monica 20:01:26 +monica; got it 20:01:36 gpilz has joined #ws-addr 20:01:44 +Gilbert_Pilz 20:01:48 dhull has joined #ws-addr 20:01:48 zakim [Microsoft] is ram 20:01:52 monica has joined #ws-addr 20:01:54 +[Sun] 20:01:59 +Mark_Little 20:02:18 +David_Hull 20:02:18 zakim, [Sun} is rama 20:02:19 sorry, bob, I do not recognize a party named '[Sun}' 20:02:24 +??P10 20:02:26 -??P10 20:02:31 +Tom_Rutt 20:02:31 zakim, [Sun] is rama 20:02:32 zakim, ??p10 is me 20:02:33 +rama; got it 20:02:35 I already had ??P10 as ??P10, TonyR 20:02:39 zakim, who is on the phone? 20:02:39 On the phone I see [IPcaller], Bob_Freund, David_Illsley, Paul_Knight, [Microsoft], monica, Anish_Karmarkar, Gilbert_Pilz, rama, Mark_Little, David_Hull, Tom_Rutt 20:03:08 zakim, [Microsoft] is ram 20:03:08 +ram; got it 20:03:12 TRutt__ has joined #ws-addr 20:03:22 zakim, ??p10 is me 20:03:22 I already had ??P10 as ??P10, TonyR 20:03:26 zakim, [IPcaller] is katy 20:03:26 +katy; got it 20:03:36 zakim, why don't you show me? 20:03:36 I don't understand your question, TonyR. 20:04:30 zakim, can you hear me? 20:04:30 I don't understand your question, dhull. 20:05:22 zakim, have you met my friend Eliza? 20:05:22 I don't understand your question, dhull. 20:05:34 scribe: katy 20:05:43 zakim, who is here? 20:05:43 On the phone I see katy, Bob_Freund, David_Illsley, Paul_Knight, ram, monica, Anish_Karmarkar, Gilbert_Pilz, rama (muted), Mark_Little, David_Hull, Tom_Rutt 20:05:46 On IRC I see TRutt__, monica, dhull, gpilz, Rama, anish, PaulKnight, TonyR, Katy, David_Illsley, Zakim, Ram, RRSAgent, bob 20:06:41 +??P10 20:06:50 zakim, ??p10 is me 20:06:50 +TonyR; got it 20:07:36 TOPIC: Approve Meeting minutes from last week 20:07:47 RESOLUTION: approved 20:09:15 TOPIC: New Issues - comment from Ashok concerning examples 20:09:16 dorchard has joined #ws-addr 20:09:27 tony, i noticed that Umit name is spelled in an interesting way ;-) 20:09:39 +Dave_Orchard 20:09:42 Chair: those examples were contained in email to ws-policy group 20:09:53 ...and we have not heard back from then yet 20:10:14 i had a similar problem with her name and ended up create an entity for her name, which worked a little bit better wrt xsl processors 20:10:32 ... WS-policy co-chairs hoping to get response back by end of next ws-policy call 20:11:55 +1 on not going to LC until we hear back from WSP 20:12:05 TOPIC: Date to go to last call 20:12:26 waiting seems appropriate 20:12:30 Chair: Is group happy to wait until we have receieved response to ws-policy prior to going to LC 20:12:52 RESOLUTION: Agreed, we will wait for wsp response prior to LC 20:13:02 q+ 20:13:18 q+ 20:13:20 ack tru 20:13:27 q- 20:14:18 TOPIC: LC 139 20:14:18 http://www.w3.org/2002/ws/addr/lc-issues/Overview.html#lc136 20:14:40 TOPIC: LC 136 20:15:46 DavidH: We already discussed what kind of response endpoints are valid, would be nice to also say 'these sort of addresses are ok or not' 20:16:03 ... we agreed not to design for this at the moment 20:16:07 q+ 20:16:24 ... but I would like to be confident that we can extend to cater for this at a later date 20:16:47 ack anish 20:17:03 q+ 20:17:30 Anish: Is this something that one could do via the extensibility point on the anonymous/nonanonymous response assertions 20:18:01 ... do we have this extensibility for this case, would attribute extensibility be enough 20:18:39 q+ 20:18:58 DavidH: If we have nonAnonymous and someone could add 'mailTo only' that would be what we want 20:19:09 ack tru 20:19:41 Tom: These elements were designed for exactly this for the makeConnection protocol 20:20:00 q- 20:20:10 ... rather than extensibility elements, do an 'wsp:All' composing wsaddressingNonAnon with makeConnection 20:20:11 +1 Tom 20:20:58 ... no need to use attribute and element extensibility - just have mailTo as its own highlevel assertion 20:21:35 DavidH: But makeConnection composes if that's the only thing that I can do 20:22:12 q+ 20:22:17 ... what if I know that from one source my server can cope with http&mailTO and http&java - intersection should be java 20:22:33 Tom: You can do this already with wsp vocab 20:23:05 DavidH: Not convinced that the intersection worked in this case 20:23:22 q+ DaveO 20:23:31 ack gpil 20:24:28 Gil: Most of DaveH's comments are critiques of wsp - should not be burden of this group to take on these issues 20:25:53 ack daveo 20:26:40 DaveO: Given wsp current status, going to LC of the document anytime in next couple of weeks would be premature 20:27:09 q+ 20:27:24 ... very fundamental issues like absence is negation - tricky stuff not goiing to be completed in next week or so 20:28:45 ... may just be a case of proving that the composability with makeconnection and intersection performs as required 20:29:38 ... encouraging group to do the work at this stage to check that the extensibility points can by used to do what wsa required 20:30:14 Chair: At very minimum prove that use case for CR 33 is solved 20:30:56 q+ 20:31:32 DaveO: should prove that the assertions do what we expected them to 20:31:39 ack dhull 20:32:00 chair: +1 lots of work been done already on this but we should all critique and check we are happy with this 20:32:36 DavidH: From project management point of view - we cannot do anything until wsp gets its story straight 20:33:56 ... I would like to be absolutely sure that the vocab allows to define what addresses are allowed for future 20:34:14 q+ daveO 20:34:20 ack tru 20:34:58 Tom: Investigated these intersections and they are difficult. I would like to understand DavidH's concerns 20:35:28 ... perhaps David and I could have private email exchange to try to work through these issues without cc-ing the whole group 20:35:34 q+ 20:36:22 ack dhull 20:36:37 Chair: Would be good to write up and share the results of this discussion with the group for us all to understand/critique 20:37:00 DavidH: happy to work with Tom on this 20:37:09 q- 20:37:21 ack daveo 20:37:49 q+ 20:38:49 q+ to ask a question about assertion extensibility and negation to the policy experts 20:38:54 -katy 20:39:10 oops, lost katy 20:39:17 DaveO: ws-a is inherently dependent on wsp current issues. advocate holding on until wsp complete 20:39:23 just re-dialing :o) 20:40:18 q? 20:41:17 DaveO: the addressing policy assertions seem simple, however it concerns me that ws addressing is having a dificult time meeting their requirements with ws policy. It concerns me that this has been so time consuming, 20:42:23 +??P0 20:42:23 Bob: some ot the ws policy terms are not used in familar manner, IF the policy spec could be made less obscure it would help normal people use it. 20:42:49 just back - sorry ran out of skype minutes :o) 20:43:14 I just joined 20:44:09 q+ 20:44:48 ack dhull 20:45:27 DavidH: Question is what we could do now prior to wsp resolution 20:46:20 Chair: We can look into this issue and take assumption that alternative G is the right one 20:46:43 ... and work on how to resolve this issue with this assumption 20:47:07 ... Agree with DavidH we should get this recorded somewhere 20:48:54 (aside) I believe our current schema prevents future parameters or nested assertions of the wsam:NonAnonymousResponses assertion 20:49:11 -Dave_Orchard 20:49:31 david, i'm begining to think the same thing 20:49:32 ACTION: DavidH and Tom to work together to produce thought exercise on composability to cover LC 136 20:49:51 ... and i wonder if ws-policy framework is structured to encourage that 20:50:07 q? 20:50:13 ack anish 20:50:13 anish, you wanted to ask a question about assertion extensibility and negation to the policy experts 20:50:41 ACTION: (cont) Target date middle of next week for meeting in fortnight 20:51:39 q+ 20:51:48 Anish: Assuming that absence=negation, does this mean that policy assertions are not meant to be extensible, 20:51:52 ack tru 20:52:03 ... works with makeconnection maybe not others 20:52:37 Tom: there is distinction between top level assertions and nested assertions 20:52:49 ... because nested assertions are applied within a context 20:53:06 ... whereas top level ones are in global context 20:54:43 Chair: DavidH's issue remains open 20:54:51 TOPIC: Interop 20:55:12 Chair: Hopes for interop in May appear dashed 20:55:13 q+ 20:55:14 q+ 20:55:29 ack ram 20:55:31 ... would like an idea of who can participate 20:56:00 Ram: Feel positive that MS could participate but not committed plan 20:56:08 q+ 20:56:13 ... do we have test scenarios that we can use for testing? 20:56:40 q+ 20:56:46 David: May be able to salvage some of the work that we did last summer for this but haven't had time to look over it in detail 20:56:51 ack david 20:56:57 ack ram 20:57:07 David: IBM still also abls to commit to some kind of interop when spec returns to LC 20:57:37 Ram: In order to do an interop, the WG has to approve a set of test scenarios 20:57:55 q+ 20:57:58 Chair: Yes, we need to start looking at this now - need participation 20:58:12 Ram: Happy to be part of task force 20:58:29 ... would be useful to have some focus on future calls to discuss this 20:59:08 Chair: We did have separate calls for testing before or we could just use the regular calls 20:59:44 q+ 20:59:45 ACTION: David and Ram to refresh group on statud of test cases and what needs to be developed in 2 week's time 21:00:04 ack ram 21:01:07 Chair: I don't expect a meeting next Monday 21:01:15 Chair: AOB? 21:01:41 q+ 21:01:42 Chair: Assume that we will cancel next Monday but keep on calandar just in case 21:02:23 ack ram 21:02:27 ... we have published editors' draft of new spec, please take good look at it to check resolutions incorporated 21:03:40 TRutt__ has left #ws-addr 21:03:46 -Gilbert_Pilz 21:03:57 -Anish_Karmarkar 21:03:59 -Tom_Rutt 21:04:00 -Paul_Knight 21:04:01 -David_Hull 21:04:02 -TonyR 21:04:03 -ram 21:04:03 -Bob_Freund 21:04:04 TonyR has left #ws-addr 21:04:04 -monica 21:04:05 -rama 21:04:07 -David_Illsley 21:04:28 katy, thanks for scribing 21:04:35 np 21:04:41 rrsagent, please generate minutes 21:04:41 I have made the request to generate http://www.w3.org/2007/04/30-ws-addr-minutes.html bob 21:05:17 rrsagent, make logs public 21:05:28 rrsagent, please generate minutes 21:05:28 I have made the request to generate http://www.w3.org/2007/04/30-ws-addr-minutes.html bob 21:06:14 rrsagent, make logs public 21:06:30 rrsagent, generate minutes 21:06:30 I have made the request to generate http://www.w3.org/2007/04/30-ws-addr-minutes.html bob 21:07:32 Rama has left #ws-addr 21:09:37 bob has left #ws-addr 21:25:35 dhull has joined #ws-addr 21:56:51 -Mark_Little 22:05:00 disconnecting the lone participant, katy, in WS_AddrWG()4:00PM 22:05:01 WS_AddrWG()4:00PM has ended 22:05:03 Attendees were Bob_Freund, David_Illsley, Gilbert_Pilz, Paul_Knight, Anish_Karmarkar, monica, Mark_Little, David_Hull, Tom_Rutt, rama, ram, katy, TonyR, Dave_Orchard