A reminder that we will have a virtual meeting next Tuesday, 17 March 2026 at 4pm UTC<\/strong> to which all Community Group members are invited. This meeting is a chance for the co-chairs to provide an update on each of the CG’s specifications \u2013 SMuFL, MusicXML, and MNX \u2013 and for the new MusicXML specification editor and co-chair, Karim Ratib, to introduce himself to the community.<\/p>\n\n\n\n Adrian has completed the specification for which characters are allowed in IDs (issue #503<\/a>): up to 256 ASCII characters, and no spaces or non-printable characters can be used. This ID system is designed to make it possible to use the internal IDs used by other applications (for example, MuseScore) in MNX documents.<\/p>\n\n\n\n We spent a bit of time discussing the default file extension for MNX documents, and whether we would need an OCF-style container for MNX, per discussion #416<\/a>. Our current thinking is that we probably do not need a container, so we propose that MNX documents should have the file extension .mnx.json<\/strong>. Consuming applications can check the file extension, that the document parses as JSON successfully, and that it has a top-level The next meeting is the Community Group virtual meeting on Tuesday 17 March 2026<\/strong>. The next co-chairs’ meeting is scheduled for Tuesday 24 March 2026<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":" Community Group meeting A reminder that we will have a virtual meeting next Tuesday, 17 March 2026 at 4pm UTC to which all Community Group members are invited. This meeting is a chance for the co-chairs to provide an update … Continue reading MNX<\/h2>\n\n\n\n
mnx<\/code> key.<\/p>\n\n\n\nNext meeting<\/h2>\n\n\n\n