IRC log of ixml on 2025-03-04
Timestamps are in UTC.
- 14:53:35 [RRSAgent]
- RRSAgent has joined #ixml
- 14:53:40 [RRSAgent]
- logging to https://www.w3.org/2025/03/04-ixml-irc
- 14:53:42 [norm]
- rrsagent, draft minutes
- 14:53:43 [RRSAgent]
- I have made the request to generate https://www.w3.org/2025/03/04-ixml-minutes.html norm
- 14:53:47 [norm]
- rrsagent, set logs world visible
- 14:54:23 [norm]
- Meeting: Invisible XML Community Group
- 14:54:26 [norm]
- Date: 4 March 2025
- 14:54:54 [norm]
- Regrets: Nico, Steven
- 14:54:57 [norm]
- Scribe: Norm
- 14:57:37 [john]
- john has joined #ixml
- 15:02:04 [norm]
- Present: John, David, Norm, Bethan
- 15:03:04 [norm]
- Present: +Fredrik
- 15:03:07 [norm]
- rrsagent, draft minutes
- 15:03:08 [RRSAgent]
- I have made the request to generate https://www.w3.org/2025/03/04-ixml-minutes.html norm
- 15:03:44 [norm]
- Present: John, David, Norm, Bethan, Fredrik
- 15:04:27 [norm]
- Chair: Norm (pro tem)
- 15:04:33 [norm]
- Topic: Accept the minutes of the previous meeting
- 15:04:48 [norm]
- Accepted.
- 15:04:56 [norm]
- Topic: Review of open actions
- 15:04:59 [norm]
- No progress.
- 15:05:04 [norm]
- Topic: Status reports
- 15:07:02 [norm]
- Norm: I got NineML 3.2.9, includes an attempt to provide better diagnostics on failed parses.
- 15:07:21 [norm]
- John: I've done something similar with my parser, it shows you the open rules.
- 15:08:00 [norm]
- ... The real problem is when you have ambiguity as well.
- 15:08:24 [norm]
- Bethan: Even when you have ambiguity, the failure comes at a particular point in the parse. You can't be parsing more than one thing.
- 15:08:48 [norm]
- John: There are two cases, one is a failure in the middle of the input. There's nothing else that can be predicted. That might be under a number of different branches.
- 15:09:11 [norm]
- ... The other one is where you got to the end of the input and there's nothing left. What was supposed to come next?
- 15:10:04 [norm]
- Bethan: What I'm interested in working on are tools that will treat your grammar as a generator rather than a recognizer.
- 15:10:14 [norm]
- ... So that you can for fairly small grammars generate a sample of what is recognized.
- 15:10:25 [norm]
- ... So you can look at that and go "Uh, no, not that!"
- 15:10:59 [norm]
- ... Sometimes it can be very helpful to walk through a regular expression, for example, and recount what could be matched.
- 15:11:08 [norm]
- ... That process of talking through is a process of generating from the regular expression.
- 15:11:17 [norm]
- John: Can you do this from any grammar without ambiguity?
- 15:11:28 [norm]
- Present: John, David, Norm, Bethan, Fredrik, Jim
- 15:11:35 [norm]
- Some discussion of generators.
- 15:13:05 [norm]
- Bethan: I'm also interested in trying to work out what a grammar might be *trying* to match: phone numbers, UK post codes, etc.
- 15:13:25 [norm]
- ... And then point people to versions of those grammars.
- 15:13:45 [norm]
- Fredrik: I've been thinking about rendering parts of the graph when a parse fails.
- 15:15:02 [norm]
- Bethan: I wonder if we can make something like Guther's railroad diagrams; or maybe overlapping circles, some way to indicate what belongs to what and what is partial.
- 15:16:50 [norm]
- John: Starting to find users finding really weird errors which is nice.
- 15:19:47 [norm]
- Some discussion of the origins of the test case that demonstrated the problem of non-XML output (a single text node)
- 15:20:45 [norm]
- John: It's worth making people aware that record-oriented can produce output that isn't well formed.
- 15:21:35 [norm]
- Fredrik: With the current state of the parsers, it's very expensive to parse a huge file. It's more efficient to do it in a record-oriented way.
- 15:22:20 [norm]
- Bethan: One of the things I've been thinking about recently is that we have a bunch of dynamic errors that are things like there not being a single root node, or two attributes with the same name on the same element.
- 15:22:33 [norm]
- ... Earlier the spec says that conformance is about processors and grammars, not the combination of a grammar and in input.
- 15:22:53 [norm]
- ... That being the case, I think these should be static errors on the grammar; not errors that are only thrown if a particular input produces not-well formed XML.
- 15:23:02 [norm]
- ... I'm convinced you can do it.
- 15:23:25 [norm]
- John: Take the case of duplicated attributes, it depends on the input if that's the case.
- 15:23:49 [norm]
- ... If you said that it was a static error, that would be a problem.
- 15:24:00 [norm]
- Fredrik: Do you have an example?
- 15:24:28 [norm]
- Bethan: I think a single root element is relatively easy to work out; but suppressed elements make it a little harder.
- 15:24:59 [norm]
- ... I think we should think about removing the statement from the spec or we should talk about changing those to static errors.
- 15:25:32 [norm]
- Fredrik: I sort of agree, but I think it might be easy to create a grammar that will create a root node or not. And that's entirely dependent on the input.
- 15:25:57 [norm]
- Bethan: I think the spec implies that if a grammar could produce not well-formed XML, the grammar isn't conformant.
- 15:26:10 [norm]
- John: Does that not imply that the universe of inputs is infinite?
- 15:26:38 [norm]
- Some further discussion of what this analysis would look like.
- 15:28:47 [norm]
- ACTION: Bethan to review the dynamic errors and see which ones might possibly be resolved statically.
- 15:32:11 [norm]
- Topic: Issue #294, “parse tree” is not defined in the specification
- 15:32:29 [norm]
- Norm: Let's wait for Steven.
- 15:32:32 [norm]
- Topic: Perspectives on serialization
- 15:33:13 [norm]
- Norm: Wait for Steven
- 15:33:25 [norm]
- Norm: Should I try to improve that though?
- 15:33:49 [norm]
- Thumbs up, consensus that it's worth making another pass to improve it.
- 15:34:30 [norm]
- Topic: Next meeting
- 15:35:18 [norm]
- No regrets given.
- 15:35:43 [norm]
- Topic: Any other business
- 15:35:46 [norm]
- None heard.
- 15:40:29 [norm]
- rrsagent, draft minutes
- 15:40:31 [RRSAgent]
- I have made the request to generate https://www.w3.org/2025/03/04-ixml-minutes.html norm
- 15:41:35 [norm]
- s/No regrets given./18 March. Note that will be 1 hour later in the US. No regrets heard./
- 15:41:41 [norm]
- rrsagent, draft minutes
- 15:41:42 [RRSAgent]
- I have made the request to generate https://www.w3.org/2025/03/04-ixml-minutes.html norm
- 17:20:27 [norm]
- norm has joined #ixml
- 17:20:45 [norm]
- s/Guther/Gunther/
- 17:20:50 [norm]
- rrsagent, draft minutes
- 17:20:52 [RRSAgent]
- I have made the request to generate https://www.w3.org/2025/03/04-ixml-minutes.html norm