- From: W3C Community Development Team <team-community-process@w3.org>
- Date: Tue, 10 Mar 2026 19:45:30 +0000
- To: public-music-notation@w3.org
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 on each of the CG's specifications – SMuFL, MusicXML, and MNX – and for the new MusicXML specification editor and co-chair, Karim Ratib, to introduce himself to the community. MNX Adrian has completed the specification for which characters are allowed in IDs (issue #503): 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. 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. 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. Consuming applications can check the file extension, that the document parses as JSON successfully, and that it has a top-level mnx key. Next meeting The next meeting is the Community Group virtual meeting on Tuesday 17 March 2026. The next co-chairs' meeting is scheduled for Tuesday 24 March 2026. ---------- This post sent on Music Notation Community Group 'Co-chair meeting minutes: March 10, 2026' https://www.w3.org/community/music-notation/2026/03/10/co-chair-meeting-minutes-march-10-2026/ Learn more about the Music Notation Community Group: https://www.w3.org/community/music-notation
Received on Tuesday, 10 March 2026 19:45:31 UTC