14:55:05 RRSAgent has joined #xproc 14:55:05 logging to http://www.w3.org/2006/04/06-xproc-irc 14:55:06 zakim, this will be xproc 14:55:16 ok, Norm; I see XML_PMWG()11:00AM scheduled to start in 5 minutes 14:55:32 Meeting: XML Processing Model WG 14:55:32 Scribe: Norm 14:55:32 ScribeNick: Norm 14:55:32 Date: 6 Apr 2006 14:55:32 Chair: Norm 14:55:33 Agenda: http://www.w3.org/XML/XProc/2006/04/06-agenda.html 14:57:49 rlopes has joined #xproc 15:00:15 Alessandro has joined #xproc 15:00:29 AndrewF has joined #xproc 15:00:31 XML_PMWG()11:00AM has now started 15:00:45 +[IPcaller] 15:01:06 zakim, [IPcaller is rlopes 15:01:21 zakim, who's on the phone? 15:01:23 zakim, please call ht-781 15:01:27 +Norm 15:01:31 Zakim, [IP is Alessandro 15:01:41 +rlopes; got it 15:01:58 On the phone I see rlopes, Norm 15:02:00 ok, ht; the call is being made 15:02:04 +Ht 15:02:06 +[IPcaller] 15:02:06 AndrewF has joined #xproc 15:02:16 +Alessandro; got it 15:02:24 +MoZ 15:02:26 zakim, who's on the phone? 15:02:37 zakim, who's talking? 15:02:38 beautiful noise :D 15:03:02 On the phone I see rlopes, Norm, Alessandro, Ht, MoZ 15:03:26 +??P15 15:03:36 Norm, listening for 10 seconds I heard sound from the following: Ht (40%) 15:03:59 zakim, ??P15 is AndrewF 15:04:13 zakim, who is making noise? 15:04:32 +AndrewF; got it 15:05:00 ht, listening for 10 seconds I could not identify any sounds 15:05:45 Present: Alessandro, Andrew, Henry, Mohamed, Norm, Rui 15:05:59 Regrets: Erik, Jeni, Michael, Richard, Paul 15:06:15 Topic: Accept this agenda? 15:06:15 -> http://www.w3.org/XML/XProc/2006/04/06-agenda.html 15:06:24 Accepted. 15:06:28 Topic: Accept minutes from the previous teleconference? 15:06:28 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2006Mar/0069.html 15:06:38 Accepted. 15:06:42 Topic: Next meeting: 13 Apr telcon 15:06:42 Any regrets? 15:06:54 No regrets given 15:07:05 Topic: Publication status 15:07:17 Norm submitted the transition request and got approval. 15:07:25 Norm submitted the publication request dated 11 Apr 2006 15:07:52 PGrosso has joined #xproc 15:07:52 -> http://www.w3.org/XML/XProc/docs/WD-xproc-requirements-20060411/ 15:08:17 +[ArborText] 15:08:37 Topic: Face-to-face meeting: 2-4 August 2006, north of Toronto 15:09:19 zakim, who is on the phone? 15:09:19 On the phone I see rlopes, Norm, Alessandro, Ht, MoZ, AndrewF, PGrosso 15:09:46 Norm proposes: who can commit to attending? 15:11:57 Rui: unsure; Norm: yes; Alessandro: unsure (also for Erik); Henry: yes; Mohamed: unsure, but probably; Andrew: no; Paul: yes; Henry says Alex, Michael, Jeni say yes; Richard: unsure 15:12:45 Tally: 6=yes; 5=unsure; 1=no 15:13:59 s/6=yes/7=yes/ 15:14:17 Proposed: we will meet in Toronto on the dates specified. 15:14:23 Accepted. 15:14:34 ACTION: Norm to get this into the CG calendar 15:15:22 Henry points out that formally we can't decide to do this, all we can do is ask the CG to allow us. No one seriously expects the CG to say anything but "yes" 15:15:39 Topic: Starting a working draft 15:16:06 The chair asks if we have a volunteer editor. 15:16:12 Norm volunteers. 15:17:00 Norm warns that editing, chairing, and taking minutes may prove too much for one person. He suggests that Henry, Michael, and perhaps others may get called upon to take minutes. 15:17:25 Norm wonders if rotating the minute taking is the right thing. 15:17:55 Topic: Richard's proposal 15:19:09 Norm wonders if it makes sense to consider Jeni's proposal of passing URIs instead of documents around. 15:19:17 http://www.cogsci.ed.ac.uk/~richard/pipeline.html 15:20:24 Henry doesn't think passing filenames (URIs) around is really going to work. 15:20:45 Henry: Jeni's story could be read either way (as passing filenames or using filenames) 15:21:14 Henry: I'm still interested in thinking about this in terms of giving local names to things (inputs/outputs) and using those names to refer to them. 15:21:49 Norm: With respect to giving names to local things, did you mean inputs and outputs 15:22:10 Henry: Yes, but I also mean static resources/secondary inputs/whatever you want to call them. 15:23:16 Henry: In the pure piped ontology which Richard offered at the f2f, there is a qualitative difference between an XSLT component that has one pipe coming in and one going out and a parameter which is the name of a static stylesheet and an XSLT component that has two pipes coming in and one going out. 15:24:17 Norm: My proposal, to unify these, is to allow a shortcut for a "read-from-URI" component that attaches to the stylesheet input pipe. 15:25:39 Norm: Do you see any problem with that approach? 15:26:08 Henry: No, but I'm still swinging back and forth between thinking of the pipeline runtime as a resource manager and the pure dataflow model. 15:26:31 Norm: I tend to swing back and forth as well. I hope that we don't have to pick one. 15:27:41 Norm: The resource manager view has the problem of dealing with a pipe that contains a sequence of otherwise anonymous docments. 15:28:20 Henry: Local names are just conveniences. They are single documents or doucment streams as appropriate. 15:28:34 Henry: The only interesting case is when you use a non-local name. 15:29:38 Henry: In MT pipe, the convention is if you use a #-ed name, it just plugs together. If however it's a primary input/output connection and you give it a non-#'d name, then you get the single document if it's one or the last document if it's a sequence. 15:30:19 Henry: There's no clear answer to the question of what does the label mean if a sequence of documents is addresed by a lable in the resource-manager view. 15:31:05 Norm ponders the idea of a resource manager that handles a collection 15:31:53 Norm suggests the fragment question as a next reasonable point to discuss 15:34:40 Norm describes the situation as an interoperability issue (since some implementations might not even notice and others might fall over) 15:35:10 Henry: It's entirely reasonable for some implementations to fall over if you pass anything other than real XML "Document"s . 15:36:35 Norm expresses a view that either the pipeline author has to fix it, or the pipeline engine has to fix it. 15:36:57 Norm: I suggest for V1 that we say it's the pipeline author's problem 15:37:01 Henry: works for me 15:37:31 Norm wonders if the rest of the group agrees 15:37:47 Rui: I believe that just documents is good enough for me. 15:37:50 No one objects. 15:38:45 Proposal: only XML 1.x documents (proper Documents in the XML sense) pass between components; if you need to pass something else in your pipeline, the pipeline author has to wrap and unwrap as necessary. 15:39:01 Accepted. 15:40:00 ACTION: Norm to begin summarizing the points of consensus 15:40:18 Topic: Conditionals and sub-pipelines 15:40:35 Norm: Richard proposed a single standard conditional that takes a document and an XPath, is that enough? 15:41:18 + +1.519.378.aaaa 15:41:20 Norm wonders if the WG thinks that's all we need 15:41:37 Henry: If you need something really complicated, you can write an arbitrarily complicated computation that produces a document. 15:41:43 Henry: And then switch on that conditional. 15:41:50 zakim, aaaa is Murray 15:41:50 +Murray; got it 15:42:46 Proposal: The pipeline conditional component is XPath expression over document. If you need more, build a document and use that? 15:43:00 Accepted. 15:43:56 Topic: What about XPath 1 vs. XPath 2? 15:44:05 Murray: We could put the statement in terms of the availbale processor. 15:44:57 Norm suggest that won't work 15:45:08 Henry: Several possibilities: 15:45:38 Henry: 1. Use a convention for naming XPath expressions that are the values of attributes; xpath=, xpath1=, or xpath2= 15:46:09 Henry: A question we have to address is, are we going to subset XPath in order to guarantee that it isn't hard to do this. 15:46:21 Henry: I think we should subset. 15:46:46 Henry proposes that the XPath expressions that you can use in conditionals to being ones that are streamable 15:47:00 ht, what about attribute minxpathversion="1.0" to parse 15:47:12 Henry: bearing in mind again that if you need the full power of XPath, then you can use an XSLT processor to build a document ove rwhich a streaming test will succeed. 15:47:58 -Murray 15:48:00 Alessandro: We can say that the expression is going to be XPath 1 or 2 and the engine can analyze the expression and stream if it wants to. Otherwise, it can just run a full XPath engine 15:48:41 Norm asks if Alessandro is opposed to the subset 15:48:45 Alessandro: Yes 15:49:14 Henry: The problem I have is that it puts a huge burden on the implementor for functionality that we've already determined most users won't ever use 15:49:34 Norm: My concern is inventing the subset. Do you think the XML Schema schema subset is appropriate. 15:49:36 Henry: Not quite. 15:49:47 Henry: The thing that's missing is [@foo] 15:50:48 Norm: So the tradeoff is inventing a subset or using an off the shelf processor. Or is the problem really the analysis for streaming? 15:51:18 Henry: The analysis is hard. Can we float a trial balloon and examine the possibility of using that in V1? 15:51:44 Henry: Two issues for V.next are, should we accept any XPath or should we require people to detect a certain class as streamable 15:52:06 Norm: Why detect? Non streaming will always work. 15:52:43 Henry: One of the crucial things about a viewport is that the XPath expression be streamable because that's how you deal with documents that are too large to read into memory. 15:53:04 Henry: Conditionals are not the only place where XPath expressions are going to turn up. 15:53:13 Henry: It seems plausible to try to tell a consistent story. 15:53:49 Norm: I agree, I don't want XPaths on different components to have a different flavor. 15:54:10 Henry: Maybe the regex for detecting the streaming subset isn't too hard. 15:55:03 Norm ponders the plausibility of using a regex 15:55:47 Henry: I think a regex could detect the the Schema subset 15:56:01 Norm objects to the idea of *requiring* a processor to support streaming 15:56:18 -Ht 15:56:33 Norm proposes that we take the XPath 1/2/subset question to email 15:57:03 Topic: Any other business? 15:57:48 Alessandro: Did we have a conversation about setting up bugzilla 15:58:36 Norm: Yes 15:58:48 -> http://www.w3.org/Bugs/Public/ 15:58:54 Excellent 15:59:33 Norm will make the XPath question an issue as an example 15:59:50 -PGrosso 15:59:52 -rlopes 15:59:53 -Norm 15:59:54 -Alessandro 15:59:55 rlopes has left #xproc 15:59:57 PGrosso has left #xproc 15:59:59 -AndrewF 16:01:11 rrsagent, set logs world-visible 16:01:20 rrsagent, draft minutes 16:01:20 I have made the request to generate http://www.w3.org/2006/04/06-xproc-minutes.html Norm 16:01:22 -MoZ 16:01:24 XML_PMWG()11:00AM has ended 16:01:25 Attendees were [IPcaller], Norm, rlopes, Ht, Alessandro, MoZ, AndrewF, PGrosso, +1.519.378.aaaa, Murray 16:08:17 MSM has joined #xproc 17:18:08 Good morning MMS 17:18:10 Uh, MSM even 17:21:01 good evening, Norm. mea culpa 17:21:18 Evening? In Europe, I suppose :-) 17:21:26 No worries, Michael, you gave regrets last week 17:21:36 That's where some of us are, for sure :-) 17:21:59 Fair point, ht 17:22:14 But not MSM, I agree :-) 17:23:11 Maybe he never went to sleep? Partying all night with the query gang, were you, MSM? :-) 17:32:01 Good progress today, I think 17:32:19 ht, I put the xpath issue in bugzilla; Alessandro asked about it just moments after you left 17:32:22 rrsagent, bye 17:32:22 I see 2 open action items saved in http://www.w3.org/2006/04/06-xproc-actions.rdf : 17:32:22 ACTION: Norm to get this into the CG calendar [1] 17:32:22 recorded in http://www.w3.org/2006/04/06-xproc-irc#T15-14-34 17:32:22 ACTION: Norm to begin summarizing the points of consensus [2] 17:32:22 recorded in http://www.w3.org/2006/04/06-xproc-irc#T15-40-00 17:32:23 zakim, bye 17:32:23 Zakim has left #xproc