Co-chair Meeting Minutes: May 12, 2020

MusicXML 3.2 vs. 4.0

Following the discussion in the recent Community Group meeting, Michael created issue #314 to canvass the community over the issue of whether or not the version number for the next version of MusicXML should be 3.2 or 4.0. There is a narrow majority in support of MusicXML 4.0 so this is what we are going to do. Michael will create an initial pull request to change the version number, copyright date, and switch the license back from the Final Specification Agreement (FSA) to the Contributor License Agreement (CLA), which is the appropriate license to use for the development process.

The co-chairs also discussed issue #313, which can be closed. Michael will review the outstanding issues in the MusicXML repository for those that will be deferred to MNX, ensure that a corresponding MNX issue exists, and then close those issues.

MNX-Common

Adrian has added a new section for Parts to the MNX-Common by Example page, and has added a test case to the mnxconverter project to capture this test.

Adrian will next add some examples for transposing instruments to the MNX-Common by Example.

Adrian will add links to the new mnxconverter project to the various pages on GitHub that should have them, and Michael will contact our W3C representative to add a link to the mnxconverter repository to the CG home page.

Next up will be a proposal for how to encode repeats in their generality, including repeat barlines, repeat endings, and repeat jumps.

On the subject of how MNX-Common and MNX-Generic should be named, following the discussion at the Community Group meeting a couple of weeks ago, Adrian will start a new issue to capture any further feedback from the community.

Next meeting

The next co-chair meeting will be on Tuesday 26 May 2020.