IRC log of ixml on 2022-02-22

Timestamps are in UTC.

15:12:41 [RRSAgent]
RRSAgent has joined #ixml
15:12:41 [RRSAgent]
logging to https://www.w3.org/2022/02/22-ixml-irc
15:12:50 [Steven]
rrsagent, make logs public
15:13:06 [Steven]
Date: 22 Feb 2022
15:14:03 [john]
Scribe: john
15:14:10 [john]
Chair: Steven
15:14:19 [john]
Meeting: Invisible XML community group call
15:14:25 [john]
Agenda: https://lists.w3.org/Archives/Public/public-ixml/2022Feb/0179.html
15:14:33 [john]
Previous meeting: https://www.w3.org/2022/02/15-ixml-minutes.html
15:14:40 [Steven]
rrsagent, make minutes
15:14:40 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/22-ixml-minutes.html Steven
15:17:51 [john]
present: Steven, john
15:19:05 [Steven]
rrsagent, make minutes
15:19:05 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/22-ixml-minutes.html Steven
15:21:55 [john]
present+: cmsmcq
15:23:05 [Steven]
rrsagent, make minutes
15:23:05 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/22-ixml-minutes.html Steven
15:26:37 [tovey-walsh]
tovey-walsh has joined #ixml
15:27:13 [john]
present+ tovey-walsh
15:27:51 [Tom]
Tom has joined #ixml
15:28:02 [john]
present+ Tom
15:30:52 [john]
topic: Review of Actions
15:31:39 [john]
MSM renamed grammars to sample in the demo folders
15:32:12 [john]
Prefix parsing actions completed - conformance of processors in spec.
15:32:26 [john]
Topic: Status of implementations
15:33:03 [john]
NDW now passing all tests, MSM passing most, but not all, improved by having time-out in his test harness!
15:33:51 [john]
Steven: what about the time taken to parse iXML - NDW about 13s, MSM about 7 minutes
15:34:30 [john]
NDW: Lauren approved the introductory iXML article by NDW on XML.com
15:35:26 [john]
Topic: Review of issues
15:36:08 [john]
Test case issues (#24,-#42) generally resolved
15:36:29 [Steven]
https://github.com/invisibleXML/ixml/issues/44
15:36:35 [john]
Subtopic: Issue #44 error codes
15:38:55 [john]
MSM - error code overlaps could be an issue - checking correct error cases could be crucial
15:39:29 [john]
NDW: what are we going to use as error code forms?
15:40:00 [john]
s/MSM -/MSM: /
15:40:53 [john]
Tom: What categories of error are we going to encounter?
15:42:18 [john]
Not clear whether warning 'codes' will be useful or problematic
15:42:31 [Tom]
“we won’t know until we have a collection of errors”
15:42:48 [john]
Steven: we already have some classes, such as parsing, input etc...
15:45:07 [john]
Action: NDW to make a proposal for possible error codes
15:46:44 [john]
Steven: Errors in an appendix - but it all needs to be held in a coherent form
15:51:12 [john]
Subtopic: non-XML output
15:53:14 [john]
MSM: Issue #18 - non-XML names - required to flag on dynamic, but not when the possible error is not exercised
15:54:26 [john]
... the same for the other cases (#23, #31, #47)
15:55:30 [john]
... some possible overlap with those error codes for an XML parser
15:56:11 [john]
NDW: hasve a 'non-XML' catchall behind finer codes
15:56:21 [john]
s/hasve/have/
15:57:23 [john]
Action: Steven to outline examples in the spec. to differentiate static and dynamic errors
16:01:04 [john]
Issue #23 is a dynamic error for non-XML in the output... this would not be the case for JSON or other formats, but are they central to our technological approach
16:01:59 [john]
Tom: think about whether we want to make it easier for future possibilities in the non-XML output state
16:03:22 [john]
Resolved: non-XML element names shall be signalled as a dynamic error
16:03:55 [john]
Resolved: multiple attributes of the same name shall be a dynamic error
16:06:54 [Tom]
Tom has joined #ixml
16:08:10 [Steven]
The first rule in a grammar may not be marked as an attribute. If it is marked as hidden, all of its productions must produce exactly one non-hidden non-attribute nonterminal and no non-hidden terminals before or after that nonterminal.
16:08:21 [john]
Action: Steven - Issue #47 - @root (Outermost effective nonterminal as attribute) - to be proposed in the spec as a dynamic error.
16:11:42 [cmsmcq]
[One problem is that the constraint does not apply just to the children of the start symbol ...]
16:12:59 [john]
Tom: We may not need to go into this detail if we rely on 'you must produce valid XML'
16:14:05 [cmsmcq]
s/valid/well-formed/
16:17:17 [john]
Bethan:we're not considering post-processing here
16:20:04 [john]
Action: Steven - simplify the spec to require the output of 'well-formed' XML. Does that have some subcodes in terms of the violation of well-formedness
16:20:51 [john]
s/about i/about it/
16:23:55 [john]
Action: Steven Issue #33 (s = @a, b, @c) - this needs to be explicit
16:25:44 [john]
Action: NDW Issue #45 (Unused non-terminals) - NDW - two test suites - undefined and unused non-terminalsed and un
16:26:06 [john]
s/ non-terminalsed and un//
16:27:52 [john]
Some of these issues of unreachability etc might be indicative of 'hygiene' issues.
16:28:32 [john]
Topic: Any other business
16:29:12 [john]
Next meeting: 1st March
16:30:45 [john]
Bethan: should terminology be deinfed in the spec, or in another document?
16:31:00 [john]
s/deinfed/defined/
16:32:06 [Steven]
rrsagent, make minutes
16:32:06 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/22-ixml-minutes.html Steven
16:32:14 [john]
Agenda item - Bethan on terminology
16:33:40 [Steven]
Parsing ixml with my processor:
16:33:41 [Steven]
real0m14.176s
16:33:41 [Steven]
user0m14.164s
16:33:41 [Steven]
sys0m0.016s
16:35:07 [Steven]
present+norm
16:35:13 [Steven]
rrsagent, make minutes
16:35:13 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/22-ixml-minutes.html Steven