13:49:26 RRSAgent has joined #ixml 13:49:30 logging to https://www.w3.org/2023/10/03-ixml-irc 13:49:38 RRSAgent, make logs public 13:49:49 Meeting: ixml Group Teleconference 13:49:57 Date: 3 October 2023 13:50:02 Chair: Steven 13:50:47 Previous meeting: https://www.w3.org/2023/09/05-ixml-minutes 13:50:55 Agenda: https://lists.w3.org/Archives/Public/public-ixml/2023Oct/0000 13:51:40 rrsagent, make minutes 13:51:41 I have made the request to generate https://www.w3.org/2023/10/03-ixml-minutes.html Steven 13:54:56 john has joined #ixml 13:55:46 cmsmcq_ has joined #ixml 13:56:33 Hmm. I wonder why I am here twice 14:02:47 Present: Bethan, Norm, John, Michael, Steven 14:03:31 Michael: Nothing done, even the easy ones! 14:03:42 norm has joined #ixml 14:04:21 ACTION 2023-07-25-a: Norm to create an issue w.r.t. end of line 14:04:21 normalization: Done 14:04:55 Norm: All my actions done except publishing the reoprt 14:05:07 s/reoprt/report/ 14:06:02 John: Done ACTION 2023-07-25-c: JL to redraft his notes on grammar combination 14:06:02 and send something to the public list. 14:06:18 John: Done ACTION 2023-09-05-g: John to implement the renaming proposal 14:06:35 Topic: Status of implementations 14:06:45 John: Added renaming 14:07:15 ... works fairly well 14:07:29 ... Need to talk about "version" later 14:07:53 ... there are a number of symbols we haven't used, like % 14:08:10 ... we might want to bear in mind that they are available 14:10:07 Norm: Working on improve,emts 14:10:11 s/,// 14:10:22 Topic: Status of testing and test suites 14:10:40 John: Are there renaming tests? 14:10:41 We definitely do need tests for renaming. 14:11:03 ACTION: Norm create tests for renaming 14:12:02 Topic: Issue #199 Require whitespace between prolog and first rule? 14:12:46 Michael: It's not ambiguous, but we should do it for consistency 14:12:58 Steven: So resolved 14:13:41 ACTION: Steven to make pull request for grammar for space after prolog 14:14:26 Topic: Issue #197 Remove the Unicode non-character constraint 14:15:05 Norm: RFC for JSON, and they have a rule that includes non-unicode characters 14:15:53 "An encoded character is an optionally marked hexadecimal number. It starts with a hash symbol, followed by any number of hexadecimal digits, for example #a0. The digits are interpreted as a number in hexadecimal (error S06) , and the character at that Unicode code-point is used [Unicode]. The number must be within the Unicode code-point range (error S07), and must not denote a Noncharacter or Surrogate code point (error S08)." 14:17:54 Norm: I'm happy to say that you can't have them in Unicode, and you can't use them. 14:18:39 Michael: the ixml grammar of the JSON grammar can't then be a simple transcription. 14:20:28 Steven: We leave the spec as is then. 14:20:43 ACTION: Norm close issue 197 without changes 14:20:56 Norm: Should we have an FAQ? 14:21:14 Michael: A good idea. 14:23:34 Norm: You could create a range that is expressible, but that includes noncharacters... 14:24:48 Michael: But the input still can't contain those characters 14:24:56 Norm: I can live with that 14:25:36 ACTION: Michael draft a FAQ 14:28:05 Steven: The spec requires UTF-8 encoding, but doesn't explicitly restrict noncharacters 14:29:22 Michael: I think that our rules effectively mean that noncharacters are excluded 14:29:50 Steven: Except exclusions 14:30:00 ... would allow noncharacters 14:30:48 .... input: ~[]*. 14:32:01 ... input: -~[]*, +'.'. 14:32:53 Norm: I'd like to see what Michael writes in the FAQ. 14:33:20 Topic: Issue #189 What are the control characters 14:33:57 Norm: THis is resolved using character classes. We can close. 14:34:10 Topic: Issue #181 Non-serializable characters in the input 14:34:15 s/TH/Th/ 14:34:27 Norm: Has been closed 14:34:41 ... raises error D04 14:36:14 Topic: Issue #139 Sample grammars for IRIs and URIs 14:36:22 Steven: Where are we at? 14:36:48 Michael: Awaiting review 14:37:18 Steven: On the agenda for next time 14:38:09 Topic: Issue #192 Normalizing line endings in ixml inputs 14:38:47 John: Before that. About version 14:38:51 Topic: Version 14:39:08 John: Are the version numbers collatable? 14:39:17 ... is there a strict ordering 14:39:22 s/ing/ing? 14:39:39 Bethan: It would be good to agree a format 14:40:46 Norm: I'd rather put off the decision till when we have a versionable number 14:41:51 Michael: How about "Tokenise on '.', that is a sequence of keys, if a key is a number, then compare numerically, otherwise lexically 14:42:03 s/lexically/lexically"/ 14:42:20 Bethan: Rather just use numbers 14:43:12 Michael: Are we the only ones to create a version number? 14:43:18 Bethan: Yes. 14:43:35 John: Leave it on the backburner 14:44:39 Topic: Issue #13 Renaming proposal (for v.Next) 14:45:07 Steven: Nothing to discuss? 14:45:45 Norm: Merge? 14:45:49 All: Yes 14:45:58 Topic: Issue #192 Normalizing line endings in ixml inputs 14:46:44 Norm: 4 options. 14:46:50 ... it is a pain 14:47:36 Michael: I would like our abstraction to be that we are parsing unicode characters, without an abstraction on top of that. 14:48:05 ... normalising default is OK; require it to be disableable 14:48:31 ... I see uses cases for not normalising 14:49:09 John: So what do I write? 14:51:58 Steven: I was thinking of U+2028 14:52:10 ... line separator 14:52:47 Bethan: I like the idea 14:53:31 ... would it be in input anyway 14:53:35 Michael: Could be 14:55:28 Michael: We need a written proposal 14:57:04 Topic: AOB 14:57:29 Steven: Next meeting in 2 weeks 14:57:36 John: Regrets 14:58:10 [ADJOURN] 14:58:19 rrsagent, make minutes 14:58:20 I have made the request to generate https://www.w3.org/2023/10/03-ixml-minutes.html Steven 14:59:10 i/Michael: Nothing done, even the easy ones!/Topic: Actions 14:59:13 rrsagent, make minutes 14:59:14 I have made the request to generate https://www.w3.org/2023/10/03-ixml-minutes.html Steven 14:59:53 s/improveemts/improvements 16:54:38 cmsmcq_ has joined #ixml 16:54:49 cmsmcq has joined #ixml