14:51:00 RRSAgent has joined #xproc 14:51:00 logging to http://www.w3.org/2008/06/05-xproc-irc 14:51:02 Meeting: XML Processing Model WG 14:51:02 Date: 5 June 2008 14:51:02 Agenda: http://www.w3.org/XML/XProc/2008/06/05-agenda 14:51:02 Meeting: 114 14:51:02 Chair: Norm 14:51:03 Scribe: Norm 14:51:07 ScribeNick: Norm 14:56:45 ruilopes has joined #xproc 14:57:35 Vojtech has joined #xproc 14:58:27 Zakim, this will be xproc 14:58:27 ok, Norm; I see XML_PMWG()11:00AM scheduled to start in 2 minutes 14:58:33 XML_PMWG()11:00AM has now started 14:58:38 +Vojtech 14:58:40 +Norm 15:00:14 Regrets: Paul 15:02:56 AndrewF has joined #xproc 15:03:36 +??P36 15:03:42 zakim, ? is Andrew 15:03:42 +Andrew; got it 15:05:03 ruilopes has joined #xproc 15:05:41 + +1.857.362.aaaa 15:06:01 Zakim, aaa is ruilopes 15:06:01 sorry, Norm, I do not recognize a party named 'aaa' 15:06:05 Zakim, aaaa is ruilopes 15:06:05 +ruilopes; got it 15:06:21 zakim, please call ht-781 15:06:21 ok, ht; the call is being made 15:06:23 +Ht 15:06:56 Zakim, who's on the phone? 15:06:56 On the phone I see Norm, Vojtech, Andrew, ruilopes, Ht 15:07:34 Present: Norm, Vojtech, Andrew, Rui, Henry, Richard 15:07:45 Topic: Accept this agenda? 15:07:45 -> http://www.w3.org/XML/XProc/2008/06/05-agenda 15:07:57 Accepted. 15:08:02 Topic: Accept minutes from the previous meeting? 15:08:02 -> http://www.w3.org/XML/XProc/2008/05/29-minutes 15:08:11 Accepted. 15:08:14 richard has joined #xproc 15:08:23 Topic: Next meeting: 12 June 2008 15:08:38 +??P15 15:08:41 zakim, ? is me 15:08:41 +richard; got it 15:08:44 Norm gives likely regrets 15:09:02 Henry to chair if Norm sends an agenda in time 15:09:26 Rui gives regrets for 12 June 15:09:35 Andrew gives regrets for 12, 19 June 15:10:16 Topic: Kind of node matched 15:10:28 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2008May/0035.html 15:11:02 Norm: I think the thrust here is that we should be more explicit in all our steps 15:11:25 Henry: If it is the case that there's a majority case, then we could document that and only document exceptions 15:12:38 ACTION: Norm to incorporate the suggestion to clarify the types of nodes matched by the steps into the next draft 15:14:33 Some discussion of (public-)xproc-dev@w3.org list; action on Henry ongoing 15:15:27 Vojtech: We should align error codes for matched nodes of the wrong type. 15:15:40 Norm: So a single error code for "you got the node type wrong"? 15:15:53 Vojtech: Or one for each kind of error. 15:16:40 Norm: I think that's a good idea. 15:17:22 Henry: We could have errors for text-node-not-allowed, element-node-not-allowed, etc. 15:17:32 Norm: Ok, I agree that's more informative. 15:18:19 Proposal: Replace random dynamic errors for this case with a set of five, one for each node type. 15:18:34 Accepted. 15:18:53 ACTION: Norm to replace the random dynamic errors with the five so agreed 15:19:03 Topic: p:pack 15:19:56 Wait until Mohamed is present, 15:20:00 s/present,/present./ 15:20:09 Topic: pfx:atomic-step 15:20:53 Vojech: I think it's about the same prefix that we're using for built-in steps and extension steps. 15:21:36 MoZ has joined #xproc 15:21:46 Norm: Right. I'll fix that. 15:22:18 ACTION: Norm to fix the patterns so that they don't have the same prefix in 4.7 and 4.8 15:22:32 MoZ, is that what you wanted for the pfx:atomic-step comment? 15:22:49 Topic: Questions about p:http-request 15:23:22 Vojtech: A couple of points; first, one of the examples is still using c:http-request/c:http-request. 15:23:25 Norm: Ok, that's a bug. 15:24:20 Norm, sorry I just joined so I don't have access to IRC history, I'll take a look to the minutes after the telcon 15:24:25 Vojtech: In Section 7.1.9.3 there's an attribute @detailed which if it's set to false, it's not clear what the step should generate. 15:25:42 Vojtech: I think that if detailed=false, the c:response is not generated. 15:25:47 ACTION: Alex to investigate 15:27:13 Vojtech: And then there's the question of what to do if the response is a multipart response where there are nested multiparts. 15:27:51 Norm: It's not immediately clear that that makes sense for us, but we should investigate. 15:28:03 ACTION: Alex to investigate 15:28:19 Vojtech: Two more things. 15:28:28 zakim, please call MSM-617 15:28:28 ok, MSM; the call is being made 15:28:30 +MSM 15:29:01 ...In Section 7.1.9.2 there are two conditions: if the content-type is XML or the encoding is base64 or not. 15:29:22 ...Then different things can happen, but it seems to me that if the content-type is XML and encoding is base64 then the result is unspecified. 15:30:04 Norm: I think the right thing is decode it and parse it, but we should say that. 15:30:08 ACTION: Alex to fix. 15:30:43 Vojtech: The last one is more of a question, in 7.1.9.4 there's a note about text/html 15:31:20 ...that says it'll be base64 encoded. But earlier it says that text types aren't encoded that way. 15:31:27 ...So I wonder what the right answer is. 15:32:13 Norm: Yeah, that does seem strange. I'd have expected the text to just be escaped markup. 15:32:55 Topic: Any other business 15:33:18 None heard. 15:33:29 -MSM 15:33:30 -richard 15:33:32 -Norm 15:33:33 -Vojtech 15:33:35 -ruilopes 15:33:36 -Andrew 15:33:36 RRSAgent, set logs world-visible 15:33:37 XML_PMWG()11:00AM has ended 15:33:38 Attendees were Vojtech, Norm, Andrew, +1.857.362.aaaa, ruilopes, Ht, richard, MSM 15:33:42 RRSAgent, draft minutes 15:33:42 I have made the request to generate http://www.w3.org/2008/06/05-xproc-minutes.html Norm 17:32:22 Zakim has left #xproc 18:24:30 MSM has joined #xproc