- From: W3C Community Development Team <team-community-process@w3.org>
- Date: Thu, 4 Jul 2024 16:26:33 +0000
- To: public-music-notation@w3.org
MNX Adrian has added an example MNX document for grand staff instruments, illustrating three key aspects: the part object has a staves object to specify the number of staves, each sequence needs to specify which staff it belongs to, and each clef likewise needs to specify its staff. No specification changes were required to accommodate this example. We discussed briefly whether it makes sense to move the staff from inside clef up to the positionedClef object, where the rhythmic position lives, and agreed that we should. Adrian has also created a pull request for the support element, which in the first instance is intended to specify whether the document encodes the visibility of accidentals (pull request #347). The field useAccidentalDisplay defaults to false, i.e. by default it is assumed that the consuming application is expected to use its own algorithmic approach to determining where accidentals should appear. If the document does not have useAccidentalDisplay set to true, but then nevertheless specifies accidentalDisplay for one or more notes, we have specified that will be invalid MNX; we are not yet sure whether we can make the JSON schema complain about this issue, but we will look into it. We welcome community feedback on this pull request before we merge it. MusicXML Adrian has made the corresponding change to the doc generator for MusicXML to encode long strings as arrays to improve the readability of the diffs (pull request #526). Next meeting The next co-chairs' meeting is scheduled for Friday 19 July 2024. ---------- This post sent on Music Notation Community Group 'Co-chair meeting minutes: July 4, 2024' https://www.w3.org/community/music-notation/2024/07/04/co-chair-meeting-minutes-july-4-2024/ Learn more about the Music Notation Community Group: https://www.w3.org/community/music-notation
Received on Thursday, 4 July 2024 16:26:34 UTC