Co-chair meeting minutes: January 30, 2025 [via Music Notation Community Group]

MNX



Robert Patterson reported that two of the MNX documents in our set of examples didn't pass JSON Schema validation, so Adrian has fixed those, such that all example documents now validate.



Robert also raised two issues concerning system layout (issue #367) and the placement of system objects (issue #368) which need further thought. We agreed that we would digest these issues and respond directly in GitHub.



In Issue #363 Adrian Kulisch suggests that we should explicitly use the language codes defined in RFC 5646, which updates the earlier ISO 639 standard. We agreed that this would be a good change for MNX and indeed for MusicXML 4.1.



We also discussed issue #366 concerning the accidental display object, as raised by Robert. We propose that to address the concerns here we will add an optional force bool to the accidental display object, which will allow the encoder to specify whether the accidental is explicitly shown or explicitly hidden. We will wait for community feedback before we add this to the specification.



Work continues on the list of notation types that we are creating in order to identify the areas of MNX where the specification is ready for implementation. Adrian has created a prototype single-page web app that as discussed in our previous meeting, and we agreed that he should continue working on this in the coming weeks. We will share it with the community once it is a little further along. 



Next meeting



The next co-chairs' meeting will be on Thursday 13 February 2025.



----------

This post sent on Music Notation Community Group



'Co-chair meeting minutes: January 30, 2025'

https://www.w3.org/community/music-notation/2025/01/30/co-chair-meeting-minutes-january-30-2025/



Learn more about the Music Notation Community Group: 

https://www.w3.org/community/music-notation

Received on Thursday, 30 January 2025 17:52:48 UTC