Meeting minutes
Accept the minutes of the previous meeting
Accepted.
Review of open actions
2023-01-10-f: NTW to produce draft documentation of the XML vocabulary, issue #137
Continues
2024-03-05-c: SP to prepare pull request to resolve issue #139 (new grammars, new README)
Continues
2024-10-01-f: SP to make a PR for both versions of the RFC grammar
Overtaken by events, same as preceding.
2025-04-15-a: NW to try to clarify “parse tree” in the specification in a way that is satisfactory to everyone
Pending 2025-08-19-a
2025-08-19-a: SP to review pull request #296.
Continues
2025-08-19-c: BTW to attempt to rewrite #19 so that it's clearer.
Completed.
2025-08-19-d: SP to add the modularization paper to the Invisible XML repository
Withdrawn
j2025-10-14-a: NW to add a link to Steven’s modularization paper to the list of papers
ACTION: 2025-10-14-a: NW to add a link to Steven’s modularization paper to the list of papers
Status reports
Norm: I've implemented modularity in NineML 3.3.2.
ACTION: 2025-10-14-b: NW to summarize the design decisions that differ from SP's paper.
New open issues
Postpone until DB and JL are back.
License for the samples
SP: It's been a long time since I reviewed the different licenses.
NV: The problem is that the GPL v3.0 license is viral.
Investigation reveals that SP committed the GPL V3 license when the repository was created.
<Steven> https://
<Steven> "Permission to copy, and distribute the contents of this document, or the W3C document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that you use:"
Some discussion of the problems associated with licensing.
NW: I think using the W3C Software and Document license makes sense.
Further discussion leads to ambiguity about whether or not a Community Group can use that license.
<Steven> https://
<Steven> Here is the license agreement: https://
SP: But this is only for contributors who have joined the group.
NW: We could just make the samples CC0.
SP: Shall we?
BTW: Yes.
NV: Yes.
ACTION: 2025-10-14-c NW to update the README in the samples to make them CC0 explicitly.
ACTION: 2025-10-14-d SP to reply to Alain.
Review of materials for the proposed symposium
SP: We want to get the announcement out soon.
Some discussion of deadlines and timelines.
SP: Should we make the deadline 15 December?
Consensus: Yes.
NW: SP made some suggestions in email.
Consensus: make the symposium page a single page, don't have a separate page for the CFP.
Some discussion of "Invisible XML" versus "Invisible Markup"
NW: I prefer Invisible XML in the title for visibility.
SP: I'd like "Invisible Markup" in the description somewhere.
BTW: I don't think "Invisible Markup" is an established term. It may be confusing if we use it here without first establishing it.
SP: I'm not sure. We created the group as an "Invisible Markup" group.
Some discussion of "markup" vs "XML" in this context.
Consensus: NW will update the pages with his best effort and then we'll publish them.
SP: Where are we going to announce: Slack, LinkedIn, Facebook, XML-related mailing lists. Mastodon, our weblogs.
SP: I'll make a LinkedIn page and an event on Facebook.
SP: What mailing lists.
BTW: Ours!
NV: We can announce it as Declarative Amsterdam.
SP: I'll do LinkedIn and Facebook.
NW: I'll Slack, and our mailing list.
NV: I'll send something to XML.com.
<Steven> https://
ACTION: 2025-10-14-e NW to fix the iXML grammar link on the home page.
Next meeting
28 October at the usual time. Note that it will be one hour *later* in the United States (for one week only) as the clocks change for standard time.
Adjourned