14:06:16 RRSAgent has joined #ixml 14:06:16 logging to https://www.w3.org/2021/06/08-ixml-irc 14:06:32 john has joined #ixml 14:06:34 Meeting: ixml monthly meeting 14:06:39 Chair: Steven 14:06:53 Agenda: https://lists.w3.org/Archives/Public/public-ixml/2021Jun/0000.html 14:07:01 Date: 8 June 2021 14:07:07 rrsagent, make minutes 14:07:07 I have made the request to generate https://www.w3.org/2021/06/08-ixml-minutes.html Steven 14:08:14 Present: Aleksei, John, Michael, Steven 14:08:32 Topic: Previous Actions 14:08:53 ACTION: Steven to research where to put S for attributes. 14:08:53 Sorry, but no Tracker is associated with this channel. 14:08:59 Constinues 14:09:33 Action: Michael to comment on conformance section of new draft 14:09:33 Sorry, but no Tracker is associated with this channel. 14:09:35 DOne 14:09:49 Action: Steven to apply Michael's text to spec 14:09:49 Sorry, but no Tracker is associated with this channel. 14:10:02 [Done] 14:10:11 Steven: Not yet pushed to github 14:10:49 https://homepages.cwi.nl/~steven/ixml/ixml-specification.html 14:11:09 Steven: Please check. 14:11:33 https://lists.w3.org/Archives/Public/public-ixml/2021Apr/0040 14:12:09 Steven: I don't think we answered those questions; not added to the spec. 14:13:01 ... two questions unanswered there: code points, and grammars 14:13:43 MSM: I am confident that the spec should have a story if input doesn't obey the rules, it should be clear if it should be flagged as an error, or be 'undefined'. 14:14:17 šŸ‘‹ from toronto canada 14:15:13 ... if it must 'raise an error', then it protects us from future changes to the spec. 14:15:40 ... I asked what SQL does, they said behaviour is undefined. 14:15:47 found this channel in https://w3c.github.io/cg-monitor/ 14:16:17 .. which allows processors to add their own features. 14:16:47 Steven: I'm a big fan of letting the user know (i.e. error) 14:16:58 MSM: I'm ok with that. 14:19:55 MSM: hex values MUST indicate an assignable unicode character. 14:23:39 rrsagent, make minutes 14:23:39 I have made the request to generate https://www.w3.org/2021/06/08-ixml-minutes.html Steven 14:23:58 Present+Tomos 14:24:24 Stevven: And that is to protect output from nonsense Unicode sequences 14:24:49 ACTTIN: MSM to check conformance text in spec 14:24:57 s/vv/v/ 14:25:19 s/ACTTIN/ACTION/ 14:25:33 Steven: All other actions continue 14:25:50 Topic: Namespaces/Text injection 14:26:54 Steven: Thanks for the new suggestions. I suggest that we create requirements for the next version, just to get a first version out of the door. 14:27:24 MSM: If we provide for declaration of namespaces, then namespace qualified elements and attributes just use a QName 14:27:49 ... and then use a pragma/structured comment for the actual binding 14:28:05 ... not local bindings 14:28:15 ... NS injection may be easy. 14:28:49 ... For text injection, the grammar has the same declarative meaning. 14:29:00 ... it's the mirror image of the minus marker 14:29:12 ... which gives it a certain appeal 14:29:31 John: ANd that could happen in any rule. 14:29:36 s/AN/An/ 14:30:28 MSM: "Is it possible to create a nondeterministic grammar?" 14:31:03 Steven: Inserted text has no effect on the parse, only on the serialisation 14:31:44 ACTIoN: MSM to check conformance text in spec 14:31:44 Sorry, but no Tracker is associated with this channel. 14:32:08 https://lists.w3.org/Archives/Public/public-ixml/2021Jun/0004.html 14:32:23 Tom has joined #ixml 14:32:32 https://lists.w3.org/Archives/Public/public-ixml/2021Jun/0004.html 14:34:34 Tom: I like suggestion 3.2 14:36:17 MSM: The aim is to target to a particular vocab, except it requires more. Getting
    is easy, but is not 14:37:29 Tom: I would like plusses on nonterminals as well as terminal text. 14:39:12 MSM: We don't need it. There is a way to do that. 14:39:40 Tom: If we expect users to understand "+", we should make it do the same thing. 14:41:17 Steven: We dont need plus on a nonterminal, because they are already plussed. 14:42:00 MSM: It is like the ^ symbol. 14:42:59 Tom: Plus feels right. 14:45:06 Steven: We have the QNames, just not the bindings for namespaces 14:46:16 Aleksei: We want to avoid clashes between grammars. If we use qnames in ixml, it will fix the prefix in the grammar 14:48:12 If Iā€™m reading the spec correctly, colon is not currently allowed in names. 14:48:25 Steven: YOu may be right 14:48:31 s/YO/Yo/ 14:48:52 Adding it will require some rewriting, to prohibit colon as a final character (if we want to match the rule in xml-names). 14:49:06 Tom: As long as there are bindings, it's ok. 14:50:11 MSM: Let's agree on + 14:50:16 ... postpone namespaces 14:50:19 Tom: Agree 14:50:46 RESOLUTION" adopt 3.2 "Use a + for inserting text" 14:50:54 RESOLUTION: adopt 3.2 "Use a + for inserting text" 14:54:01 Topic: Resolving ambiguity 14:54:36 Steven: You can always fix it by writing an unambiguous grammar. 14:54:54 MSM:: We have closed this issue. Steven has an action. 14:55:17 s/::/ 14:55:27 s/MSM/MSM:/ 14:56:15 MSM: If there is more than one tree, the processor can return any one and is not obliged to explain its choice 14:58:19 Topic: Next meeting 14:58:30 6 July 2021 usual time 14:59:04 rrsagent, make minutes 14:59:04 I have made the request to generate https://www.w3.org/2021/06/08-ixml-minutes.html Steven 14:59:36 Tom has joined #ixml 14:59:36 john has joined #ixml 14:59:36 cmsmcq has joined #ixml 14:59:36 Steven has joined #ixml 14:59:36 liam_ has joined #ixml 14:59:36 join_subline has joined #ixml 15:11:18 rrsagent, make logs public 15:11:44 rrsagent, make minutes 15:11:44 I have made the request to generate https://www.w3.org/2021/06/08-ixml-minutes.html Steven 15:13:46 s/DOne/Done/ 15:15:03 rrsagent, make minutes 15:15:03 I have made the request to generate https://www.w3.org/2021/06/08-ixml-minutes.html Steven 17:21:38 cmsmcq has joined #ixml