Meeting minutes
<norm> No one on video @steven?
Review of agenda
All OK
Previous Actions
ACTION 2022-06-21-a: Tom to set up a schematron demo
Steven: Dropped
ACTION 2022-12-13-b: Steven to propose a route forward on Issue #139
<Github> invisibleXML/
Steven: I am working on this. I have something running.
Steven: It is an accepting grammar rather than a strict one, but reveals more structure.
John: Should we make that a principle?
Michael: I think we should do both
John: We should say which is which.
ACTION 2022-12-13-c: Steven to propose an iXML grammar for IRIs and
illustrate the places where it might fail.
Steven: Continues
ACTION 2022-12-13-f: Norm to produce a concrete proposal for combining
grammars. John offers to assist
Norm: Done. Agenda item
ACTION 2023-01-10-a: Norm to put the information about Joel's
EarleyBird implementation on the home page
Norm: Done
ACTION 2023-01-10-b: Michael to take another pass on the EBNF to BNF
document
Michael: Continues
ACTION 2023-01-10-c: Steven to expand the tests in PR 169.
Steven: See email.
ACTION: Steven Pull request for Unicode test
Michael: Use Notofu fonts to see the characters
ACTION 2023-01-10-d: Michael to work out the metadata for identifying
the Unicode version(s) associated with a test.
Michael: Continues
ACTION 2023-01-10-e: Norm to merge the erratum on control characters
and close #147
<Github> invisibleXML/
Norm: Done
ACTION 2023-01-10-f: Norm and Michael to do a bit of revision to
improve the draft documentation of the XML
vocabulary (see #137) for further discussion.
<Github> invisibleXML/
Norm: Continues
ACTION 2023-01-10-g: Norm to start a use cases and requirements
document for combining grammars.
Norm: Done
ACTION 2023-01-10-h: Michael to review RELAX NG rules and report back.
Michael: Continues
ACTION 2023-01-10-i: Michael to close issues #29 and #30. (done)
<Github> invisibleXML/
<Github> invisibleXML/
Status reports
John: Nothing much.
Norm: Cleaning up.
Steven: I was impressed that you accepted Cn characters
John: Supplied by the javascript library
Michael: The schema for test results may have a gap: we need a slot with information about the underlying browser.
Norm: And the version of Java
Michael: And XQuery
ACTION: Michael to think about adding to the test suite schema to cover browser (etc) version
Steven: I have updated the Unicode handling for Cn, still have to clean it up
Issues
Issue #75 A Combining grammars (for v.Next)
https://
<Github> invisibleXML/
Norm: I think we should accept this and then continue to update
John: There is a requirement that in transivity two grammars can import the same thing
Michael: For visibility you could do it from either direction, either export or import.
… I would like that illustrated with a decision later
John: Very like packaging in XSLT
Steven: Make both available?
John: Yes.
… and is there only one start token?
… you should be able to import some sub-nonterminal
ACTION: Norm to split NT-Visibility into two
Steven: We need to decide whether we are importing at text level, or parsed level, or at runtime.
Michael: So what does the XML form of an importing grammar look like in other words.
… we need names to refer to those.
… To make it easier to talk about.
Bethan: Should we be able to merge rules?
Michael: There are such use cases.
John: There is a collision issue here
… which may mean scoping or renaming.
Norm: We are thinking about renaming.
ACTION: Norm add a COMBINE option to the usecases
Aob
Steven: The MarkupUK call is open.
Bethan: Should we make stickers?
ACTION: Bethan order stickers
Steven: Next call 14 March
[ADJOURN]