IRC log of xproc on 2008-10-24

Timestamps are in UTC.

07:33:13 [RRSAgent]
RRSAgent has joined #xproc
07:33:13 [RRSAgent]
logging to http://www.w3.org/2008/10/24-xproc-irc
07:33:14 [Zakim]
Zakim has joined #xproc
07:33:28 [Norm]
Topic: Reviewing use cases and requirements
07:35:30 [alexmilowski]
alexmilowski has joined #xproc
07:37:04 [Vojtech]
Vojtech has joined #xproc
07:43:24 [Norm]
Henry: With respect to 5.19, we found it useful to have a filter on input, so that you can say that the pipeline begins by processing *its* input with a filter and then proceeds.
07:46:54 [Norm]
Henry: A use case that I had to implement was "here comes a document, it's a product-database-related document, there's a key field in this, you need to look up this field, if it exists in the database, you add the attribute, otherwise, add it to the database.
07:47:04 [Norm]
(This is with respect to 5.20)
07:51:06 [Norm]
ACTION: Norm to check with Erik Bruchez about use case 5.24
08:07:40 [Norm]
Some discussion of the NVDL steps.
08:07:49 [Norm]
http://lists.dsdl.org/dsdl-comment/2008-09/0048.html
08:36:51 [Norm]
Some discusssion of versioning. We can ask what XPath version we have, but not what XSLT version.
08:37:07 [Norm]
Alex argues in favor of being able to check versions of XSLT, Schema Validation, etc.
08:37:30 [Norm]
Henry proposes an XML document that lists all the steps and the supported versions of each.
08:50:17 [ht]
ht has joined #xproc
09:41:23 [Norm]
In short: all but a very small number of the use cases are satisfied by XProc V1.0
09:57:08 [Zakim]
Zakim has left #xproc
10:06:55 [Norm]
Henry: Propose that the editor produce a CR draft.
10:07:12 [Norm]
Accepted.
10:07:32 [Norm]
ACTION: Norm to produce a CR draft.
10:07:39 [Norm]
Topic: CR exit criteria
10:08:42 [Norm]
Henry: The ideal would be one of two things: one is a very carefully annotated issues list that shows we've dealt with all the CR comments and we have buyin from everyone reasonable and everyone we don't have buyin is unreasonable.
10:09:05 [Norm]
...And the other is an implementation report that shows three complete implementations of every feature.
10:09:15 [Norm]
...The bare minimum is two implementations of every feature.
10:16:20 [Norm]
Norm: Do we need a timetable?
10:16:49 [Norm]
Henry: Yes, we're being rechartered, so we should have a plan for getting to Rec and it better be before December, 2009.
10:18:45 [Norm]
Henry: Aim to publish a CR draft in the middle of November, and set the CR period to end on 1 March.
10:21:42 [Norm]
Topic: Default XML Processing Model
10:24:21 [Norm]
Henry: There are two lines of potential exploration: One is that the XML spec itself leaves certain choices to the processor (e.g., external parameter entity references are expanded)
10:25:05 [Norm]
...And what that means is when you publish an XML document on the web, the question is, what are you held to. What is the document that is what you published? Or what is the infoset?
10:26:22 [Norm]
...The objective question that lurks behind it is, if there are entity references defined in an external parameter entity, and your parse doesn't retrieve them, are you bound by the statements present in the document when they involve unknown entity references.
10:26:30 [Norm]
...By the same token, what about XInclude processing.
10:27:14 [Norm]
Henry: The infoset spec explicitly declines to answer the question of what is an XML document. Nor does the spec.
10:27:44 [Norm]
Henry: The other line is this notion of the recursive, compositional semantics of XML documents.
10:28:39 [alexmilowski]
alexmilowski has joined #xproc
10:30:28 [Norm]
Some discussion of what the default might be...
10:30:57 [Norm]
Henry: Another approach is, should we be talking about a third component to the XML media types. When you fetch a document, you can say, I want the 0 model, the 1 model, or the 2 model.
10:31:17 [Norm]
...Where the 0 model means what the parser gives you, the 1 model gives you XInclude, the 2 model gives you XInclude/validation model, etc.
10:31:30 [Norm]
...Another model says that you should be able to put a pipeline in a URI.
10:38:29 [Norm]
Consensus seems to be forming around the idea that the defalut XML Processing Model is normal XML parsing (with some constraints like, always chase external parameter entities for entity declarations), followed by XInclude.
10:45:27 [Norm]
Topic: Any other business?
10:49:03 [Norm]
Some discussion of the expectation of schema-location hints and what the defaults should be for try-namespaces= and use-schema-location=
11:01:29 [Norm]
There's some desire to have a consistent story around schema-location hints and schemas that arrive on the schemas pot.
11:01:32 [Norm]
s/pot/port/
11:01:49 [Norm]
But it's not clear how implementations can support that.
11:02:35 [Vojtech]
Vojtech has joined #xproc
11:06:32 [Norm]
Not clear what resolution we came to.
12:00:23 [MoZ]
MoZ has joined #xproc
12:13:45 [Norm]
Norm has joined #xproc
12:15:14 [alexmilowski]
alexmilowski has joined #xproc
12:15:18 [Norm]
RRSAgent, set logs world visible
12:15:18 [RRSAgent]
I'm logging. I don't understand 'set logs world visible', Norm. Try /msg RRSAgent help
12:15:25 [Norm]
RRSAgent, set logs world-visible
12:15:37 [Norm]
RRSAgent, draft minutes
12:15:37 [RRSAgent]
I have made the request to generate http://www.w3.org/2008/10/24-xproc-minutes.html Norm
12:16:14 [alexmilowski]
alexmilowski has left #xproc
12:26:39 [ht]
ht has joined #xproc
13:12:55 [MoZ]
MoZ has joined #xproc
14:13:32 [MoZ]
MoZ has joined #xproc
14:32:51 [MoZ]
MoZ has joined #xproc