14:06:23 RRSAgent has joined #xproc 14:06:23 logging to http://www.w3.org/2015/06/24-xproc-irc 14:06:26 rrsagent, set logs world-visible 14:06:26 Meeting: XML Processing Model WG 14:06:26 Date: 24 June 2015 14:06:26 Meeting: 273 14:06:27 Chair: Norm 14:06:27 Scribe: Norm 14:06:29 ScribeNick: Norm 14:07:40 Topic: Accept this agenda? 14:07:40 -> http://www.w3.org/XML/XProc/2015/06/24-agenda 14:08:07 Accepted. 14:08:25 Topic: Accept minutes from the previous meeting? 14:08:25 -> http://www.w3.org/XML/XProc/2015/06/10-12-minutes.html 14:08:36 Accepted. 14:08:40 Topic: Next meeting 14:08:48 Any regrets for 1 July? 14:08:59 Murray gives regrets. 14:09:48 Topic: Review of actions 14:09:48 which I sent here 14:09:48 https://github.com/xproc/specification/issues/136 14:09:56 and ann on mailing list 14:10:00 Jim reports progress on A-265-02; Norm will make sure that's on the agenda for next week. 14:10:02 mine 14:10:04 muted 14:10:17 Topic: Review of the “small-fixes” draft. 14:10:23 -> https://ndw.github.io/specification/ 14:10:42 https://ndw.github.io/specification/langspec/small-fixes/head/xproc20/diff.html 14:11:28 Comments on 2.10 Value Templates 14:12:11 Henry: I think there are a lot of problems with the terminology. There's overloading of the attribute/element that might contain something in curly braces and the strings that contain curly braces. 14:12:24 ...They're both called value templates and I don't think that's helpful. 14:13:20 ...I tried to rework it but it wasn't obvious. Introducing different terms for contexts where value templates are allowed on the one hand and on the other, the thing that's in there that gets expanded and so on. 14:13:35 Norm: Entirely fair; I tried to copy what was in the XSLT draft and I don't think it works. 14:14:18 Henry: A few more comments then. 14:14:28 ...The word "alternating" should be removed from the first paragraph. 14:15:05 ...It's just a sequence because {$foo}{$bar} is prefectly fine. 14:15:23 Isn't "{}" just a variable part that returns an empty sequence / empty string ? 14:15:24 ...The next to last sentence of that paragraph and the note that follows contradict each other. 14:16:02 its an error 14:16:07 }{ 14:16:34 Right, got it. 14:16:58 (still drinking my coffee; coffee good) 14:18:05 Henry: The "fixed part of" following the note has only been removed in one place. That seems an error. 14:18:36 ...In 2.10.1 but not 2.10.2, in the second bullet don't we need a reference to the process in XPath? 14:18:57 ..."converting the value to a string" is non-obvious: you have to atomize, etc. 14:20:05 Henry: And finally, below the deleted note in 2.10.2, the sentence that begins "The rules for text value templates..." should be removed. 14:20:30 Are we going to say something about: xyzzy{@y} ? 14:21:22 Henry: We should have a note that says that. 14:23:16 ...Perhaps we could point to something in XQuery that describes how that construction works. 14:25:06 5.2 ? 14:25:08 Norm: The change in 5 is entirely editorial, I added new sections. 14:25:29 Norm: In 5.2, I removed @expand-text. 14:26:16 5.51 & 5.5.3 - same change 14:26:34 5.5.1 14:27:48 Norm: The changes in 5.10 are an attempt to get non-XML inlines. 14:30:19 Editorial: make the non-XML content subsection first as it is very short. 14:30:36 @encoding is separable from this. 14:31:31 Henry: "Interpretation of the content" is wrong; it's "decoding of the content" 14:34:24 Alex: The right way to slice this is to say you're starting with two things, an encoding attribute that gives you a sequence of bytes or you have a sequence of nodes (children of the inline) and you have to coerce that into a document. 14:35:18 ...What happens if you have element nodes in the content. 14:35:50 Henry: I'm happy to special case that. If it's an XML application type, then elements are ok. 14:37:00 Norm: The case of XML that's base64 encoded needs to be considered as well. 14:37:48 Alex: Can't we just make encoding XML an error? This is an inline. 14:38:41 We have three categories: text/*, XML media types, everything else 14:38:55 Henry: Are we clear that you can specify a charset on the content type? 14:39:26 encoding=base64, content-type=text/xml is an error 14:39:32 Norm: If you base64 encode the text then you have to be able to specify the charset. 14:40:04 encoding=base64, content-type=text/plain; charset=ASCII should work 14:42:41 Alex: Maybe we should just show the matrix: encoding, text, XML, non-XML 14:45:27 Some discussion of media type vs. content type. 14:45:37 Alex: The syntax we're relying on is the value space of content type. 14:45:57 Change MediaType to ContentType 14:45:58 (Internet) Media Type vs Content-Type (the header ?) 14:49:10 Topic: Primer 14:49:52 Norm mutters on a bit about a primer. 14:50:02 Norm: We thought of you Murray. 14:50:07 to add- as well as editing primer and getting others to contrib 14:50:15 Murray: I'm busy for at least a month but then I might be interested. 14:51:29 Alex: Consensus generally was that we also need someone to think creatively about this. 14:51:34 Murray: Sure. 14:51:55 Topic: The problem of variable placement. 14:51:59 https://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2015Jun/0012.html 14:54:03 +1 to accepting p:variable everywhere 14:54:55 agree no need to put in atomics 14:56:34 ACTION: Norm to draft p:variable everywhere. 14:57:46 and I've put a comment in https://github.com/xproc/specification/issues/132 that we should probably close (as p:variable in atomic may not mean anything) 14:57:55 Topic: Any other business? 15:00:17 Adjourned. 15:03:43 rrsagent, draft minutes 15:03:43 I have made the request to generate http://www.w3.org/2015/06/24-xproc-minutes.html Norm 16:59:33 ht has joined #xproc 16:59:37 ht has left #xproc