15:49:44 RRSAgent has joined #xproc 15:49:44 logging to http://www.w3.org/2007/11/15-xproc-irc 15:54:59 ruilopes has joined #xproc 15:55:53 Meeting: XML Processing Model WG 15:55:53 Date: 15 November 2007 15:55:53 Agenda: http://www.w3.org/XML/XProc/2007/11/15-agenda 15:55:53 Meeting: 92 15:55:53 Chair: Norm 15:55:54 Scribe: Norm 15:55:56 ScribeNick: Norm 15:57:09 Regrets: Paul, Mohamed 15:58:15 avernet has joined #xproc 16:00:09 XML_PMWG()11:00AM has now started 16:00:16 +Norm 16:02:16 zakim, please call ht-781 16:02:16 ok, ht; the call is being made 16:02:17 -Norm 16:02:19 +Norm 16:02:20 +??P26 16:02:32 zakim, ? is avernet 16:02:32 +avernet; got it 16:02:39 +??P21 16:02:55 Zakim, ??P21 is richard 16:02:55 +richard; got it 16:03:00 richard has joined #xproc 16:03:02 Zakim, who's on the phone? 16:03:02 On the phone I see Norm, avernet (muted), richard 16:03:11 zakim, please call ht-781 16:03:12 ok, ht; the call is being made 16:03:12 +Ht 16:03:24 Zakim, unmute avernet 16:03:24 avernet should no longer be muted 16:03:29 +??P28 16:03:35 Zakim, ? is me 16:03:35 +ruilopes; got it 16:03:44 Zakim, who's on the phone? 16:03:44 On the phone I see Norm, avernet, richard, Ht, ruilopes 16:04:20 Zakim, who's talking? 16:04:32 Norm, listening for 10 seconds I heard sound from the following: richard (4%), avernet (56%) 16:05:12 -avernet 16:06:01 +??P20 16:06:05 zakim, ? is avernet 16:06:05 +avernet; got it 16:06:12 Andrew has joined #xproc 16:06:23 +Murray_Maloney 16:06:41 Present: Norm, Alessandro, Richard, Henry, Rui, Andrew, Murray 16:06:45 Zakim, who's on the phone? 16:06:45 On the phone I see Norm, richard, Ht, ruilopes, avernet, Murray_Maloney 16:07:06 +??P0 16:07:07 alexmilowski has joined #xproc 16:07:11 zakim, ? is Andrew 16:07:11 +Andrew; got it 16:07:17 I'll be on in just a second... 16:07:18 Present: Norm, Alessandro, Richard, Henry, Rui, Andrew, Murray, Alex 16:07:28 Topic: Accept this agenda? 16:07:28 -> http://www.w3.org/XML/XProc/2007/11/15-agenda 16:07:31 Accepted 16:07:37 Topic: Accept minutes from the previous meeting? 16:07:37 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Nov/0031.html 16:07:47 Accepted 16:07:56 Topic: Next meeting: telcon 29 November 2007 16:08:22 Alessandro gives regrets for 29 Nov 16:08:32 (Note that we are not meeting on 22 Nov!) 16:08:48 Topic: XPath versions 16:08:48 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Nov/0038.html 16:09:13 + +1.415.404.aaaa 16:09:38 Zakim, aaaa is alexmilowski 16:09:38 +alexmilowski; got it 16:10:12 Norm summarizes the state of play 16:10:43 Henry: The traditional schema group compromise seems appropriate: call attention to it in the next draft of the spec and ask for implementor feedback. 16:11:48 s/implementor/implementor and user/ 16:11:56 MoZ has joined #xproc 16:12:11 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Nov/0053.html 16:12:46 Alex: So we're going to allow for different answers in the two versions. 16:12:55 Norm: Yes, for now, with Henry's suggestion for priority feedback 16:14:08 Henry: The 99.99% case is when you're comparing strings in XPath 1, one of the strings will coerce to a number. In that case, you will get the same answer. 16:14:23 Murray: Why can't we settle on XPath 2.0 16:14:49 Henry/Richard: Because right now there are too many implementation communities where 1.0 is only available. 16:15:22 Murray: I think it'd be better to leave them behind than to possibly give different results. 16:15:46 Henry: The proposal as it stands includes the idea that we give authors guidance for interoperability. 16:16:13 ...It's extremely unlikely that the kinds of xpaths that don't interoperate will really turn up in practice. 16:16:28 ...I'd rather include the XPath 1.0 people in at the expense of that very small problem than exclude them to get rid of it. 16:17:20 Alex: Interoperability is more than just getting the same answer; there are also cases where the XPaths simply won't work on some implementations. 16:18:35 Norm: I think saying XPath 2.0 only would be a tactical error. 16:18:42 Murray: So can we say 1.0 only? 16:18:54 Norm: There are implementors that only plan to support 2.0. 16:19:17 Alex: I'm not sure that guiding authors to use some squishy middle ground is the right answer. 16:19:35 ...I think it'd be better to explain the interoperability probems. 16:19:38 s/probems/problems/ 16:20:41 Some discussion of the right interoperability story. 16:22:04 Henry: I'd like to see the editor try to write up the point that we arrived at. 16:22:42 Norm: Uh, I did that. 16:22:53 Alex: Do we want to allow the xpath-version attribute on any element? 16:24:02 Norm: I was thinking of cut-and-paste 16:24:18 ...But I'm perfectly happy to try putting it only on p:pipeline-library and p:pipeline 16:26:19 Some discussion of what the differences between 1.0 and 2.0 actually are 16:26:43 Richard: Should we just make it a static error to attempt to use XPath 2.0 with an XPath 1.0-only processor? 16:27:13 Henry: I'm happy with the silent attempt because it is amenable to conditional pipelines. 16:28:53 Murray: Back in the days when we were first talking about SGML on the web, one of the expressions that came up was "perverse obscurity". 16:29:05 ...This discussion of 1.0/2.0 corners is perverse obscurity. 16:30:05 Murray: We're setting up a situation where it is possible for pipelines to generate the wrong answer. 16:30:13 Henry: I think you're exhagerating the situation. 16:31:06 Norm: I think the number of cases where you're going to give the wrong answer is quite small. 16:31:55 Richard: Presumably users of XSLT 2.0 processors with XSLT 1.0 stylesheets are experiencing the same problems. 16:31:57 Norm: yes. 16:32:11 Henry: I've been doing this for years and I've never had a problem. 16:34:50 Norm: We could make XPath 1.0 compatibility mode a MUST for implementors 16:35:31 Richard: And we could say that XPath 1.0 implemntors MUST only run expressions that will give teh same result 16:36:56 Norm: Bah, I don't think I want to go there. 16:37:14 Henry: I sort of like this road; nobody loses, it's just that some people win more than others. 16:38:07 Henry: I think the spec should say that if someone asks for XPath 2.0 evaluation, your XPath 1.0 implementation MUST only evaluate those XPaths which they know have the same value. 16:38:23 Richard: And if yours doesn't know any, it must reject them all. 16:39:53 Norm: So we're going basically the route I outlined, but saying that 2.0 processor must implement 1.0 mode and a 1.0 processor must not evaluate any expression that it cannot determine will give the same result in XPath 2.0. 16:40:06 Richard: Can we find out what the subset is? 16:40:13 Alex: Maybe. There's an appendix in XPath 2.0 spec. 16:40:28 Proposed: Go forward as above for the next draft. 16:40:32 Accepted. 16:40:46 Topic: XSLT versions 16:40:46 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Nov/0016.html 16:42:21 Norm outlines his plan 16:42:23 Alex: I'm all for it. 16:42:45 Proposed: go this way for the next draft. 16:42:47 Accepted. 16:42:51 Zakim, what is the code ? 16:42:51 the conference code is 97762 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), MoZ 16:43:02 Topic: New public working draft 16:43:31 +MoZ 16:43:32 Norm: I think we need a new draft asap. 16:43:45 Richard: We also need the stuff about what types are in scope. 16:44:19 Norm: I'm happy to do the next draft with a fair number of "TBD" sectins. 16:44:24 s/sectins/sections/ 16:46:58 Proposed: editor will make a new public draft with the XPath/XSLT decisions and as many other decisions as possible to be published as soon as practical. 16:47:53 Accepted. 16:48:22 Topic: Other last call comments (implicit inputs/outputs; default bindings) 16:48:30 Topic: New step types (p:hash, p:uuid, p:www-form-url(en|de)code 16:48:57 Norm: Anyone object to putting those in the next draft? 16:49:10 Mohamed, do we have strong use cases for them 16:49:34 Norm: Yes, and they're optional anyway 16:49:52 Accepted. 16:50:03 Topic: Other last call comments (implicit inputs/outputs; default bindings) 16:50:51 -> http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Nov/0032.html 16:50:54 Norm summarizes 16:52:19 s/summarizes/summarizes the state of default bindings 16:53:33 Accepted. 16:55:23 Norm attempts to summarize the default input/output case. 16:57:07 See 2.3 in the 13 Nov editor's draft. 16:57:24 Accepted. 16:57:51 ACTION: Norm to change all the examples 16:58:15 Topic: Any other business 16:59:17 Henry: It occurs to me that wrt the visible step types, it's not completely clear whether we have schema rules or xslt rules. If I import something that imports something else, do I get to use what's in the third thing or not. 16:59:32 ...Richard and my prose supposes that the answer is yes. The current draft suggests that it's no. 16:59:56 ...And the message about circular imports clearly suggests that it's no. 17:00:09 Richard: I believe that Henry's message is right, modulo that fix. 17:00:28 Henry: I'd like to particularly encourage Alex to review it. 17:00:34 Alex: Right. Will do. 17:01:01 Adjourned 17:01:03 -alexmilowski 17:01:04 -ruilopes 17:01:05 -Norm 17:01:06 -avernet 17:01:07 -Ht 17:01:09 -Andrew 17:01:10 -richard 17:01:12 -MoZ 17:01:14 -Murray_Maloney 17:01:15 XML_PMWG()11:00AM has ended 17:01:16 Attendees were Norm, avernet, richard, Ht, ruilopes, Murray_Maloney, Andrew, +1.415.404.aaaa, alexmilowski, MoZ 17:01:20 RRSAgent, set logs world-visible 17:01:23 RRSAgent, draft minutes 17:01:23 I have made the request to generate http://www.w3.org/2007/11/15-xproc-minutes.html Norm 18:25:40 Zakim, bye 18:25:40 Zakim has left #xproc 18:25:41 RRSAgent, bye 18:25:41 I see 1 open action item saved in http://www.w3.org/2007/11/15-xproc-actions.rdf : 18:25:41 ACTION: Norm to change all the examples [1] 18:25:41 recorded in http://www.w3.org/2007/11/15-xproc-irc#T16-57-51