19:26:51 RRSAgent has joined #ws-ra 19:26:51 logging to http://www.w3.org/2009/04/14-ws-ra-irc 19:26:53 RRSAgent, make logs public 19:26:53 Zakim has joined #ws-ra 19:26:55 Zakim, this will be WSRA 19:26:55 ok, trackbot; I see WS_WSRA()3:30PM scheduled to start in 4 minutes 19:26:56 Meeting: Web Services Resource Access Working Group Teleconference 19:26:56 Date: 14 April 2009 19:27:16 WS_WSRA()3:30PM has now started 19:27:24 + +20756aaaa 19:27:36 - +20756aaaa 19:27:37 WS_WSRA()3:30PM has ended 19:27:37 Attendees were +20756aaaa 19:27:39 WS_WSRA()3:30PM has now started 19:27:44 Geoff has joined #ws-ra 19:27:44 + +1.919.349.aaaa 19:28:03 +Mark_Little 19:28:36 +[Microsoft] 19:28:54 +Bob_Freund 19:29:26 TRutt has joined #ws-ra 19:29:31 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Apr/0084.html 19:29:42 + +1.408.970.aabb 19:30:48 Sumeet has joined #ws-ra 19:30:52 asir has joined #ws-ra 19:31:14 + +1.703.860.aacc 19:31:20 +JeffM 19:31:30 +Tom_Rutt 19:31:46 + +0759029aadd 19:31:57 + +1.408.642.aaee 19:32:08 Ashok has joined #ws-ra 19:32:14 + +25669aaff 19:32:29 zakim, aaff is katy 19:32:29 +katy; got it 19:32:30 +Wu_Chou 19:32:45 Katy has joined #ws-ra 19:33:05 +Ashok_Malhotra 19:33:10 gpilz has joined #ws-ra 19:33:21 DaveS has joined #ws-ra 19:33:33 dave S here 19:33:44 +Yves 19:35:47 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Apr/0084.html 19:37:24 scribenick: li 19:37:47
  • TOPIC: approval of agenda 19:38:27 do the dogs get a vote ;-) ? 19:38:41 rofl 19:39:15
  • no objection to agenda 19:39:28
  • TOPIC: approval of minutes 19:39:55
  • no objection to minutes 19:40:27
  • bob: no new issues at this point 19:41:34
  • bob: please review fpwd of 5 specs in 1 week and publish comments to mailing list 19:42:38
  • TOPIC: discuss use of wiki for proposal refinement and primers 19:43:02
  • TOPIC: making progress 19:44:13
  • bob: this group is contentious and not moving toward concensus 19:44:54
  • bob: hope to work in more friendly fashion 19:45:17
  • TOPIC: issues & proposals 19:45:59
  • geoff: ok with ram's proposal 19:46:03 http://www.w3.org/Bugs/Public/show_bug.cgi?id=6730 19:46:18 Topic: 6730 19:47:08
  • 6730 accepted with no objection 19:47:54
  • TOPIC: 6594 19:48:00 q+ 19:48:10 http://www.w3.org/Bugs/Public/show_bug.cgi?id=6594 19:48:48 ack geoff 19:49:13
  • geoff: 6594 and others are joined together 19:49:43 ai: Geoff to prepare new proposals for 6594, 6672, and 6673 19:50:08 ACTION: Geoff to prepare new proposals for 6594, 6672, and 6673 19:50:08 Created ACTION-57 - Prepare new proposals for 6594, 6672, and 6673 [on Geoff Bullen - due 2009-04-21]. 19:50:36
  • dug: 6594 are related to others 19:50:49 last AI is due before next call 19:51:02 q+ 19:51:14
  • dug: 6594, 6672, and 6673 are somewhat different 19:51:32 q+ 19:51:45 ack asir 19:51:45 q- 19:51:58 ack dave 19:52:24
  • daves: 6594 3rd comment links three proposal already 19:53:29
  • daves: dug already finish them 19:53:36 email at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0088.html 19:54:20 q? 19:55:22
  • geoff: looked the joint proposal and to provide more comments by next week 19:57:07
  • TOPIC: http://www.w3.org/Bugs/Public/show_bug.cgi?id=6413 19:58:13
  • geoff: raised issues and katy responded them, need to look them 19:59:11
  • geoff: request clarifications from katy 19:59:43
  • katy: explain the reponses 20:01:49
  • katy: merge part of rt into t (only fragment feature) 20:02:49
  • AI: bob to retitle the proposal to "move fragment from rt to t" 20:02:55 q+ 20:03:20 ack wu 20:03:25
  • wu: like to see the concrete proposal 20:04:17 q+ 20:04:18
  • katy: the proposal is already available from the issue 20:04:19 fragments in T seems to not be the ideal place. (like URI fragments are not in HTTP) 20:04:45 q+ 20:04:57 ack geoff 20:06:32
  • geoff: is this merge confusion? we need to discuss this decision: why only part of it instead of all? 20:06:52 ack dave 20:07:44 gpilz has joined #ws-ra 20:07:46 - +1.408.642.aaee 20:08:09
  • daves: basic fragment vs. complex fragment, take basic fragment into T, which is clear 20:08:15 + +1.408.642.aagg 20:08:40
  • bob: difference between ws-rt fragment and ws-man fragment 20:09:22
  • daves: not sure, but think ws-rt fragment addresses ws-man requirement 20:09:46
  • and grid community as well 20:10:01 q+ 20:10:27
  • dug: too much to move all rt into t, take a phase based approach 20:10:58 ack geoff 20:11:04
  • dug: only frag id in difference places 20:11:33 q+ 20:11:34 how about creating a ws-frag spec? (if you want to extract it from RT) 20:12:03
  • geoff: still not sure if the use cases can be solved separately by two specs, instead of using the merged one 20:12:29 ack katy 20:12:37
  • geoff: use cases can't be solved by rt alone? 20:12:49 q+ 20:13:35
  • katy: single spec (merged) will cover all cases, except a few, which can be addressed by extending merge t 20:14:49 that would be fine by us 20:15:09
  • yves: separating fragment is more reusable for ws-man and grid 20:15:38
  • katy: fragment is not in the core of t, but in a appendix 20:16:02 q+ 20:16:13 ack geoff 20:16:24
  • daves: fragment is separated in the appendix 20:16:51
  • geoff: don't think appendix is a good idea 20:17:48
  • geoff: many usages of t don't need fragment, 80% don't need, 20% may need it 20:17:49 ack wu 20:18:50
  • wu: yves's idea is good, making it its own standard is more valuable than appendix 20:19:46
  • dug: if fragment not in t, it may result ad-hoc solution 20:20:08 too much noise on the line 20:21:28
  • jeffM: our goal is not just to make ws-man work, but to make ws-* work 20:22:08
  • jeffM: we need to make decision on our goal 20:22:48 q+ 20:23:00
  • jeffM: packaging is not that important, but operations are 20:23:29 fragment is relative to a resource, so it fits better alog the EPR definition, but editing ws-addr-core is close to impossible now, otherwise I agree that the content is what matters 20:23:30 ack geo 20:23:59 q+ 20:24:12 q+ 20:24:16
  • geoff: basic functions in base class, more functions in subclass, not sure why changing this design decision 20:24:30 q- 20:24:50 ack dave 20:25:41
  • daves: merging frag into t is to eliminate ad-hoc solutions to frag with t 20:26:38
  • daves: don't want ws-man to redo frag with t 20:26:43 dave's thought is worth investigation... 20:26:44 +1 to daves 20:26:54 +1 Dave 20:27:13
  • dug: frag in t is optional, what is the pain? 20:28:15
  • geoff: it's not completely optional, force people to reprofile ws-t in light of frag merge 20:28:25 Doug - your phone is noisy 20:29:09
  • dug: we can make sure it's completely optional, people has to change ws-t anyway 20:29:40
  • geoff: changing namespace does not justify greater changes 20:30:17 - +1.919.349.aaaa 20:30:23 q+ 20:30:42 + +1.919.349.aahh 20:31:04 There are such examples in W3C 20:31:11 For instance SOAP Part 1 and Part 2 20:31:21
  • bob: daves' proposal is to make ws-t optional but normative 20:31:22 Part 1 carries an ad for Part 2 20:32:18
  • bob: any objection to daves' direction? 20:32:20 ack Ashok 20:33:09 q+ 20:34:15 ack wu 20:34:18 q+ 20:34:22
  • ashok: puting in appendix is better to avoid confusion 20:34:33 q+ 20:34:49
  • wu: 3 specs or 2 specs 20:35:05
  • bob: current proposal is 3 20:35:35
  • dug: changes to ws-t is necessary, like to see mroe detail 20:35:49 ack asir 20:36:51 My phone keeps breaking up - I need to drop off an re-dial 20:36:52
  • asir: frag in a separate doc means all about frag in one doc, not just appendix 20:36:57 -katy 20:37:43 +??P10 20:37:50
  • asir: advertisement is ok but how to formulate the normative language 20:38:00 We are okay with the precedents set by SOAP, WSDL and WS-A 20:38:02 q+ 20:38:11 q+ 20:38:33
  • daves: ws-security may help us with the normative languages 20:39:00 Sorry - my phone breaking up again 20:39:06 will try to fix 20:39:21 q+ 20:39:36
  • wu: if we can ask other standards using ws-t to make this connection, instead of link frag to ws-t 20:39:38 ack wu 20:39:45 ack dave 20:39:55 - +1.703.860.aacc 20:40:09 q+ 20:40:36 -??P10 20:40:43
  • daves: ws-man using ws-t may not aware frag if frag not in the appendix 20:41:02 ack wu 20:41:19 asir2 has joined #ws-ra 20:41:30 how can we tell WSMAN what do do? 20:41:39 +1 20:41:42 q+ 20:41:46 Gil - are you a member of WS-Man WG? 20:41:52 yes I am 20:41:55
  • wu: ws-man can specify requirement for ws-t and frag 20:41:58 + +962.8.6.aaii 20:42:07 Gil .. you are a powerful voice! 20:42:21
  • wu: we should let users to decide which to use 20:42:48 asir has joined #ws-ra 20:42:49 asir: loud doesn't help 20:42:51 q+ 20:42:52
  • daves: worry ws-man may choose other way, creating problems 20:43:15 ack katy 20:43:34 q+ 20:44:08 ack bob 20:44:13
  • katy: separate specs looses the context of frag spec, we need to make contexts for both ws-t and frag clear 20:45:03 +1 to Bob 20:45:04
  • bob: ws-addressing is a model we can use 20:45:57 q+ 20:45:59
  • dug: having free choices is not good for ws-* 20:46:31
  • dug: we need to restrict composition choices 20:46:32 ack asir 20:46:36 q- 20:47:05
  • asir: ws-addressing and soap 1.2 are good models for multiple documents of one spec 20:47:52
  • asir: ws-ra can influence ws-man with good values 20:47:59 ack gpi 20:48:05
  • asir: we should respect other bodies choice 20:48:53
  • gil: ws-man may use ws-ra, but the schedule is up in the air 20:49:08 q+ 20:49:24 q- 20:49:50 ack yves 20:49:56
  • gil: ws-man is just one case that may invent its own frag 20:50:57
  • yves: ws-t is related to frag, we need to make requirement of frag clearer 20:51:39
  • bob: more time to decide direction? 20:51:53 q+ 20:52:11 s/ws-t is related to frag/thers is a link from frag to ws-t, not the opposite/ 20:52:24 +1 to doug 20:52:26 ack asir 20:52:54 let's look at the changes to WS-T as stand-alone changes 20:53:00
  • dug: taking stepwise change to ws-t leading to merge 20:53:26 +q 20:53:50
  • asir: refine requirements for frag 20:53:56 ack katy 20:55:18
  • katy: puting appendix on hold, but do changes on the core ws-t, is asir ok with this? 20:55:42
  • asir: we have issues on those changes too 20:56:28
  • katy: is it ok to incorporate dialect support, for example? 20:57:00
  • geoff: why dialect attribute is required? 20:57:23
  • katy: it provides a simple extension point to add frag and others 20:57:33 q+ 20:58:02
  • dug: 6712 show dialect is more than ext point 20:58:17 ack asir 20:58:34
  • asir: ambiguity can be resolved without 6712 20:58:59
  • dug: element under is ambiguous 20:59:28
  • asir: one->data, more->any particle 20:59:43 and zero->null 21:00:07 s/any particle/data, any particle/ 21:00:24
  • bob: volunteers to discuss frag issue in wiki 21:00:42
  • geoff and katy volunteered 21:01:06 -Tom_Rutt 21:01:08 -Mark_Little 21:01:10 -JeffM 21:01:15 -Wu_Chou 21:01:17 -Ashok_Malhotra 21:01:19 -[Microsoft] 21:01:19 - +0759029aadd 21:01:21 - +1.408.970.aabb 21:01:21 I have made the request to generate http://www.w3.org/2009/04/14-ws-ra-minutes.html Yves 21:01:25 -Yves 21:01:28 - +1.408.642.aagg 21:01:30
  • bye 21:01:30 -Bob_Freund 21:01:50 Li, thanks for scribing 21:02:02 rrsagent, generate minutes 21:02:02 I have made the request to generate http://www.w3.org/2009/04/14-ws-ra-minutes.html Bob 21:02:03 - +962.8.6.aaii 21:02:05 - +1.919.349.aahh 21:02:06 WS_WSRA()3:30PM has ended 21:02:07 Attendees were +1.919.349.aaaa, Mark_Little, [Microsoft], Bob_Freund, +1.408.970.aabb, +1.703.860.aacc, JeffM, Tom_Rutt, +0759029aadd, +1.408.642.aaee, +25669aaff, katy, Wu_Chou, 21:02:10 ... Ashok_Malhotra, Yves, +1.408.642.aagg, +1.919.349.aahh, +962.8.6.aaii 21:03:18 I have made the request to generate http://www.w3.org/2009/04/14-ws-ra-minutes.html Yves 22:05:20 gpilz has left #ws-ra 22:54:48 asir has joined #ws-ra