15:56:01 RRSAgent has joined #xproc 15:56:01 logging to http://www.w3.org/2010/11/18-xproc-irc 15:56:04 Zakim has joined #xproc 15:56:11 zakim, this will be xproc 15:56:11 ok, Norm; I see XML_PMWG()11:00AM scheduled to start in 4 minutes 15:58:19 Meeting: XML Processing Model WG 15:58:19 Date: 18 November 2010 15:58:19 Agenda: http://www.w3.org/XML/XProc/2010/11/18-agenda 15:58:19 Meeting: 184 15:58:19 Chair: Norm 15:58:19 Scribe: Norm 15:58:22 ScribeNick: Norm 15:58:34 Regrets: Henry, Mohamed 16:00:39 XML_PMWG()11:00AM has now started 16:00:46 +Norm 16:01:10 Vojtech has joined #xproc 16:02:14 +Jeroen 16:02:22 zakim, jeroen is Vojtech 16:02:22 +Vojtech; got it 16:02:42 Can you hear me? I can't hear you? 16:02:47 I can't here you. I meant. 16:02:48 PGrosso has joined #xproc 16:02:58 alexmilowski has joined #xproc 16:04:11 I don't hear anything 16:04:18 That's weird I heard you say that. I'll dial in again. 16:04:23 -Norm 16:04:40 +??P13 16:04:50 +Norm 16:05:00 zakim, ??P13 is alexmilowski 16:05:00 +alexmilowski; got it 16:05:17 Alex, can you hear me? 16:05:19 I'm on skype without a headset, so we'll see how this goes 16:05:32 No. 16:05:38 I can hear others. 16:05:41 Vojtech, I heard you say "The silence is almost absolute" then you went away 16:05:52 Vojtech/Alex can you hear each other? 16:06:12 Apparently I can hear Vojtech and Alex 16:07:00 Topic: Accept this agenda? 16:07:00 -> http://www.w3.org/XML/XProc/2010/11/18-agenda 16:07:06 Accepted. 16:07:10 Topic: Accept minutes from the previous meeting? 16:07:10 -> http://www.w3.org/XML/XProc/2010/11/04-05-minutes 16:07:18 As amended yesterday. 16:07:22 Accepted. 16:07:36 Topic: Update on LC draft of processor profiles 16:07:43 Henry reports he'll have something for us next week. 16:07:58 Topic: Next meeting: telcon, 9 Dec 2010? 16:08:10 +[ArborText] 16:08:58 Present: Norm, Alex, Vojtech, Paul 16:09:06 Accepted. 16:09:31 Topic: Review of p:document-template note 16:10:03 Norm: I think the only substantive issue is how to parse curly brace 16:10:10 s/brace/braces/ 16:11:33 Vojtech: XQuery handles curly braces by watching for quotes. 16:11:54 ...I think doing it like that would be more consistent for users, but harder for implementors. 16:12:06 Norm: Well... 16:12:15 Vojtech: On the other hand, maybe it's not really that hard. 16:13:21 Norm attempts to summarize: 16:13:53 When you see a "{" (not doubled), switch to xpath-mode. When you see a ' or " in xpath-mode, switch to quote-mode. In quote-mode everything is quoted until the closing quote. 16:14:00 At the closing quote, go back to xpath-mode. 16:14:10 In xpath-mode, a "}" whether it is doubled or not, immediately ends the expression. 16:15:41 Some discussion of what happens if you leave a quote out. You'll read the whole content of whatever text node you're looking at. 16:16:11 Norm: Are those the rules everyone preferes? 16:16:15 s/preferes/prefers/ 16:16:25 Vojtech: What happens if you use character references for quotes? 16:16:37 Norm: No. We'll only see the expanded references. 16:17:48 Alex: I like it. 16:18:02 Norm: In the common case, you'll be able to write { concat('{', $foo, '}') } 16:18:13 ...That probably is easier than doubling all the curly braces 16:18:23 Vojtech: What about the rules for doubled braces? 16:18:56 Norm: We could say "{" is an error in XPath mode. 16:20:12 Vojtech: What happens if XPath 3 introduces "{" in XPath? 16:20:17 Alex: We'll have to change the parsing rules. 16:20:58 Norm: Given that XSLT and XQuery both use curly braces to bound expressions, it seems unlikely to me that they'll decide to use them for something else in XPath V.x 16:22:26 In regular-mode, {{ is a {. In regular-mode, { (undoubled) starts xpath-mode. 16:22:26 In xpath-mode, ' or " starts quote-mode. In quote-mode no characters are 16:22:26 speciall except the matching quote that returns us to xpath-mode. 16:22:26 In xpath-mode { is an error. In xpath-mode } ends the expression and returns 16:22:26 to regular-mode (after inserting the result of evaluating the expression). 16:22:57 s/speciall/special/ 16:23:04 yes 16:23:11 yes 16:23:12 Norm: Is that what people like? 16:23:14 General agreement. 16:23:32 Norm: Any other discussion about document templates or the note? 16:23:40 Topic: GRDDL step? 16:24:33 Alex: I was looking at GRDDL and think it's something we should do as a standard step, but I haven't looked into it yet. 16:25:05 Vojtech: I looked at the spec and from what I read, it seemed to me that parts of it we could do already. 16:25:34 e.g. 16:25:35 xmlns:grddl='http://www.w3.org/2003/g/data-view#' 16:25:36 grddl:transformation="glean_title.xsl 16:25:36 http://www.w3.org/2001/sw/grddl-wg/td/getAuthor.xsl" 16:25:36 > 16:25:39 ...It just checks for attributes and fetches a stylesheet. It looks like something that should be possible with XProc. 16:25:46 ...There's also the merging of the RDF graphs. 16:26:06 Alex: That's what I was thinking about. One interpretation is that you'd output RDF directly. Another is that you output Turtle or something like that. 16:26:23 ...We should consider what would be useful for people doing something like harvesting. 16:27:25 ACTION: Alex to review GRDDL and return with a suggestion. 16:28:16 Alex: one outcome might be a standard pipeline but implementors could do it natively. 16:28:52 Alex: That leads to an interesting possible enhancement: the ability to say "here's the fallback implementation of this step" but with the explicit provision that a native implementation could be used instead. 16:30:42 Vojtech: The GRDDL spec says that the transformation can be any process, typically it's XSLT. But XProc is also a possibility now too. 16:30:55 ...I wonder if we do the GRDDL step if we want to say something about what languages are supported for the transformations. 16:31:16 Alex: Right. 16:32:07 Norm: Alex, as you consider GRDDL, please keep those things in mind. 16:32:28 Topic: Possible erratum: definition of an XProc Processor 16:33:05 Vojtech: We don't have a definition of an XProc Processor. 16:33:08 Alex: How did we do that? 16:33:51 Norm: Does anyone think they can write a concise definition of an XProc processor? 16:34:08 Vojtech: There are all sorts of rules in the spec, it has to apply the steps in the right order, etc. 16:34:25 ACTION: Vojtech will review the spec and propose a definition of an XProc Processor. 16:34:30 [Definition: The software responsible for transforming source trees into result trees using an XSLT stylesheet is referred to as the processor. This is sometimes expanded to XSLT processor to avoid any confusion with other processors, for example an XML processor.] 16:35:18 Norm: Yes, I think we'll want something like that. 16:35:24 Topic: Any other business? 16:35:51 Vojtech: I was wondering if having a p:sort would add any value. 16:36:17 ...something like split-sequence that takes an XPath expression to use for ordering the documents. 16:36:59 Norm: I'm not opposed. I never even thought of doing it. 16:37:13 Vojtech: Maybe it's better to put something like this in EXProc. 16:37:42 Norm: Yeah, we can leave it there and see if we get requests for a better job. 16:37:55 Vojtech: My concern is that it might not be sufficient for more complex use cases. 16:39:05 ...if the sort criteria are not easy to express in an XPath expression, for example. 16:39:14 Alex: I'm just not sure what the use cases are. 16:40:05 Vojtech: The use case that I had was that I was trying to implement OAuth and you have to sort the request parameters before you hash them. 16:40:20 ...For that I needed a sort. It was simple string sort so you could do that with XSLT or XQuery. 16:41:36 Adjourned. See you in two weeks. 16:41:39 -Vojtech 16:41:40 -Norm 16:41:41 -PGrosso 16:41:42 -alexmilowski 16:41:44 XML_PMWG()11:00AM has ended 16:41:46 Attendees were Norm, Vojtech, alexmilowski, PGrosso 16:41:48 rrsagent, set logs world visible 16:41:52 rrsagent, draft minutes 16:41:52 I have made the request to generate http://www.w3.org/2010/11/18-xproc-minutes.html Norm 16:43:08 PGrosso has left #xproc 16:59:52 fgeorges has joined #xproc 17:56:33 ht has joined #xproc 18:24:25 Zakim has left #xproc 18:25:35 ht has left #xproc