14:55:11 RRSAgent has joined #ws-desc 14:55:11 logging to http://www.w3.org/2006/12/14-ws-desc-irc 14:55:21 Zakim has joined #ws-desc 14:55:31 zakim, this will be wsdl 14:55:31 ok, TonyR; I see WS_DescWG(WSDL)10:00AM scheduled to start in 5 minutes 14:58:19 Jonathan has joined #ws-desc 14:58:36 zakim, who's on the phone? 14:58:37 WS_DescWG(WSDL)10:00AM has not yet started, Jonathan 14:58:41 On IRC I see Jonathan, Zakim, RRSAgent, TonyR, chinthaka, sanjiva, charlton 14:58:47 zakim, code? 14:58:49 the conference code is 9735 (tel:+1.617.761.6200), Jonathan 14:58:57 ok 15:01:10 WS_DescWG(WSDL)10:00AM has now started 15:01:17 + +1.617.314.aaaa 15:02:05 Zakim, +1.617.314.aaaa is me 15:02:05 +chinthaka; got it 15:02:23 +??P8 15:02:29 zakim, ?? is me 15:02:29 +TonyR; got it 15:02:54 zakim, who is on the phone? 15:03:02 On the phone I see chinthaka, TonyR 15:03:24 +[IPcaller] 15:03:33 Zakim, IPcaller is Jonathan 15:03:33 +Jonathan; got it 15:06:45 +Canon 15:08:03 +Arthur_Ryman 15:09:08 Arthur has joined #ws-desc 15:10:58 -Jonathan 15:11:32 +Jonathan_Marsh 15:16:03 jjm has joined #ws-desc 15:22:35 ACTION: Jonathan to fix transferCodings - add control group. 15:23:26 youenn has joined #ws-desc 15:36:35 http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/Dashboard.html 15:37:38 jjm has joined #ws-desc 15:48:34 -Jonathan_Marsh 15:48:35 -TonyR 15:48:37 -Canon 15:48:38 -chinthaka 15:50:03 This conference is scheduled to end in 10 minutes; all ports must be freed 15:54:12 zakim, who is on the phone? 15:54:12 On the phone I see Arthur_Ryman 15:55:03 This conference is scheduled to end in 5 minutes; all ports must be freed 15:55:15 zakim, this will be WSDWG 15:55:15 ok, TonyR; I see WS_DescWG()11:00AM scheduled to start in 5 minutes 15:55:33 WS_DescWG()11:00AM has now started 15:55:35 charltonb has joined #ws-desc 15:55:40 +Charlton_Barreto 15:59:51 JacekK has joined #ws-desc 16:00:46 +JacekK 16:00:58 +??P7 16:01:06 zakim, ??p7 is me 16:01:06 +TonyR; got it 16:01:16 zakim, who is on the phone? 16:01:16 On the phone I see Charlton_Barreto, JacekK, TonyR 16:01:17 Allen has joined #ws-desc 16:01:38 +m2 16:02:05 asir has joined #ws-desc 16:02:10 +Allen_Brookes 16:02:26 Roberto has joined #ws-desc 16:02:48 +Jonathan_Marsh 16:02:49 notrahc has joined #ws-desc 16:02:53 +??P39 16:03:04 +Roberto 16:03:39 pauld has joined #ws-desc 16:03:43 Jonathan has joined #ws-desc 16:03:54 +Paul_Downey 16:04:51 zakim, who is here? 16:04:51 On the phone I see Charlton_Barreto, JacekK, TonyR, m2, Allen_Brookes, Jonathan_Marsh, asir, Roberto, Paul_Downey 16:04:54 On IRC I see Jonathan, pauld, charlton1, Roberto, asir, Allen, JacekK, charltonb, jjm, youenn, Arthur, Zakim, RRSAgent, TonyR, chinthaka, sanjiva, charlton 16:04:56 alewis has joined #ws-desc 16:04:57 +Amelia_Lewis 16:07:10 Zakim, who is on the phone? 16:07:10 On the phone I see Charlton_Barreto, JacekK, TonyR, m2, Allen_Brookes, Jonathan_Marsh, asir, Roberto, Paul_Downey, Amelia_Lewis 16:08:25 + +aaaa 16:08:40 Zakim, aaaa is Canon 16:08:40 +Canon; got it 16:08:46 jjm has joined #ws-desc 16:09:11 scribe: JacekK 16:09:20 topic: approval of minutes 16:09:31 minutes: http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/att-0032/20061207-ws 16:09:31 -desc-minutes.html 16:09:39 RESOLUTION: minutes approved 16:09:43 topic: action items 16:10:14 zakim, who's making noise? 16:10:24 JacekK, listening for 10 seconds I heard sound from the following: 11 (95%), Jonathan_Marsh (44%) 16:11:05 Jonathan: we shouldn't spend time on component model interchange document before January 16:11:51 topic: Administrivia 16:12:25 Jonathan: membership of Vivek was corrected in WBS 16:12:50 notrahc has joined #ws-desc 16:13:08 -Allen_Brookes 16:13:15 Jonathan: how many people won't make it next week? 16:13:40 regrets from Asir, JacekK, Roberto? 16:14:28 asir: please move WS-Policy comments to the telcon after next so I don't miss it 16:14:47 Jonathan: we can discuss it some, but let's postpone actualy resolutions 16:15:35 Jonathan: thanks to charlton for submitting policy review, to be discussed next week and later 16:16:20 Jonathan: databinding not yet reviewed, time until Jan 12 16:16:30 topic: MTOM description 16:17:19 Jonathan: is there something we can do now to move this topic ahead? 16:17:52 jjm: probably disregard my latest message 16:18:37 jjm: are we waiting for XMLP WG now? 16:19:23 plh has joined #ws-desc 16:19:24 Jonathan: haven't heard from Philippe in some time 16:19:27 +Plh 16:20:25 Jonathan: two possible approaches - 1) dual-purpose wsdl extension and policy assertion 16:21:21 Jonathan: 2) how would it work with WSDL - direct extension, policy... does it introduce critical dependency on policy? 16:21:59 Jonathan: it would be useful what Canon's high-level requirements are on this 16:22:19 Jonathan: to get a feeling about whether it can be just a policy or something else 16:23:46 jjm: 1) we need MTOM in WSDL soon, would like to have interop 16:23:53 jjm: or a way to upgrade later 16:24:03 jjm: 2) we don't plan to support WS-Policy 16:24:57 asir: do you expect interop with a WSDL extension? 16:25:37 jjm: I don't know what's happening regarding MTOM in Policy 16:26:38 plh: XMLP will work on this as soon as they are allowed to do so, that's should be very soon 16:26:48 charltonb has joined #ws-desc 16:26:57 plh: "this" meaning MTOM assertion 16:27:09 WS-Policy is in the W3C, has widespread support and as we have demonstrated has a simple syntax for applying assertions. What's not to like? 16:28:28 jjm: can we describe MTOM in WSDL using policy without having to support full policy? 16:28:38 q+ 16:29:05 Jonathan: there may be a profile of policy that would satisfy everyone 16:29:23 jjm: many embedded applications don't have resources for support for compositors 16:30:13 plh: simplest policy is - your impl can reject anything more complex 16:31:48 asir: it might be easy to look into the policy to see if mtom is there, then do it 16:31:58 +Paul_Bagshaw 16:32:01 plh: there'd be more complexity, but it could be usefully doable 16:32:21 ack plh 16:33:05 Jonathan: let's move to issues 16:33:34 asir: if we're talking about a profile, would we need to do it formally, with a recharter? 16:33:35 +??P2 16:33:46 zakim, ??P2 is Allen 16:33:46 +Allen; got it 16:33:57 plh: we don't need to document it formally here, maybe Canon could just put it in their docs as a limitation 16:34:24 jjm: I'd prefer a W3 spec to describe this 16:35:05 q+ 16:35:12 Jonathan: the primer showed it using f&p, but it can do the same using policy 16:35:39 Jonathan: with options of showing full policy support, or just a subset for only MTOM 16:36:02 jjm: I was assuming we had a stronger (than primer) support for MTOM 16:36:11 jjm: I discovered later that we didn't, only in the primer 16:36:30 Use of MTOM assertion + WSDL 20 is well described at http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117/#wsdl20-example 16:36:58 ack arthur 16:37:10 Jonathan: so you would like WSDL to add description of MTOM sufficient to guarantee interop? 16:38:13 Arthur: does anything need to be done in policy spec to support this usage with MTOM? 16:38:18 asir: no, I don't think so 16:38:28 Arthur: the primer would be a good place for this then 16:38:37 Jonathan: jjm may not agree, but let's move on for now 16:39:53 plh: we should add an example, but that's all because other groups are specifying it normatively 16:40:03 plh: and we can mention a subset of policy, but not specify it 16:40:44 plh: would a policy with only the MTOM assertion in it solve your problem? 16:40:46 jjm: maybe not 16:41:12 plh: this would not only work for you, it would also work for others who do support policy 16:41:19 Jonathan: jjm should clarify the maybe not 16:42:02 topic: Issue CR098 16:42:04 alewis has changed the topic to: Trust us. We're from the W3C. *puts on sunglasses* 16:43:03 Jonathan: Types-1300002 doesn't seem to be an assertion 16:43:20 Arthur: I agree, we should clean up the sentence and remove assertion mark up 16:43:51 Jonathan reads the poetry suggested by Arthur 16:44:11 RESOLUTION: accept Arthur's proposal 16:44:25 topic: issue CR099 16:44:45 Jonathan: Types-1300003 doesn't seem to be an assertion 16:44:55 Jonathan: similar problem here 16:45:35 Arthur: if a statement is not an assertion, I make it a note and remove uppercase keywords 16:45:46 RESOLUTION: accept Arthur's proposal as well 16:45:59 topic: Issue CR108 16:46:31 Jonathan: two assertions seem (to lawrence) to be duplicate 16:46:42 notrahc has joined #ws-desc 16:46:44 Jonathan reads the spec poetry 16:47:37 Arthur: the two statements are logically equivalent - negating the first gives the second 16:48:07 Arthur: they have the same truth tables 16:48:58 Jonathan: one expresses a dependency, other co-constraint, same intent, first one seems easier to read 16:49:07 Arthur: I'd suggest a symmetrical wording 16:50:01 Jonathan: amy suggests to remove the last assertion 16:50:59 Jonathan: it's not prohibited for a binding op to have an output if the interface op doesn't have it 16:51:16 Jonathan: should MessageLabel-0014 be stricken? 16:51:38 charltonb has joined #ws-desc 16:51:49 alewis: it's not only duplicate, it's unreachable, you violate stuff much earlier trying to get there 16:52:19 alewis: but only one should be removed, it's not an exact duplicate 16:52:24 alewis: that's 0014 16:53:44 alewis: the assertion in 2.10.1 says each binding message reference must uniquely refer to an interface msg ref 16:54:58 gpilz has joined #ws-desc 16:55:14 Arthur: if 0006 and 0014 are equivalent, both should be striken 16:55:34 +Gilbert_Pilz 16:55:42 alewis: they're not equivalent 16:55:50 alewis: 0014 is subsumed by the one in 2.10.1 16:56:33 alewis: we don't even have a test case because we don't have a suitable MEP 16:56:53 q+ 16:57:30 Arthur: they're the same 16:57:34 alewis: they're not 16:57:38 Arthur: are too! 16:57:58 ack roberto 16:57:58 Arthur: let's get this offline and compare our reasoning 16:58:07 Arthur: if they're equivalent, both should be removed 16:58:33 notrahc has joined #ws-desc 16:58:40 Roberto: we can first settle the equivalence, then we can see if we should remove both 16:58:52 alewis: there is the same pattern elsewhere as well 16:59:39 Jonathan: let's give an action to somebody to analyze this 17:00:31 ACTION: Arthur to examine the equivalence of 0006 and 0014 17:00:42 topic: CR109 17:01:46 Jonathan: is the suggestion a good idea? 17:02:24 RESOLUTION: editors will add an assertion that when using SOAP 1.2 the fault code QName is constrained to the five values from the spec 17:02:50 topic: CR110 17:03:12 Jonathan: arthur asks, what does it mean when cookies="true"? 17:04:19 Arthur: it's not good if cookies="true" just means service will send them but client may ignore them 17:04:35 Arthur: it would be better if we mandate something, e.g. that the client accept and support the cookies 17:05:57 Arthur: the property is required but binding says cookies MAY be indicated 17:06:04 Jonathan: let's say "every binding does indicate" 17:06:44 RESOLUTION: first part - we clarify that "true" means the service relies on cookies and client must understand them; second part change MAY indicate to indicates 17:07:13 topic: CR111 17:08:05 Jonathan reads the issue 17:08:37 Jonathan: should robust in-only bind to a specific HTTP code? 17:08:43 charltonb has joined #ws-desc 17:08:48 plh: I'd say 202, empty response 17:08:57 plh: that's what SOAP does 17:09:10 plh: we can do the same thing 17:09:31 youenn: +1 for 202 17:10:35 youenn: and it seems there's potential for other things we're missing 17:11:21 Jonathan: yes, are we sure this MEP is the only one that needs to be specified? 17:13:12 Arthur: should we consider 204 as well? 202 implies async, 204 implies action done, no return 17:13:53 Arthur: does the MEP imply async? 17:15:56 Arthur: 204 should be used for robust MEP, because it guarantees there's no fault coming up 17:16:36 q+ 17:16:52 Jonathan: we have two proposals, 202, and 204 17:16:56 ack plh 17:17:19 plh: 202 for in-only is appropriate, you don't care what happens, 204 gives you more info than you request 17:17:42 Arthur: agree 17:18:13 plh: for robust, it seems it should be 204 17:18:31 youenn: maybe the code is app-dependent? 17:18:45 plh: if you get 202 from robust-in-only, you can't get the fault later if it occurs 17:19:03 notrahc has joined #ws-desc 17:19:57 JacekK: agrees with Arthur, for robust it should be 204 17:20:22 youenn: should we let XMLP know? 17:21:03 Jonathan: it seems we should do 202 for in-only, 204 for robust-in-only 17:21:57 ACTION: plh to check with XMLP whether they should be interested in 204 as well 17:22:19 topic: CR112 17:23:26 Jonathan: we're combining location with address prematurely in the spec 17:24:14 Jonathan: if I don't have an endpoint and only binding (or multiple endpoints), we cannot compute the value of the property 17:24:28 Jonathan: looks editorial 17:25:24 Jonathan: no, looks substantial 17:25:33 TonyR: let's get a proposal from the editors 17:27:48 ACTION: plh to come up with a more detailed proposal for CR112 if possible 17:28:38 topic: CR113 17:30:04 youenn: we're missing properties in SOAP binding for reuse of HTTP binding 17:30:26 Arthur: why did we even allow different query separators? 17:30:34 charltonb has joined #ws-desc 17:30:39 Jonathan: best practice differs from real practice 17:31:14 Jonathan: proposal: import the query separator properties to the SOAP binding as well 17:31:20 +1 17:31:48 RESOLUTION: import the query separator and query separator default properties to the SOAP binding 17:32:11 -Paul_Downey 17:32:13 -m2 17:32:13 -Roberto 17:32:14 alewis has left #ws-desc 17:32:15 -Allen 17:32:16 -Paul_Bagshaw 17:32:18 -Gilbert_Pilz 17:32:19 -Jonathan_Marsh 17:32:20 rrsagent, set log world 17:32:20 -asir 17:32:22 -Canon 17:32:24 -JacekK 17:32:25 rrsagent, draft minutes 17:32:25 I have made the request to generate http://www.w3.org/2006/12/14-ws-desc-minutes.html Jonathan 17:32:26 -Plh 17:32:27 TonyR has left #ws-desc 17:32:28 -TonyR 17:32:30 -Amelia_Lewis 17:32:32 -Charlton_Barreto 17:32:34 WS_DescWG()11:00AM has ended 17:32:36 Attendees were Charlton_Barreto, JacekK, TonyR, m2, Allen_Brookes, Jonathan_Marsh, asir, Roberto, Paul_Downey, Amelia_Lewis, +aaaa, Canon, Plh, Paul_Bagshaw, Allen, Gilbert_Pilz 17:44:46 notrahc has joined #ws-desc 18:28:01 sanjiva_ has joined #ws-desc 19:07:59 Jonathan has joined #ws-desc 19:08:25 Meeting: WS Description WG telcon 19:08:28 Chair: Jonathan 19:08:38 RRSAgent, draft minutes 19:08:38 I have made the request to generate http://www.w3.org/2006/12/14-ws-desc-minutes.html Jonathan 19:34:42 Zakim has left #ws-desc