Co-chairs’ meeting minutes – July 31, 2025 [via Music Notation Community Group]

MNX



We have addressed the following issues:




#440: Adrian has removed smuflFont from events, in line with the change made to remove smuflFont from notes



#438: Adrian renamed the new soundID key name to simply sound, for consistency with other similar places in the specification



#441: Adrian added some additional fields to kitNote: id, class, and perform.




Myke fixed a problem in the doc generator that was resulting in Windows newline characters unexpectedly appearing in the HTML output.



We discussed #436, which raises the issue of how to represent more than two spellings for a note, given the and came to the consensus view that if you require more than two spellings for a note, for the time being, our recommendation will be to encode the whole part separately, and use layouts to exclude any alternative transpositions from the score and part instantiations as needed.



We also discussed #432, concerning the naming and use of the interval object, and decided that we would change the names of both keys of the interval object: instead of diatonic, we propose staffDistance, and instead of chromatic, we propose halfSteps. Using staffDistance instead of diatonic makes a value of zero clearer, i.e. it doesn't move the note by any staff positions; and if we're not going to use diatonic, we should likewise not use chromatic. 



Next meeting



The next meeting is scheduled for Thursday 14 August 2025.



----------

This post sent on Music Notation Community Group



'Co-chairs’ meeting minutes – July 31, 2025'

https://www.w3.org/community/music-notation/2025/07/31/co-chairs-meeting-minutes-july-31-2025/



Learn more about the Music Notation Community Group: 

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

Received on Thursday, 31 July 2025 22:42:08 UTC