- From: C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>
- Date: Mon, 07 Mar 2022 13:00:51 -0700
- To: public-ixml@w3.org
It's not clear to me whether we are planning to meet tomorrow or not. - Notes from earlier meetings say we have regrets from Steven (though his mail about getting Covid suggests otherwise) and John. - Norm has several times said he would not like to skip two weeks in a row. - But no one seems to have responded to his inquiry about whether people can meet on any other day. I expect to be available tomorrow (unless something comes up), in case we have critical mass. And I am available other days at our normal time. In any case, here is a draft agenda. In all substantive respects it's the same as the agenda for 1 March. ................................................................ ixml meeting 08 March 2022 When: Tuesday 8 March 2022 15:30 UTC for 1 hour https://www.timeanddate.com/worldclock/fixedtime.html?msg=ixml+online+meeting+08+March&iso=20220301T1530 Where: Location: https://meet.google.com/dfz-rwpj-opq Minute taker: NDW IRC: the meetings will be minuted on IRC at irc://irc.w3.org:6667/%23ixml Details of W3C IRC use are at [1] and [2]. [1] https://www.w3.org/wiki/InternetRelayChat [2] https://www.w3.org/wiki/IRC Previous minutes: - 22 Feb https://lists.w3.org/Archives/Public/public-ixml/2022Feb/0184.html https://www.w3.org/2022/02/22-ixml-minutes - 1 Mar https://lists.w3.org/Archives/Public/public-ixml/2022Mar/0008.html AGENDA Topic: Review of agenda 0 Identify minute-taker 1 Review of action items 2 Status reports Status of implementations Status of testing and test suites 3 Review and resolution of issues See below. 4 Other topics Terminology Website Release plan 5 Next meeting (and next scribe) 6 Any other business **************************************************************** Topic: Previous Actions **************************************************************** ACTION (20220222-01): NDW to make a proposal for possible error codes (issue #44). ACTION (20220222-02): Steven to outline examples in the spec. to differentiate static and dynamic errors (issues #25, #18, #23, #31). ACTION (20220222-03): Steven - Issue #47 - @root (Outermost effective nonterminal as attribute) - to be proposed in the spec as a dynamic error. ACTION (20220222-04): 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. (Issues #25, #18, #23, #31, #47.) ACTION (20220222-05): Steven Issue #33 (s = @a, b, @c) - this needs to be explicit. ACTION (20220222-06): NDW Issue #45 (Unused non-terminals) - NDW - two test suites - undefined and unused. Pull request awaiting review. **************************************************************** Topic: Status reports **************************************************************** Topic: Status of implementations Topic: Status of testing and test suites **************************************************************** Topic: Review and resolution of bug reports and technical issues **************************************************************** For all active issues, see https://github.com/invisibleXML/ixml/issues/ ................................................................ Topic: Conformance cluster: which grammars to accept and reject (et al.) ................................................................ ................................................................ Sub-cluster: constraints on grammars ................................................................ https://lists.w3.org/Archives/Public/public-ixml/2021Dec/0072.html https://lists.w3.org/Archives/Public/public-ixml/2021Dec/0073.html https://lists.w3.org/Archives/Public/public-ixml/2021Dec/0077.html Topic: Issue #43 One rule per nonterminal (again) https://github.com/invisibleXML/ixml/issues/19 https://github.com/invisibleXML/ixml/issues/43 ................................................................ Sub-cluster: responsibilities of the processor ................................................................ Topic: Issue #20: What grammars to accept and reject? https://github.com/invisibleXML/ixml/issues/20 Topic: Issue #21 May a conforming processor run out of memory? https://github.com/invisibleXML/ixml/issues/21 Topic: Issue #25 Static and dynamic errors? https://github.com/invisibleXML/ixml/issues/25 Clarification needed: may a processor reject a grammar statically because a dynamic error may arise for some inputs? Or only if a dynamic error will arise for any input? ................................................................ Other issues ................................................................ Topic: Issue #28 Schema for grammars https://github.com/invisibleXML/ixml/issues/28 https://lists.w3.org/Archives/Public/public-ixml/2021Dec/0009.html Topic: Spec issue #26 - how is ambiguity defined? https://lists.w3.org/Archives/Public/public-ixml/2022Jan/0030.html https://github.com/invisibleXML/ixml/issues/26 Topic: XML, VXML, output of ixml processing Dave Pawson asked that this be a "(hopefully brief) agenda item". https://lists.w3.org/Archives/Public/public-ixml/2022Jan/0150.html Topic: Terminological issues: what is an 'error'? Is it an 'error' for the input string not to be a sentence in the language described by the input grammar? Agenda item requested by Dave Pawson. See https://lists.w3.org/Archives/Public/public-ixml/2022Feb/0085.html and the surrounding thread Topic: Pragmas proposal (continued) (issues #10, #29, #30) Brief summary of TM proposal: https://lists.w3.org/Archives/Public/public-ixml/2022Jan/0029.html Proposal: misc/pragmas-proposal.md in proposal-pragmas branch: https://github.com/invisibleXML/ixml/blob/proposal-pragmas/misc/pragmas-proposal.md Background: misc/pragmas.md in proposal-pragmas branch: https://github.com/invisibleXML/ixml/blob/proposal-pragmas/misc/pragmas.md (This is a longer discussion of the proposal, with alternatives; discussion of requirements, desiderata, and design principles; and worked examples showing how processors might use the pragmas proposal for support of various kinds of additional functionality.) Strawman proposal from SP: https://lists.w3.org/Archives/Public/public-ixml/2022Jan/0102.html Specific issue: is there a reason for pragmas to nest? https://github.com/invisibleXML/ixml/issues/30 Specific issue: are the constraints on what a pragma can change or do? https://github.com/invisibleXML/ixml/issues/29 See also (older discussions): https://lists.w3.org/Archives/Public/public-ixml/2021Jun/0003 (pragmas) https://lists.w3.org/Archives/Public/public-ixml/2021Jul/0002 (namespace decls, locality) During the discussion, Dave Pawson asked that the application of pragmas to parse trees be an agenda item: https://lists.w3.org/Archives/Public/public-ixml/2022Jan/0169.html **************************************************************** Topic: Other topics **************************************************************** Topic: Terminology Topic: Website https://invisiblexml.org https://github.com/invisibleXML/ Topic: Release plan **************************************************************** Topic: Next meeting **************************************************************** Normal date for ixml meetings is every Tuesday at 15:30 UTC On the usual schedule, the next meeting would be Tuesday 15 March, at 15:30 UTC for one hour; the U.S. is on DST on that date, so the times in the U.S. are one hour later than usual. https://www.timeanddate.com/worldclock/fixedtime.html?msg=ixml+online+meeting&iso=20220315T1530 N.B. Most of the U.S. shifts to Daylight Savings Time on Sunday 13 March 2022. Expected scribe next week: volunteers sought. [For the record: we have regrets from SP for 8 March, from JL for 8 and 15 March.] [For the record: the current state of the minute-taking rota is: Steven Pemberton 2022-01-25 Norm Tovey-Walsh 2022-02-08 M Sperberg-McQueen 2022-02-15 John Lumley 2022-02-22 Tomos Hillman 2022-03-01 **************************************************************** Topic: Any other business **************************************************************** -- C. M. Sperberg-McQueen Black Mesa Technologies LLC http://blackmesatech.com
Received on Monday, 7 March 2022 20:01:11 UTC