14:57:25 RRSAgent has joined #xproc 14:57:25 logging to http://www.w3.org/2008/05/01-xproc-irc 14:57:32 Meeting: XML Processing Model WG 14:57:33 Date: 1 May 2008 14:57:33 Agenda: http://www.w3.org/XML/XProc/2008/05/01-agenda 14:57:33 Meeting: 110 14:57:33 Chair: Norm 14:57:33 Scribe: Norm 14:57:35 ScribeNick: Norm 14:59:00 XML_PMWG()11:00AM has now started 14:59:07 +Norm 14:59:46 Regrets: Rui, Vojtech 14:59:56 +[ArborText] 15:00:45 alexmilowski has joined #xproc 15:01:07 MoZ, you asked to be reminded at this time 15:01:58 Huh... trying to call in... but not getting in... 15:02:05 Thanks Zakim 15:02:07 try again :-) 15:02:16 +alexmilowski 15:02:30 + +95247aaaa 15:02:36 Zakim, aaaa is me 15:02:36 +MoZ; got it 15:02:57 Zakim, who's on the phone? 15:02:57 On the phone I see Norm, PGrosso, alexmilowski, MoZ 15:03:50 zakim, please call ht-781 15:03:50 ok, ht; the call is being made 15:03:52 +Ht 15:04:20 Present: Norm, Paul, Alex, Mohamed, 15:04:21 zakim, mute ht 15:04:21 Ht should now be muted 15:04:24 AndrewF has joined #xproc 15:04:29 zakim, disconnect ht 15:04:29 Ht is being disconnected 15:04:31 -Ht 15:04:32 Present: Norm, Paul, Alex, Mohamed, Henry, Andrew 15:04:57 +??P19 15:04:58 zakim, please call ht-781 15:04:58 ok, ht; the call is being made 15:04:59 +Ht 15:05:01 zakim, ? is Andrew 15:05:01 +Andrew; got it 15:05:19 Zakim, mute ht 15:05:19 Ht should now be muted 15:05:28 richard has joined #xproc 15:05:37 -Ht 15:05:52 Present: Norm, Paul, Alex, Mohamed, Henry, Andrew, Richard 15:05:57 +??P6 15:05:59 zakim, ? is me 15:05:59 +richard; got it 15:06:09 zakim, please call ht-781 15:06:09 ok, ht; the call is being made 15:06:11 +Ht 15:06:31 Zakim, mute ht 15:06:31 Ht should now be muted 15:06:37 ht, maybe you need to go to richard's office :-) 15:06:48 -Ht 15:07:14 Topic: Accept this agenda? 15:07:14 -> http://www.w3.org/XML/XProc/2008/05/01-agenda 15:07:53 Accepted 15:08:05 Norm's affiliation changes on Monday to Mark Logic, but he anticipates participating as usual. 15:08:09 +??P22 15:08:11 ...without any changes. 15:08:32 Let's add the items that Mohamed posted if there's time. 15:09:00 Topic: Accept minutes from the previous meeting? 15:09:00 -> http://www.w3.org/XML/XProc/2008/04/24-minutes 15:09:02 Accepted. 15:09:07 Topic: Next meeting: telcon 8 May 2008? 15:09:14 No regrets given. 15:09:24 Topic: New public working draft 15:09:26 Was published today! 15:09:54 Topic: Update to p:www-form-urlencode 15:10:07 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2008Apr/0065.html 15:10:39 Mohamed: I think URL encode would be useful if it could keep the content that is in the element that matches. 15:10:54 ...The content could be, for example, the start of the URI. 15:12:14 Norm: What would the option contain? 15:12:25 Mohamed: My first idea was an option that says concatentate or not. 15:13:09 Alex: Why not do what we did for generate-id, where we have an XPath expression. 15:13:55 zakim, please call MSM-617 15:13:55 ok, MSM; the call is being made 15:13:57 +MSM 15:14:01 Norm: Ugh. Seems like a lot of complexity for a fairly narrow case. 15:14:10 So e.g. , with input 15:14:28 Present: Norm, Paul, Alex, Mohamed, Henry, Andrew, Richard, Michael [xx:15-] 15:14:29 would give 15:15:09 Mohamed: I don't know if the "?" is in or not. 15:15:11 Norm: It's not. 15:15:24 Henry: Is there an obvious way to do this otherwise? 15:15:31 ...It looks useful and hard to do any other way. 15:16:06 Alex: You can manipulate the parameter port beforehand in any way you want. 15:16:20 Norm: But this is for the GET case. 15:17:45 Alex: Right now you'd have to use XSLT to combine the two. 15:19:20 ...I think we should keep these concerns separate, otherwise it's a slippery slope. 15:19:39 ...We have the match because we do this operation and we have to put the encoded string somewhere. 15:19:56 ...But outside of the scope of perform this algorithm, I'm not sure that we need to more. 15:20:13 ...If that's the case, then we need a better insertion algorithm. 15:20:48 Mohamed argues about streamability. 15:21:21 Henry: Can we back up one step? I'd like to bring www-form-urldecode into the discussion. I think these ought to be as straightforwardly semetrical as we can make them. 15:22:54 Some discussion of where *decode* is likely to get its input. 15:23:44 Alex: It's there for symmetry. It's a bit of an edge case. 15:24:07 Henry: Then I want parse URL. 15:24:15 Alex: Yes, that would be good. 15:24:29 Norm: You can do what Mohamed wants with url-encode and string-replace 15:27:33 15:27:33 ... 15:27:33 15:27:33 15:27:33 15:27:34 15:27:36 15:28:57 Norm: Are you satisfied with that, Mohamed? 15:29:09 Mohamed: Yes, but I think Henry has raised a good question about decoding. 15:29:30 Henry: XPath 2.0 will let you do it, it'd be very hard with XPath 1.0. 15:30:02 ...There's definitely a slippery slope here. 15:30:23 Alex: There's a real need here, but it would be nice to have a URI-handling step that did a good job. 15:30:40 Norm: Stop. We're way off topic, if that's a good idea, someone write a proposal. 15:30:45 What we're really talking about is microparsing and generating steps, I realise 15:31:49 So we're not changing anything about p:www-form-urlencode. 15:32:00 Topic: Short form of p:base-uri and p:resolve-uri 15:32:09 Norm: For consistency with XPath 2.0, I think we need to leave them. 15:32:57 ...we said they'd be exactly the same as the 2.0 functions, so we shouldn't change them. 15:33:05 Accepted. 15:33:20 Topic: Support for other media types in p:unescape-markujp 15:33:23 s/ujp/up/ 15:33:32 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2008Apr/0095.html 15:34:23 Leave until Vojtech can be present. 15:34:39 Topic: Where are @psvi-required, @xpath-version, and @ignore-inline-prefixes allowed. And what are the rules for when they are nested? 15:35:37 Proposal: Allow them all on p:pipeline, p:declare-step, and p:library. Also allow ignore-inline-prefixes on p:inline. 15:36:32 Norm: I think a convenience for authors argument could be made for allowing ignore-inline-prefixes in more places, but I'm not going to make it. 15:36:51 Mohamed: I think Jeni's point was that you could group it better if it was allowed anywhere. 15:37:19 Richard: What about nesting? 15:37:26 Norm: We don't say anything yet, that we'll have to decide. 15:37:36 Henry: It's a lexically scoped union, so you can fix it. 15:37:57 Norm: Any comments about where I propose to allow them? 15:39:05 Mohamed: If it's allowed in p:declare-step, it will be allowed for both pipeline and atomic steps. 15:40:16 Norm: Yes, it'll apply to default binding for p:inline. 15:41:35 Some discussion of nesting for @xpath-version 15:42:08 Norm: Everyone content with where I said they could go? 15:42:10 Accepted. 15:42:20 Norm: I think we have a nesting story for xpath-version 15:42:37 Norm: I think the nesting story for ignore-inline-prefixes is lexical scope and union. 15:42:56 Accepted. 15:44:22 Henry: I think the semantics of psvi-required should be straightforward: if you don't have an implementation that can do PSVI, it's a dynamic error if you encounter one. 15:45:25 Alex: If you're impl supports PSVI, then every step in your impl is using that API. So having a psvi-required=false doesn't mean you're not going to construct one. 15:46:12 Norm: I think psvi-required=false is either pointless or serves only as documentation. 15:47:56 Some discussion of the semantics. 15:50:52 Alex: The psvi-required error is currently *static* 15:51:08 Norm: I think that's silly, it should be dynamic. 15:52:59 Proposed: Add a new system property taht says whetehr or not PSVIs are being used by this invocation fo this pipeline. 15:53:10 s/taht/that/ 15:53:21 s/whetehr/whether/ 15:53:23 Accpted. Name to be determined by the editor. 15:55:41 Mohamed: I think it would be better if the property just told you whether or not the implmentation *can* do PSVIs. 15:59:02 Richard: What PSVI properties appear on documents? 15:59:18 Richard: So a p:wrap step will throw out the PSVI properties. 15:59:20 Henry: Right. 16:00:08 Richard: So PSVI properties only arise from the steps that say they can produce them and other steps don't change them. 16:00:11 Henry: I think that's right. 16:02:08 ...Next week we should discuss what sort of preservation we want. 16:02:45 Propsal: We make the psvi-required error a dynamic error. 16:02:48 Accepted. 16:02:53 Topic: Any other business? 16:02:56 None heard. 16:03:01 -ht 16:03:04 -Norm 16:03:05 -richard 16:03:05 -Andrew 16:03:06 -MoZ 16:03:06 -PGrosso 16:03:07 -alexmilowski 16:03:09 -MSM 16:03:10 XML_PMWG()11:00AM has ended 16:03:11 Attendees were Norm, PGrosso, alexmilowski, +95247aaaa, MoZ, Ht, Andrew, richard, MSM 16:04:04 Adjourned 16:04:10 RRSAgent, set logs world-visible 16:04:14 RRSAgent, generate minutes 16:04:14 I have made the request to generate http://www.w3.org/2008/05/01-xproc-minutes.html Norm 16:06:29 PGrosso has left #xproc 17:19:49 Zakim has left #xproc