We believe that any remaining issues arising from the move from the Work to replace the specification based on the doc generator with a new version built on Astro is proceeding well. Progress can be followed at issue #644<\/a> and pull request #651<\/a>.<\/p>\n\n\n\n Karim reported on the interesting discussions that have been proceeding in the issues and discussions on the MusicXML GitHub repository, and some of the ideas that are percolating. In particular, he is excited about the possible boundaries that are being revealed, and especially where the line should be drawn between being descriptive versus prescriptive.<\/p>\n\n\n\n Karim is also working on a set of semantic tests (issue #621<\/a>) which aims to supplement schema validation of MusicXML. If members of the community have ideas for the kinds of MusicXML documents that could form the basis of these kinds of tests, where there are clearly invalid constructs that are syntactically valid, they are welcome to contribute them to this thread. As an example of the kind of semantically invalid structures that this could include, a document that contains a “to coda” marking but is missing the “coda” marking with a matching label. These situations are very common and impossible to avoid using only schema validation.<\/p>\n\n\n\n Daniel briefly described a new issue (#336<\/a>) he added to the SMuFL 1.5 milestone to describe the basic appearance of a music font, i.e. whether it has an engraved or handwritten appearance.<\/p>\n\n\n\n The next co-chairs’ meeting is scheduled for Wednesday 13 May 2026<\/strong>.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" GitHub organisational changes We believe that any remaining issues arising from the move from the w3c GitHub organisation to w3c-cg have now been resolved. However, we think that there is more we could do in future to protect against these … Continue reading w3c<\/code> GitHub organisation to w3c-cg<\/code> have now been resolved. However, we think that there is more we could do in future to protect against these kinds of changes, and are considering a new domain for all the projects of the CG to live behind, so that we can have new canonical URLs completely under our control. We’ll provide more details in due course.<\/p>\n\n\n\nMusicXML<\/h2>\n\n\n\n
SMuFL<\/h2>\n\n\n\n
Next meeting<\/h2>\n\n\n\n