14:57:47 RRSAgent has joined #xproc 14:57:47 logging to http://www.w3.org/2007/08/02-xproc-irc 14:59:30 MoZ has joined #xproc 14:59:58 Zakim, what is the code ? 14:59:58 the conference code is 97762 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), MoZ 15:00:31 Meeting: XML Processing Model WG 15:00:31 Date: 2 August 2007 15:00:31 Agenda: http://www.w3.org/XML/XProc/2007/08/02-agenda 15:00:31 Meeting number: 78, T-minus 13 weeks 15:00:31 Chair: Norm 15:00:32 Scribe: Norm 15:00:34 ScribeNick: Norm 15:00:56 XML_PMWG()11:00AM has now started 15:01:10 + +43.56.aaaa 15:01:12 +Norm 15:01:17 +[ArborText] 15:01:22 zakim, aaaa is MoZ 15:01:23 +MoZ; got it 15:01:31 +??P38 15:01:37 zakim, ? is avernet 15:01:37 +avernet; got it 15:01:51 richard has joined #xproc 15:02:50 zakim, who's on the phone? 15:02:50 On the phone I see PGrosso, MoZ, Norm, avernet 15:02:59 +??P41 15:03:00 zakim, ? is me 15:03:00 +richard; got it 15:03:04 zakim, please call MSM-Office 15:03:04 ok, MSM; the call is being made 15:03:06 +MSM 15:03:08 Regrets: Henry 15:04:00 zakim, who's on the phone? 15:04:00 On the phone I see PGrosso, MoZ, Norm, avernet, richard, MSM 15:04:41 Present: Paul, Mohamed, Norm, Alessandro, Richard, Michael 15:05:15 Topic: Accept this agenda? 15:05:15 -> http://www.w3.org/XML/XProc/2007/08/02-agenda 15:05:27 Accepted. 15:05:33 Topic: Accept minutes from the previous meeting? 15:05:33 -> http://www.w3.org/XML/XProc/2007/07/26-minutes 15:06:04 Norm thanks Paul for chairing. 15:06:15 Topic: Next meeting: telcon 9 August 2007 15:06:33 Michael gives regrets 15:06:34 Andrew has joined #xproc 15:06:51 Topic: Question about position/size in loops 15:06:51 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/0035.html 15:07:04 +??P2 15:07:08 zakim, ? is me 15:07:08 +Andrew; got it 15:07:58 Norm explains his confusion. 15:08:25 alexmilowski has joined #xproc 15:08:38 Richard agrees it seems confusing. 15:08:58 +Alex_Milowski 15:10:59 Norm: I propose that we add an extension function for iteration-size in for-each and viewport. 15:11:22 Norm: Simultaneously, I'd like to suggest renaming them to iteration-position and iteration-size. 15:11:30 +1 to that 15:11:32 Accepted. 15:11:39 Topic: Proposal to add p:directory-list 15:11:39 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/0007.html 15:12:30 Norm wonders if his revised proposal addresses the concerns raised last week. 15:12:36 Alex: I had security concerns. 15:13:11 Norm: I attempted to address that by saying the step could raise a dynamic error. 15:14:24 Alex: I also wanted the results to be given as a URI relative to the base URI. 15:14:40 ...What I want is to be able to pass the output of this to XSLT and be able to take the href and the right thing will happen. 15:15:37 Norm: I made the paths absolute so it wouldn't be an issue. 15:15:55 Alex explains how he wants relative URIs to some base. 15:16:44 q+ to take into the discussion the fact that the result of p:directory should be usable with p:load 15:17:11 Norm expresses concerns about the user having to construct the absolute path. 15:18:02 15:18:27 15:19:04 Some further discussion about file: as the default. 15:19:09 15:19:11 15:19:12 15:19:14 15:19:15 15:19:17 15:19:56 Norm concedes that he's wrong. 15:20:50 We don't have AVTs, MoZ! 15:22:02 15:22:03 15:22:05 15:22:06 15:22:08 15:22:09 15:22:11 15:22:12 15:23:15 Richard: I think we should try to make this work in as many environments as possible. 15:23:39 ...It follows that p:directory-list might not return file: URIs. So it should always put the file: on the front. 15:24:02 Norm: Let's consider the proposal as amended to say that the path names are absolute URIs. Usually file: but not necessarily. 15:24:40 Richard: I can imagine both absolute and relative URIs being useful. 15:25:46 Norm: I propose then that c:directory set xml:base and provide both path and filename. One absolute, one relative. 15:25:55 Mohamed asks about the absoluteize step. 15:26:00 Norm agrees we could do that. 15:26:12 Richard: I propose that the 'path' attribute be spelled 'uri'. 15:26:45 Richard: And for the recursive case? 15:26:52 Norm: I don't know what to do about symbolic links. 15:27:27 Richard: I don't think we should do anything about symbolic links. 15:27:38 Norm: So you want to treat them as files, not directories. 15:28:35 Richard: I think this thing should not follow any symbolic links. 15:29:45 Norm: I'm perfectly happy to say that what happens if you have a loop in the directory structure is implementation-dependent. 15:30:44 More discussion of symoblic links 15:30:49 s/symoblic/symbolic/ 15:31:50 Richard: Perhaps we should have an "other" element that identifies things that are neither files nor directories, with some sort of a detail attribute. 15:32:47 Richard: Do we have a use case for the recursive version? 15:33:27 Norm: We could leave the recursive option out for V1. Wouldn't bother me. 15:34:21 Mohamed: Can we change the semantics, maybe we don't need a recursive option; just something that can go to any number of levels. 15:34:41 Norm: We could have a 'depth' option instead of a 'recursive' option. 15:35:04 zakim, flip a coin 15:35:04 I don't understand 'flip a coin', Norm 15:36:22 Alex: We decided not to support prev/next in Atom in V1, I think we should drop recursion, it's very similar. 15:36:38 Norm: Yes, I agree. So let's leave recursion and depth out for at least the first draft in which this appears and see what users say. 15:37:09 Richard: I'd be happy with that. There's still the possibility of file systems having things aren't either files or directories. 15:38:57 Norm: I suggest we allow c:other and let implementors use extension attributes to specify what it is. 15:39:07 zakim, who is making noise? 15:39:18 MSM, listening for 10 seconds I heard sound from the following: 8 (22%), Norm (29%) 15:39:30 zakim, who's here? 15:39:30 On the phone I see PGrosso, MoZ, Norm, avernet, richard, MSM, Andrew, Alex_Milowski 15:39:33 On IRC I see alexmilowski, Andrew, richard, MoZ, RRSAgent, Norm, Zakim, PGrosso, avernet, MSM 15:39:33 ACTION: Alex to write up p:directory-list for the next draft. 15:39:41 Topic: Proposal to default step and port 15:39:41 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/0009.html 15:40:04 Norm: I don't think there's much more to be said beyond what I wrote in the email. 15:40:24 Alessandro: I don't feel strongly, but I think we should limit the number of syntactic shortcuts we provide. 15:40:56 zakim, who is making noise? 15:41:06 MSM, listening for 10 seconds I heard sound from the following: 8 (29%), Norm (4%) 15:41:07 I'm ok with this proposal. 15:41:11 Mohamed: I think this one is valuable because it means you don't have to name some steps. 15:41:25 ...But I think we need to make sure there are no ambiguous cases. 15:41:55 Norm: I don't think there are any ambiguities. 15:42:13 Richard: I think we shouldn't bother, I think there are only a small number of cases where it would be useful. 15:42:23 zakim, mute 8 15:42:23 sorry, richard, I do not know which phone connection belongs to 8 15:42:23 Norm: I detect consensus to not add this feature. 15:42:29 zakim, mute 7 15:42:29 sorry, richard, I do not know which phone connection belongs to 7 15:42:41 zakim, who's on the phone? 15:42:41 On the phone I see PGrosso, MoZ, Norm, avernet, richard, MSM, Andrew, Alex_Milowski 15:42:52 Resolved: No change, we will not adopt this feature. 15:42:58 Topic: Proposal to add p:generate-simple-document and p:set-attribute. 15:42:58 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/0017.html 15:43:25 Mohamed: A lot of components that we have take as inputs documents. 15:43:32 (All of them, no?) 15:43:49 Mohamed: Consider insert which inserts a whole document. But we can't construct a document from an option. 15:44:27 ...I think we need an easy way to construct a document from an option or parameter. 15:44:36 Alex: Can't you use a parameter and select the value of the option. 15:44:48 Mohamed: Yes, you can go that way, but you can't go the other way. 15:45:29 Alex: I can set a parameter from an option value; and then I can use the p:parameters step to output that as a document. 15:46:03 Norm: Hey, that's right. p:generate-simple-document is a funky alias for p:parameters. 15:46:27 Alex: To add attribute, I'd need two steps: I'd have to take the option, put it into a parameter, then run it through XSLT to generate the right kind of document for p:set-attributes. 15:46:37 Richard: How much of this can easily be done with XSLT and literal stylesheets? 15:47:19 Alex: I think generate-simple-document is easy, but add-attribute would require a couple of steps. 15:47:47 Norm: add-attribute does seem like a natural parallel to set-attributes 15:48:29 Some discussion of how they differ 15:48:45 Alex: Set-attributes takes all its options from documents; add-attribute would take it directly as parameters. 15:49:21 Norm: So add-attribute is just a shortcut for the parameter/xslt/set-attribute combination. 15:49:35 Richard: if the only distinction is where the values come from, I don't like the names. 15:50:23 Mohamed: Where are we going to stop inventing atomic components? 15:50:54 ...I found lots of use cases where I needed to add or change an attribute, but not many use cases where I needed to set whole groups. 15:51:09 Norm: We're going to stop when we have consensus to stop. 15:51:20 ...We don't have any hard-and-fast rules. 15:51:35 Alex: The set-attributes use cases is the streaming navigation use case from our Use Case/Requirements document. 15:52:31 Norm: The fact that add-attribute can only set one attribute is what bothers me. 15:53:20 Richard: I think it's quite common. I am concerned about adding random functions as we think of them; it would be nice if we could have a more principled approach. 15:53:33 EXPROC 15:53:52 Yes, implementors can certainly do it. 15:54:56 Richard: I think we'll get more input when we get to last call. 15:55:05 Alex: I'm inclined to wait and see if users find set-attributes too heavy. 15:55:53 zakim, who's on the phone? 15:55:53 On the phone I see PGrosso, MoZ, Norm, avernet, richard, MSM, Andrew, Alex_Milowski 15:56:05 zakim, pick a victim 15:56:05 Not knowing who is chairing or who scribed recently, I propose Alex_Milowski 15:56:13 Straw poll: Add p:add-attribute or not. 15:57:17 Seven "Yes" votes and "1" absention. 15:57:35 ACTION: Alex to add p:add-attribute. 15:57:48 Topic: Proposal to add p:pack 15:57:48 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/thread.html 15:58:54 Mohamed explains the idea behind p:pack 15:59:29 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Aug/0011.html 16:00:19 Richard: This takes a number of ports, each of which has a sequence on it. 16:01:08 Norm: Ouch; we don't have port="*" anymore 16:02:39 Mohamed: I think it would be ok if the step could just take two sequences. 16:03:19 Norm: If you only have two of them, you can do it with p:for-each. 16:05:00 Norm notices that we've run out of time. I suggest we discuss this in email and return to it next week. 16:05:05 Topic: Any other business? 16:05:11 Adjourned. 16:05:18 -Andrew 16:05:19 -avernet 16:05:20 -PGrosso 16:05:21 -Norm 16:05:22 -richard 16:05:22 -MoZ 16:05:29 -MSM 16:05:31 exproc.org is already registered! 16:05:43 -Alex_Milowski 16:05:44 XML_PMWG()11:00AM has ended 16:05:46 Attendees were +43.56.aaaa, Norm, PGrosso, MoZ, avernet, richard, MSM, Andrew, Alex_Milowski 16:05:51 rrsagent, set logs world-visible 16:05:55 rrsagent, draft minutes 16:05:55 I have made the request to generate http://www.w3.org/2007/08/02-xproc-minutes.html Norm 17:08:15 Norm has joined #xproc 17:41:36 Norm has joined #xproc 17:58:52 Zakim has left #xproc 17:59:01 rrsagent, bye 17:59:01 I see 2 open action items saved in http://www.w3.org/2007/08/02-xproc-actions.rdf : 17:59:01 ACTION: Alex to write up p:directory-list for the next draft. [1] 17:59:01 recorded in http://www.w3.org/2007/08/02-xproc-irc#T15-39-33-1 17:59:01 ACTION: Alex to add p:add-attribute. [2] 17:59:01 recorded in http://www.w3.org/2007/08/02-xproc-irc#T15-57-35