Skip to toolbar

Community & Business Groups

Music Notation Community Group

The Music Notation Community Group develops and maintains format and language specifications for notated music used by web, desktop, and mobile applications. The group aims to serve a broad range of users engaging in music-related activities involving notation, and will document these use cases.

The Community Group documents, maintains and updates the MusicXML and SMuFL (Standard Music Font Layout) specifications. The goals are to evolve the specifications to handle a broader set of use cases and technologies, including use of music notation on the web, while maximizing the existing investment in implementations of the existing MusicXML and SMuFL specifications.

The group is developing a new specification to embody this broader set of use cases and technologies, under the working title of MNX. The group is proposing the development of an additional new specification to provide a standard, machine-readable source of musical instrument data.

w3c/smufl
Group's public email, repo and wiki activity over time

Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.

Final reports / licensing info

Date Name Commitments
MusicXML 4.0 Licensing commitments
SMuFL 1.4 Licensing commitments
SMuFL 1.3 Licensing commitments
MusicXML Version 3.1 Licensing commitments

Chairs, when logged in, may publish draft and final reports. Please see report requirements.

MNX Specification Working Group meeting: November 3, 2026

Adrian, Daniel and Robert met this week; Myke was unable to attend as he is currently travelling.

Merged pull requests

We started the meeting with a brief recap of what has been merged into the spec since the last meeting:

  • Added formatted text, so it’s possible to encode text at a position in the part measure; there’s a type attached to it, but for the time being only general text is specified (pull request #565)
  • We have added the square staff bracket type (pull request #562)
  • We have added two example documents for the key flip element (pull request #500)

Formatted text

As a follow-up to the work on formatted text, Robert proposes that we should add an optional voice to formatted text, so that it’s possible to specify that it belongs to a particular voice; we agreed this, and Adrian will add this directly.

Robert also proposes that we need to expand the repertoire of types of text in order to make MNX more well-suited for interchange with MuseScore and Finale, which both encode expressions and techniques as text; at the moment, round-tripping files with those apps is tricky because we cannot preserve this type. After some discussion, we agreed to add expressive text as a type, but to come back to the issue of technique text in future, as we think it’s likely that we should encode techniques at a higher, more semantic level than purely as text.

Semantic notehead shapes

We discussed the pending pull request for semantic notehead shapes, #563.

In Myke’s absence, we decided to remove the duration variant that he had advocated (the ability to specify that a notehead should use the standard appearance of another notehead, e.g. use the white half note notehead for a note that would normally use a black notehead). It doesn’t seem to add enough value for the complexity it adds.

We discussed the need for a separate kit note notehead, and agreed that we would pull hiding and parentheses out of the notehead object, and move them up to the note (and note markings) in a follow-up commit. This allows us to do away with the separate kit note notehead. Robert will work on this after the meeting.

Chord symbols

The remainder of the meeting was spent discussing Adrian’s initial proposal for encoding chord symbols (pull request #566). We didn’t come to any firm conclusions by the end of the meeting, and so agreed that we would continue the discussion next time.

The main concerns are about ambiguity: ambiguity about which intervals and notes are implied by the kind type (which has been inherited from MusicXML’s harmony element), and ambiguity about how chord symbols should be rendered graphically.

We spent a while discussing Robert’s idea of defining chord symbols in terms of a series of intervals above the root, but the difficulty here is that it requires an external look-up to map arrangements of intervals onto types of chords as used in chord symbols; of course, the root plus kind approach requires the reverse operation, determining which actual notes are implied by the combination of root note and kind.

There is more to be decided here, so we will resume in our next session.

Next meeting

Our next specification working group meeting is scheduled for Tuesday 17 November 2026.

Co-chair meeting minutes: November 2, 2026

MusicXML

Karim has been on holiday in the last couple of weeks so has not made so much direct progress, but he’s back in the saddle and planning to resume work on the roadmap. We discussed a little bit how to continue to build relationships with the developers of commercial music applications in order to ensure that the changes in MusicXML 4.1 and beyond fit with their plans.

Karim will share his usual MusicXML progress report in due course.

SMuFL

Daniel highlighted issue #368, in order to invite community feedback about this mechanism for providing access to retired designs for glyphs in Bravura. It’s an open question whether this would be useful in general to other application developers, or whether it should instead remain a feature for providing stability in appearance to those Dorico users for whom this matters greatly.

Next meeting

We have decided to change the cadence of this meeting to monthly, with the agreement to schedule an intervening meeting if necessary. The next scheduled meeting is set for Monday 7 December 2026.

MusicXML progress update: October 15, 2026

ROADMAP PROGRESS

Milestone 4.1 is now 66% complete! I expect that the challenging issues ahead will concern guitar notation and sound effects – we welcome all your feedback on those, including schema proposals.

SPECIAL INTEREST GROUPS

Great feedback on Special Interest Groups since our call for participation! We now have 3 SIGs in action:

  • Microtonality where we discuss issues relating to extending MusicXML beyond equal temperament, a hot current topic and an unchartered territory for most engraving systems. Thanks @johnmichaelplatter for a great discussion on microtonal guitar tablature, which veered into the larger question of tuning definitions. Thanks to co-chair @dspreadbury for chiming in from the Dorico perspective.
  • Instruments which concerns instrument-specific notations. Special thanks to @PhysNovalOnGit for an extended exposition on accordion notation.
  • Accessibility which concerns ensuring that MusicXML serves individuals with special needs. Thanks @hhpmusic for highlighting concrete use cases and creating issues for them.

We welcome more community involvement into these discussions and other topics that you may suggest. One reminder about bringing changes to MusicXML: whereas existing music software may be offering features that suit your own use cases perfectly, MusicXML is primarily an interchange format, meaning that it needs to account for multiple use cases and cannot model this or that software feature without leaving room for extensibility and generalization. This principle permeates all the design decisions behind MusicXML and inevitably means that schema changes will necessitate multiple rounds of discussion, involving many use cases, diverse viewpoints, and a survey of different practices. It’s a long process that we believe yields greater durability and relevance for MusicXML.

WEBSITE

Enhancements are continuously being made to the MusicXML website at https://musicxml.formats.music/ . Whereas this URL currently hosts the 4.1 draft release only, it will also refer to the stable release once 4.1 is published. Thanks to co-chair @adrianholovaty for the initiative of giving our notation group a stable domain name!

You can find website related issues on GitHub. Please feel free to suggest enhancements on this topic as well. Thanks @davidmatthew-ie for your excellent involvement and (and indeed for suggesting Astro CMS in the first place.)

MNX Specification Working Group meeting: October 6, 2026

Updates on existing work

  • Adrian has fixed a schema bug related to dynamics
  • Pull request #556 adds support for caesuras over barlines; we agreed to merge this.
  • Pull request #554 adds support for slide in and slide out to note markings; we agreed to merge this.
  • Pull request #558 adds support for lyric extender lines; we agreed to merge this, pending some minor changes from Robert.
  • Pull request #559 adds support for D.C./D.S. al Coda types; we agreed to merge this.

We also agreed that in order to accelerate the pace of development, we will move towards merging pull requests after a few days provided there has been no strong objection, rather than waiting for the next working group meeting to confirm in person.

Chord symbols

We spent the remainder of the meeting discussing the encoding of chord symbols. The upshot is that Adrian will work on a proposal that primarily draws upon the existing harmony element in MusicXML, and share it for community feedback.

Next meeting

The next working group meeting is scheduled for Tuesday 20 October 2026.

Co-chair meeting minutes: October 5, 2026

MusicXML

Karim continues to work on roadmap items for MusicXML 4.1. There has been some good feedback for the special interest groups for microtonality and instrument techniques.

Karim is still hoping to get some traction for a special interest group for accessibility, so if there are any community members who have expertise in this area, we would love to hear from you.

Some UI fixes have been made on the MusicXML specification site, to fix some issues with scrolling on mobile devices.

SMuFL

Daniel has not had a chance to devote any time to working on SMuFL in the last fortnight. But the next step remains the same: there are some old pull requests in the SMuFL repository that need to be updated to take advantage of the new tooling. He hopes to get this done before the next meeting.

Next meeting

The next co-chair meeting is set for Tuesday 20 October 2026.

MNX Specification Working Group meeting: September 22, 2026

Viritura

Robert reported that he has been working with Peter Yang on making it possible to translate Finale .musx files into Viritura using MNX, producing a gap report that identifies areas where encoding isn’t yet possible.

Previous business

Following up on the items discussed in our last meeting, Adrian reported:

  • Percussion clefs are now implemented
  • A new boolean for hiding clefs has been added
  • Caesuras are now added to event markings; work remains to add them to global barlines.

Orientation versus placement

We discussed the thorny issue of orientation versus placement. The orientation object will be renamed to placement. The keys for markings – for example, breathmark.orient – will also be renamed from orient to placement.

We also discussed the old concept of cascading placement from events to other markings, and agreed that we will retire this.

In the light of the recent work on voice direction in MusicXML, we also discussed this for sequences in MNX, in order to specify the nominal stem direction of a voice. We settled on the name directionHint, which will use an enum with values upper, lower and auto as the value.

Next meeting

Our next meeting is scheduled for Tuesday 6 October 2026.

Co-chair meeting minutes: September 21, 2026

MusicXML

Karim’s idea to establish special interest groups attracted lots of attention, and two special interest groups are now set up:

  • Instruments and techniques, especially guitar and accordion notation (Discussions)
  • Microtonal notation (Discussions)

Karim has created special categories within the Discussions area on GitHub for each of the new special interest groups, and discussion about specific issues has already started to happen.

A useful new addition has been added to the spec this week thanks to contributions from a lot of people, providing new functionality for describing the default stem directions for voices (pull request #707). During the work on this ticket, Karim learned how to use LilyPond as a renderer for the required examples, and hopes to introduce a common pipeline for the generation of graphical renderings of full MusicXML examples, rather than a pipeline.

MNX and SMuFL

No specific updates to share this week. The next MNX specification working group meeting is tomorrow

Next meeting

The next co-chair meeting is scheduled for Monday 5 October 2026.

MusicXML progress update: September 9, 2026

ROADMAP PROGRESS

Slower progress than expected this month. Some roadmap issues opened deeper questions that kept me busy.

– Closed: Clarify fan attribute usage for multi-level beams https://github.com/w3c-cg/musicxml/issues/663  (thanks @rpatters1)

– Removed from roadmap: Add ‘smufl’ attribute to <senza-misura> https://github.com/w3c-cg/musicxml/issues/643 (thanks @lemzwerg – as per issue discussion, there’s broader work needed at the level of mixing SMuFL glyphs into textual content.)

– In progress: Clarify the whole-rest reference point for <display-step> and <display-octave> https://github.com/w3c-cg/musicxml/issues/681 (thanks @rpatters1)

SPECIAL INTEREST GROUPS

While working on roadmap issues, it became clear to me that more often than not, specialized knowledge and focused attention on specific topics would be of great help to push groups of issues forward. I am therefore calling on members of the community to express their interest in forming special interest groups around the following, and other, topics:

Please reach out at the relevant discussion thread with your interests and ideas!

MNX Specification Working Group meeting: September 8, 2026

Staff lines

Work on specifying the number of staff lines (pull request #548, issue #531) is now complete. It’s now possible to specify zero as the number of staff lines. We agreed that the pull request can be merged. There is further work to be done on how staff configurations interact with layouts, but we’ll return to this in future.

Veritura

In discussion #549, Peter Yang announced the release of a new web-based notation editor called Veritura that uses MNX as its native format. The implementation makes liberal use of the _x vendor extensions mechanism. Adrian asked Peter which of their specific extensions could be taken more or less as-is and used in upstream MNX.

Caesura

We started by discussing caesuras: these could be added to markings relatively simply, in the same way as breath marks. They will need to incorporate the different types of caesuras currently supported by MusicXML. Myke suggests that we should define the shape (“thin”, “thick”, “curved”, etc.) and the number of strokes (an enumeration with values “single” and “double”).

Percussion clefs

We then moved on to discussing percussion clefs: the main issue is how to map the note staff positions. Although the intention is that notes on unpitched percussion instruments should be written using “kit notes”, we can specify that pitched notes written on a percussion instrument will be positioned as if the percussion clef is the same as a G clef. We will add the value “percussion” to the “sign” enumeration used by the clef sign object. We will also add a boolean for “hide”, defaulting false, to allow the hiding of any clef, including the new percussion clef.

Rich text

We revisited last year’s proposal for encoding rich text from issue #459. After much lively discussion, we agreed that the current proposal is more or less fit for purpose, modulo a decision on exactly how to refer to a semantic style ID registered globally in the document. Adrian will make a fresh proposal for how text items can be encoded in measures, with a type enumeration intended to specify the text item’s purpose.

We left as a treat for our next meeting a decision on how to specify the mapping between text size and musical space size.

Next meeting

The next spec working group meeting is scheduled for Tuesday 22 September 2026.

Co-chair meeting minutes: September 7, 2026

MusicXML

Karim has been working on items from the roadmap. Progress can be slower than expected because of the hidden complexities that tackling even superficially simple-looking issues can reveal, but this is all good and interesting work.

Karim is considering proposing the formation of special interest groups for areas within MusicXML. He has seen this approach working well within the MEI community, and is considering whether this approach could work for MusicXML. He will create a discussion in GitHub to invite proposals from the community for what kinds of special interest groups could work for MusicXML.

MNX

Adrian wanted to mention the announcement of Viritura, a new web-based collaborative music notation editor that uses MNX as its native format. You can read more about it at its web site, or in discussion #549 at GitHub. Of particular interest is that it makes extensive use of the _x vendor extension method to implement support for notations not currently handled by the MNX specification. We will discuss this more in our spec working group meeting tomorrow.

Next meeting

The next co-chair meeting is scheduled for Monday 21 September 2026.