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