15:26:29 RRSAgent has joined #ws-desc 15:26:29 logging to http://www.w3.org/2007/01/25-ws-desc-irc 15:47:51 Meeting: WS Description WG telcon 15:47:56 Chair: Jonathan 15:52:14 Marsh has joined #ws-desc 15:52:26 Zakim, this will be WS_Desc 15:52:26 "WS_Desc" matches WS_DescWG()11:00AM, and WS_DescWG(WSDL)10:00AM, Marsh 15:52:34 Zakim, this will be WS_DescWG() 15:52:34 ok, Marsh; I see WS_DescWG()11:00AM scheduled to start in 8 minutes 15:54:55 Tony, you there? 15:57:37 RRSAgent, set log world 15:58:29 Allen1 has joined #ws-desc 15:59:08 WS_DescWG()11:00AM has now started 15:59:10 +alewis 15:59:15 I'm worried about the reliability of my internet, and skype connection. 15:59:30 If I disappear abruptly, please keep things swimming along ! 15:59:46 +??P16 15:59:47 -??P16 15:59:47 +??P16 15:59:57 zakim, ??p16 is me 15:59:57 +TonyR; got it 16:00:01 +??P22 16:00:06 alewis has joined #ws-desc 16:00:19 +Roland_Merrick 16:00:51 zakim, code? 16:00:51 the conference code is 97394 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), Marsh 16:01:14 +[IPcaller] 16:01:25 Roland Merrick is actually John Kaputin (Apache Woden/IBM) standing in for Arthur Ryman 16:01:27 Zakim, [IPcaller] is me 16:01:27 +Marsh; got it 16:01:49 heh. i thought roland was slumming. :-) 16:02:13 +Allen_Brookes 16:02:46 Zakim, ?P22 is charlton 16:02:46 sorry, Marsh, I do not recognize a party named '?P22' 16:02:50 Zakim, ??P22 is charlton 16:02:50 +charlton; got it 16:03:06 +m2 16:03:11 Roberto has joined #ws-desc 16:03:12 +Gilbert_Pilz 16:03:52 +Roberto_Chinnici 16:04:05 c 16:04:31 zakim, who's making noise? 16:04:44 Marsh, listening for 10 seconds I heard sound from the following: Marsh (67%), alewis (75%), TonyR (32%) 16:04:44 gpilz has joined #ws-desc 16:04:56 zakim, mute alewis 16:04:57 alewis should now be muted 16:05:19 zakim, unmute alewis 16:05:20 charlton has joined #ws-desc 16:05:22 alewis should no longer be muted 16:05:33 zakim, who is on the call? 16:05:35 On the phone I see alewis, TonyR, charlton, Roland_Merrick, Marsh, Allen_Brookes, m2, Gilbert_Pilz, Roberto 16:05:47 zakim, mute alewis 16:05:49 alewis should now be muted 16:05:58 monica has joined #ws-desc 16:06:50 scribe: tonyr 16:07:18 topic: minutes approval 16:07:38 minutes approved without dissent 16:07:55 topic: administrivia 16:08:21 +[Canon] 16:09:38 WS-Policy responses have been accepted and applied to their spec; Charlton tracking 16:09:41 +??P19 16:09:45 jjm has joined #ws-desc 16:10:05 asir has joined #ws-desc 16:10:33 Zakim, ??P19 is Asir? 16:10:33 +Asir?; got it 16:10:57 i haven't seen anything, as i recall. 16:11:36 q+ to ask a question? 16:11:43 +??P20 16:11:52 ack asir 16:11:52 asir, you wanted to ask a question? 16:12:01 -alewis 16:12:11 -Allen_Brookes 16:12:17 grr. what happened? 16:12:38 pauld has joined #ws-desc 16:12:57 zakim, ??P20 is probably me 16:12:57 +pauld?; got it 16:13:51 topic: MTOM description 16:13:57 +alewis 16:14:09 draft of charter for the XML-P group, including MTOM 16:15:02 Jonathan: suggest we forward Jean-Jacques' comments on the XML-P charter to the CG and the authors of the charter 16:15:11 JacekK has joined #ws-desc 16:15:48 JJM: pleased that the charter is happening, but would be happier if it were more detailed 16:16:02 +JacekK 16:16:50 Jonathan: any specifics? 16:18:47 Jonathan: will forward JJM's comments, but want to know if the WG has any other specific recommendations to the authors 16:19:05 Here is the link http://www.w3.org/Submission/2006/SUBM-WS-MTOMPolicy-20061101/ 16:19:09 also had a challenge when looking at the charter 16:19:27 thanks asir 16:19:43 http://www.w3.org/2007/01/XML-Protocol-Charter.html 16:19:44 jjm: could not reach the submission by clicking on the link in the charter - permissions issue 16:20:06 am wondering why such specific comments cannot be handled through Canon AC representative 16:20:07 ACTION: Jonathan to forward comments to the author of the MTOM charter 16:20:49 ACTION: Jean-Jacques to develop more concrete suggestions for expansion of the charter for the XML-P group 16:22:35 thank you for the clarification 16:22:35 topic: CR112 16:22:48 waiting on input from Philippe - skipping 16:22:53 topic: CR145 16:23:17 Jonathan: we agreed that the status quo is clear 16:24:10 Jonathan: perhaps current model is unclear, and we could remove those items that are not referred to by any WSDL component 16:24:36 Roberto: not sure that the status quo says what you said it does 16:25:11 JohnK: I agree - not certain that the spec says clearly what is included 16:25:33 zakim, who's making noise? 16:25:44 Marsh, listening for 10 seconds I could not identify any sounds 16:25:44 Roberto: argument detailed in e-mail is that we should only include in the component model those items which are referenceable 16:26:28 zakim, who's making noise? 16:26:39 Marsh, listening for 10 seconds I could not identify any sounds 16:27:15 Roberto: those elements which are inported by things which are imported cannot be referenced unless also directly imported; only those items which are directly imported should be included 16:28:08 JohnK: agreed - only those items which can be referenced should be included in the component model 16:28:56 +??P25 16:29:17 zakim, ??P25 is Allen 16:29:17 +Allen; got it 16:30:06 JohnK: Arthur had some concerns about referencability. Once we reach the component model we lose the understanding of which elements are referenceable because referenceability is a property of the document 16:31:03 Roberto: not sure that I agree. Yes, referenceability is a feature of the document, but if we follow the procedure I outline we will get a suitable set of components 16:31:51 JohnK: inclined to agree. Including everything clutters the component model with components which are not used because they were not able to be referenced 16:32:17 JohnK: prefer Roberto's proposal 16:33:00 Jonathan: like Roberto's proposal, too - it reinforces the idea of import; produces a nicer "mental model" 16:33:27 JohnK: we haven't covered the likely use cases - Arthur could address that if he were here 16:34:06 ... we may need to revisit this if Arthur has additional use cases 16:34:20 Jonathan: are we clear on the wording we require in the spec? 16:35:10 ACTION: Roberto to suggest more concrete wording for the spec for CR145 16:35:40 Look at sections 3.1.3 and the Desc Comp section 2.1.1 16:35:42 JohnK: section 3.1.3 and Description Component section in Part 1 16:36:03 topic: CR117 16:36:32 Jonathan 16:37:29 Jonathan: this is about encoding the data included in a URI - what rules we should follow in determining which parts of the data are URL-encoded? 16:37:29 youenn_ has joined #ws-desc 16:37:48 Jonathan: we had two proposals: 16:38:19 ... 1. augment the template syntax to indicate which parameters should be / should not be encoded 16:40:10 ... 2. always encode all parameters, ensuring everything is always reversible 16:40:37 q+ 16:40:59 ... in this case we'd ensure that all parameters must be separated by an unescaped character not in the set of unescaped characters 16:41:05 ack jacek 16:41:09 q+ 16:41:42 Jacek: you are talking about reconstructing the query from the URL - has this ever been an objective of the spec? 16:42:03 Jonathan: no, but our implementations have been requiring this ability 16:42:34 ack roberto 16:42:42 Youenn: yes, it makes sense to be able to reconstruct 16:43:35 Roberto: I like the idea of the different templating syntax. That would be a good solution, using two different serialisation "modes" 16:44:09 ... on the other hand, I don't like the other proposal - to insist on unique deserialisation 16:44:23 q+ 16:44:26 Youenn: I think it's just a warning, not an error 16:45:20 Jonathan: the raw vs encoded proposal doesn't solve the real problem, which is the unique deserialisation 16:45:22 ack jacek 16:45:52 Jacek: I don't like the idea of adding a new feature at this time, which would require returning to LC again. 16:46:37 ... perhaps we should add an XML simple type which disallows the set of characters which cause problems 16:47:10 Jonathan: can we create a simple type to do this? Right now we'd need a BNF 16:47:54 Youenn: the writer of the binding may not be the writer of the interface 16:48:04 Jacek: don't we already have this problem? 16:48:24 ... wouldn't mind that all that much - already constrained 16:50:20 Jonathan: Jacek's proposal is that we add descriptive text about problems in some operations due to ambiguity from including certain characters in parameters, and provide a simple type to avoid these ambiguities 16:51:07 ... This would not avoid the problem of reversability - will not be able to reconstruct the original query 16:51:23 Youenn: the server may not be able to understand the message 16:51:41 Jacek: The server will break? I can't see the problem here 16:52:39 Jonathan: unless you constrain the data in the URL, the server may be "confused" 16:53:26 Jacek: we have the problem already in other places - a "first name" field that could be "any string" could be sent a 5Mb string, which could cause problems with most servers 16:54:14 Youenn: perhaps we could insist that uncited parameters which go into the query string be encoded; cited parameters would not be encoded 16:54:25 Jonathan: how does that solve the problem? 16:54:56 Jacek: the uncited parameters would not be able to mess up the cited parameters 16:55:30 zakim, who is making noise? 16:55:41 pauld, listening for 10 seconds I heard sound from the following: Marsh (70%), TonyR (19%) 16:56:40 pauld has joined #ws-desc 16:56:46 Jonathan: sounds like my second proposal is DOA (mandatory encoding + ban ambiguity) 16:57:42 -Marsh 16:57:59 Jonathan: could adopt my first proposal, or Youenn's proposal 16:58:43 chad has joined #ws-desc 16:59:35 Jonathan has joined #ws-desc 16:59:39 chad, question: CR117 17:01:31 +??P0 17:01:48 -Roland_Merrick 17:02:00 -??P0 17:02:09 -pauld? 17:02:54 pauld has joined #ws-desc 17:03:20 chad, question? 17:03:26 chad, options? 17:03:51 vote: 4, 3, 5, 2 17:03:55 vote: 4, 2, 0 17:04:21 vote: 4, 0, 5, 2, 3 17:04:33 vote: 4, 5, 2, 3 17:04:34 vote: 5, 1, 2, 3, 4 17:04:38 vote: 4, 0 17:04:40 vote: 1, 4, 0, 5, 3, 2 17:04:41 vote: 4, 5, 3, 2 17:04:59 1,4,no others 17:05:11 vote: 3, 5, 2 17:05:14 vote: monica: 1, 4 17:05:15 vote: 5, 1, 2, 3, 4 17:05:37 chad, count 17:05:37 Question: CR117 17:05:37 Option 0: status quo (0) 17:05:37 Option 1: jonathat's 1st - new syntax for controlling whether or not to encode (2) 17:05:37 Option 2: youenn - cited parameters raw, uncited encoded (0) 17:05:37 Option 3: jonathat's 2nd - everything encoded, ambiguity forbidden (1) 17:05:38 Option 4: jacek's - all is raw, we warn people, give them guidance and maybe a restrictive simple type (6) 17:05:41 Option 5: everything encoded (2) 17:05:43 11 voters: alewis (4,3,5,2),Allen1 (4,0),charlton (4,5,2,3),gpilz (4,5,3,2),JacekK (4,2,0),jjm (5,1,2,3,4),Jonathan (3,5,2),monica (1,4),Roberto (1,4,0,5,3,2),TonyR (4,0,5,2,3),youenn (5,1,2,3,4) 17:05:46 Round 1: Count of first place rankings. 17:05:48 Candidate 4 is elected. 17:05:50 Winner is option 4 - jacek's - all is raw, we warn people, give them guidance and maybe a restrictive simple type 17:06:45 Straw poll indicates a strong preference for Jacek's proposal 17:06:49 need to play lotto 17:07:06 $240 millon in oregon 17:09:17 youenn: dislike this proposal. Might be better to support the use cases we know; don't want to block future use cases 17:09:46 Jacek: can the use cases that this proposal blocks be addressed in the application? 17:10:06 ... application can be built to use encoding where needed 17:11:09 Jacek: adding path segments is a use case which would be blocked by encoding everything 17:11:20 +[IPcaller] 17:11:44 -[IPcaller] 17:12:05 zakim, who is making noise? 17:12:17 charlton, listening for 11 seconds I heard sound from the following: TonyR (26%), [Canon] (21%) 17:12:22 RRSAgent, where am I? 17:12:22 See http://www.w3.org/2007/01/25-ws-desc-irc#T17-12-22 17:12:50 chad, clean 17:12:55 Jacek: using Youenn's proposal would still allow us to warn people of the consequences 17:12:59 chad, reset 17:12:59 new poll 17:13:06 chad, question: CR117 17:15:10 Jonathan has left #ws-desc 17:15:14 Jonathan has joined #ws-desc 17:18:27 I prefer option 1, having authors explicitly choose between raw and encoded, over option 2 17:20:00 Are there any concrete proposals written down for any of these options? 17:20:03 Tony: concerned about security issues with RAW parameters 17:20:54 Jacek: have the same issues without WSDL - a user can enter a URL without using the WSDL, so there's no security hole (that wasn't already present) 17:21:19 ... might avoid bugs / undocumented features by encoding, but nothing more 17:22:23 Youenn: would prefer to offer a choice of RAW/encoded 17:22:52 Jacek: we have a default - the status quo is that we leave everything RAW 17:23:09 Youenn: not sure that the default was thought through 17:23:31 Jacek: we are in CR - reluctant to change things at this point 17:24:06 ... we can provide advice, and offer a simple type to avoid issues 17:24:46 Youenn: but there are values which won't be valid according to the simple type - some book titles won't be accepted 17:24:47 Jonathan has joined #ws-desc 17:25:07 RRSAgent, where am I? 17:25:07 See http://www.w3.org/2007/01/25-ws-desc-irc#T17-25-07 17:25:16 Jacek: if we want to put things into a URI, you have to encode them 17:26:14 +[IPcaller] 17:29:54 Youenn: cannot automate the reconstruction of the query from the URL 17:31:31 Jacek: wonder what the web people would say about this - if we are constructing a URI, we are addressing a resource, and the resource should "know what to do" 17:32:56 Jonathan: there are fiddly bits in the HTTP binding. if we don't do any encoding, then there are more restrictions on the data we can use 17:33:22 if there are two classes of users with two different use cases, it makes sense to have two template syntaxes, i.e. option 1 17:34:07 Jonathan: guess we'll have to return this one to the mailing list. Please describe the positions clearly 17:34:12 -Allen 17:34:13 -alewis 17:34:17 -JacekK 17:34:24 Thanks Tony! 17:34:24 -Roberto 17:34:30 RRSAgent, draft minutes 17:34:30 I have made the request to generate http://www.w3.org/2007/01/25-ws-desc-minutes.html Jonathan 17:34:31 -Gilbert_Pilz 17:34:33 -TonyR 17:34:33 -m2 17:34:36 -charlton 17:34:37 -[IPcaller] 17:34:38 TonyR has left #ws-desc 17:34:45 -[Canon] 17:37:05 chad, bye 17:37:05 chad has left #ws-desc 17:39:45 disconnecting the lone participant, Asir?, in WS_DescWG()11:00AM 17:39:48 WS_DescWG()11:00AM has ended 17:39:49 Attendees were alewis, TonyR, Roland_Merrick, Marsh, Allen_Brookes, charlton, m2, Gilbert_Pilz, Roberto, [Canon], Asir?, pauld?, JacekK, Allen, [IPcaller] 17:40:01 alewis has left #ws-desc 19:34:20 Zakim has left #ws-desc