14:46:50 RRSAgent has joined #xproc 14:46:50 logging to http://www.w3.org/2007/08/09-xproc-irc 14:46:57 Meeting: XML Processing Model WG 14:46:57 Date: 9 August 2007 14:46:57 Agenda: http://www.w3.org/XML/XProc/2007/08/09-agenda 14:46:57 Meeting number: 79, T-minus 12 weeks 14:46:57 Chair: Norm 14:46:58 Scribe: Norm 14:47:00 ScribeNick: Norm 14:56:36 avernet has joined #xproc 15:00:45 MoZ has joined #xproc 15:01:22 Zakim, what is the code ? 15:01:22 the conference code is 97762 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), MoZ 15:01:50 XML_PMWG()11:00AM has now started 15:01:51 Zakim, who is on the phone ? 15:01:51 On the phone I see no one 15:01:57 +??P7 15:01:58 + +40.83.aaaa 15:02:05 zakim, ? is avernet 15:02:05 +avernet; got it 15:02:12 Zakim, aaaa is me 15:02:12 +MoZ; got it 15:03:06 Andrew has joined #xproc 15:03:42 +??P28 15:03:46 zakim, ? is me 15:03:46 +Andrew; got it 15:04:01 +Norm 15:04:04 zakim, who's on the phone? 15:04:04 On the phone I see avernet, MoZ, Andrew, Norm 15:04:34 alexmilowski has joined #xproc 15:04:55 Regrets: Paul, Henry 15:05:10 Regrets: Paul, Henry, Michael 15:05:21 +Alex_Milowski 15:05:54 zakim, who's on the phone? 15:05:54 On the phone I see avernet, MoZ, Andrew, Norm, Alex_Milowski 15:05:55 richard has joined #xproc 15:06:20 +??P0 15:06:21 zakim, ? is me 15:06:21 +richard; got it 15:06:43 Present: Alessandro, Mohamed, Andrew, Norm, Alex, Richard 15:07:01 Topic: Accept this agenda? 15:07:01 -> http://www.w3.org/XML/XProc/2007/08/09-agenda 15:07:11 Reorder items 2 and 3 15:07:35 Mohamed: I'd like to talk about p:pack. 15:07:41 Norm: Ok, we'll make that item 5 15:08:11 Topic: Accept minutes from the previous meeting? 15:08:11 -> http://www.w3.org/XML/XProc/2007/08/02-minutes 15:08:18 Accepted. 15:08:23 Topic: Next meeting: telcon 16 August 2007 15:08:39 Probably regrets from Mohamed 15:08:45 Topic: Comments on the new draft 15:08:45 -> http://www.w3.org/XML/XProc/docs/langspec.html 15:09:19 Norm: I think it's pretty good except for the namespace bindings. 15:09:42 Richard: The diffs are pretty amusing. 15:10:01 Mohamed: What happend to err:? 15:10:12 +Murray_Maloney 15:10:26 Norm: I took it out for err:errors and err:error because we can use c: for that. 15:11:02 Norm: Then I remembered error QNames, so I put it back. 15:12:32 Norm: Everyone ok with that? 15:12:33 Seems so. 15:12:56 Topic: Question of MIME type/fragid 15:12:56 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/0076.html 15:13:13 Norm: Are we going to define one and do we want one? 15:14:21 Norm: Having a MIME type lets us identify pipeline documents; having a fragid syntax would let us describe how to point to important parts of a pipeline. 15:14:52 Norm describes his attempt at a fragid syntax. 15:16:33 Richard: We need to get this right before Last Call, right? 15:16:37 Norm: Yeah, I guess so. 15:17:42 Alex: Do we need to have a fragid syntax? 15:17:45 Murray: What would we identify 15:17:53 Norm: We would identify steps, ports, and options. 15:19:39 Norm: We don't have a need, it's a question of whether we want to provide hooks for others. 15:20:17 Murray: I'm some author outside a group of pipelines; so I might write an RDF statement that talks about these things; I might create a hypertext link to one. 15:20:33 Murray: Can I invoke a step this way? 15:20:34 Norm: No 15:21:07 Norm: You could also use it for error messages. 15:21:15 Richard: Seems strange to do this when we don't use them. 15:21:59 Norm: I get the impression that we're leaning towards a MIME type but not the fragment identifier. 15:22:15 the xpath xpointer scheme doesnt exist 15:22:50 Murray: I can see the value in being able to refer to steps from the outside. I'm not sure I get the value in naming the ports. 15:22:58 s/naming the/having fragids for the/ 15:24:04 Norm: So I propose that we define a MIME type, application/xml+xproc, but not a fragment identifier syntax. 15:24:39 Murray: How hard is it to point to steps? 15:24:45 Norm: Easy, if they have names and the names are unique. 15:26:38 Richard points out that pipelines in a library could easily have the same names 15:26:45 s/the same names/steps with the same names/ 15:27:59 Alex: There's not a lot of precedent here, lots of recent specs don't have MIME types. 15:28:07 Richard: I haven't heard any compelling arguments for a fragid syntax. 15:29:17 Norm: So it seems like the consensus is MIME type yes, fragids no. 15:29:42 15:29:54 Murray: If we think pipelines are going to be popular, which I think we do, it seems like there will be lots of people who want to talk about them. 15:30:14 Alex: One rational position is to not require to sprinkle xml:id over their documents. If you want to point to something, you have to name it. 15:30:40 Alex: Then we can do something like what Norm proposed and provide a mechanism for pointing to them. 15:31:15 Richard: Though I see that you might want to talk about these things, without tools, it's not terribly useful to point to them. 15:31:22 Murray: That's a chicken and egg thing, isn't it? 15:32:47 Norm: I'd like to set this aside for a moment and go on to the next item. 15:32:55 Topic: Question about anonymous steps or defaulted names. 15:32:55 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/0077.html 15:35:31 Norm outlines his message 15:35:45 Murray: I like the idea. 15:36:11 Mohamed: I'm not sure I like the defaulting of inputs to the p:pipeline. 15:36:32 Norm: Yeah, but that's not really the issue here. 15:38:04 Alex muses about the syntax Norm proposed. 15:38:25 Richard: The presence of named ports wouldn't changed the names, would it? 15:39:55 Norm: We could actually use "source" and "result" for manufactured port names. 15:41:17 xyzzy-nn 15:41:40 Murray: Would we have to use the section symbol in the URI? 15:42:01 15:42:02 15:42:04 15:42:05 15:42:06 Norm: Yes, that's the price you pay for not having put your own name on the step. 15:42:07 15:42:09 15:42:10 15:42:12 15:42:49 Norm: Is anyone in principle against this proposal? 15:42:55 Mohamed: Yes. 15:42:56 Norm: Why? 15:43:05 Mohamed: It's giving more possibilities for users to not use names. 15:44:00 mark = "-" | "_" | "." | "!" | "~" | "*" | "'" | "(" | ")" 15:44:32 Alex: It'd be nice if we picked a character name that doesn't require URI encoding. 15:44:44 Norm: Ok, how about "!" 15:45:11 Mohamed: I'm ok with naming steps. 15:46:02 Norm: One of the goals is to remove a concept from the spec, I don't anything to be anonymous. 15:47:01 Richard: You think you're going to use these in some hypothetical fragment syntax? 15:47:39 Alex: I like the idea that you can't use the manufactured name in the syntax. 15:48:06 Richard: We're going to specify that the things have these names. Are implementations going to have to use them? 15:49:09 Norm: In a running pipeline, you'll never see them. 15:49:13 Richard: So this has no normative effect. 15:49:55 Norm: True, but the spec will still be simpler because it has one less concept. 15:50:15 +1 15:50:20 Norm: I propose that we direct the editor to give this a try and see if we like it. 15:50:25 Accepted. 15:50:50 Norm: Drat. We won't get through namespaces in 10 minutes, let's return to MIME type/fragid. 15:51:03 Alex: I'm all for using the manufactured names in a fragid syntax. 15:51:23 Norm: Anyone opposed to having a fragid syntax for steps. 15:51:37 Norm: I propose we direct the editor to give that a whack too. 15:51:43 Accepted. 15:51:57 Mohamed: Take care that we don't overlap with the use of xml:id. 15:54:24 Norm describes the problem 15:55:29 Alex: Have you looked at what XSLT does with xsl:element 15:55:35 Norm: Yes, but that doesn't work for us. 15:56:42 Richard: Suppose you just construct arbitrary strings in options, you expect those to go through. 15:57:37 Norm: Then you need the union of all the bindings on all the variables used 15:57:57 Alex: What about the opposite case, where you don't want the bindings from the document? 15:58:41 Alex: XSLT avoided all this magic 15:59:46 Norm: So the proposal is, the namespace bindings you get on the match option passed to the delete step are the ones that are in scope for that p:option. If they don't match up, you lose. 15:59:57 Richard: XSLT gives you a workaround for these cases. 16:02:12 Some discussion of the options 16:02:42 Alex: We could give another attribute on p:delete that could point to an element on which to find the namespace bindings for this expression. 16:03:31 Richard: There'd be security considerations here, yes? 16:03:53 Alex: I still think "you lose" is the simplest answer. 16:04:24 Norm: Would anyone be uncomfortable wit the "you lose" proposal? 16:04:26 None heard 16:04:32 Topic: Any other business? 16:04:34 None. 16:04:43 -Murray_Maloney 16:04:44 Adjourned. 16:04:45 -Andrew 16:04:46 -richard 16:04:47 -MoZ 16:04:48 -Alex_Milowski 16:04:49 -avernet 16:05:03 -Norm 16:05:05 XML_PMWG()11:00AM has ended 16:05:06 Attendees were +40.83.aaaa, avernet, MoZ, Andrew, Norm, Alex_Milowski, richard, Murray_Maloney 16:05:33 rrsagent, please set logs world-visible 16:05:43 rrsagent, draft minutes 16:05:43 I have made the request to generate http://www.w3.org/2007/08/09-xproc-minutes.html Norm 16:21:44 rrsagent, by 16:21:44 I'm logging. I don't understand 'by', Norm. Try /msg RRSAgent help 16:21:47 zakim, bye 16:21:47 Zakim has left #xproc 16:21:53 rrsagent, bye 16:21:53 I see no action items