15:06:44 RRSAgent has joined #ixml 15:06:44 logging to https://www.w3.org/2022/01/11-ixml-irc 15:06:50 trackbot has joined #ixml 15:09:09 trackbot, start telcon 15:09:09 Sorry, but no Tracker is associated with this channel. 15:09:23 RRSAgent, make logs public 15:09:34 Meeting: ixml Group Teleconference 15:09:51 Date: 11 January 2022 15:09:55 Chair: Steven 15:12:03 Agenda: https://lists.w3.org/Archives/Public/public-ixml/2022Jan/0061 15:14:51 john has joined #ixml 15:19:45 norm has joined #ixml 15:30:53 Present: Norm, John, Dave, Bethan, Steven 15:31:54 Present+Michael 15:32:05 Present+Tom 15:32:47 cmsmcq has joined #ixml 15:32:50 Topic: Actions 15:32:57 ACTION (2021-08-005): Tom and MSM to come with a pragma proposal. [Done] 15:32:57 Sorry, but no Tracker is associated with this channel. 15:33:12 ACTION (2021-10-001): Steven to draft a mediatypes proposal (see 15:33:12 Sorry, but no Tracker is associated with this channel. 15:33:12 https://github.com/invisibleXML/ixml/issues/6). 15:33:33 ACTION (2021-12-001): Steven to add his tests to github [Done] 15:33:33 Sorry, but no Tracker is associated with this channel. 15:33:41 Tom has joined #ixml 15:33:48 ACTION (2021-12-002): Michael to write test catalog for Steven's 15:33:48 Sorry, but no Tracker is associated with this channel. 15:33:48 tests [Done] 15:34:06 ACTION (2021-12-003): Steven to add strings proposal to spec [Done] 15:34:06 Sorry, but no Tracker is associated with this channel. 15:34:52 ACTION (2021-12-004): Steven implement the resolution for issue 19 [Done] 15:34:52 Sorry, but no Tracker is associated with this channel. 15:35:04 ACTION (2021-12-005): Steven implement resolution for issue 18 on XML 15:35:04 Sorry, but no Tracker is associated with this channel. 15:35:04 names. [Done] 15:35:44 Topic: Implementations 15:35:51 Norm: I'm writing my own parser 15:35:58 ... ongoing 15:36:19 bertje has joined #ixml 15:36:20 ... results for next month 15:36:46 Steven: I added a command-line way of calling 15:37:27 Tom: Jparser not yet highly performant 15:37:43 Dave: What should we expect by June? 15:37:52 Tom: At least two 15:38:15 Norm: I will have an implementation by June 15:38:31 s/Jparser/JayParser 15:38:34 ... integrated in XProc and Saxon 15:39:02 Michael: I have an implementation, not performant (yet). 15:39:11 ... faster by June 15:39:29 ... also planning Prolog version 15:39:47 Dave: What level confidence by June? 15:40:05 Michael: I am confident 15:40:36 Tom: Mine needs a rewrite, not sure if it will be ready by June 15:40:57 Steven: I'm confident with mine. 15:42:16 Dave: I am concerned with the stability of the spec for June release. 15:43:09 Topic: Pragmas proposal 15:44:13 Tom: We have spent some weeks on the proposal. 15:44:58 Michael: Basic requirement is that they say things to processors without interfering with other processors. 15:45:35 ... Syntactically distinct. Some way for processors to recognise whether they are being addressed. 15:45:48 ...l USes square brackets and namespaces. 15:45:57 s/I US/Us/ 15:46:39 ... Syntax is straightforward 15:47:43 Tom: We had an idea of using attributes for pragma data 15:48:06 Michael: Where do pragmas occur, and what do they mean? 15:52:07 ... identifying what pragmas need to do sets a minimum requirement. 15:53:46 ... I care about the XML representation of grammars, and so don't want pragmas to be wherever comments can be. 15:55:33 bertje has left #ixml 15:56:14 Steven: It sounds like this proposal is addressing use cases that should be separately addressed. 15:57:29 Michael: A pragma should be allowed to respond in any way it wants to pragmas, including stopping and starting a game. 15:57:36 Steven: I disagree. 15:58:29 Michael: I think you are right to be concerned. 15:58:32 ... 15:59:01 ... one of the things we want pragmas for is to provide a way to support functionality that hasn't been standardised. 16:00:03 ... extension behaviour allows you to gain experience. 16:00:17 Bertje has joined #ixml 16:01:01 ... conformance requirements mean that processors should be able to ignore all pragmas. 16:01:34 Dave: What should a non-pragma processor do with a pragma? 16:02:13 Michael: Not trip over them. 16:04:43 Steven: What would change if iso the [ we used for instance {! ? 16:05:10 Michael: It makes pragmas heavier. 16:05:46 Tom: I don't believe that should be a priority 16:06:42 Steven: I really don't like using the syntax for character sets for pragmas 16:07:18 Michael: FOr my use cases I want a single character for pragmas. 16:07:23 s/FO/Fo/ 16:08:26 Norm: we could have two representations, a single character unicode, and a multicharacter ascii. 16:08:34 Tom: I would like ASCII 16:09:30 John: When you're presenting the pragma data to the processor, you're parsing the rules 16:09:58 ... it's tempting to get structure inside the pragma. 16:10:08 ... but maybe it should be up to the processor 16:10:34 ... you can work with a reserved comment structure 16:10:45 ... as long as you can nest 16:11:06 Dave: It smells like a pre-parse 16:12:09 John: I find a prgam in my namespace, I pick up the arguments, a string, I can recursively parse that string against my pragma parser 16:12:20 s/parser/grammar/ 16:12:32 s/prgam/pragma/ 16:14:02 Michael: I have presented the proposal; we want syntax distinct, we want namespaces 16:14:27 Steven: I don't see the conclusion 16:15:59 ... also it seems a lot of mechanism for what I saw as a simple need 16:16:35 Norm: Question -- suppose you subtracted the QName stuff, and adding namespaces later. 16:16:54 Tom: I wouldn;t support that 16:16:58 s/;/'/ 16:17:22 Tom: I want a namespace part 16:18:14 Correction: I am not saying that we need a QName namespace part 16:18:29 I am saying that we need some way of avoiding namespace collision 16:18:48 Steven: Namespace collision or pragma collision? 16:18:53 Happy to hear an alternative proposal to XML namespaces! 16:19:07 pragma collision 16:19:43 Michael: I don't think that allowing namespaces there is any degree of complication. 16:20:41 Bertje has joined #ixml 16:20:41 Tom has joined #ixml 16:20:41 cmsmcq has joined #ixml 16:20:41 norm has joined #ixml 16:20:41 john has joined #ixml 16:20:41 Steven has joined #ixml 16:20:41 join_subline has joined #ixml 16:20:41 demib0y_ has joined #ixml 16:21:00 rrsagent, make minutes 16:21:00 I have made the request to generate https://www.w3.org/2022/01/11-ixml-minutes.html Steven 16:25:17 Bethan: The pragma communicates with the processor, does it have to understand the input or only serialise it? 16:25:59 Tom: If you mean writing to disc, no, but providing an XML representation, yes. 16:26:50 Bethan: so the use of a pragma implies changing the result of the parser. 16:27:07 Tom: It may 16:27:11 Michael: Not will. 16:28:21 Tom: Two issues so far: 1 - syntax (that's the easy one) 16:29:36 ... 2 - issue of namespaces. There is a wider issue with this. 16:30:27 Steven: Namespaces is an issue that needs to be addressed separately, and I'm worried by making it a part of prgmas, we block future development before we've even thought about it. 16:31:08 Dave: A statement of belief is that we need to meet more often. 16:31:53 Tom: Weekly at this time? 16:33:08 Tom: maybe deal with namespaces first, or ask Steven to suggest an alternative. 16:33:40 ACTION: Dave to propose terminology to separate document inputs and outputs. 16:33:40 Sorry, but no Tracker is associated with this channel. 16:34:30 rrsagent, make minutes 16:34:30 I have made the request to generate https://www.w3.org/2022/01/11-ixml-minutes.html Steven 16:35:55 s/l US/Us/ 16:35:59 rrsagent, make minutes 16:35:59 I have made the request to generate https://www.w3.org/2022/01/11-ixml-minutes.html Steven 18:08:31 norm has left #ixml