19:25:04 RRSAgent has joined #ws-ra 19:25:04 logging to http://www.w3.org/2009/05/05-ws-ra-irc 19:25:06 RRSAgent, make logs public 19:25:06 Zakim has joined #ws-ra 19:25:08 Zakim, this will be WSRA 19:25:08 ok, trackbot; I see WS_WSRA()3:30PM scheduled to start in 5 minutes 19:25:09 Meeting: Web Services Resource Access Working Group Teleconference 19:25:09 Date: 05 May 2009 19:25:25 fmaciel has joined #ws-ra 19:26:08
  • li has joined #ws-ra 19:26:42 WS_WSRA()3:30PM has now started 19:26:53 +Bob_Freund 19:27:58 TomRutt has joined #ws-ra 19:29:21 +Wu_Chou 19:29:30 +Tom_Rutt 19:29:42 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009May/0006.html 19:29:55 +[Microsoft] 19:30:16 zakim, [Micro is Geoff 19:30:16 +Geoff; got it 19:30:18 DaveS has joined #ws-ra 19:30:19 + +1.702.414.aaaa 19:30:25 Katy has joined #ws-ra 19:30:26 zakim, Geoff has Asir 19:30:26 +Asir; got it 19:30:43 dug has joined #ws-ra 19:30:46 Zakim, aaaa is Doug 19:30:46 +Doug; got it 19:30:48 Hi folks Dave's on line. Will dial in shortly. 19:30:57 brb 19:31:28 + +1.408.642.aabb 19:31:33 Ashok has joined #ws-ra 19:32:07 +??P7 19:32:18 zakim, aabb is a lurker 19:32:18 I don't understand 'aabb is a lurker', Bob 19:32:26 +Ashok_Malhotra 19:32:32 gpilz has joined #ws-ra 19:32:43 zakim, P7 is Katy 19:32:43 sorry, Bob, I do not recognize a party named 'P7' 19:32:59 zakim, ??P7 is Katy 19:32:59 +Katy; got it 19:33:12 zakim, aabb is Gilbert 19:33:12 +Gilbert; got it 19:33:15 +Yves 19:33:27 + +1.646.361.aacc 19:33:47 + +1.408.970.aadd 19:33:55 zakim, aacc is Vikas 19:33:55 +Vikas; got it 19:34:33 +??P11 19:34:43 zakim, aadd is Fred 19:34:43 +Fred; got it 19:34:57 Zakim, ??P11 is Dave 19:34:57 +Dave; got it 19:35:13 +Don_Wright 19:36:01 Agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009May/0006.html 19:36:09 asir has joined #ws-ra 19:37:37 scribe: Gilbert Pilz 19:38:04 TOPIC: agenda bashing 19:38:14 RESOLUTION: agenda approved by UC 19:38:27 TOPIC: approval of minutes from 04/28/2009 19:38:37 RESOLUTION: minutes approved by UC 19:39:01 TOPIC: F2F scheduling 19:39:18 Bob: June 9-11 at Oracle HQ in Redwood Shores, CA 19:39:57 ...: get your RSPs 2 weeks prior or you won't be fed 19:39:58 Vikas has joined #ws-ra 19:40:31 ...: I will set up a ballot that will close on 5/26/2009 19:40:43 ...: we are planning on all three days 19:41:09 TOPIC: new snapshots 19:41:21 Bob: we've close a few issues so we should take a new snapshot 19:41:32 ...: Yves, can you take care of that? 19:41:37 Yves: yes 19:41:47 ACTION: Yves to generate may 1st snapshots 19:41:47 Created ACTION-64 - Generate may 1st snapshots [on Yves Lafon - due 2009-05-12]. 19:42:07 Bob: just review the things that have closed since the last snapshot 19:42:08 +JeffM 19:42:23 ...: the W3C process specifies a 3 month heartbeat 19:42:35 ...: on that basis, we should have a new WGD out in June 19:42:44 -Vikas 19:42:45 + +1.571.262.aaee 19:43:01 ...: Do we have enough time to put togther such a thing, and approve it at the F2F? 19:43:14 Wu: Will this WGD be the final one? 19:43:39 Bob: There is a WGD that occurs every 3 months. There is no progressive status. It is not last call or anything like that. 19:43:41 Wu: OK 19:44:34 Gil: Want me to create an AI? 19:44:46 Bob: Too early. Wait until the end of May snapshot. 19:44:54 q+ 19:45:15 ack gpi 19:45:35 TOPIC: AI review 19:46:21 Bob: Would every one who has an AI please review them and either (a) adjust the date or (b) offer it up for someone else to do. 19:47:43 TOPIC: New Issues 19:47:54 Bob: One new issue, Gil's, 6860 19:48:07 ...: any objection to accepting this and assigning to Gil? 19:48:20 RESOLUTION: 6860 accepted and assigned to Gil 19:48:45 q+ 19:48:58 TOPIC: Task Team Progress 19:49:22 Bob: Who will speak for team 6413? 19:49:25 ack geo 19:50:05 Geoff: Not really clear what the scope of deliverables is. 19:50:29 ...: Microsoft and IBM are working on a list of questions to be answered, but there are two main points of contention. 19:50:45 ... We can't make progress until we resolve these. 19:51:01 ... Should the fragment specifiers be in the same namespace as WS-T? 19:51:21 ... Should the fragment dialects, operations, etc. be in the same specification as WS-T? 19:51:24 -Dave 19:51:33 ... It's time to return to the WG on how to decide these issues. 19:51:47 Bob: Do other member of the Task Team concur? 19:51:52 Katy: Yes. 19:52:11 Bob: It seems that these issues are described. Are they described enough to deal with them on this call? 19:52:21 ... Does everyone have their arguments in place? 19:52:22 +??P8 19:52:25 Kary: Yes. 19:52:44 Bob: Should we deal with them in that order, or the opposite order? 19:52:46 s/Kary/Katy/ 19:52:51 ... They are kind of connected, right? 19:52:56 Geoff: Yes. 19:53:16 q+ 19:53:29 Bob: Sould the fragment specification, whever it is contained, be in the WS-T namespace or not? 19:53:33 ack katy 19:54:10 Katy: We discussed this with our dev teams. 19:54:34 ... Our products teams would not implement WS-T without at least basic fragment support. 19:54:59 ... The reason that WS-T and WS-RT were split is primarily historical. 19:55:37 ... The key reason why it is bad to split these into two namespaces is that it allows a loophole of different fragment mechanisms within WS-T. 19:55:49 q+ 19:56:04 ... Putting them in the same namespace/spec removes any ambiguity about how fragments should be supported in WS-T. 19:56:38 I strongly support Katy's notion that one namespace supports better chances of interoperability. 19:56:45 Bob: (missed question) 19:56:59 Bob: can frag support be used outside of T? 19:57:10 Yes, I also support Katy's notion that one namespace supports better chances of interoperability. 19:57:11 Katy: We need to look at the 99% use case. We've looked at splitting it out into an appendix. 19:57:12 Katy: maybe in theory but we don't see it in practice 19:57:34 Bob: Any further arguments in favor? 19:57:39 Bob: Any against? 19:57:43 ack geo 19:57:52 Geoff: Not sure where to start here . . . 19:58:17 q+ 19:58:17 ... One of the primary reasons for putting it in the WS-T namespace seems to be to force people to adopt something. 19:58:35 ... This seems very strange. You're not going to be able to do this. 19:58:45 ... We don't have the right to do this. 19:58:59 ... We can offer up specs and, if we do things right, people will use them. 19:59:10 ... But it's not right to force people to do things they don't want to do. 19:59:22 ... Other issues: no real reason to make this change. 20:00:09 q+ 20:00:18 ... No evidence that I have seen that this is other than political 20:00:34 ... These have been separate in the past, they work separately, there's no value to combining them. 20:00:58 ... WS-T has been widely adopted, widely referenced, and widely implmented. 20:01:23 ... There are reasons for combining specs, we should stick to those. 20:01:34 Bob: Will allow Katy to rebut. 20:01:35 ack katy 20:01:56 Katy: This isn't forcing anyone to do anything. It simply specifies the recommended way of supporting fragment access. 20:02:15 ... This has nothing to do with politicis. It is simply about support fragment access. 20:02:33 ... It also provides a pattern for fragment extensibility that other specifications can use. 20:02:38 Geoff: We disagree. 20:02:53 q+ 20:02:55 ... I don't believe that there are any serious technical reasons for doing this. 20:03:01 constrained devices (which are impacted by additional namespace) would be impacted by having to support 2 specs instead of 1- and they would use frag support exactly because they're constrained. 20:03:07 ... This is just joining things together "for advantage". 20:03:16 ack wu 20:03:20 Wu: I'm kind of confused and concerned. 20:03:39 ... The group has already reached consensus to split the two (WS-T and frag) 20:03:42 q+ 20:03:47 q+ 20:04:00 Wu: This has already been decided. 20:04:10 Yes the WG reached consensus prior to forming 6413 taskforce 20:04:13 ... This appears to be a step back from the previous consensus. 20:04:43 Ack Yves 20:04:51 Yves: I want to restate what I said at a previous concall. 20:05:02 ...: For me, fragments are really part of the EPR 20:05:16 ... The definition of fragments is in the ??? spec 20:05:31 ... The meaning of the fragment is usually related to the MIME type 20:05:47 ... In this case things are different because we constrained to XML? 20:05:50 +1 to Yves 20:05:59 ... Don't see a reason to combine them. 20:06:04 Ack dave 20:06:17 DaveS: Primary reason to put fragments in WS-T is to promote interoperability. 20:06:20 interop can be achieved without joinign them together 20:06:38 ... I agree with Geoff that the only way this will work is if we produce a high-quality spec that is easy to use. 20:06:54 as long as a namespace is chosen for fragment, it will provide interop, there is no need to group specs on namespaces (apart to reduce the number of ns URIs in implementations runtime) 20:06:56 ... We need to produce one spec to pull the community together. 20:07:10 ack gpil 20:07:32 Gil: to Wu (re: this was decided) - not my understanding 20:07:47 ... the task force was to look at what things would look like _if_ there was a frag spec 20:08:06 ... it was not cast in stone - examine a possibility 20:08:26 Wu: disagrees 20:08:43 ... I remember it being a consensus 20:09:09 Bob: My recollection was that the idea that it could be a separate specification illicted less negative reactions than the inclusion idea. 20:09:12 Sounds like we should think about documenting the starting point and the goals and questions for any future taskforces 20:09:13 thankyou Bob 20:09:27 ack dug 20:09:33 Doug: I agree with Gil's interpretation 20:10:03 ... IBM think a separate frag spec will not work because a reference from WS-T to another spec isn't a strong enough link to assure interop. 20:10:13 ... One primary example is Member Submission specs. 20:10:32 ... They all say "THis doc is just for evaluation" "This may change" 20:10:36 ... People ignored that. 20:10:53 ... People implemented these specs and now scream loudly when you propose changes. 20:11:19 ... So its unlikely that a simple reference and admonishment will produce the desired result (interop) 20:11:23 W3C has plenty of precedences for establishing such links - SOAP, WS-A and WSDL 20:11:33 ... To Yves, I'd like to see a concrete proposal around your ideas. 20:11:41 ... I can't see how that would work. 20:11:51 W3C has plenty of precedences for establishing such links - SOAP, WS-A and WSDL 20:11:56 asir has joined #ws-ra 20:12:06 ... Fragment support is driven by the client and service-minted EPRs should not be changed by the client. 20:12:12 Yves: The thing is . . . 20:12:42 ... In a way you are using the EPR if you use the specified policy to talk to the service. 20:12:59 q+ 20:13:07 ... You should be able to say that you only want "one part" of "this" (the thing referenced by the EPR) 20:13:20 ... This should be part of WS-Addr so you don't need to tie it to WS-T 20:13:28 ... It should support more that just WS-T 20:13:43 ... In a way you are right about not changing EPRs . . . 20:13:45 ack geoff 20:14:06 Geoff: There is plenty of precendent in the W3C for having links between specifications (SOAP, WS-Addr) 20:14:14 ... This is a commonplace way of doing things. 20:14:19 jeffm has joined #ws-ra 20:14:23 ... Yves comment is interesting and valid. 20:14:31 ... WS-Man was thinking that way 20:14:47 ... They put the definition of the resource in the header, not the body of the message. 20:14:52 note: SHOULD is a meaningless way of saying "please, but if you don't, oh well" 20:15:11 ... They were working towards this idea of the concept of a frag being an extension of the concept of an address. 20:15:30 Bob: Do we have a consensus that frags do need to part of our work? 20:15:36 Doug: It is part of our charter. 20:15:47 Bob: Nobody disputes we need frags as part of our output. 20:15:54 ... The question is, where do we put it? 20:16:03 ... In the input specs, it is part of WS-RT. 20:16:16 ... We could just mumble along and have it part of a WS-RT that we produce. 20:16:38 ... Thinking about our alternatives, the namespace issue connects frags to WS-T. 20:16:56 ... Even if frags were in WS-RT, a common namespace would connect them. 20:17:20 ... Conceptually writing it as an EPR extension is another approach. 20:17:29 ... catalog approaches 20:18:01 ... (a) Include (in WS-T with same namespace, (b) Separate (with WS-T namespace), (c) Separate (as an EPR)? 20:18:09 ... (c) do nothing 20:18:40 q+ 20:18:45 isn't "do nothing" a (d) ? 20:18:54 what is do nothing 20:19:44 Gil: It's a 3 x 2; in WS-T, in separate spec, as an EPR extension then in/out of the WS-T namespace - then "do nothing" 20:20:27 ack wu 20:20:28 a) in T, b) in separate RT spec, c) EPR extension ? 20:20:45 .. (a) in WS-T, same namespace as WS-T 20:20:59 ... (b) in a separate spec, same namespace as WS-T 20:21:13 asir: that's the msft motto 20:21:14 ... (c) as an EPR extension, same namespace as WS-T 20:21:26 :-) 20:21:28 ... (d) in WS-T, different namespace than WS-T 20:21:53 ... (e) as a separate spec, different namespace than WS-T 20:22:08 ... (f) as an EPR extension, different namespace than WS-T 20:22:22 ... (g) do nothing (WS-RT as today) 20:22:45 Thanks for clarifying 'do nothing' 20:23:07 (all) Ridicule Gil for his noisy keyboard 20:23:48 Bob: We don't have Chad, but we do have Open STV 20:23:59 Jeff: Why don't we have Chad? 20:24:01 Bob: Yves? 20:24:15 Yves: We'd have to get it from Paul Downey 20:24:25 Jeff: Open STV works just fine 20:25:27 Bob: Think about your choices, type the letters 'a' through 'g' in IRC scrambled to your taste 20:25:35 ... First one most favorite, last one least. 20:25:43 Jeff: As many as you want 20:27:08 e, g, f, 20:27:15 a,d,b,g 20:27:17 f e g d 20:27:18
  • f,e,g 20:27:19 Fujitsu: a, b, d, e, g 20:27:21 a d b g 20:27:23 egf 20:27:34 a,b 20:27:41 a,g 20:27:43 egf 20:28:31 a, b, d, e, g 20:29:30 b, a, d, e 20:30:37 a,b,c 20:31:33 what about Bob? 20:34:15 I assume this is a straw poll, right? 20:36:28 (all): Attempt to work Open STV 20:36:42 Geoff: Just to be clear, the purpose of this poll is to winnow things down? 20:36:44 Bob: Yes. 20:37:37 Bob: We should have done a dry-run of this before . . . 20:38:16 ... results 20:38:19 ... a - 7 20:38:41 ... e - 3 20:38:45 ... f - 2 20:38:49 ... b - 1 20:39:01 ... (a) wins on the count of first choices 20:39:31 ... (a) was in same spec as WS-T with the same namespace as WS-T 20:39:42 Election title: ballot 1 20:39:44 Method: Scottish STV 20:39:45 Number of total ballots: 13 20:39:47 Number of invalid or empty ballots: 0 20:39:48 Number of ballots used in the count: 13 20:39:50 7 candidate running for 1 seats. 20:39:52 R|a |b |c |d |e |f |g |Exhaust|Surplus|Thresho 20:39:53 | | | | | | | |ed | |ld 20:39:55 ================================================================================================================== 20:39:56 1|7.00000|1.00000|0.00000|0.00000|3.00000|2.00000|0.00000|0.00000|0.00000|7.00000 20:39:58 |--------------------------------------------------------------------------------------------------------------- 20:40:00 | Count of first choices. Candidate a has reached the threshold and is elected. The election is over since all 20:40:01 | seats are filled. 20:40:03 Winner is a. 20:41:02 Bob: To take it from here, things other than 'a' or 'e' seem to have little support. 20:41:14 ... Hitachi doesn't have that strong an opinion on this 20:41:27 ... 'a' seems to have the advantage by more than a factor of 2 20:41:46 ... For those people that support things other than 'a', is there a way 'a' can be made palatable. 20:42:07 Asir: What was the question? 20:42:09 Ashok has joined #ws-ra 20:42:42 ... Alternatives other than 'a' don't have enough support that, even if they coalesced, couldn't win out over 'a'. 20:42:58 Asir: This is just a strawpoll, right? 20:43:30 Jeff: This clearly shows that there is a group that supports 'a' and a group that supports 'e'. Other than that, there isn't much support for the others. 20:43:37 fruitful options are a and e 20:43:42 Bob: The only two that are fruitfull are 'a' and 'e'. 20:43:49 ... We can eliminate the others 20:44:09 DaveS: If we do 'e', it is a separate frag spec, not the full WS-RT 20:44:15 Bob: Agrees. 20:44:28 ... But its not clear at that point what would remain WS-RT 20:44:40 Asir: We have an issue on this. 20:44:57 Bob: For those people that want to move frag support, what would be left in WS-RT. 20:45:13 Doug: Mulitple frags, metadata on ???, resource lifecycle stuff 20:45:25 DaveS: multiple dialects 20:46:00 Asir: these need to be documented 20:46:09 Doug: They are in the WS-RT spec. 20:46:33 Bob: Trying to find another alternative . . . we've come down to a pretty black and white situation. 20:46:43 ???: looks like it Bob. 20:47:15 Bob: Anyone object to taking this to a decision? 20:47:24 Geoff: What do you mean "a decision"? 20:47:38 Bob: Another poll (binding?) 20:47:51 Asir: I think we can explore other alternatives. 20:47:55 Bob: Do you have one? 20:48:02 Asir: Not off the top of my head. 20:48:05 I'd like to go for a decision. 20:48:16 Jeff: How many months would you like to come up with another alternative? 20:48:35 (Asir & Jeff): {discuss the amount of time spent on this issue} 20:48:49 (Asr & Bob): {discuss the amount of time spent on this issue} 20:48:55 s/Asr/Asir/ 20:49:22 Bob: How much more time are we going to spend looking for an alternative? There don't seem to be any. 20:49:26 Asir: Not right now. 20:49:37 DaveS: There have been a lot of ideas and proposals. 20:49:50 I wonder if the TAG would have an answer for this one 20:49:53 ... Nothing seems to be gaining traction. 20:50:23 Bob: Yves, are you asking for a TAG ruling on this one? 20:50:28 Yves: We can always ask. 20:50:39 We could ask the TAG a specific question .. 20:50:42 Ashok: Is this a technical question or a procedural question? 20:50:44 re teh topic 20:50:53 ... The TAG only does technical questions. 20:51:00 ... What are you going to ask them? 20:51:19 the question would be "where does a fragment definition belong, addressing or actions" 20:51:25 Bob: What I'd like to do at this point is to push this off until the next call. 20:51:38 Yves: that is a good question to ask 20:51:49 ... The problem with the polarization is that the fundamental point revolves around the namespace. 20:51:56 ... There doesn't seem to be any middle ground. 20:52:16 ... We've reduced the issue to a very binary, polarizing choice. 20:52:30 ... I'm going to call around to see if there are any reasonable alternatives. 20:52:57 ... If we don't have what looks like the start of a reasonable alternative, we're just going to have to decide. 20:53:08 RESOLUTION: issue defered until next week 20:53:17 TOPIC: team 6401 20:53:30 Wu: we have a concrete detailed proposal based on Gil's approach 20:53:40 ...: We sent this to Gil and Geoff 20:53:49 ... We are awaiting feedback from Gil 20:53:53 q+ 20:54:06 Bob: When did you send this out? 20:54:10 Wu: Last Monday 20:54:20 ack asir 20:54:39 q+ 20:54:48 q+ 20:55:05 +1 to Ashok. 20:55:13 ack ashok 20:55:15 Asir: Should we use the public mailing list? 20:55:18 Ashok: Yes 20:55:44 Gil: I got Wu's proposal this Monday (5/5/2009) 20:55:58 q- 20:56:08 Wu: Would you like me to send this to the group list? 20:56:10 Bob: Yes 20:56:29 Wu: We'd like to work this out before brining it to the group, but OK. 20:56:50 LOL another easy one 20:56:53 q+ 20:57:20 ack gpi 20:57:20 http://www.w3.org/2002/ws/ra/wiki/Proposals_for_6692 20:58:05 Gil: there are 4 proposals on the Wiki 20:58:19 ... they look like valid candidates 20:58:31 Geoff: I wasn't aware that we were using the Wiki 20:59:11 -Don_Wright 20:59:51 Bob & Gil: {comment on desireable qualities of the Wiki} 21:00:02 Geoff: but some of the pros and cons seem pretty subjective 21:00:08 ... what do you do if you don't agree? 21:00:13 Bob: you can edit them 21:00:29 ... The whole idea was simple to get the list of proposals 21:00:38 Geoff: that's what I thought 21:00:53 ... but they have "pros" and "cons" associated with them 21:01:00 Bob: You can delete them 21:01:09 Doug: or add to them 21:01:34 (all): {discussion about process of using Wiki} 21:01:51 q+ 21:02:03 Bob: I do want to get to a list that we agree is a minimized list of options. 21:03:57 ack asir 21:04:22 Asir said, re 6413 ... if we purge duplicate reps in the poll then the result is (a) is 4 and (e) is 3 21:05:59 -Ashok_Malhotra 21:06:01 -??P8 21:06:07 - +1.571.262.aaee 21:06:09 s/6413/6413 strawpoll/ 21:06:09 -Geoff 21:06:09 -Wu_Chou 21:06:10 -Tom_Rutt 21:06:11 -Doug 21:06:11 -Fred 21:06:12 -Bob_Freund 21:06:13 -Yves 21:06:15 -JeffM 21:06:17 I have made the request to generate http://www.w3.org/2009/05/05-ws-ra-minutes.html Yves 21:06:17 -Gilbert 21:06:18 -Katy 21:06:20 rrsagent, generate minutes 21:06:20 I have made the request to generate http://www.w3.org/2009/05/05-ws-ra-minutes.html Bob 21:06:20 WS_WSRA()3:30PM has ended 21:06:23 Attendees were Bob_Freund, Wu_Chou, Tom_Rutt, [Microsoft], +1.702.414.aaaa, Asir, Doug, +1.408.642.aabb, Ashok_Malhotra, Katy, Gilbert, Yves, +1.646.361.aacc, +1.408.970.aadd, 21:06:26 ... Vikas, Fred, Dave, Don_Wright, JeffM, +1.571.262.aaee 21:06:26 trackbot, end teleconference 21:06:26 Zakim, list attendees 21:06:27 RRSAgent, please draft minutes 21:06:27 I have made the request to generate http://www.w3.org/2009/05/05-ws-ra-minutes.html trackbot 21:06:27 TomRutt has left #ws-ra 21:06:28 sorry, trackbot, I don't know what conference this is 21:06:28 RRSAgent, bye 21:06:28 I see 1 open action item saved in http://www.w3.org/2009/05/05-ws-ra-actions.rdf : 21:06:28 ACTION: Yves to generate may 1st snapshots [1] 21:06:28 recorded in http://www.w3.org/2009/05/05-ws-ra-irc#T19-41-47