Meeting minutes
ACTION: Norm construct a page of links to the minutes
Steven: Fabulous symposium. Lots of good remarks from people.
Accept the minutes of the previous meeting
Accepted.
Review of open actions
2024-03-05-c: SP to prepare pull request to resolve issue #139 (new grammars, new README)
Continues
2026-02-03-a: JWL to study SP’s subtraction operator proposal
Completed
Status reports
Norm: I released NineML with support for both flavors of modularity and bounded matching.
First Int’l Symposium on Invisible XML
Steven: I have a list. 1. We should remember next time to put breaks in the schedule.
… More time for opening remarks; we allocated five minutes, but it took at least five minutes to get joined.
… We had forty-something attendees over two days.
… We have to decide whether we want to make times approximate and tell people that, or stick strictly to the schedule.
Bethan: People tended not to run long because they had to say up front how long they wanted.
Norm: I think resyncing the schedule at the breaks makes sense.
Steven: We should make it clearer to speakers that the time they request includes Q&A time.
Bethan: It's also worth allowing speakers to say if they *want* Q&A.
Steven: Remind people that there's a different link for the second day.
… One external comment: we should have included the abstracts on the web.
David: Why are there different links on the two days?
Steven: I'm not sure, Zoom generates them. I just add a meeting to the agenda.
Norm: If we're going to publish the abstracts, we have to tell people that up front.
Bethan: A recurring meeting would have the same link.
Steven: We should try to do that next year.
… The other external proposal was that we begin with a slot that describes the status of the CG.
John: Everyone seemed very happy with two afternoons.
Bethan: Yep.
Some discussion of what we'd do for scheduling if we had participants from Asia/Pacific.
Steven: We could also allow someone to submit a video if they would be at odd hours.
Bethan: I think it makes sense to allow users to record a video in their native language and subtitle it.
… That's something we should be encouraging anyway.
Steven: I have split the talks into individual sections.
… I want to cut out the problematic moments were something goes wrong. Just generally clean it up.
… There are three things: 1. we need to agree on a startup screen. Do we want a tiny bit of music.
Bethan: If we put them on YouTube, they'll get copyright strikes, so it isn't worth it.
ACTION: Bethan to try making the title screen
Bethan: I'll do the editing and the subtitling.
Steven: Okay, I'll put them somewhere.
Some discussion of how we might do subtitles.
Bethan: I'll aim to try to provide subtitles with an eye towards accessibility.
ACTION: Steven make videos available
ACTION: Norm to ask around again about where to host the videos.
Steven: I've forward the slides to the submission address.
ACTION: Norm will attempt to collate the slides
Norm, Bethan, and David give regrets for 17 and 31 March.
David: I pointed out some inconsistencies in the titles.
… Can we fix them?
ACTION: Norm to fix the titles. Except for technical terms like "ixMl"
Steven: Do we want to set a deadline for having everything published.
ACTION: Topic for next meeting: how are we progressing on the symposium output? Do we want to set a deadline?
John: We should send a message to the mailing list saying that we're working on it.
Steven: We should be able to get the slides up fast; it's the video editing that will take time.
Steven: Congratulations to us all. It was great and worth doing and we should plan to do it next year.
Some discussion of the timing. General agreement that this time of year works.
Steven: The end of the month is the paper deadline for XML Prague and Balisage.
David: Should this group do a spec update at the conferences?
ACTION: Norm to write to Jirka and ask if there's a "spec update" slot planned for XML Prague (QT4CG and iXML)
Next meeting
14 April; John gives regrets.